You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Half-Tempo Pattern with "Print to Clip" on a Launchpad Pro Mk3 #113
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
Open a new or existing Bitwig Studio project.
Connect an up-to-date Novation Launchpad Pro Mk3 with the official integration.
Hit the "Sequencer" button on the device.
Sequence a simple single-bar, 4-on-the-floor kick drum pattern. In other words: one note per beat, 4 beats total.
In Bitwig, select a clip slot (to set the destination for the MIDI messages).
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:
"Clip" menu.
"Content Scaling" section.
"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 😄
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.
Activity
matheusvilano commentedon Feb 17, 2026
Pinging @ericahrens for visibility and assistance! Also, thank you so much for your work on the Launchpad Pro Mk3 integration 😄
matheusvilano commentedon Feb 18, 2026
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.