Muzys: Saving assigned midicontrollers

Audio Plugin Hosts and other audio software applications discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

Hey

In Muzys you can assign midicontrollers to 99% of everything. For example, i turn a knob in vanguard, click options for that synth and choose OSC1 and then turn a knob on my midicontroller and ok. Now OSC1 responds to that hardware controller. But how the dwell do i save that? I really dont want to do that every time and for every synth i add.

Enlighten me please! :)
:hug:

Post

Hmmm - I don't know if there is a way to do what you're looking for.

I know that whatever controllers you assign are saved with the project.

But I don't think there is any way to save controller maps outside of a project.

I've only ever assigned controllers to parameters casually so I've never really needed anymore than what is already given.

Maybe another Muzys user has a solution - but I don't think it's possible. :?

Caleb
Happiness is the hidden behind the obvious.

Post

A pretty good workaround for this would be to set up a blank (i.e. no music data) file that has all your MIDI controllers, synths, mixer channel allocations, etc., pre-assigned, and then use this file as a starting-point template. So instead of starting up a new project with an empty file, one would start it up with this template file. Just make sure to do a Save As... the first time you save your project so you don't erase your template. I do this right now with output mixer channel allocations; I have a two-channel template, and another for my 8 channel, ASIO setup.

Post

lepwisk wrote:A pretty good workaround for this would be to set up a blank (i.e. no music data) file that has all your MIDI controllers, synths, mixer channel allocations, etc., pre-assigned, and then use this file as a starting-point template. So instead of starting up a new project with an empty file, one would start it up with this template file. Just make sure to do a Save As... the first time you save your project so you don't erase your template. I do this right now with output mixer channel allocations; I have a two-channel template, and another for my 8 channel, ASIO setup.
Good one. That's it.
Once you assign a controller to a parameter in a synth, that setting seems to stay in the project somehow whether that synth remains in the project or not.

I just experimented with PolyIblit and assigned controller 9 to Osc 1 fine tune, then dropped PolyIblit from the project, saved the file and closed Muzys.

Then I started up Muzys again, loaded up the project, loaded up PolyIblit, checked the controller allocation and Controller 9 was still assigned to Osc1 fine tune.

So setting up a template file is what you should be doing as it saves all the controller mapping whether the VSTi is there or not.

Thanks lepwisk.

Caleb
Happiness is the hidden behind the obvious.

Post

As far as I remember (not doing much automation these days), Muzys seems to remember "slot and controller" positions, rather than anything to do with what plugins you've actually got loaded. So, if you set up automation of the first synth rack entry's first parameter, I think whatever you plug in will have its first parameter automated.

What I don't remember is the more complex stuff. Put in two plugins with unequal numbers of parameters. Automate the first parameter on the second plug. Then swap the plugin positions. Is the first parameter on the second (was first) plugin now automated or has Muzys got "confused"?

Post

Oh - that doesn't sound too good or useful.
Hehehehe.

I can't be bothered testing that at the moment.

It's probably a good thing that I never needed to do this with Muzys. :hihi:

Caleb
Happiness is the hidden behind the obvious.

Post

pljones wrote:As far as I remember (not doing much automation these days), Muzys seems to remember "slot and controller" positions, rather than anything to do with what plugins you've actually got loaded. So, if you set up automation of the first synth rack entry's first parameter, I think whatever you plug in will have its first parameter automated.
I believe you're right here. The "slot and controller" function is what appears to keep the MIDI players communicating with the proper MIDI input and output port. Switching OMS profiles can muck up your MIDI players.

To me, this isn't really a big issue. I would just suggest keeping your favourite synths "permanently" allocated to particular synth rack slots. Of course, with effects this may prove a bit more difficult. But hey... it's just a workaround!

Post

Thanks all for your help!

I just bought a behringer bcr-2000 and was hoping that i could assign all controllers to my favourite synths. Its nice to see that even though vanguard only has a few CC's implented (eight i think), Muzys still can allow me to connect controllers to what is not supposed to be controlled! Tricky sentence :-o ;)

Hmm.. since its so easy to assign controllers im going to be very ok with it even if it didnt work the way i wanted :) Do you know if there is possible to assign a keyboard command for assigning controllers? That would be super!

Heh.. the more i work with muzys, the more i can see how Jo is a genious. Even the manual is good :D :love:
:hug:

Post Reply

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”