Piano Roll view jumps down 3 octaves after record

[geariatric]

I'm a new Logic user and not used to all the various ways you can customize its behaviors. I've done pretty well so far, via experimentation and searching this forum (thanks!), but this one has me stumped and I couldn't find anyone posting about the same thing...

If I'm recording MIDI with the Piano Roll pane open, with all my notes in view—which I like to do as I'm editing and just want to play in a new idea quickly—the view of said notes jumps down several octaves the moment I end the recording. The location stays the same time-wise, it's just jumping down vertically. So EVERY time I record something, I have to scroll back up to the notes to be able to edit them again. This behavior never happens when I'm editing and just playing the notes back. Only after recording.

For example, right now I'm recording a part where most of the notes are around the octave of C5. Every time I record in any new notes, the view stays in the same position in time, but jumps down to where C2 is centered in my view.

Is there a preference or setting that I'm missing that's causing this behavior?

[David Nahmani]

I tried to reproduce but wasn't able to when doing a simple MIDI recording: 

1. New empty project, create one software instrument track. 
2. Open Piano Roll, which displays the C2—C4 range.
3. Record notes in the C6—C7 range.
4. Stop recording.

The Piano Roll stays in the C6—C7 range and I can see the notes I just recorded. 

Is it possible that your workflow is different from what I just tested? Are you recording in take folders, or overlapping recordings? Are you recording data other than notes (Sustain pedal, automation...)? Anything else that you could find out that would help to reproduce the behavior you're experiencing?

[fisherking]

have you rebooted your mac? i've seen occasional quirky behaviors (like what you've described), usually fixed with a restart.

[geariatric]

Thanks for the quick replies!

Fisherking: I followed your advice and rebooted first just to eliminate the easiest fix, but no dice, still doing the same thing.

David: Just recording in regular midi notes, with no additional CC or anything. Not even pitchbends or sustain.
I went ahead and made a blank session like you did and tried to reproduce the behavior, but like your session, it behaves how it should.
I went back to the session in question and it still reliably misbehaves as described. Which I guess either points to my suspicion that I have some behavior selected that's causing this, or the session is corrupted somehow? (Does that even happen in Logic, where a session itself corrupts in some way that causes odd behavior in a specific way, but otherwise functions correctly?)

I've been looking at what options and preferences I have selected that might be different from a blank session, but to be honest, for me, it's like looking for a needle in a haystack. I'm still getting acclimated to the User preferences vs. project settings vs. window/pane options (and how they can behave independently based on linked/unlinked status etc.). So I was hoping this behavior might ring a bell for someone.

If it helps any, I'm on the bleeding edge here version-wise of everything: M1 MacBookAir, MacOS 12.4, Logic 10.7.4

[David Nahmani]

2 minutes ago, geariatric said:

I went back to the session in question and it still reliably misbehaves as described. Which I guess either points to my suspicion that I have some behavior selected that's causing this, or the session is corrupted somehow? (Does that even happen in Logic, where a session itself corrupts in some way that causes odd behavior in a specific way, but otherwise functions correctly?)

Yes, it's possible. Do you want to attach your project file here so that one of us can have a look? 

[geariatric]

I've tried a few other things to see what's going on. So far the only thing that's solved the problem is deleting all of the other MIDI files in the session. Even tried deleting them one at a time and different combos, but deleting them all is what did it—obviously not an acceptable workaround!
So, I'm guessing they must be linked in some way that's not obvious to me. (I tried looking at the region inspector, etc. to see if there was some sort of linking or grouping of regions I had accidentally enabled, but I didn't see anything. Granted, I don't know every place I could be looking.)
My guess was that even though I'm only selecting the one region, the piano roll view is somehow jumping down to display the content of some other region, even though it's not selected/visible. And maybe this is the case somehow, but I stripped the MIDI notes out of every other region in the session, and it still does the same thing. ¯\_(ツ)_/¯ 
AND, just to see if it was other MIDI regions in the session, or those particular regions, I deleted all of the other existing regions—problem solved—and created a fresh MIDI region on one of those tracks—and problem still solved. So whatever's happening is related to those specific MIDI regions.

I'm attaching a version of the session with everything stripped out (I think, haha) as I'm working on it for a client. But, as I said, even with MIDI notes and everything else being stripped from the session (regions still there), the behavior persists on my end.

LogicProHelp.logicx.zip

[fisherking]

you could try importing everything into a virgin logic project, see if the problem carries over... or not (hopefully not).

[geariatric]

Just imported it into a blank session (rhetorical: why am I forced to add a track of some type to even keep the session open, even though I know I won't be using it? 🙄) and the behavior persists. So it must be something I've done somewhere along to link these regions somehow, I just can't figure out for the life of me what I did.

[Atlas007]

Do you have anything (recorded or added or edited) before 1.1.1.1?