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: ASIO and Windows 10 (Read 6134 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

ASIO and Windows 10

Hi,

I don't know if it's related to foobar, to ASIO plug-in or to my DAC driver.

I try to explain hoping someone can help.

I have a DAC that support ASIO bit perfect with a LED on the DAC that show where I am in bit perfect.

In Windows 7 when I pause a song that led remain ON and everything is Ok.

In Windows 10 when I pause a song that led switch OFF and I hear ugly clicks from the speakers (because the PC disconnect itself from DAC). Then I play again and that LED become again ON and I hear other ugly clicks. These clicks are very quick but they are ugly especially in headphones.

The behaviour of Win 10 is wrong because when I pause a song foobar must keep its connection to the DAC instead to lose it.

I can understand when I STOP the song, then, yes, it can lose the connection but in pause the connection must be kept (just like happen in Win 7).

HELP!!!

Re: ASIO and Windows 10

Reply #1 –
When I fist upgraded to Windows 10 I needed to uninstall my DAC's drivers and reinstall them.  Also, FWIW, with my hardware the Windows Sound control panel affects the output even when using ASIO.  In the sound control panel for my DAC I have to disable all enhancements in the enhancement tab and make sure that both of the exclusive mode checkmarks are set in the advanced tab.  Obviusly I also need to set the volume to 100 (and the balance to 100/100) to get a bit perfect output.

Re: ASIO and Windows 10

Reply #2 –
Apparently, changes can't please everyone. Someone complained that pausing their WASAPI output did not allow them to regain control of their sound device. Here, you complain because ASIO does not retain the sound device while paused.

Re: ASIO and Windows 10

Reply #3 –
Quote from: kode54 on
Apparently, changes can't please everyone. Someone complained that pausing their WASAPI output did not allow them to regain control of their sound device. Here, you complain because ASIO does not retain the sound device while paused.

I don't understand those people, on STOP I see they want their sound device, but on PAUSE why the should want that the DAC lost his connection bit perfect???

Wow, I really don't understand. If I pause the BIT PERFECT foobar lose the control of the DAC so I hear the ugly "switch off" from it. Pause is not stop, is different! It's like it still playing!!!
In Win 7 If I pause it it KEEP THE CONTROL and I hear nothing bad (the LED BIT PERFECT keep ON).

There's something I can do to have the behaviour that I want (pause must KEEP control of DAC, stop must LOSE the control of DAC)?

Re: ASIO and Windows 10

Reply #4 –
FWIW I don't see that behavior here at all, at least none of the clicks.  The implementation of bit perfect testing on my DAC is different: it looks for a pattern and, of course, that pattern is disrupted when the source is paused so the bit perfect indicator goes out on pause and comes back when the source is resumed, but without noise or a change of sample rate, etc. at the transitions to and from pause.  Not that I'm sure it will help but I did need to reinstall my DAC's USB driver on Windows 10 to go from the state you describe to having things work like Windows 7 again and I did need to change the properties of the DAC in the windows sound control panel as described to get bit perfect playback (even for ASIO.)

Also someone suggested going to foobar2000 1.3.12 since it's changelog mentions "Corrected various 1.3.11 pause regressions."

Re: ASIO and Windows 10

Reply #5 –
Quote from: tedsmith on
FWIW I don't see that behavior here at all, at least none of the clicks.  The implementation of bit perfect testing on my DAC is different: it looks for a pattern and, of course, that pattern is disrupted when the source is paused so the bit perfect indicator goes out on pause and comes back when the source is resumed, but without noise or a change of sample rate, etc. at the transitions to and from pause. 
Also someone suggested going to foobar2000 1.3.12 since it's changelog mentions "Corrected various 1.3.11 pause regressions."

My led goes out too when I press pause but, differently to you, when the led goes out (of bit perfect) I hear strange clicks but It was always normal with my DAC. But, In Win 7, I haven't these issues because PAUSE meant to NOT LEAVE BIT PERFECT.

I was unlucky with the update, the result is the same :-(

Re: ASIO and Windows 10

Reply #6 –
Quote from: kode54 on
Apparently, changes can't please everyone. Someone complained that pausing their WASAPI output did not allow them to regain control of their sound device. Here, you complain because ASIO does not retain the sound device while paused.

I was thinking that in my Win 7 I have an older version of foobar while in Win 10 (when I have my "issue") I have a newer (latest) version of foobar2000 and I casually re-read this sentence... maybe it will fix my problem... if I understand good (please correct me if I am wrong):

Is the disconnection of bit perfect in PAUSE a wanted feature that is come out from a recent version of foobar?

Can somebody tells me? If is so:

1) what old version of foobar I have to use to have the behaviour I want (pause=not disconnection of bit perfect stream)

2) the DEVS instead of make this change for everyone CAN ADD AN OPTION in the advanced preferences:
A) DO NOT DISCONNECT the bit perfect mode in PAUSE for ASIO and WASAPI
B) DO DISCONNECT the the bit perfect mode in PAUSE for ASIO and WASAPI

So everybody can choose... it could be possible?

Re: ASIO and Windows 10

Reply #7 –
Nothing has changed in foobar2000 regarding this behavior. Device is kept open when you pause and device is only closed when you stop playback. It does sound like your soundcard drivers are not behaving nicely.

Re: ASIO and Windows 10

Reply #8 –
Quote from: Case on
Nothing has changed in foobar2000 regarding this behavior. Device is kept open when you pause and device is only closed when you stop playback. It does sound like your soundcard drivers are not behaving nicely.

It's exactly what happen on Win 7 to me. Now I have Win 10 UA and on STOP I lose the bit perfect.

But another user here says exatly the behavior that I blame:


"Quote from: tedsmith on 19 September, 2016, 11:38:40 AM
    FWIW I don't see that behavior here at all, at least none of the clicks.  The implementation of bit perfect testing on my DAC is different: it looks for a pattern and, of course, that pattern is disrupted when the source is paused so the bit perfect indicator goes out on pause. "

Re: ASIO and Windows 10

Reply #9 –
Perhaps I misunderstand your point, but I don't quite understand your desire to have the bitperfect indicator on when you are paused.  When you are paused you are getting all 0's and you can easily hear whether something else is happening.  It's when you are playing that bitperfect delivery matters...  I was trying to say in my post that all output methods can deliver a bit perfect output (and my DAC shows them as bit perfect) and I was also indicating that my DAC can't possibly have a bit perfect indicator when I'm paused since it's looking for a pattern that all zero's doesn't match.  I don't know why anyone would expect anything different.

Re: ASIO and Windows 10

Reply #10 –
Quote from: tedsmith on
Perhaps I misunderstand your point, but I don't quite understand your desire to have the bitperfect indicator on when you are paused.  When you are paused you are getting all 0's and you can easily hear whether something else is happening.  It's when you are playing that bitperfect delivery matters...  I was trying to say in my post that all output methods can deliver a bit perfect output (and my DAC shows them as bit perfect) and I was also indicating that my DAC can't possibly have a bit perfect indicator when I'm paused since it's looking for a pattern that all zero's doesn't match.  I don't know why anyone would expect anything different.

When you press PAUSE you don't press STOP. When you press PAUSE the DAC must be BUSY from foobar and the song that foobar is playing.
When you press PAUSE you should not listen anything else on that DAC, because it's a PAUSE not a STOP.
When you press STOP the bit perfect led must go away and the DAC must be free for other software that want to stream audio on it.

In Win 7 I had this behaviour, in Win 10 I don't. In Win 10 in PAUSE the DAC is not busy but become FREE. I don't want it. A PAUSE is a PAUSE not a STOP.

I wuold like that foobar has an option at least, when you press PAUSE it streams silence so the DAC is still busy with foobar. IF somebody doesn't like it, another option for foobar when it LEAVE THE DAC on PAUSE.

My precious problem is that my DAC when it leaves the bit perfect makes a noise, it's normal, also in Win 7 it does it, but at least in Win 7 it does it only on STOP. In PAUSE I want the bit perfect stream to REMAIN. How?

Re: ASIO and Windows 10

Reply #11 –
Are you sure this is foobar2000's ASIO plugin problem and not your DAC's driver/Windows 10 problem? Did you test your DAC's behavior with other software that supports ASIO under Windows 10?

Re: ASIO and Windows 10

Reply #12 –
Most other ASIO supporting software would not pause the audio output, since ASIO isn't really an audio output API for music or media players.