View Single Post
Old 08-27-2021, 11:00 PM   #86
thevisi0nary
Human being with feelings
 
thevisi0nary's Avatar
 
Join Date: Nov 2011
Posts: 530
Default

Quote:
Originally Posted by Dex View Post
The problem with all the suggestions of manually freezing, or using a script to automatically freeze and unfreeze things, is that FREEZING LOCKS REAPER while the freezes are rendering. You can't do anything while Reaper is freezing your tracks.

The whole point of the OP's suggestion is to have a low-priority background thread constantly "freezing" things without blocking you from working on your song. During playback, if you change something on a "frozen" (memoized) track, Reaper would discard its memoized version of the track and immediately switch back over to its normal realtime processing until it has a chance to memoize the track again.

I can think of no reasonable downside to memoization, as the OP has suggested.
Not saying it’s impossible but it’s sort of pedantic, you are trading one cpu expense for another since it’s constant rendering instead of real time playback. It’s also wasted cpu resource if it applies to a track you are currently working on / editing, as it’s creating and generating audio to immediately be replaced. The sound also needs to come from somewhere so reaper would essentially need to make a duplicate of the track if you want it to create audio while still having access to that track.

Maybe automatically freezing tracks in the background that haven’t been touched for X period of time could be helpful.
thevisi0nary is offline   Reply With Quote