Experiencing a serious render in place issue here with Cubase 14.
Selecting a few clips from a few different channels to render them together, it would bounce it down with other channels that are not involved at all in the render request. Seriously disturbing as this can bring up big mistakes in the track if you don’t see it.
Happening here and there without real logic it seems. Sometimes it would do the job properly and sometimes would just add other tracks in the bounce that shouldn’t.
1 Like
Here is a video showing the problem, I just can’t get it… seems like a proper bug to me or please somebody explain.
It does make render in place very hard to trust, unless there is a specific setting that I’m completely missing.
Thanks for your help !
I raised this months ago and again in Cubase 14 here:
Does that describe your issue?
It’s an absurd bug. As you said Render can’t be trusted, which is a very fundamental function in audio production.
This bug has been around for a while, s I find a post from 2017 about it.
Really poor.
1 Like
Dang! Thanks for confirming an issue here.
I don’t exactly relate my experience with muted elements overlapping here. I didn’t get the logic of the bug yet, but it totally makes render in place hard to trust !
I just upgraded from 9.5 to 14, with some great improvements I must say, but going downwards with what you grant as rocking solid functions like that is a hard one to digest. Indeed this is a very fundamental function you should be able to trust, clic and process… If not, it can ruin lots of hours of work… damn
Now this is serious problem !
I just rendered strictly my bass channels and I get random snare & drum channels to be added to the bounced track or whatnot. Unusable whatsoever, sad !
Back to test in 9.5, same track and same process, all is great.
Luckily we can work on newer versions of Cubase and open the same project in older versions!
So yeah… I’m down to stay with 9.5 here. Probably great to have this and that in newer versions, but if we kill such important behaviour with upgrading, I don’t give my money for you yet!
Just curious, so I can narrow down what to watch for when rendering:
Are you using side chain compression between your bass and drums by any chance?
I wish I could relate a side chain signal to create the problem, but it doesn’t seem to be linked.
I do have SC quite often, but they are relatively basic (kick to bass, or kick to something)… the issue happened where no SC was involved
1 Like
Is it only happening when trying to combine multiple tracks into one render? I just rendered out 12 or so VI tracks the other night so I could move a project to the ‘mixdown’ phase and it had no trouble doing the whole batch (but I also have it set to render each one individually).
I put an empty region at bar 1 of every track too I can bounce out a full wav file to line up at the start, and everything was fine there.
1 Like
Only happening when combining at least 2 tracks into 1, yes… I don’t think this issue happens when you don’t have the “render into one audio file” option on.
I’ve first noticed the problem when bouncing like 10 tracks into 1, then figured out it would do it just with 2. But I “believe” if each track gets rendered individually, it’s all fine.
1 Like
Mac or PC?
I wont be home from work for about an hour and a half (loooong drive once Im off in 30 haha). I’ll do that same project again on the Mac, but this time bounce them all down to 1 render and see if it does it here too. I think I’ve only ever used it to do individual tracks by themselves, never needed to try to group them before…
Hmm didnt have any issue here. I picked 4 Halion tracks I had, these are ‘effects’ and whatnot and some vocal samples so there is a lot of dead space between the parts to give it room for error.
Matched your settings but left the tail at default length and there’s no reason to render audio files in 32 bit float so that stayed at 24. Not a single issue. Did a few different sets of tracks just for kicks to test it out, including some audio tracks just to make sure, everything was fine.
1 Like
Did the process 100 times and everything was fine. But there has been some random cases where it completely failed, and it would fail each time of trying the same one.
So yeah, I guess it’s possible that you won’t have it happening on your side, I can’t tell what’s the cause of the wrong behaviour, but if you see the video I made it clearly shows there is a bug. It did happen in 2 different projects so far. And if I didn’t see it I’d have put serious mistakes in my rendered files.
Back on 9.5 anyway, I uninstalled 14…
Yeah I was wondering if it was maybe audio vs virtual instruments, and then when I noticed your Inspector window, it looked like one of those tracks went to a group so I thought maybe it was picking up the rest of the tracks in the group too for some reason…
But to rule that out, I picked two of my drum tracks in the song which were audio tracks recorded from my S3000XL sampler. All six or seven of the drum tracks in it go to a drum bus for “glue”. Only the two tracks I picked to render went through, and this was with the same settings as well (I thought maybe it could have been that you bounced through the whole signal path too but nope). I picked the drum tracks that start during the ‘drop’ of the song, and was half expecting to see the break I used during the intro pop up but only the ‘drops’ were there, I could see it right away when it made the waveform again.
Do you see it happen often? It could just be the old cursed corrupted project rearing its head again if its just the one. Then again, I’m also on a Mac too, so we may be looking at a Windows only issue??
From my understanding, render in place would solo the tracks where you have selected clips or regions, activate the group & fx tracks where those soloed channels go, then bounce.
The random sounds and channels that would be added in my bounce were not related to the selected clips whatsoever (drums or bass in my case) which aren’t shared in terms of groups, maybe they share some send FX or something else, but I couldn’t bother to dig further into that issue I must admit. Never had such a problem with 9.5.
This is a function I really need to trust blindly, as I compose without really caring how many new tracks I create, and of course I have to bounce down at some point to reorganise the whole thing. I can’t go with the software adding mistakes like that.
It happened only a few times over a 100 bounces or so.
And yeah I’m running windows, it could possibly be just a windows user issue, can’t tell about that.
I totally admit that it could be a specific case according to my projects & setup, but since I couldn’t figure it out logically, I just wanted to report, maybe get a clear “why this is happening”, and warn other users that use that function.
Yeah always good to report it either way… It may be a 1 every 100 thing just because of some random error every now and then. I may have gotten by just fine last night, but who knows if I try to combine some tracks down the line, maybe it will trigger. I use the render function a lot myself so I want to make sure its 110% hah.
Could be a Win/Mac specific thing, who knows, better to get it out there so they can look into it!
I came back to testing as C14 has got some very cool performances improvements compared to my old 9.5…
Still came across this render in place issue, and what I could figure out is :
My selected track(s) to render are going to a Group channel.
Other audio channels have this same Group channel set as input but are not selected to be rendered.
Result will be a mix of all.
I guess this might be funny routings to some of you, but it’s for the basic sake of recording in real time tracks within the same project.
Please tell me how you do it otherwise, but I really need that workflow :
- open a VST instrument, you want to jam with it in real time and record straight the audio while you’re playing.
my way to go was always to create a group track, route the vst to this group track, open a new audio track and set the group track as an input.
Play and record live…
Then needing the ability to route FX tracks back to the same group to have send channels added to the signal.
So basically in all my projects I have this so called “rewire/loopback” track for the purpose to record sounds played on the go.
Now this routing makes it seems a big mess in the “render in place” function. I think in cubase 9.5 (that I’m the most familiar with) it was soloing the tracks you selected clips from, and would allow the routings of FX sends if you select “complete signal path” by soloing those fx channels as well, and the groups (you would actually see all tracks not being involved muted and only the involved tracks in the signal path to be soloed)
Now in cubase 14, it doesn’t react the same way at all… and would let other channels not involved in the selection to go through the same rendering process… (you don’t see any solo/muted tracks while rendering) which is very very very annoying and hard to deal with, or please explain me the logic behind it that I do wrong. If I select something, I want these selected elements (clips/tracks/channels) only to be taken into account and I don’t want any other random elements to be rendered with it because they share certain similar routings.
I’m happy to dig further to demonstrate where this issue is appearing.
Hey, I just wanted to report the same issue in hope of a soon solution from Steinberg…
It happens with my 12 Drums Tracks (audio recordings) after editing them with Audio Warp/Free Warp. Each Track composes of two takes cut together, they are not going to any bus or what so ever, no fx, no insert, etc. I am using windows.
I have also observed that the rendering process does not go from top to bottom but seems to follow a random order. Also it seems to switch channels in no logical order, so after rendering Ch1 to Ch12 I will get like 2 times Ch1, then Ch8, then 2 times Ch4, and so on (i tried to replecate the problem for the exact Channel orders but then it worked perfectly fine ._. tell me if someone needs exact information).
Saving the project and then restarting cubase seems to work. By the way, you can see if it works by the order of rendering. If it goes from top to bottom without skipping any Tracks it should work fine, else you should cancel and restart cubase.
I hope they’ll fix it soon, this programm was expensive enough to expect the basics to be functioning.
Edit: The issue also occurs by rendering the tracks one after another and restarting won’t help every time, so I find there is no save workaround…
Hey there, i have noticed that the problem only ocurs when i try to render my grouped tracks with the setting “edit as group” or “phase-coherent editing” activated. So after deactivating these settings rendering worked fine every time.. even though I am still checking every single rendered audio for a petential error 
Please respond if you by chance had activated the same settings and if the error disappears when you deactivate these… I hope this helps 
sorry, my mistake