Active lane(s) not restored correctly after unfreeze

[plant-on]

On Reaper 7.14, Win 11 it appears that all lanes are activated when unfreezing a track. My expectation is that upon unfreeze, lanes and their active state would be restored to it's state prior to being frozen.

To recreate;

1. Record into two separate lanes
2. Select only one as the active lane
3. Freeze the track
4. Unfreeze the track
5. Both lanes are now active

[plant-on]

Upon further investigation behavior of freeze/unfreeze and lanes appears quite odd.

For example, sometimes when you freeze it will put it in a lane that is not activated, and then when you unfreeze it doesn't activate the correct lane.



Or, similar, if you disable lanes, freeze, the frozen media disappears into a lane that isn't visible;

[plant-on]

Can others replicate this? Does anyone have a workaround? My only workaround is to freeze a parent folder but it's not really the same thing.

[drewyeah]

Any word on this? I am able to recreate this and I've been having this problem as well. I've found 3 problems

1. Freezing will only work as expected if the top lane is the one that is selected. If you have 3 lanes, select lane 3 and freeze, then the resulting lane will be renamed whatever the top lane is named (ex 1), and when you unfreeze, both the top lane and whatever lane was frozen are selected (ex 1 and 3).

2. Also lanes must be enabled when you freeze or reaper will just display an empty lane and hide the freeze in the bottom lane. So if you have 5 lanes and lane 1 is the only visible lane when you freeze, then the freeze will be printed to lane 5 which is hidden.

3. Freezing will also lose any lane name not on the top lane. So if you have lanes 1-5, lane 1 will still be named but 2-5 will be blank when you unfreeze

My work around is:
1. DON'T DISABLE LANES BEFORE FREEZING
2. Make sure the lane you want to freeze is the top lane
3. Use take markers to identify recordings as the lane names will be erased

[schwa]

Improving this behavior, thanks for the report!

[plant-on]

Looks like this is fixed in REAPER 7.22: Okey dokey!

Thanks!!!