Logic X Out of tune bug

Well, the issue proves impossible to create again so far (I did some more MIDI recording in the same project - all fine.)

Also, for affected regions there is a fix, luckily: Export the track as a MIDI file and then re-import it.

It seems that the heart of this corruption is in the region, since I could copy over a faulty region to a new LP X project and it kept exhibiting the anomaly.

Well, the issue proves impossible to create again so far (I did some more MIDI recording in the same project - all fine.)

Also, for affected regions there is a fix, luckily: Export the track as a MIDI file and then re-import it.

It seems that the heart of this corruption is in the region, since I could copy over a faulty region to a new LP X project and it kept exhibiting the anomaly.

Well, the issue proves impossible to create again so far (I did some more MIDI recording in the same project - all fine.)

Also, for affected regions there is a fix, luckily: Export the track as a MIDI file and then re-import it.

It seems that the heart of this corruption is in the region, since I could copy over a faulty region to a new LP X project and it kept exhibiting the anomaly.

Test 2 Erik?

The forum was still being "temperamental" after whatever it was they fixed (or tried to?) during the outage? I only got timeout messages when trying to post these, so I copied the text and saved it in a document, so I could post it later, when the glitches had cleared up. Apparently they did post anyway, in spite of me being told they didn't.

First posts don't appear, then they all appear - I wonder "wuttuf" they are doing? 😮

This one took 11 seconds...

Yes.. strange things™ going on this weekend.. and still cannot edit an existing post on an iPad.. which is what they said they were trying to fix.

I also have this problem. I don't think it is a bug in a region, as I have re-recorded the bugged MIDI track, and upon playback the problem occurs (even if its recorded onto a different track). Reverting back to previous versions (10.01) doesn't fix it. God this is annoying!

I have another pitch problem symptoms now:

- I have Mackie Control + 2 Expanders and C4

- They are recognized correctly as a control surfaces

- They are not connected in Environment to seq input

... but when moving the volume faders except of the volume the fader changes also pitch of the External instrument (same for plugins). The same behaviour happens in the oposite direction, when I move pitchbend wheel on my master keyboards - the motorised faders on Mackies start to move (only on selected track)

Same here. B becomes D# on playback, every octave.

Created new region on same track, cut & paste notes, problem gone.

Fix that nonsense, Apple. Frikkin amateur hour.

Same here and it's always B to D#. I thought maybe it had to do with my using a novation controller with automap which doesn't seem to quite behave well with LX. Whatever it is I concur with commonhare- it's open mic night in Recording platformville

I´m making ethnic music and I have the same problem.

I´m using blue tones, some tones to -50 cent ot +50. All was working in LP9 without bugs. But in LPX when I close and open a project ist´detuned/out of tune.

I have to go to tuning, uncheck end recheck the costum scale to get it tuned again. I hope Apple will fix it soon!

I'm getting the same issue. B2 in the piano roll plays as D#2. The 'Piano Roll keyboard' plays the right note, but the B2 in the 'Piano Roll grid' sounds very D#2. The Event panel shows the correct note, but clicking on the event plays the wrong one.

Additionally, clicking on a MIDI region on another track doesnt show it in the piano roll.

Hi commonhare, dieboldcracy and terryat22, could you post which version of Logic Pro X this happened in? And will you please all report it to Apple feedback?

I'm hoping you're still on 10.0.4 or earlier, so that it might mean that this bug has been fixed in the enormous (the Logic app got about 25 % bigger) 10.0.5 update..

Even though it is now clear this is a bug, it is also weirdly specific (B becomes D#), and very occasional. I haven't encountered it again thus fair, though there are B's in all my projects... no idea if this "occasionality" makes it easier or harder for the devs to repair...

Sorry to say that mine is a fresh installation of 10.0.6. My project was created in this same version and not 9 as had been a suggest cause. I've tried but can't seem to track down the cause, so I'm also thinking bug. I'll report it to feeback now.

Too bad indeed, but thanks for reporting back. And about the "migration" issue: I never believed that, although I first encountered in a LP9 created project imported in X - but it was on a track that was created in LP X., and later I "caught" the bug in an LP X started project.

On the upside: it only happens very occassionaly, and it is generally easy to catch because of the dissonance (aug. 5th down) it creates in most situations. And it's easily fixed. Still, it is a very odd bug.