I like to have all my mixers configured like this:
Mixer 1: Audio channels
Mixer 2: Instrument channels
Mixer 3: FX Returns and Groups
But it seems I have to set this up for EVERY project I’m working on.
I have set up Workspaces with the mixers configured this way, but they are not recalled when switching projects. Am I expecting too much?
This has to be implemented and a key command to switch between configs.
I’m sure this will happen in a future update.
Thanks Bredo, but I’m very familiar with the process. It just doesn’t work!
Same problem here Steve. Plus I had to redo all my workspaces because of the new mixconsole, and after all that they don’t work. It is for this reason, and various graphic and UI issues that I’ve gone back to 6.5 and couldn’t be happier.
Denis
It sure is!
ah finally found a thread talking about my #1 ‘this workflow is utterly useless’ issue…
If you really want to get depressed, trying ‘faking’ it with macros…(ie using combinations of ‘hide’)
That doesn’t even work…you get jumbled results, nothing like the combinations…even worse you can’t assign key commands to the macros…
It’s a bit of a mess, and not ready for prime time.
There seems to be be a general misunderstanding of how people work in studios at steinberg.
The new mixer is just example.
Steinberg seems to think in general that it’s useful to have things stored with the project that should be saved generally:
I can imagine several situations (and experienced them) where saving audio and display setting (such as workspaces) globally makes sense. For instance when loading older projects after I bought a new display or soundcard. I can’t imagine a single situation where it could be useful to have them stored individually with every project.
So from my point of view the Mixconsole/Workspace situation is just a detail where a wrong concept is especially wrong. It should be changed generally anyway.
regards, Greque
Hi, Grecore
Absolutly agreeing with you on the VST connections : it’s a PITA to have them project dependent. Fortunately, there is the solution to save them in a template, but still… I’m glad that I don’t have the need to change them from my DAW to another system.
I would be more balanced, though, about the Workspaces, as they can be stored as ‘Global’, making them act as a possible kind of ‘Workspace template’. I use them often this way, by locking them until I pass the ones needed to the left in the ‘Organize workspaces’ window, unlocking them at this stage.
Cheers,
I have a myrriad of different scenarios for varying project types. Simple example, I might want to record one artist or two artists for which I may need 1 or 2 que sends resp.
Once recorded however, I no longer need the cues, so I might convert these to aux sends or something else. This would indeed be a PITA if e.g. the settings for VST connections were not Project based.
I’ve been asking for this since 7.0.0. Still not present in 7.0.3.
See my thread: Steinberg Forums
This can’t be a hard feature to implement, they already have the code written for it (as it saves to project file). Why not just import/export to an XML file or something? It’s absence is making things painful.
Couldn’t believe, that it’s still not in 7.0.3 !
Urgently needed !
Always have 3 mixers open.
Always need to load older Songs …
OK, first we’d need the song to store the mixer settings correctly !
Bump for this thread…
this needs to be in 7.0.4 badly.
Then this should be posted in the Issue Reports subforum instead, or it won’ t be tracked.
+1, though i like to have the option of both global and project-based workspaces. as someone suggested above, i will most often start by importing the global ones, then adjust them for a specific need of a project, eg. adjusting a workspace to display and arrange the GUIs of certain plugins that may only be inserted in that one project etc. the presets should just be able to include in them all the settings of the displayed mixers.