ASIO timeout reason |
foobar2000 Development Forum RulesThis forum is for developer discussions only. If you have a problem / bug report / idea / feature request that isn't related to foobar2000 SDK, post it in an appropiate forum instead - tech support questions go to support forum, everything else goes to general forum.
All non-developer posts on this forum will be removed. Continued abuse of this forum will result in admin actions (warnings, account suspension).
  |
ASIO timeout reason |
 Sep 13 2012, 15:51
Post
#1
|
|
|
Group: Members Posts: 3 Joined: 13-September 12 Member No.: 103127  |
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 This post has been edited by borges: Sep 13 2012, 15:52 |
 |
 
|
|
Sep 13 2012, 16:07
Post
#2
|
|
 Group: Admin Posts: 3229 Joined: 30-September 01 Member No.: 84 |
Timeout means unresponsive/deadlocked driver code.
-------------------- This job would be great if it wasn't for the users.
|
|
|
|
|
Sep 13 2012, 17:20
Post
#3
|
|
|
Group: Members Posts: 3 Joined: 13-September 12 Member No.: 103127 |
QUOTE (Peter @ Sep 13 2012, 16:07)  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 |
|
|
|
|
Sep 13 2012, 20:48
Post
#4
|
|
|
Group: Admin Posts: 3229 Joined: 30-September 01 Member No.: 84 |
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.
-------------------- This job would be great if it wasn't for the users.
|
|
|
|
|
Sep 13 2012, 21:16
Post
#5
|
|
|
Group: Members Posts: 3 Joined: 13-September 12 Member No.: 103127 |
QUOTE (Peter @ Sep 13 2012, 20:48) 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 |
|
|
|
|
Sep 14 2012, 03:21
Post
#6
|
|
|
Group: Members Posts: 1 Joined: 14-September 12 Member No.: 103137 |
QUOTE (borges @ Sep 13 2012, 23:20) QUOTE (Peter @ Sep 13 2012, 16:07) 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 |
|
|
|
|
|
Lo-Fi Version | Time is now: 19th June 2013 - 18:13 |
