Half-Tempo Pattern with "Print to Clip" on a Launchpad Pro Mk3

[matheusvilano]

System Summary

• Linux (CachyOS, Arch-based)
• Bitwig Studio 5.3.13
• Novation Launchpad Pro Mk3 with latest firmware at the time of writing

Description

When programming a pattern on the Launchpad Pro, using "Print to Clip" does print to Bitwig, but it seems there is something wrong with the step size or something similar? I am assuming the problem is in here.

Steps to Reproduce

1. Open a new or existing Bitwig Studio project.
2. Connect an up-to-date Novation Launchpad Pro Mk3 with the official integration.
3. Hit the "Sequencer" button on the device.
4. Sequence a simple single-bar, 4-on-the-floor kick drum pattern. In other words: one note per beat, 4 beats total.
5. In Bitwig, select a clip slot (to set the destination for the MIDI messages).
6. Back on the Launchpad device, hit "Print to Clip" once to create a clip, then hit it again to print.

Results

• Expected: Pattern in Bitwig matches the pattern on the Launchpad perfectly (disregarding sync offsets). Both patterns have a kick drum sound for every beat.
• Actual: Pattern in Bitwig is "stretched" to be twice as long. It has a kick drum sound every other beat.

Reproducibility

100%. I can reliably reproduce this issue.

Workaround

Selecting the clip, then using the "Scale 50%" option fixes the discrepancy:

1. "Clip" menu.
2. "Content Scaling" section.
3. "Scale 50%" option.

Notes

• I'm not sure if having to hit "Print to Clip" twice is by design, but I always have to do that: once for creating a clip, then another time for actually printing to the clip.
• Though I found a decent workaround, this is really killing my workflow. I have to constantly stop performing to fix my printed clips.
• Let me know if there is any other info I can provide 😄

[matheusvilano]

Pinging @ericahrens for visibility and assistance! Also, thank you so much for your work on the Launchpad Pro Mk3 integration 😄

[matheusvilano]

I tried to repro this issue today on Windows, and to my surprise it's not reproducible on Windows. I haven't tried on macOS yet, but at least this is already good info. It seems we might be dealing with a platform-specific issue.