I have a project with about twenty tracks, mostly BBC SO. I want to finish the project so I am rendering in place which I thought would reduce the load on CPU/memory, but what I’m finding is that when I first load the project it’s fine, the track plays through ok. However when I render a couple of tracks (with the default to Disable Source Track) I’m finding that playback is very glitchy and latent. So I close down Cubase, reboot the PC and start again, and it’s all fine until the next couple of tracks. This is my setup:
First well done for including your system specs.
Your buffer size is high, very high, so that really should not be a problem there.
It would be helpful to see your Studio Setup, eg how Asio Guard is setup.
You have plenty of RAM so it should run the audio files easily …
But there’s been people talking about the poor Core distribution issues with Cubase so it could be that.
I’m also on PC and had issues like that, I have tried dozens of tweaks, I cannot say which one helped or not, it’s been fairly random. One I did stick with was to disable the Nahimic Services.
Good luck
Hi there, Cubase 15 has done some weird things with the audio. I can’t recall the glitches and bugs, but I had to revert to 14 for a while, until I will feel confident it works well.
Perhaps install 14 and see if you still have the same problems when rendering in place?
Hey, do you mean how much reverb/effects to add in terms of how wet/dry a reverb can be?
If you are referring to weather you are able to export dry, with channel FX, full chain etc. you can set this under Preferences to do with the Render In Place settings.
In all honesty, Render in Place is a massive deal to me, as I export parts all the time.
I have assigned a key command to it and it is super fast.
Yes, I meant how much reverb/effects you can add. And yes, I know about the various render in place options for this. However, render in place isn’t working for me, and to be honest the few seconds it takes to add an audio track, route it and record from the MIDI is an acceptable overhead.
There’s clearly a problem there, my setup is more modest than yours and I’m working great with 14 - not 15 yet - using orchestral samples. Why the enormous buffer? When mixing I’m increasing it to 512 and that’s plenty enough for complex mixing, and somewhere I read something about problems with very large buffers - sorry, can’t remember where, perhaps the sound on sound forum…
I also read sometimes the spitfire player can be problematic. As I’m in the old kontakt versions I can’t help you there. Are you on the newer player or still in kontakt? If the latter, what settings are you using within kontakt? (CPU and disk preload)
I’m using the Spitfire Player. I have had some issues in the past with the buffer size being too low so on advice from my tutor (I’m doing a master’s in composition) I increased it.
Probably 512, but I don’t recall. From speaking to fellow students I think the Spitfire player is a bit glitchy, but my workaround upthread is fine for my purposes.
Here’s a key thing that I noticed. Cubase 15, as opposed to 14, have new Video-related features. Render In Place actually also fetches information from the video side of the coding. That explains why there was a bug that RIP didn’t work when video was involved. The temporary workaround was to mute the video track. But here’s the thing, even if there’s NO video track, RIP still works under practices that fetches information from the video side of things. It has been severely affected by such programming.
The only not-ideal workaround, is to render in small batches at a time at this moment.
