On 03.08.2006, at 07:26, remixvillain wrote: > ... i feel like > i am having to hack the enviroment to get what i need done. What you want is not a hack but actually what the environment is for. There are objects with dedicated functions and several universal objects. Working in the environment is not really programming although it feels like. The Logic environment is, simply spoken, a collection of objects which can be combined to achieve almost any MIDI routing you can think of. The less simple part is that you won't find a prefabricated patch exactly for your needs and for your controller. There are a lot of patches on the web but some of them are simply too old to work with newer Logic versions and some are too sophisticated. The latter means that the makers were ingenious but their work was screwed up by some Logic upgrade. You might download a couple of environments, they will at least give you an idea about the possibilities. The environment is obviously not in the current focus of the Logic developers and we don't know what will happen to that unique feature in the future. However, it is a mighty tool. > anyone care on shedding some light on multi record setup both live > and in the studio > for complex multitimbrality? Multitimbrality is not the problem, actually it is quite easy and Logic gives you more possibilities than you can handle on stage. But it is complicated to make a setup for both, live playing and recording. For live usage you can route your incoming messages through environment patches and then directly to the audio objects in Logic. That way you are completely independent from selected tracks and all plugins and channel parameters follow your commands. But these commands get not necessarily recorded because the automation does not know about your custom messages. It is possible but I doubt that is it worth the months of development. I would concentrate on a live setup with your controller and think about MIDI recording later. There are several ways to control Logic. You can use a supported hardware controller, a software emulation, Logic's Controller Assignments or any MIDI messages which reach the program. If you want to exclusively use your controller keyboard (which makes sense) the "custom" MIDI messages are probably the best way because the Controller Assignments of Logic are not manageable and they don't support third party plugins. Best start is to catch the incoming messages from your keyboard, transform them into something usable for a plugin and cable the result directly to one or more audio objects. You will only need transformers for that. Later you might add faders to change parameters and cable switchers to select certain routes and/or audio objects. That should give you enough to learn for the first week ;-) > I am seriously looking at getting NI Kore for this reason but i would > like to be able to do this in Logic. I don't know the Kore yet but according to the description it doesn't seem to be what you are looking for. > btw i also recently picked up the Pro 88 > seems like a great buy for the money and the feel is pretty good True. It is a pretty good device if you don't have to carry it on your own ;-} > still haven't tried the faders for Logic control becasue the > autoload they give you is pretty ridiculous and can't make sense of > it... Forget about the autoload and the presets they deliver, they are all useless. And I am not sure if you should program it in any way if you use Logic as your "sound machine". I personally prefer not to program hardware at all. I took Enigma and assigned almost all controllers of the 10th bank to the numbers which are written on the Keystation's case. That way I know always what I am doing because I make my patches myself and have just to look at the keyboard to know which knob is where. ___ Peter Ostry