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 timeout reason (Read 4692 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

ASIO timeout reason

I'm debugging an audio system which uses USB Audio Class 2 firmware on an MCU and an ASIO driver on Windows. Occationally, I get "Unrecoverable playback error: Timeout" in foobar2000 (version 1.1.13).

Could you please share some details on what is causing this error? Is there a particular ASIO function call which fails? Knowing more about how the error appears in foobar2000 I'll hopefully be able to track it through driver and firmware.

The Audio Widget project may perhaps interest you, both firmware, ASIO driver and hardware schematics are open source. More info at www.qnktc.com.


Thanks,
Børge

ASIO timeout reason

Reply #1
Timeout means unresponsive/deadlocked driver code.
Microsoft Windows: We can't script here, this is bat country.

 

ASIO timeout reason

Reply #2
Timeout means unresponsive/deadlocked driver code.


Thanks Peter. I was hoping you could tell me which ASIO fuctions you call to determine a deadlock, so that I can add debug messages to them.

Børge

ASIO timeout reason

Reply #3
I don't call ASIO functions to determine a deadlock, I presume a deadlock when some ASIO call takes more than 10 seconds to execute and kill the process running ASIO code.
Microsoft Windows: We can't script here, this is bat country.

ASIO timeout reason

Reply #4
I don't call ASIO functions to determine a deadlock, I presume a deadlock when some ASIO call takes more than 10 seconds to execute and kill the process running ASIO code.


OK, good to know. Would it be too much to ask to name the offending call in the error message? :-)

Børge

ASIO timeout reason

Reply #5
Timeout means unresponsive/deadlocked driver code.


Thanks Peter. I was hoping you could tell me which ASIO fuctions you call to determine a deadlock, so that I can add debug messages to them.

Børge

Hi Børge,

I know where is deadlock. Problem in ASIO function bufferSwitch. In some cases, after you press play and immediately stop my ASIO driver enough time to call bufferSwitch, but from bufferSwitch doesn't returning

Nikolay