Posted
Feedback, manual page 51 calls the parameter "Automatic Sectioning" but I think it's now Keep Child Containers in A Row
Questions:
From the release notes: Option to skip loading last used global rack on startup -- how do I do that?
Also I think I'm confused about global racks in general, they seem to grow every time I add a new project and I have to prune them manually. I'd like to have a default global rack and have the ability switch them and it seems to do this at least according to the docs "Saving The Global Rack
The Global Rack is an ordinary fle that you can save and open at any time. That is,
you can create as many global racks you want and use them as needed.
With File >> Save you can save the Global Rack to disk. This state, including all settings, is restored automatically when Synfre is started next time. With File >> Save
As... you can save the Global Rack under a diferent flename. This is very useful if
you want to work with multiple diferent racks.
" but when I go to file save as.. it just saves my arrangement as per normal
Lastly, what's the difference between stacked and nested containers? I have express and not pro if that matters, but
it seems that stacking containers the bottom level container overrides higher level containers, and nested containers override higher level containers so I
Thanks in advance,
Fri, 2015-02-20 - 20:44 Permalink
Option to skip loading last used global rack on startup -- how do I do that?
There is an option in the Audio & Midi Setup. Playback >> Audio & Midi Setup >> Settings >> Checkbox "Load Last Used Rack on Startup".
As... you can save the Global Rack under a diferent flename. This is very useful if
you want to work with multiple diferent racks.
" but when I go to file save as.. it just saves my arrangement as per normal
The "Save As" command at the Audio & Midi setup window is meant, not the "Save As" command from the arrangement window.
Lastly, what's the difference between stacked and nested containers? I have express and not pro if that matters, but
it seems that stacking containers the bottom level container overrides higher level containers, and nested containers override higher level containers
The rule for containers at the same nesting level (stacked containers) actually is that containers with a later starting point override the containers with earlier starting points. Only for containers with the same starting point the rule is "bottom container overrides upper containers". In this case you can change the vertical order of the containers with the arrow keys, btw.
For nested containers the rule is as you have pointed out: Nested containers override higher level containers.