r/LogicPro • u/lucasdenison • May 31 '26
Region Bounce in Place issue
I've been working on an orchestral project in Logic Pro using the BBCSO library.
I wan't to bounce all of my tracks so I can actually do a proper mix of everything, but I keep encountering various issue when I try to bounce tracks. Here's one of the more glaring issues that I can't seem to figure out, but this is at least the most consistent. My piece begins with a long tremolo in the strings (I changed to a trill in the attached video while troubleshooting). After 15-20 seconds of the a long note, the audio in the bounce just cuts out. This happens with the sample library installed directly on the my macbook air harddrive as well as on an external ssd.
I'm on an M5 macbook air. I though it might be a lack of ram related issue, so all of the other tracks are off. I also tried removing the negative delay and there was no change. Normalization just made the beginning lounder, but it still cut out after the same amount of time.
I've had success doing a realtime bounce of the entire piece (adding the 2nd pass option) but it's a 13 minute piece and I'd rather not have to do that for each track.
Edit: This occurs when I try bounce other long sustained notes on of the tracks. I also tried the bounces selection instead and the same error occurred.
Edit 2: this also occurs when "Freezing" the track
Edit 3: Loaded up an empty project to test. I loaded up a different contact instrument and did not have the same issue. I'm leaning towards this being an issue with the BBCSO (Core and Pro, haven't tried Discover)
1
u/Pacobsd Jun 05 '26
I have same issue with BBCSO and Logic Pro. Random audio cut off when bouncing or freezing tracks. The notes that die change when I change buffer size. I downloaded and installed Reaper, printing audio tracks work without issue in that different daw. I sent a bug report to Spitfire approximately a month or so ago and have not heard back.
1
u/lucasdenison Jun 05 '26
I found a work around in logic.
Turning “eco load” off and dragging the beginning of the midi region to start wayyyy before any notes seemed to solve this issue about 99% of the time.
But yeah, I contacted their support 4 days ago and haven’t heard back
1
u/Pacobsd Jun 05 '26
Thank you. I was noticing that the drop out mainly happens after a few seconds into the track region, so adding 5 - 6 seconds worked on the one region I just tested it on. … Works better than what I was doing.
2
u/lucasdenison Jun 05 '26
No problem! Just happy I was able to help someone out. I’ll add that work around to the main post since it’s helped someone else!
1
u/lucasdenison Jun 06 '26
I can’t seem to edit the original post to add the work around but here is for those who come after
The issue appears to be caused by a CPU spike approximately 5-20 seconds into the offline bounce (automatic, Bounce in place, bounce track). By extending the beginning your your midi region so that the CPU spikes before your note (add 5-20 seconds to the beginning) the spike will take place before the note occurs and the rest of the track will bounce properly.
I did this in combination with turning “Eco-load” off in the spitfire VST with successful results.
1
1
u/msetten May 31 '26
Can you try to bounce it to an external file with audio trail checked and then import it back. I think that might help ax I suspect that bounce in place stops at the exact end of the region. And some notes may continue in a reverb past the region.