Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: 1.6.7 beta3 new exclusive output mode problem (Read 9246 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

1.6.7 beta3 new exclusive output mode problem

During playback, the sound may be interrupted or the playback speed may slow down.
No problem with foo_wasapi.dll

OS Windows10 Home 64bit Version 21H1
Audio IDT High Definition Audio Codec

Re: 1.6.7 beta3 new exclusive output mode problem

Reply #1
foobar2000 v1.6.7 beta 3 Output: DAC Driver [exclusive]

Continuous playback for about 1 hour (mp3, AAC). Sound cracking is terrible.
I don't use DSP.
NuPrime uDSD, ifi ZEN DAC, iFi nano iDSD, xDuoo X05, Roland UA-M10, FiiO Q1

foobar2000 v1.6.6 WASAPI output support 3.4 (foo_out_wasapi) No problem.

Lenovo G570
Intel(R) Core(TM) i3-2350M CPU @ 2.30GHz 2.30 GHz
16.0 GB
Windows 10 Pro 21H1 19043.985
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD 490 PRO, DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, Bose QuietComfort 45 (made a Upgrade/Balanced Cable by myself)

Re: 1.6.7 beta3 new exclusive output mode problem

Reply #2
The same effect here: after about 20 minutes of Flac playback (CD image with embedded CUE sheet).
It looks a bit to me as if the WASPI settings in the advanced settings are ignored.

Re: 1.6.7 beta3 new exclusive output mode problem

Reply #3
Thanks for reporting.
The problem is known and will be addressed for the next update.
WASAPI advanced settings belong to the old WASAPI component and are not utilized. I'll make equivalent settings available for the built-in exclusive output if necessary.
Microsoft Windows: We can't script here, this is bat country.

Re: 1.6.7 beta3 new exclusive output mode problem

Reply #4
Beta 4 posted, known issues should be addressed.
Microsoft Windows: We can't script here, this is bat country.

Re: 1.6.7 beta3 new exclusive output mode problem

Reply #5
Exclusive output options are broken on my system in Beta 4, Beta 3 worked correctly. Win 10 20H2, resample & convolver in DSP, DX3Pro DAC (USB 2). This reminds me of the problem I had with the old WASAPI component. It only worked in Push mode with USB2 DAC's unless I installed the DAC's proprietary driver.

Re: 1.6.7 beta3 new exclusive output mode problem

Reply #6
foobar2000 v1.6.7 beta 4 Output: DAC Driver [exclusive]
DAC xDuoo X05, FOSTEX HP-A4

The sound is terribly dirty.Worse than beta 3.
Continuous playback is under test.
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD 490 PRO, DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, Bose QuietComfort 45 (made a Upgrade/Balanced Cable by myself)

Re: 1.6.7 beta3 new exclusive output mode problem

Reply #7
Unfortunately nothing changed.

Re: 1.6.7 beta3 new exclusive output mode problem

Reply #8
Thanks for reporting.
The problem is known and will be addressed for the next update.
WASAPI advanced settings belong to the old WASAPI component and are not utilized. I'll make equivalent settings available for the built-in exclusive output if necessary.

Please do, as now one can't choose WASAPI buffer sizes. It'd be much appreciated to have that option back.
foobar2000_v1.6.7_beta_4

Re: 1.6.7 beta3 new exclusive output mode problem

Reply #9
Situation became better for me with beta 4, but i still sometimes get glitches on some radio streams if fading is disabled. For example this stream - https://stream.radioparadise.com/rp_192.ogg
Windows 7, realtek

Re: 1.6.7 beta3 new exclusive output mode problem

Reply #10
Internal buffer size configuration will be added in beta 5.
Other issues are being investigated, thanks for all the reports.
Microsoft Windows: We can't script here, this is bat country.

Re: 1.6.7 beta3 new exclusive output mode problem

Reply #11
Sorry...
I reinstalled DAC driver (xDuoo X05 (XMOS) etc).
WASAPI exclusive: All problems have been resolved.
foobar2000 v1.6.7 beta 4 Output: DAC Driver [exclusive]
NuPrime uDSD, ifi ZEN DAC, iFi nano iDSD, xDuoo X05, Roland UA-M10, FiiO Q1 and FOSTEX HP-A4.
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD 490 PRO, DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, Bose QuietComfort 45 (made a Upgrade/Balanced Cable by myself)

 

Re: 1.6.7 beta3 new exclusive output mode problem

Reply #12
Beta 5 released.
Default mode is now push instead of event, as with some devices event mode behaves erratically no matter what I try.
Buffer size configuration has been added.
Please test, thanks.
Microsoft Windows: We can't script here, this is bat country.

Re: 1.6.7 beta3 new exclusive output mode problem

Reply #13
Seems that now exlusive output with fading is fine.

Re: 1.6.7 beta3 new exclusive output mode problem

Reply #14
Beta 5 released.
Default mode is now push instead of event, as with some devices event mode behaves erratically no matter what I try.
Buffer size configuration has been added.

Beta 5 playing music without issues so far. Exclusive push mode works, event does not work. Beta 3 worked in whatever the default mode was. I had the same issue with the WASAPI component and several USB 2 dac's.
(Topping DX3 Pro, fade and DSP in use.

Re: 1.6.7 beta3 new exclusive output mode problem

Reply #15
Beta 5 released.
Default mode is now push instead of event, as with some devices event mode behaves erratically no matter what I try.
Buffer size configuration has been added.
Please test, thanks.

I am using Dragonfly black, Beta5
With smooth seeking enabled and Advanced-Playback-Exclusive mode - Hardware Buffer set to 0 and Use event checked
Above works perfectly, thank you

Re: 1.6.7 beta3 new exclusive output mode problem

Reply #16
Dragonfly is USB 1.0, probably why it works in the event mode.


Re: 1.6.7 beta3 new exclusive output mode problem

Reply #18
Hi,
how I can switch to the event mode?




Re: 1.6.7 beta3 new exclusive output mode problem

Reply #22
I have USB Class 2 audio working in the exclusive event mode. I set the buffer very small, 12 ms and voila. I think the default was 25 with the WASAPI component. Someone here set it to 0.

Re: 1.6.7 beta3 new exclusive output mode problem

Reply #23
Some results of new exclusive mode on fb2k beta 5 and Windows 7. Devices are Realtek and Dr DAC 2 DX (UAC 1 device that uses standard windows driver)

Dr DAC 2 DX, Fading on, Event, buffer 100 ms - OK
Dr DAC 2 DX, Fading off, Event, buffer 100 ms - OK
Dr DAC 2 DX, Fading on, Push, buffer 100 ms - always error "Buffer too large"
Dr DAC 2 DX, Fading off, Push, buffer 100 ms - glitches on local files; error "Buffer too large" on radio stream playback

Realtek, Fading on, Event, buffer 100 ms - playback just doesn't start and no errors are reported; after closing fb2k, process hangs with 25% CPU load and must be killed with task manager.
Realtek, Fading off, Event, buffer 100 ms - almost OK, but "eats" few milliseconds (noticeable by ear) on start of playback
Realtek, Fading on, Push, buffer 100 ms - OK
Realtek, Fading off, Push, buffer 100 ms - on local files it is OK but glitches on radio stream playback

Dr DAC 2 DX, Fading on, Event, buffer 25 ms - OK
Dr DAC 2 DX, Fading off, Event, buffer 25 ms - on local files it is OK but glitches on radio stream playback
Dr DAC 2 DX, Fading on, Push, buffer 200 ms - always glitches in start of playback; after few seconds of playback - error "Buffer too large"
Dr DAC 2 DX, Fading off, Push, buffer 200 ms - OK

Realtek, Fading on, Event, buffer 25 ms - OK
Realtek, Fading off, Event, buffer 25 ms - on local files it is almost OK, but "eats" few milliseconds (but less with 100 ms buffer) on start of playback; glitches on radio stream playback
Realtek, Fading on, Push, buffer 200 ms - OK
Realtek, Fading off, Push, buffer 200 ms - OK