I think it was schwa who worked on itelam wrote:I was waiting for you to chime in hombre. I was ready to post on Reaper forum about "freezing item" option as some people talk about it a little while ago when Justin bring the "freeze tracks" on the table.
This is how I work:
Once I've set up all my levels (gain staging), I start adding Nebula instances per track and I work on 2 or 3 tracks at once (my computer can't handle more than that). Preamp+Tape+Boost+Console per track (sometimes it's just Tape+Console, etc.). OK, now once I get the sound I want from those tracks I freeze them. If I want to keep the console instance I just set it to offline state before freezing so REAPER won't take it into account in the freezing. Once I've frozen that track I just set that instance back to online state and continue my work. Freezing in REAPER doesn't work like other programs where frozen tracks aren't editable/modifiable. In REAPER, if you freeze a track you can unlock the new rendered file and edit it. You can offline FXs that you don't want to be present in the freeze and then set them online again and continue your work. You can freeze all your equalization and then freeze your compression, for example. You can go all the way back to your original state and REAPER will maintain your FXs (it doesn't keep your item edits, though). So, in conclusion, you can freeze as many times as you like and always come back to your previous/original state. REAPER will recall your "frozen" FXs and will put them there in their place in the chain again (you need to be careful with this, if you unfreeze a track all nebula instances will come back and that may collapse your CPU/RAM).