Anyone else notice this? It may be a bug but all my bounces are 30 seconds longer than the actual track. It is the same for MP3 and Wave file mixes. Very strange
Hi,
youâll probably find some sort of event behind the track lon an automation lane , a muted event, etc
If a correspondig effect (like reverb) is inserted, the audio file can be longer (reverb tail).
Thanks for the suggestions. I turned off all spatial effects and it made no difference. There are no extra events that I can see and I canât zoom out any further. In the Project Setup window the project length is set to 2:20 and the track is about 2:12 but the final bounce comes out at 2:43. This means it is adding an extra 31 seconds of silence at the end.
Are there any insert or send FX? If yes, try to deactivate (or remove) all of them.
Thanks. Removing all inserts and sends fixed it. The bounce is now 2:20 - exactly as it is set in the project length. Now to find out which plugin is causing the problem 
1 Like
So, you can only export it without effects? Iâm facing the same issue, but Iâd like to have the option to send effects along with the export. 
Quick Export always includes all activated effects. If these include any that linger, this will be taken into account at the end and the mix may take longer than a dry export would.
So itâs not quick export, or very useful then, if it ignores loop regions and requires further editing and additional rendering to remove 30 seconds of silence that it adds on.
To avoid the so-called silence at the end, the project must be exported without insert and send effects.
I still think it is a bug but I found another solution. By placing a gate across the master bus with maximum hold (2 seconds) and release (1 second) times the Quick Audio Export feature only adds about 8 seconds of unwanted silence at the end of the bounce.
Observation proves, that every audio file created with Quick Audio Export without effects has exactly the same length as the audio in the project. However, if active effects are involved, Cubase calculates a decay time to extend the audio file. This can be the decay tail of a reverb effect, for example, in which case it is audibly NOT silence. However, it can also be an âinaudibleâ decay phase that may appear to be silence. Steinberg has not made the algorithm for calculating the decay phase transparent. This leaves room for suspicion that something is ânot quite rightâ.
A common calculation for reverb time is RT 60 or when the reverb decays to 60 dB lower than its original level, it is considered silence.
I think this new algorithm is miscalculating the level at the end of a track. I have listened to the added âsilenceâ at high volumes and there is nothing there.
As mentioned, the algorithm is not documented anywhere, but itâs likely not a volume threshold; rather, the output activity of the plugins used is probably monitored, similar to how it is used for automatic VST3 plugin deactivation.
(post deleted by author)
This feature seems broken currently. I cannot see how this could be working as intended.
Surely it should not be ignoring loop regions?!
Surely it should be a way to quickly export a stereo mix down in audio or mp3 without needing too many options.
as it is, it is not âquickâ. The rendering takes a lot longer, the rendered audio file is messed up and requires re-editing, unless you remove the processing from your mix and mess that up to make the âquick exportâ work.
1 Like
(post deleted by author)
And what is the point of quick export than? We should do also 5 push ups and we are all set for the âquick exportâ. the function si broken as many many things in cubase 15
I think âquickâ refers to the elimination of the need for previous settings. Measurements have shown that the actual export process for quick export takes exactly the same amount of time as for conventional export.
Incidentally, depending on the length of the project, it is entirely possible to do some fitness exercises while it is running. 