MachFive 3 forgets my automation settings...

[FMiguelez]

Hello.

What I want to do is to find a way to make MF remember my automation assignments and settings at the Multi, or more usefully, at the CHANNEL (Part) level (not Program level).

This is the thing:
I successfully programmed all the programmable knobs and fades of each of the 5 sample oscillators, so I can tweak them from my Novation controller. This is my default-state channel, the way I want to see new channels open when created.
Works great EXCEPT for the fact that if I load a different oscillator (or any sound) from the main browser, then the settings are gone!
Same happens if I switch from one kind of sampler oscillator to another, say from Stretch to ICRAM.

How can I make my settings stay, even when I load different sounds? This is making too little sense. There must be something I'm missing, unless I'm expected to reprogram them every time I load something, which would be ridiculous...

I suppose that I'd need to find a way to store that automation information in the channels/Parts themselves, not in the programs.

Stylus RMX has a great feature that allows for this: you simply overwrite the default multi with everything the way you like it (including automation assignments), so next time you load a new instance, it opens with your preferred assignments. And when you load new sounds nothing changes.

The only workaround that I've found, but is totally unsatisfactory, is to load oscillators from the sidebar browser (instead of the main browser) on a previously set program (which is blank except for the automation settings).
But this doesn't work if I want to change the sampler oscillator from one to another.

This pseudo-works because I'm loading an oscillator - not a program. But I don't like that side browser and it's quite inconvenient, slow and clumsy. Not to mention that loading another program or changing the oscillator wipes my settings out.

Any ideas or suggestions?

[wvandyck]

Any chance you could post a couple of screen shot examples of the parameters you've assigned Novation control of?

Working in Stand Alone or as a plug-in in DP?

I can retrace your steps with my SL mkll25.

[FMiguelez]

Thanks!

I'll post them when I get back to the studio.

In the mean time, I can tell you MF is in a slave computer as a plugin in VE Pro.

It had been a while since I last used MF, and I just discovered a NASTY surprise:
It's actually worse than I thought because MF "learns" and stores the automation at the KEYGROUP level. So if I have 15 keygroups under the ICRAM Granular oscillator, I could make it learn all those parameters (all 10). But that only applies to the selected keygroup. That means I would have to make it learn the same parameters for every keygroup (10x15)...

PLASE tell me I am overseeing something!

All I want to do is being able to tweak any of those parameters regardless of keygroup or program. I want them to always be available after I did the MIDI-learn thing ONLY ONCE, globally.

I wonder if Macros would be a solution? Can those be stored at the Part Level?

[FMiguelez]

These are the screenshots.

If I MIDI-Learned all 10 parameters for the selected keygroup (I can only program them by selecting a keygroup), it only applies to that particular keygroup instead of being available globally for any keygroup (or program), just like in Stylus RMX.

What do you think?

[MIDI Life Crisis]

Hello.

What I want to do is to find a way to make MF remember my automation assignments...

I don't think I can offer any help, but you might not want to call it "MF" but rather "M5."

MF has such a vulgar alternate meaning... LOL!

[FMiguelez]

Hello.

What I want to do is to find a way to make MF remember my automation assignments...

I don't think I can offer any help, but you might not want to call it "MF" but rather "M5."

MF has such a vulgar alternate meaning... LOL!

I guess I hadn't seen it that way


The more I look into this the less likely it seems it will do what I want

It would basically render my (or anyone's) controller useless. But I suppose this could partially and easily be solved if MOTU added a Copy/Paste Automation Settings command, just like it's done in VSL's VI Pro and in Stylus RMX.

Or are we really expected to program these things one by one and countless times, doing the same thing over and over? That doesn't seem very logical...

Please, MOTU!

[wvandyck]

... MF "learns" and stores the automation at the KEYGROUP level. So if I have 15 keygroups under the ICRAM Granular oscillator, I could make it learn all those parameters (all 10). But that only applies to the selected keygroup. That means I would have to make it learn the same parameters for every keygroup (10x15)...

PLASE tell me I am overseeing something!

All I want to do is being able to tweak any of those parameters regardless of keygroup or program. I want them to always be available after I did the MIDI-learn thing ONLY ONCE, globally.

I wonder if Macros would be a solution? Can those be stored at the Part Level?

Shown here are 3 keygroups consisting of a sample and IRCAM.
The Novation can learn IRCAM Granular parameters for each key group as they are individually programmed using the same bank of knobs. Playing a given keygroup would make it's parameters active.

The same thing with simple analog oscillators with a different bank of knobs.


I understand what you want to accomplish but I don't think M5 is gonna work like RMX due to the M5 3's complex architecture: Part>Program>Layer>Keygroup>Oscillators.

After a while, the Novation the stopped controlling M5. I'll take a fresh look tomorrow.

[wvandyck]

Take 2:
Previous post screenshots were from the MacPro1,1 with 10.7.5.

Workout today is with a brand new clean install of 10.8.2 and all apps on an i5 MBP. This time I selected all of the samples before adding an IRCAM layer versus the previous approach of adding an IRCAM per sample to replicate what I understood to be your set up.

MIDI learn for the first 4 parameters: First test assigning the same SLmkll MIDI CC#'s (21 through 24) to each IRCAM layer (red arrows in screenshot below). Saved the program. Quit M5 3, reopened, loaded the program. Controllers intact! Second test as above but assigning separate CC#'s: 21-24 and 31-34. Controller assignments were intact upon reloading the program.

Here's a thread regarding remembering automation settings: http://www.motunation.com/forum/viewtop ... =5&t=39918

Go figure.

One thing is certain, the IRCAM granlular synthesis produces some really out of this world sounds. The samples used today were from Hollow Sun instruments. Twiddling the IRCAM parameters put me at 10050 Cielo Drive at the very moment... Really creeped my self out.

[wvandyck]

Pushing the envelope a bit, I loaded a "New Program" with no samples in 3 different parts, added an IRCAM layer with no sample and assigned different MIDI CC# to the IRCAM layer in each Part, then saved the Multi.

Automation assignments were intact when the Multi was reloaded! However, loading a different program to a Part would wipe out the IRCAM layer for that Part.

It would be very cool if "sounds" could be loaded into a new Layer within a Part much like a contextual selection of "Add FX, Add Even Processor" etc.

Looks like the best you can do is to create an empty (no samples) but loaded (with IRCAM layers and assigned CC#'s) Multi in which you drag and drop samples on to the layers in the various Parts...

This exploration is now concluded.