Page 1 of 1

some preset manager problem

Posted: Sun Feb 17, 2013 1:38 am
by tester
I'm trying to isolate the issue, but either I'm blind or tired.

What I'd like to achieve is. Saving/loading the whole program - uses all 3 units. Saving 1 unit stores only data about "1 general unit". Now - "loading 1 unit" should work in the same way on all 3 units - load "1 general unit" to active window. For some reason - loading that 1 unit works only for first one, on others - loading is ignored.

On technical side. When a whole program is used, then all presets have their "prefix" (unit related). When 1 unit is in use, then prefix is removed, but storing feature is disabled for all other units except the active one. Or I missed some properties of the preset primitive?

Re: some preset manager problem

Posted: Wed Feb 20, 2013 9:37 pm
by tester
This one is solved.

You can save a whole program, and load the whole program or you can save only one unit and load that unit anywhere else. Whole programs and individual units don't interfere with each other (names are changed for unit/program exchange). Let me know if I missed something.

//edit:
In "normal mode" - Reaper seems to work fine, despite the fact that the preset name is changed for loading/saving of one individual unit. Haven't tested it yet in "automation mode", but I guess that should work too, it will probably have a gap in playback (it's only a guess), like reset to default or last setting.