first midi note at the beginning does not play

[heyciao (heyciao@inwind.it)]

Hi all, Ardour 6.9 in linux Debian unstable. If I use jack transport, the very first midi note at the beginning does not play. If I use internal, it does. Could you please help me to solve this? With Ardour 5 from kxstudio that was not happening.
But after upgrading to the newest version, it happens.

[x42 (Robin Gareus)]

My Ardour MIDI rant

I’ve commented about this in #8217. It can be avoided (“worked around”) by not mixing snapped and unsnapped eding (for example, creating Regions without snap mode enabled, and then later trimming regions with snap mode enabled). It can’t be fixed until we do the time representation changes that will be in 7.0. It is caused by tiny rounding errors. In the test case I used to track it down, for example, the region start was at beat 2.24192 and the note start was at 2.2398. This does not happen…

Losing the first note on a midi region

It is a known and understood issue that has been reported many times (search the forum and bug tracker) and is so far present in all versions of Ardour. In short: This is caused by rounding (music-time bar|beat to audio sample-clock time), and nudging the MIDI region a sample backwards can work around the issue. Ardour 7 will address this issue.

The surprising bit is that this didn’t happen in Ardour5. It is a math rounding problem, depend on sample-rate, BPM and region-postion, it may well be that you were lucky so far.

[heyciao (heyciao@inwind.it)]

Yes, I think those are similar.
I hope the issue is still the same so it will be hopefully solved in Ardour 7, but it occurs to me just at the very beginning of the time line, so at 00:00, anche just when in source (JACK) transport.

Being like that, I cannot move on the left the region.
So as workaround, I can move on the right by a measure and maybe everything go fine.

Is there anything in JACK settings that can be done?

I wait for 7.
many thanks!!!

[heyciao (heyciao@inwind.it)]

Update:
I’ve downloaded Ardour 7 nightly build.
The issue still remain, it is not solved yet.

Just to let know that maybe what is happening to me is something that has to do with jack configuration.

I wish to remark that the issue happen to me just when I use SOURCE transport, i.e. sync with Jack Transport.

If I use INTERNAL, everything is good.

Luciano

[paul (Paul Davis)]

Please provide substantially more detail, preferably via a bug report at tracker.ardour.org, with the session where this happens attached, and details on the sample rate and buffer size that you are using.