Open andreasdc opened 4 months ago
Could you provide a log that captures the moment the issue is occuring?
Also, what do you mean exactly by "doesn't detect input and output"? Do you get silence, or the stream just stops?
How can I show it to you? It happens after maybe 2 hours. Input and output don't show anything when it happens.
You should be able to gather a log for a couple of hours until the issue occurs, and then you can attach it to a comment here. (You may want to compress it into a zip file first as it will likely be very large but it should be highly compressible.)
Do you want something specific from there?
Given I have no way of knowing what the issue may be (it's the first time I hear of this particular problem), it logically follows that I have no way of knowing what may be of interest in the log until I see it. Usually the interesting parts are the beginning and the end, but not always.
Won't it be really big log file?
Yes, but it should be extremely compressible.
Today it happened after like 1 hour of talking and couple hours of being not so active.
I sent you the log file on your e-mail
Thanks. The log ends abruptly in the middle of streaming, which means one of two things: (1) FlexASIO got stuck and stopped firing callbacks, or (2) it means you copied the log while FlexASIO was still streaming. Did you close the application before sending the log, or did you copy the log while it was still running? I guess what I'm really asking is, did the issue happen at 2024-02-16T19:58:58.2596568+01:00
(which is when the log ends) or earlier.
Aside from that, nothing in the log looks out of the ordinary. Honestly, given the lack of available information and the difficulties that would be involved in reproducing this, I'm not optimistic we will be able to get to the bottom of the issue. You may want to experiment with different settings (e.g. larger buffer size, different backend) and see if that helps.
I think I copied the log file after 10 minutes of this time, I think I still have the log. It reproduces everyday for me.
I think I copied the log file after 10 minutes of this time
That would mean FlexASIO somehow gets stuck and stops firing stream callbacks. Best guess is a subtle bug in the PortAudio WASAPI code, but root causing this is going to be challenging. The callbacks just suddenly stop firing with no indication as to why.
It reproduces everyday for me.
I meant it would be difficult for me to reproduce it, as I don't know what's special about your setup that triggers this issue.
Happened again after less than 30 minutes :/ Maybe some kind of debug version will help?
And again, I see that it's pretty easy to have. Again after 5 minutes. Maybe after inactivity time?
I don't think I have it when I changed from 512 buffer size to 1024 in Adobe Audition, is there a fix for that?
If it's a subtle issue such as a race condition, it's quite possible changing the buffer size may "accidentally" work around the problem, so I'm not surprised you're seeing different results.
If it's a subtle issue such as a race condition, it's quite possible changing the buffer size may "accidentally" work around the problem, so I'm not surprised you're seeing different results.
Is it possible to fix that on 512 buffer size? 1024 increased the latency a bit and on 512 it's pretty easy to reproduce.
It happened on 1024. Is the fix possible?
When using auto convert instead of exclusive I don't have it, but I think the audio quality is wrong and I think delay is not predictable.
I found a way to replicate this: I can only say when using Adobe Audition, they have free 7 days trial. It happens with latest or older version.
Let me know if I can help in anyway.
After some time Adobe Audition doesn't detect input and output and it needs to be restarted to have them working again.