How to freeze tracks in v7
-
- KVRer
- 24 posts since 8 Jun, 2014
I have searched and searched and searched but can find no way to freeze tracks. All I see is a way to render track to audio.
I have attached screen grab of my scenario.
I have my kick, snare, high hat and cowbell recorded on separate tracks under Battery drums (they all go to the same main rack but use separate outputs. I want to output each of those to a separate audio track. When I select render track to audio I get all 4 drums even though I have only selected cowbell.
In Reaper I just click a freeze icon on the track I want rendered and it is rendered to a track below, but I seem to have to mute all other drums go to menu select render to audio, move that track from the bottom up to under the track I have just rendered, then mute that midi track, unmute the next and repeat.
I have searched for freeze in docs but am just taken to a page with no info. I am sure it is possible and simple, I just cant find any information, other than the "Whats new in v7" which says under the Rack heading that Freeze / Render has been added. However I do not want to freeze rack (all drum parts), I want to freeze the individual tracks.
Any help would be much appreciated
I have attached screen grab of my scenario.
I have my kick, snare, high hat and cowbell recorded on separate tracks under Battery drums (they all go to the same main rack but use separate outputs. I want to output each of those to a separate audio track. When I select render track to audio I get all 4 drums even though I have only selected cowbell.
In Reaper I just click a freeze icon on the track I want rendered and it is rendered to a track below, but I seem to have to mute all other drums go to menu select render to audio, move that track from the bottom up to under the track I have just rendered, then mute that midi track, unmute the next and repeat.
I have searched for freeze in docs but am just taken to a page with no info. I am sure it is possible and simple, I just cant find any information, other than the "Whats new in v7" which says under the Rack heading that Freeze / Render has been added. However I do not want to freeze rack (all drum parts), I want to freeze the individual tracks.
Any help would be much appreciated
You do not have the required permissions to view the files attached to this post.
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
OK, it's not as obvious as in some programs - partly because MuLab allows more flexibility, so you have to be more specific about what you're rendering. The function I think you're looking for is "Render Selected Parts as New Sample" on the Project menu. In the composer view, select the Part or Parts you want to turn into an audio file, then click "Project->Render Selected Parts as New Sample", then set the folder you want to use (if you've saved the project in a folder already, that's the best place), pick the audio quality and the duration and click OK. This will then render the selected parts and created a MuSampla player to play the new sample. You can then mute the parts you rendered.
-
- KVRist
- 41 posts since 20 Dec, 2016
Currently I am right clicking on the track -> "Select all parts on this track", then Project -> "Render selected parts as new sample", toggling "create new part using result", muting old track. As you can see, it's too much hassle, at least it can be done. Would also like to know how to freeze without doing all that. Too bad MuLab doesn't have auto-actions like drawing applications have, where you can automate a bunch of stuff by just recording your own action.
-
- KVRer
- Topic Starter
- 24 posts since 8 Jun, 2014
Thanks for that pljones, yes that works, but that does seems an unnecessarily long winded and wasteful way to do it.
My understanding of freezing a track is that it is an option within a DAW where the original data can be temporarily rendered as audio and the track now uses this rather than the original data, when the project is playing, thereby lightening the load on resources. A truly frozen track should have an option to unfreeze the track to get back to the original data if and when you need to.
Rendering as audio in Mulab is just that, rendering the file as a permanent audio file, which it can copy to a new track (a stem track), thereby doubling the number of tracks you have. It is not actually freezing the track, but creating another track with the rendered audio of the original track on it.
My understanding of freezing a track is that it is an option within a DAW where the original data can be temporarily rendered as audio and the track now uses this rather than the original data, when the project is playing, thereby lightening the load on resources. A truly frozen track should have an option to unfreeze the track to get back to the original data if and when you need to.
Rendering as audio in Mulab is just that, rendering the file as a permanent audio file, which it can copy to a new track (a stem track), thereby doubling the number of tracks you have. It is not actually freezing the track, but creating another track with the rendered audio of the original track on it.
-
- KVRAF
- 1925 posts since 29 Mar, 2013
You can then "bypass" the instrument or rack and that will save you some cpu and you can still access the original.
Beauty is only skin deep,
Ugliness, however, goes right the way through
Ugliness, however, goes right the way through
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Freezing in any DAW renders to stored audio data that is then played back. How an individual DAW implements this is DAW-specific. As bibz1st says, you can turn of functionality within MuLab that you're not using. As MuLab is modular, it isn't always clear that one track is the only thing that could possibly be using a component, so it's best left to the user to decide. If you have a simple set up, where only one Track routes to any Rack, then disabling the Rack will do nicely.
-
- KVRist
- 388 posts since 28 Oct, 2002
I'm running out of cpu so did a search and found this thread. For some reason I'm having a mental block with the process. I've rendered a cpu hog of a track to audio then turned off that track but no reduction in cpu usage. I know the answer will be a "oh why didn't I see that " moment, but I'm tired and slow of thinking 
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Instead of muting the track, switch off the rack it is playing, that will stop processing that rack.
