So I think I may have most of this figured out finally but have a few remaining questions. Any help is greatly appreciated! I have an X-Station and when i assign a certain knob to a parameter it works no problem so i am happy with that. also just like Emagic said it seems it puts those learn settings in preferences so they are always there and thats cool too. BUT how do you do this: say you load an audio instrument then you load a logic effect such as bitcrusher but 1 knob controls a parameter on the synth but you've assigned the bitcrusher a parameter earlier that uses that same knob when you move that one knob they both move! How can you constrain that learned assignment to the plug in window or switch it? any ideas? Thanks in advance

On 23.04.2005, at 20:49, kendrickhughes wrote: > also just like Emagic > said it seems it puts those learn settings in preferences so they are > always there and thats cool too. And you get "soft-takeover", which means your values do not change suddenly if the hardware fader is on a different position. That is cool either. But you cannot store your own settings. And if you execute "rebuild defaults" once - all of your settings are gone. Both is not cool. > BUT how do you do this: say you load > an audio instrument then you load a logic effect such as bitcrusher > but 1 knob controls a parameter on the synth but you've assigned the > bitcrusher a parameter earlier that uses that same knob when you move > that one knob they both move! How can you constrain that learned > assignment to the plug in window or switch it? any ideas? Unfortunately you cannot handle this yet, you need a supported control surface to let Logic know which plugin on which position in which channel strip you mean when you turn a knob. Controller Assignments were introduced to change settings of supported surfaces. Letting us assign our own commands is a nice and logical idea but at the moment it is only half-way implemented. We need at least storable user preferences and a way to bypass connected controllers. Peter Ostry

Peter Ostry <po@o...> wrote: > Unfortunately you cannot handle this yet, you need a supported control > surface to let Logic know which plugin on which position in which > channel strip you mean when you turn a knob. Controller Assignments > were introduced to change settings of supported surfaces. Letting us > assign our own commands is a nice and logical idea but at the moment it > is only half-way implemented. We need at least storable user > preferences and a way to bypass connected controllers. > > Peter Ostry Thanks peter I thought that was the way it was i appreciate both of your replies if I ever see you in need of help I will try to help you as well!

On 23.04.2005, at 23:23, Peter Ostry wrote: >> BUT how do you do this: say you load >> an audio instrument then you load a logic effect such as bitcrusher >> but 1 knob controls a parameter on the synth but you've assigned the >> bitcrusher a parameter earlier that uses that same knob when you move >> that one knob they both move! How can you constrain that learned >> assignment to the plug in window or switch it? any ideas? > > Unfortunately you cannot handle this yet, you need a supported control > surface to let Logic know which plugin on which position in which > channel strip you mean when you turn a knob. This is incorrect. When learning a plug-in parameter, it doesn't matter if the control surface is supported or not. Also unsupported control surfaces allow binding assignments to a certain plug-in's parameter. > Controller Assignments > were introduced to change settings of supported surfaces. Letting us > assign our own commands is a nice and logical idea but at the moment it > is only half-way implemented. Processing of Controller Assignments is exactly the same code, no matter if supported or unsupported control surface. Where you are right (there are differences) is: * only supported control surfaces can show feedback * only automatable track parameters and key commands key be learned for controller assignments * learning plug-in parameters only works in the "bound to plug-in ID" mode - not in the mode "parameter x or current insert" Regarding the track association, you have to know that Logic by default sets "Selected" track for assignments learned for the currently selected track. To learn an assignment for a certain track (e.g. track 3 in the fader bank) you first have to select another track. To switch a control between different meanings, you can set up zones and modes, using the Controller Assignments Editor. There were however several user interface bugs in version 7.0.x which are all fixed in version 7.1. Zones and Modes is the way controls (e.g. encoders) are switched in assignment for supported control surfaces. To validate this, just open the Controller Assignments Editor and operate some controls on a supported control surface. You will see how modes are switched. > We need at least storable user > preferences and a way to bypass connected controllers. ?? Beste Gruesse - best regards, Michael Haydn - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The above message is my private opinion. It is not an official Apple or Emagic message. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

>>> BUT how do you do this: say you load >>> an audio instrument then you load a logic effect such as bitcrusher >>> but 1 knob controls a parameter on the synth but you've assigned the >>> bitcrusher a parameter earlier that uses that same knob when you move >>> that one knob they both move! How can you constrain that learned >>> assignment to the plug in window or switch it? any ideas? >> >> On 23.04.2005, at 23:23, Peter Ostry wrote: >> Unfortunately you cannot handle this yet, you need a supported control >> surface to let Logic know which plugin on which position in which >> channel strip you mean when you turn a knob. > > On 30.04.2005, at 23:31, mhaydn wrote: > This is incorrect. When learning a plug-in parameter, it doesn't matter > if the control surface is supported or not. Also unsupported control > surfaces allow binding assignments to a certain plug-in's parameter. If you use the learn mode with a supported surface, ok. His problem was the he wanted to assign the same knob to different parameters with "some" controller. That is not what you usually do with a supported device unless you definitely want it. Normally you have to select a specific plugin and only that one reacts. That is not possible with learn mode and an unsupported surface, right? > To switch a control between different meanings, you can set up zones > and modes, using the Controller Assignments Editor. Sorry, I cannot recommed that because at the next "rebuild defaults" all your settings are gone. >> We need at least storable user >> preferences and a way to bypass connected controllers. > > ?? I guess that was not clear, I try again: We need to store our own settings like we can do with plugins and channel strip settings - I cannot spend a couple of hours to do a sophisticated setup i.e. for a Keystation Pro if I am always in danger to lose that with a single and sometimes necessary "rebuild defaults". Second, bypassing a supported controller is a must. Think about devices like the Korg KONTROL series. Those are instruments and controllers simultaneousely. How is that handled in Logic 7.1? Does it grab the device and you lose the velocity sensitive pads, joystick, programmable "scenes" and so on? Then everybody who bought such a thing will disable it as a surface. I have a microKONTROL and I love to play percussion on the pads. Will that still possible when it acts like a supported Logic controller? ___ Peter Ostry

I am fellow XStation / Logic User. I am trying to fathom out if it possible to assign multiply controllers from the Xstation to parameters of a virtual synth. e.g the EXS24 in the Controller assignment Setup window. I want to use it as an synth editor - Something the XStation is ideally suited to. I have just upgraded my Logic to 7.1. I realise the XStation is not yet supported. But is there any way of using it in the way I want. I tried assigning one of the supported control surfaces and then seeing if it would learn from the XStation - But the Logic completely hung. Anyone any ideas would greatly appreciated - It may simply be not yet possible. Regards Richard Pearce

--- In logic-users@yahoogroups.com, soupsounds <richard@p...> wrote: > I have just upgraded my Logic to 7.1. > I realise the XStation is not yet supported. You may find LC Xmu useful - see my signature. There's a dedicated input module allowing the Remote 25 (and XStation) rotaries to be used as LC vpots - not in the demo (which will still work for you on other controls), but available to purchasers. I think there was a post from Michael Haydn recently describing the use of Controller Assignments for plugins/synths - try searching for his posts at gmane - see http://search.gmane.org/?group=gmane.comp.audio.emagic.logic.users John Pitcairn -------------------------------------------------------------------------- LC Xmu Logic Control emulation, LC Xview software LC/MC display, Logic environments & stuff: http://www.opuslocus.com --------------------------------------------------------------------------

--- In logic-users@yahoogroups.com, Peter Ostry <po@o...> wrote: > >>> BUT how do you do this: say you load > >>> an audio instrument then you load a logic effect such as bitcrusher > >>> but 1 knob controls a parameter on the synth but you've assigned the > >>> bitcrusher a parameter earlier that uses that same knob when you move > >>> that one knob they both move! How can you constrain that learned > >>> assignment to the plug in window or switch it? any ideas? > >> > >> On 23.04.2005, at 23:23, Peter Ostry wrote: > >> Unfortunately you cannot handle this yet, you need a supported control > >> surface to let Logic know which plugin on which position in which > >> channel strip you mean when you turn a knob. > > > > On 30.04.2005, at 23:31, mhaydn wrote: > > This is incorrect. When learning a plug-in parameter, it doesn't matter > > if the control surface is supported or not. Also unsupported control > > surfaces allow binding assignments to a certain plug-in's parameter. > > If you use the learn mode with a supported surface, ok. His problem was > the he wanted to assign the same knob to different parameters with > "some" controller. That is not what you usually do with a supported > device unless you definitely want it. Normally you have to select a > specific plugin and only that one reacts. That is not possible with > learn mode and an unsupported surface, right? > > > > To switch a control between different meanings, you can set up zones > > and modes, using the Controller Assignments Editor. > > Sorry, I cannot recommed that because at the next "rebuild defaults" > all your settings are gone. > > > >> We need at least storable user > >> preferences and a way to bypass connected controllers. > > > > ?? > > I guess that was not clear, I try again: > > We need to store our own settings like we can do with plugins and > channel strip settings - I cannot spend a couple of hours to do a > sophisticated setup i.e. for a Keystation Pro if I am always in danger > to lose that with a single and sometimes necessary "rebuild defaults". > > Second, bypassing a supported controller is a must. Think about devices > like the Korg KONTROL series. Those are instruments and controllers > simultaneousely. How is that handled in Logic 7.1? Does it grab the > device and you lose the velocity sensitive pads, joystick, programmable > "scenes" and so on? Then everybody who bought such a thing will disable > it as a surface. I have a microKONTROL and I love to play percussion on > the pads. Will that still possible when it acts like a supported Logic > controller? > > ___ > Peter Ostry Hey Haydn or anyone else care to reply to this I completely agree with Peter and he nailed it in the head!