Several of months ago I had a problem with REQ131 not passing any audio over it.
It was a heavy project with lots of native devices and REs and just one of the multiple REQ131 instances stopped passing audio.
I had to restart Reason for it to work again, but after a few minutes, the same REQ131 instance stopped passing audio. I rebooted PC, bounced some tracks to ease up on the DSP usage, and the problem did not has not reoccurred.
This Sunday, it happened again, but in a low DSP project and this time, one of the multiple Softube AMPs refused to pass any sound (even bypassed). After I reloaded Reason, it was OK, I did not had any problems even though I worked for hours on the same project.
I don't know what the culprit could be, didn't bothered me that much as it only happened twice in several months, but I want to know if others have experienced this so far?
If yes, then maybe we can help find the root cause, or the common denominator of the problem and inform Propellerhead about it.
PS. My system has an i5 3570k with 16GB RAM running Win8.1 and RME Fireface 400 audio interface with latest drivers.
A random RE stops processing audio
-
- Competition Winner
- Posts: 4059
- Joined: 16 Jan 2015
Hmm, ... I'd run a memory corruption test first. Check CPU temperatures and drive health as well.
Also does restarting windows resolve it.
When you have a bug that happens rarely but continues to happen in the same day, if it is a reason bug it's more likely to be caused by memory corruption, which itself is somewhat more likely than not to occur in dynamically allocated objects but is dependent on system states that persist between launches of reason that affect allocation patterns that only expose overflow and internal access violations on rare occasions.
When it happens I'd also check to see if any VSTs also suffer as well as whether it happens in other DAWs and whether RRP is what subject to it.
Reason Studios could provide you with a logging version of reason you could run next time it happens, but there's always the possibility it won't happen on that version.
If it has happened to others it would be interesting to see if there are any differences in frequency and whether they happen on the same date.
Intermittent and rare intermittent bugs tend to be the trickiest to find for the main reason that you first have to have the bug occur first to debug it.
Also does restarting windows resolve it.
When you have a bug that happens rarely but continues to happen in the same day, if it is a reason bug it's more likely to be caused by memory corruption, which itself is somewhat more likely than not to occur in dynamically allocated objects but is dependent on system states that persist between launches of reason that affect allocation patterns that only expose overflow and internal access violations on rare occasions.
When it happens I'd also check to see if any VSTs also suffer as well as whether it happens in other DAWs and whether RRP is what subject to it.
Reason Studios could provide you with a logging version of reason you could run next time it happens, but there's always the possibility it won't happen on that version.
If it has happened to others it would be interesting to see if there are any differences in frequency and whether they happen on the same date.
Intermittent and rare intermittent bugs tend to be the trickiest to find for the main reason that you first have to have the bug occur first to debug it.
-
- Information
-
Who is online
Users browsing this forum: CommonCrawl [Bot], Rising Night Wave and 13 guests