macros like in absynth and massive

this would make fm8 host automation a lot easier and cleaner to set up. i'm mainly asking it because ableton live (which i use) has a 128 vst parameter limit. that way i don't see the parameters i want to edit. but next to it, macros make the automation less cluttered.

cheers,
michel

 

I think morphing is why this isn't included as they are very similar.

 

nope, morphing is for morphing between sets of parameter values. has nothing to do with the automation of separate parameters.

 

is you want macros in FM8, just use KORE.

 

i appreciate your help, but 'just' use kore?

i would have to buy kore and that's 200 euros just to host-automate fm8. and besides, i want direct automation... not via another application.

 

well right, yeah it seems like a shitty solution, but.... !

I think if you had KORE, and you gave it a chance....

You're thinking that you want a direct implementation and that you would just be buying KORE _just_ for fm8. Obviously if you think that way you would feel like it was wasted money.

but, bare with me, I'm sure there are more effects and instruments you would like to macro-ize other than just FM8? with KORE you can. You can have macros that automate sets of plugins, and they're actually easier to bind than in Massive or Absynth as you can set KORE to group learn based on whatever knobs you move. So....... it depends on how flexible you are to bend with your original vision for fm8.

i would also like to point out that they probably considered macros for fm8 as it came out at a time when macros were being implemented for abysynth and massive. So, in all likelihood they decided against macros when fm8 was being built.... Why? because the sond produced by morphing is very similar to that of macros. Yes, they're not the same thing, I KNOW, trust me, but, you can work within the limitations of _either_ paradigm and produce very similar sonic results.

peace.

 

listen... i just want to automate one parameter. period. i've said that ableton has a bug and only the first 128 parameters are automatable. and the parameters i want are not in there. so that's why i asked for macros. but luckily this has been solved in live8, so i don't need the macros anymore. consider this thread closed.

i've tried kore already and i know exactly what it can do. before there was kore, i programmed custom max/msp patches and ran them as vsts inside of plogue bidule vst to do the stuff kore does. if i want that kind of stuff, i know exactly where to look.

frankly, i don't care what the guys at ni were thinking when they designed fm8. i just want my product to work like i want it. and if i miss something, i'll tell them. whatever they do with my feedback is up to them. but i can at least tell them.

"because the sond produced by morphing is very similar to lots of macros. Yes, they're not the same thing..."

nope, not the same thing at all. and i was not even referring to lots of macros. i was talking about one macro. one parameter. try to set that up with morphing. shall i walk you through it? make a patch. set the parameter you want to automate to minimum. copy the patch to another corner on the morphing square. set the parameter you want to automate to minimum. and now choose the morphing x or y from the dropdown menu in ableton. does that sound to you just as simple as directly choosing one parameter from the dropdown menu? and even if they sound the same... the way you get there is completely different.

it's nice to be extremely flexible and have infinite possibilities. but if you want to finish some music, some things have to be as simple as possible. so if i sound pissed of, it's because i ask for a simple solution and get a really complex one. again, i really appreciate you're trying to help, but you don't really seem to know what i want. or wanted.

 

> i just want to automate one parameter. period

Well, thats a _whole_ different story. It was completely unobvious to me that you wanted to use the macro system as a hack around the automation system. IE, you wanted to use Macros in a way that wasn't their intended use... abstracting groups of automation onto one controller.

> frankly, i don't care what the guys at ni were thinking when they designed fm8. i just want my product to work like i want it. and if i miss something, i'll tell them. whatever they do with my feedback is up to them. but i can at least tell them.

Yeah but this is Abletons fault, not NI.

cheerio.

PS

>but if you want to finish some music, some things have to be as simple as possible.

I wouldn't be using Bidule and Max/MSP if that was your goal :lol:

 

aha... that's what they intended with macros... damn, i've even learned something... thanx!

yeah, i just wanted to use them to work around the faulty automation system of live. and now i see why you say morphing gives the same result. if macros were specifically intended for multiple parameter use, you're completely right. so sorry if i sounded pissed off.

luckily, in live8, you can choose exactly parameters you want to show up as the first 128.
---

nope... if i want to get that complex, kore does it way more elegantly and is more stable. it's on my wishlist for sure.

 

Well perhaps "intended" is not the right word. "Implicit" use is maybe more correct. In the Massive and Absynth manuals, the macro section example is a multi parameter example, so from the get-go they are pushing the idea of using multiple parameters with the macro system. However, I guess one parameter is a suitable way to use it, too, if thats ones desire.

 

yeah, but if you wanted just to automate 1 parameter, you could do it directly from your host. if your host is able to do it, that is....

 

definitely should be done via the host where possible. Glad they fixed it in live 8... that seems like an odd thing to have working that way for 7 versions (years?)...

 

Yes, I know I'm being redundant by posting the definition, but I thought it is kind of interesting (and I'm somewhat bored)

http://www.thefreedictionary.com/Macro