FEATURE REQUEST: Export Frozen Tracks

Hello.

As we do a lot of collaboration with geographically distant people, we use a lot the track import/export feature (track archive).

I send you the new vocal track, you send me the new guitar solo…

This works only with audio tracks and midi tracks, but not with frozen VSTi tracks.

Have a nice day.

Andy

Couldn’t you just unfreeze the track and export the MIDI and/or audio?

Or even send the audio file created when freezing occurs?

Cubase would have to load everything back in anyway (I think).

Thanks for your reply.

If I unfreeze the track and I don’t have the VSTi installed on that machine, I loose all sound.

I’ve never messed up with the Freeze Files Folder, but I think that if I have a (e.g.) piano part at the beginning, another in the middle and another at the end, I would have to send 3 audio files without any timing reference, so importing would be a nightmare.

It would be nice if frozen tracks would just be handled as any other track, so when I have to export e.g.12 tracks, I don’t have to render individual frozen VSTis before the export.

Andy

I was assuming VST mirroring on the machines.

I think it’s one audio file per track. It’s basically an export then import of that track.

I would think that the audio files from freezing would be the best way.
In reality, a frozen instrument track is just an audio file (in-place render).
I just don’t know about how their named.

The trouble with frozen tracks is it strips out the silent bits and sticks it all together!

…so you are saying that I can go to the freeze folder, take the file and insert it at bar 1.0.0 and I have the rendered track?

I never tried this.

Great if that works, but it still looks like a workaround, but great idea.

Thanks.

Andy

I’m not sure of that.

Try before committing.

Cubase may just keep track of the location of the start of the VST playing and insert the freeze file there.

What do you mean by that Split?

That means that wherever the frozen track is silent, that information is not stored in the frozen wave file to reduce filesize. You have all the information in that wave, but the timing will be wrong unless the frozen instrument was playing in the song from the beginning all the way till the end.

Ah…

So @AndyThommen, I guess it won’t work.

Thanks to all.

No worries, I’ll continue to manually bounce the frozen tracks (via internal bus) to audio and then export them, until this feature (or a simple one-button bounce) will be implemented.

Have a nice day.

Andy

Freeze as a function is on a permanent backburner

As you’re using an i7 machine you should not need to freeze any tracks IF you use a reasonable number of tracks/parts.
There is a limit. If you need freeze then the amount of work you have in a Project would be very close to unmanageable brainwise anyway.
Maybe have a good think about the way you work and if you could do anything more economically so as not to overload your components. Taking a little time now could save you loads in future.

Freeze is a stop-gap for older machines to enable users to carry on working when they need a bit extra to finish off a Project. I don’t think it was meant as a main feature for very long and If I needed to use it I’d use it as sparingly as possible and not plaster it all over the Project. I’d expect some real funny trouble if I had to. It’d be more realistic to convert it to audio and mute the midi track. Job done. Overload eased and exportable.

I have to politely disagree with Conman.

I have an i7 with 64-bit Win 7 w/ 8gb. Windows itself takes about 1gb and large sample sets can quickly eat the rest. Freezing these days is about freeing memory, not cpu, at least for me. I use Mach 5 and Kontakt mosty and the best sounding large sample sets can eat 6-7 gb in no time at all… so I freeze to free up ram.

It doesn’t really matter what it’s for, the fact is it is a relatively cr@p feature that has been neglected since its’ inception.

Sorry, you didn’t read the post.

During the creative/writing phase, the keyboarder (in city “A”) creates keyboard tracks in a project with VSTis that will be frozen and then sent to the recording studio in city “B” where those VSTis are not installed.

We use freeze for compatibility reasons, not to reduce CPU usage.

Again: the workaround is a bounce via internal buss and then export, but it would be easier to have a feature to simply export the track.

Andy

To my way of thinking freeze should be fully integrated with the pool.

1 Like

During the creative/writing phase, the keyboarder (in city “A”) creates keyboard tracks in a project with VSTis that will be frozen and then sent to the recording studio in city “B” where those VSTis are not installed.

We use freeze for compatibility reasons, not to reduce CPU usage.

Point me to the page in the MANUAL that says that frozen tracks can be exported and I will believe that you have read it. :mrgreen:
Compatibility with WHAT? Are you exporting to a mortuary? :mrgreen: :mrgreen:

What’s wrong with exporting as OMF ?

Freezing to save RAM? (Audiocave) I’d just buy more ram. It’s be cheaper in the long run.

Actually freezing the odd track to quickly stop a high latency plugin getting in the way of a quick overdub is very handy on occasion.

I’d agree with that. Nice trick with it. Creative, and you didn’t have to ask Cubase to add it as a feature. :mrgreen: