Piano roll timeline bar mismatch

#1

I did some searching and couldn’t find this, but hopefully this is a me issue and not a bug. I recorded some Midi and ended up needing to nudge the notes back to the beat (probably a separate issue). After nudging I quantized and in the edit view the notes all look aligned with my 1/8 time:

image

But if double click on the region and open the piano roll, the notes aren’t aligned to the grid:

image

Have I done something wrong here?

Thanks,

Derek

#2

Make sure the midi region starts on beat line on the timeline. The pianoroll panel/window takes the beginning of the region as its grid origin.

#3

This is probably fixed in current builds, I think.

#4

Thanks, I’ll try testing a current build!

#5

Current nightly (9.2-642-g6cc89c8470) seemed to address the alignment issue, but it seems to crash every other time I open the piano roll.

#6

Actually, no, it’s still off, I was just looking at the wrong track. I still see alignment in the main window:

image
image1335×243 5.37 KB

But misaligned in the piano roll:

image
image765×593 2.55 KB

I’m happy to gather any information that might help triage.

Thanks,

Derek

#7

Please put a small test session that demonstrates this somewhere I can download it from.

For the crash, please see Debugging Ardour | Ardour DAW … a backtrace would be appreciated.

#8

Here’s an example session of the misaligned MIDI info: https://paste.c-net.org/HallwaysEllis

As for the crash I’ve bisected it to commit 19fc0327cc44
All subsequent versions up to the most recent 35c0d29a8c71d80 crash if you double click on the MIDI region to open the piano roll window, close it and then double click the region again.

Here’s a crash backtrace : https://paste.c-net.org/WindyDelegate
Compiling warns about

/usr/include/glibmm-2.4/glibmm/containers.h:212:12: warning: binding dereferenced null pointer to reference has undefined behavior [-Wnull-dereference]
  212 |     return *static_cast<pointer>(nullptr); // boom!

so I’m guessing it could have something to do with pianoroll_window (nullptr) in gtk2_ardour/editing_context.cc

#9

Could you attach the whole session rather than just .ardour file? Thanks.

I can’t reproduce the crash as described at this point. When you say “open the pianoroll window” do you mean the separate, standlone window, or the bottom pane?

#10

That’ll have to be tomorrow then.
But you can just draw a couple of MIDI notes, quantize them to nearest quarter note and then double click on the region to see the the misalignment dchenbecker’s images are showing.

I mean double clicking on the MIDI region so that the separate piano roll window opens.

#11

What is happening here is that you trimmed the original region a bit later than its original condition; this moves the region start later in its underlying source file; when the pianoroll is opened, we’re showing the whole source file (plus the region boundaries).

This was done intentionally (since often being able to see the rest of the source file is valuable), but ti’s not clear that it’s the right thing to be doing.

#12

Here’s the entire session : https://paste.c-net.org/ConferGrades

#13

OK, I see what you mean. I trimmed and shifted the region because there was some sort of delay recording MIDI notes, so clearly I need to fix that. However, on the point of “is this the right thing to do”, the main problem I’m running into with this behavior is that because the piano roll grid isn’t aligned, I don’t know how to snap notes as I’m editing.