Skip to main content
Topic: ABX module closes on error (Read 443 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

ABX module closes on error

Hello,

I am using foobar 1.4 beta 15.
If the ASIO driver is occupied (usually because playback wasn't stopped a few seconds ahead) I receive an error message "Could not initialize the driver". That is perfectly fine but the ABX module is closed as well, thus  forcing restart of the module and decoding again.

Is it possible to let the module stay open even with this  error message alert?

Thanks.

Re: ABX module closes on error

Reply #1
Noted, thanks for reporting.

Re: ABX module closes on error

Reply #2
New version posted, recovery from audio output errors has been improved.

Re: ABX module closes on error

Reply #3
Thank you, Peter.

I have noticed another thing: once ABX testing has started, even if it is paused or stopped, playback could not be started - neither from the playlist nor from another ABX window. Until that ABX window is closed no other playback can be initiated.

I am using foobar V1.4 with ABX plugin V2.0.5 and ASIO (V2.1.2) as output device. Is it possuble set the ABX to release the output device once it is stopped or paused?

Re: ABX module closes on error

Reply #4
Are you sure you're not trying to cheat the ABX test by comparing to tracks outside of the ABX window?

Re: ABX module closes on error

Reply #5
Is it possuble set the ABX to release the output device once it is stopped or paused?
No, closing the device would add a distracting delay with CPU load on some ASIO drivers. There is no point keeping the ABX session open without playing for long periods of time.

I can play other files to WaveOut or to another ASIO channel as long as the sampling rate matches.

Re: ABX module closes on error

Reply #6
j7n,
It was possible before. I don't think it is meant as an intentional behavior but has just been overlooked.

kode54,
Not cheating. honest :)

 
SimplePortal 1.0.0 RC1 © 2008-2018