v3.21pre2

The folders are a problem, and that is when you drag the parent or a child track outside of its folder space. I think Cockos are on top of that situation. Several solutions are possible. It'll depend what the default should be, and what should be done with modifiers. When moving outside the folder area with your dragged/selected track(s) should the entire folder range be moved right along, as if you're automatically selecting the parent folder and all its children tracks, or, should the default be to let the user just drag stuff outside but have Reaper remind the user of the implications with a visual hint ? This could take the form of a simple red(instead of blue=moving with no possible problems) surrounding the entire folder area.

One solution that may work for the folder is a bus situation: Make the master send of each track user definable and put an option somewhere (global preset, but maybe also with the option to change per track/folder) if insertion into a folder changes this bus allocation or not. If set to change, behavior would remain as is, if not folders actually become organizational tools.

I love track folders as they are but the "Projects In Projects" system could also give us the addition of real item folders with a little adapting. :)

Plugin "new" folder not showing up during f5 refresh of plugins. Only shows up if total reaper restart here. Can anyone confirm this? Say adding a plugin during a session and hitting f5. (should bring up newly installed) folder. ~Rob.

hm. moving tracks from MCP. i liked the idea - then i noticed that this ALSO moved tracks in TCP. i'd love it if i missed something and there was a way to re-order tracks in MCP without them also moving in TCP.

right-click on the mixer, untick "auto-arrange mixer tracks"

i figured i'd missed the trick. very sick this morning and couldn't read the whole business of this thread. sorry to jump the gun, and thank you, evan