Phantom automation moves. Possible bug.

I had a very similar issue in a LP8 project last month, with no solution. Extremely annoying. If you're saying this is happening in LP9, I'm frustrated to hear they haven't fixed that bug.

Have you checked the 'automation' button on the top of the arrange window? it's quite clear LP is full of bugs which they have no intention of dealing with as i found out today (or at least dealing with it for free;] ) I had a case where couldn't deal with automation being overwritten and getting all confused as i couldn't get rid of it, but as i went into 'automation' it shows every automation applied to certain track. if you haven't checked that out yet maybe that's a way to do it.

Not a bug. Automation is generally rock solid.

When you see automation "fighting" against itself like that, 99 times out of 100 it's because of what rheuddog described -- you have a MIDI controller outputting a MIDI volume command that got recorded in a region.

Happens to me occasionally... one of my keyboard's sliders is programmed for CC#7. If I've left it at a position that's right on the edge of being detected as a new position, vibration from playing on the keyboard can cause it to move a miniscule amount and output a CC#7 value.

But OP had changed automation from "Read" to "Off" -- so what you suggest can't possibly be happening.

I'm having similar very strange automation issues (even when OFF) -- example is when I copy and paste a Midi region it generates a bunch of automation points??

I've also hard crashed LP9 when I had Automation set to "Read" (sent bug report to Apple). I'm not exactly sure what the problem is as I need to spend more time diagnosing the issues -- maybe this weekend. But my automation issues are specific to LP9, going back to LP8 no problems.

Maybe OSX 10.5.8 fixed it 😉

I'll do more testing this weekend to see if I can't narrow the problem down and/or find a way to work around it.

Rob

The OP himself said that it was a MIDI volume command coming from his footpedal that was causing the problem. And if he's got track automation running along with any of those errant pedal commands (and the track is in read/touch/latch) you're going to see that kind of fighting going on.

I'm having similar very strange automation issues (even when OFF) -- example is when I copy and paste a Midi region it generates a bunch of automation points??

Which are you talking about: MIDI data (like CC#7 data) that's in the region already? Or actual trac based automation data that comes from the source track and gets copied to the destination track cuz your automation prefs are set to 'always'?

Guess I mis-understood OP, to OFF means no read/touch/latch.

Copy and paste a midi region on the same track and it will insert bizarre automation data -- no idea where it comes from. The track has no automation data. I'll check my automation prefs tonight, but the track in quesiton has no automation data.

Rob.

If you're ever in doubt as to why a channel or instrument's fader is moving and you don't think you have automation data that's affecting it, assign that channel to a track. If the automation display is enabled you'll see the yellow line right away. If not but the fader is still mysteriously moving, hook up a key command for "Automation Event List..." Select the track and hit the command. If you see volume data in the list then you'll know there's a potential culprit.

I've experienced a similar problem with my FaderPort controller but only under odd circumstances.

If I accidentally unplugged my FaderPort and then plugged it back in, the Control Surfaces preferences that I had assigned it would get deleted and the MIDI messages would come through as note data and other really weird stuff depending on what track I had selected in the arrange window...

What I noticed was that when I just went in and re-did my Control Surfaces stuff for that controller it would reset and work perfectly.

Eventually I had to contact PreSonus and let them know what was happening. Turns out it was a problem with the driver, and the driver had to be updated to accomodate 8.0.2.

I can only imagine that this is still the case for many companies (including the ones who made your volume pedal) since Logic 9 came so suddenly, without even a 8.1 ever being released....Try contacting that company and seeing if there are any known issues with the driver for the device and Logic 9... might help, can't hurt.