distressor

Any news on this? There's 10.3.2 now...

Did the new Logic 10.3 fixed this annoying behaviour? fingers crossed...

I would recommend updating to Mavericks. I run it smoothly on my MacPro with LP9 and LPX. I was running snow leopard until 2 years ago. I did a clean install and almost all of my Apps still work. Apple is constantly dumbing down their OS and the newer versions seem to have more bugs than the older versions. At least on my machine. SnowLeopard was much better than Mavericks but it would not run LPX. That was the only reason to update. Now i'm still using LP9 most of the time because LPX is so damn annoying. It has some great features but Apple screwed with the workflow again and lot's of stuff that make me work fast don't seem to function anymore. I see this with lots of software recently. It's sad times for workflow fanatics. Anyway... You can get a bootable USB sticks with Mavericks or any other OS on ebay for around 15$. There's no need to get the latest and greatest dumbed down OS from the App store. Cheers

Hi Jordi, thanks for the tip. That is extremely helpful!

The "External Instrument" plugin "lost" a midi port. I have 3 amt8 connected to my Mac Pro (proper one, no trashcan) that show up in logic as midi port 1 to 24. Somehow port six is missing in the "External Instrument" plugin. The port shows up in the audio/midi setup as well as in logics midi environment. I can select it if i create a midi instrument in the environment and it also shows up as an input in the physical input object. Sadly the "External Instrument" plugin doesn't care about the environment objects anymore and now lost a port. I tried resetting the midi drivers but that didn't help. I have no idea how to fix this. Has anybody had the same problem? Cheers

I don't think you can load Logics stock plugins anywhere else but in Logic. Any 3rd party plugin will be in library/audio/plug-ins/... Either in the system or user library. Cheers

I'll do the same. I found a dirty way around this annoying bug. I programmed a macro that saves a zoom, enables automation and then recalls that zoom we just saved. All in one keystoke. Sadly i have to wait with the recall until Logic has finished it useless "switching to automation" animation. So i see tacks expanding but as soon as the animation has finished all track jump back to the size they were before enabling automation. I use a software called controllermate for this. Maybe there is some app that hijacks the keyboard even better than controllermate does? Cheers

Hi, thanks a lot for the input. Eric this doesn't seem to work. I zoomed in with the global zoom slider in the upper right until i had the same zoom setting as with automation enabled. I then scaled every track to -21 so they are small again. I then locked the screenset. Now when i toggle automation on and off nothing would expand. So far so good. Now i tried the "toggle individual track zoom" shortcut to see my automation curves. The shortcut is simply key 1 as i use this all the time. Sadly as soon as i use the individual track zoom shortcut Logic resets the individual zoom factor to 0 and we are back to the problem. This is really frustrating .

Is there a way to prevent Logic from changing the track size while enabling automation? I usually have a small track size and a shortcut for expanding and collapsing tracks on demand. This is extremely helpful when dealing with lots of tracks. You can focus on a few tracks this way. In Logic 9 when enabling automation it would only show automation data on those tracks that are expanded and leave all other. The zoom would not change at all. Now it zooms all tracks and i have to scroll and search for the track that i want to edit. This is really annoying and made me thing about downgrading to Logic 9 again. Did someone found a way around this stupid behaviour? Cheers

Hi, Does anyone here have a contact to the Apple Logic department? My Company has build a dedicated control surface for logic and we would like to program a dedicated Control Surface Plugin for it so we can make it commercially available. It really speeds up the workflow and gives almost 100% hands on control. I have contacted the Apple developer support but they have no clue about anything Logic. Cheers, Phil

Hi great tip with that capture object. I used midi monitor so far. i recorded a bunch of messages. some are very similar and some are very different. I'll look for one byte that i can use like in your setup. So far my setup doesn't work. There is nothing coming out the ctlout but i'll figure it out at some point. P.

I have around 20 sysex messages that i need to process. They are all quite different and pretty long. I'm still decoding... The midi implementation is different from the actual messages i get from the unit. I haven't found out why yet. What does the loadbang and midiinfo in your patch do? The midiout i have doesn't have an output to connect it to ctlout. Is that a version difference? P.

I found the midi in and outputs they just look different here. I'll watch some max basics tutorials. I think i need that to completely follow you

http://imageshack.us/a/img43/2992/screenshot20130428at111.png

Hi, thanks for the patch. I have max 5 and tried to program exactly the same thing but how do you get that midi input and midi output menu? How do i get that unpack with multi output? I'm a noob when it comes to max.