Fat Tony

Hey all, this worked perfectly for me too on OS 10.13.2. Don't skip the csrutil bit (like I tried to), that bit's important The Alphatrack lives on!

Just had the same issue opening an old, old project in Logic 10.3.1 - clicking the link button revealed the missing notes. Thanks!

I know this is a super-old thread but it's one of the top hits when you look up "Delete All Flex Markers", so I thought I'd post the answer. I was trying to flex a bunch of grouped and phase-locked stems but came across the problem that Logic places a load of flex markers for you when you first turn Flex on. So if you're trying to tighten the whole group a bar at a time everything following your manual flex stays locked where it is - unhelpful in this situation. Reset flex edits command doesn't delete them, just resets their position. Solution is to get the Eraser tool and drag it over all transients, erases them all in one sweep. Make sure to do it on the region, not the region header, otherwise will delete the whole region. Hope this saves y'all some time!

Hallelujah! Since the issue only affected MIDI input, I went to Clicks and Ports in the Environment and deleted the Sequencer Input object. I then recreated it and wired it back up to the Input View. When I returned to the Arrange area it showed that my track was transposed by -90! Set that back to 0 and order has been restored to the universe. Who says you'll never need the Environment again in Logic X..! Many thanks for the feedback David, I appreciated the moral support. Stick with it guys, X's gonna be awesome once we've passed through the version 0 twilight zone..

Nothing funky, standard midi keyboard. It is a doozy isn't it! I'm wondering if it might be something to do with the new MIDI transform slots but there's not much I can do practically about that. Tried trashing the plist, it seems to be song-based. Had to go back several versions before I found a song version that didn't have the error, so it's kind of pernicious, can creep in there without you realising! Will post if I find a fix, thanks for your reply

Came across an 'interesting' MIDI input bug last night. Still haven't found a solution. At some point during the session the MIDI input has gone awry. All audio plays back normally, and preexisting MIDI or MIDI that is drawn in plays back perfectly. When you play MIDI in live from a keyboard, here's what happens - the MIDI monitor shows the note correctly, but internally it's played back 3 octaves lower and also just the same octave repeating over and over! Crazy. Once the affected project is opened, if I close that then start a new session the bug is carried over to the new song, requires a restart of Logic... Anyone else experienced this?