Add support for sending/receiving MIDI Song Position Pointer (SPP) and/or MIDI Timecodes (MTC)

What is the problem?

There is no way to sync Trackers/Plays in specific time.

What should this feature achieve?

By adding support for (ideally both sending and receiving) SPP and/or MTC, it would make it a lot easier to have Polyend devices precision sync with each other, 3rd party gear and DAWs.

I personally think SPP is more important than MTC.

Are there any workarounds?

Nope.

Any links to related discussions?

This topic was my inspiration for this wish.

SPP mentioned here and here.

This question about syncing with Ableton Live mentions MTC.

This wish about pattern sync via Program Change messages is another approach to keeping various devices in sync, which follows the path Elektron has gone with their Digi/takt line of devices.

Any references to other products?

The Octatrack supports SPP, according to its manual.

Bumping … been trying to hash this one out in Bitwig for quite some time. No answers with the release of 6, seems like SPP is still the answer from the Tracker’s side.

Workaround has always been start from the beginning. :laughing:

My workaround to get my Polyend devices and Bitwig play together, is to use this Bitwig controller script that I made. It makes Bitwig listen to PC messages and launch clips based on it. Then I have a Bitwig clip for each pattern on my Play/Tracker that I launch by sending a corresponding PC message from the device.

This is genius … thank you!!!

Gonna tinker around with this, wondering if a similar approach can be applied for cue points.

Remember that Bitwig clips can be set to launch immediately or when the currently playing clip is completing its iteration. Which gives you 2 options that have their pros and cons:

A) Set clips to launch immediately and send a PC message in the first step in the corresponding pattern on your device. Pro: Patterns refer directly to the matching clip. Con: If the PC message is a little late (it’s MIDI after all) and something important happens in the start of the clip, the clip start events may not play out.

B) Set clips to launch on next iteration and send a PC message during or near the end of a pattern that matches the next clip to launch. Pro: You don’t risk losing early clip events. Con: Patterns don’t refer to their direct clip counterpart and you can’t loop a pattern with it’s clip looping as well, as the pattern will trigger the next clip.

It might take some time to wrap your head around. It at least took me some time to figure it all out :slight_smile: