Hello,
I'm usually quite good at working these things out, but I am COMPLETELY stumped by this one. I'm hoping there might be some clever people on here who can help me out! I have been running a rather large project (90 odd tracks... no big plugins.. just EQs/Comps and a few of the Matrix Reverbs) in Reaper over the past few days quite happily, but after having just upgraded to v4.32 a few hours ago and then tinkering with a few buffering settings to see if I could improve performance slightly with automation etc, the audio has just stopped passing, even though my master's metering within Reaper is showing healthy signal.
I went through the usual initial steps of re-booting the Mac, power cycling the sound card etc etc, but audio would still not pass - it was as if Reaper was having trouble 'talking' to Core-Audio. I then tried running another audio application called QLab, which worked fine to all audio cards etc. The interesting thing was when I tried setting up another project in Reaper... this DID work ok. Therefore, it suggests the problem is PROJECT related. I opened a previous backup of the same project from earlier in the day, and this STILL didn't work. I can't even route audio to my internal sound card, and importing a fresh wav into the project and routing directly from the track doesn't help... which suggests it isn't 'Master Bus' related.
The only other thing worth mentioning is that I also tried running my project in Reaper 64bit. I can't remember if the audio cut out for the first time in the 64bit or 32bit version of Reaper. Either way, both versions still run new projects quite happily.
I'm running a Mac Pro with 2x2.8GHz Quad-Core Intel Xeon Processor and 8gb RAM.
Thank you for reading. I look forward to hearing from anyone who may have some words of wisdom!
I'm on quite a tight deadline for this project.
Andy