Post by Chris on Aug 30, 2013 16:05:49 GMT
I'm experiencing some weird behaviour with the v2.11beta versions (1&2) that didn't show up
in v2.10 of asio4all on Win7 x64.
Starting REAPER with a4a I always get one channel on one audio device which is marked with the
red cross for being unavailable. This happens while the Windows-Audio Service is running (not the
Audio Endpoint Builder Service).
The blocked channel seems to dependant on the audio device order in Windows - I tried this by
disabling some of the virtual audio devices on my box.
When I stop the Windows Audio service (or if it's going to sleep after some time), the channel
becomes available again. The procedure to free the blocked channel is a pain - especially after a
Windows startup/restart (either stop the Windows-Audio Service manually and restart after
asio4all is loaded or wait until the service stops his HeapValidation and such).
There's for sure no other application (or midi) blocking the channel, it's a bug in a4a itself since
v2.10 works flawlessly!
Hope this helps on further development ... ;-)
And a4a is just great .... in case I didn't mention it before :-))
Chris
in v2.10 of asio4all on Win7 x64.
Starting REAPER with a4a I always get one channel on one audio device which is marked with the
red cross for being unavailable. This happens while the Windows-Audio Service is running (not the
Audio Endpoint Builder Service).
The blocked channel seems to dependant on the audio device order in Windows - I tried this by
disabling some of the virtual audio devices on my box.
When I stop the Windows Audio service (or if it's going to sleep after some time), the channel
becomes available again. The procedure to free the blocked channel is a pain - especially after a
Windows startup/restart (either stop the Windows-Audio Service manually and restart after
asio4all is loaded or wait until the service stops his HeapValidation and such).
There's for sure no other application (or midi) blocking the channel, it's a bug in a4a itself since
v2.10 works flawlessly!
Hope this helps on further development ... ;-)
And a4a is just great .... in case I didn't mention it before :-))
Chris