I understand exactly what you’re trying to achieve, and I’d like to explain why Playbeat behaves differently from a traditional MIDI drum sequencer.
In a conventional drum machine, each sound is assigned to a fixed MIDI note. For example, C1 triggers a kick, D1 triggers a snare, and so on. This makes it straightforward to export a MIDI pattern, edit it in your DAW, and send it back to the instrument.
Playbeat works differently, mainly because of its real-time Pitch engine.
In Playbeat, all eight sequencers independently have access to the entire MIDI pitch range (C-2 to G8). No sequencer is restricted to a particular note, and no sample is permanently assigned to a specific MIDI pitch.
This is what allows each sequencer to generate and manipulate pitch variations dynamically through the Pitch tab.
Here’s a practical example of the problem this creates:
Imagine you have two sequencers running simultaneously:
-
Sequencer 1 plays a kick sample at MIDI note C3.
-
Sequencer 2 plays a snare sample, also at MIDI note C3.
Within Playbeat, this works perfectly because each sequencer has its own sample and independently processes its pitch.
However, if you export these events as MIDI and send them back into Playbeat, both events are represented by exactly the same note: C3.
How would Playbeat know that one C3 should trigger the kick while the other should trigger the snare?
Now imagine adding real-time pitch variations to both sequencers, with notes changing across the entire keyboard range. The problem becomes even more complex, since the same MIDI notes can represent different sounds and pitch values across multiple sequencers simultaneously.
We could theoretically assign one fixed MIDI note to each sequencer, as conventional drum machines do, but that would introduce another problem: those notes would now have to serve two different purposes — identifying which sample to trigger and representing the pitch variations generated by Playbeat’s Pitch engine.
With Playbeat’s current architecture, these functions cannot be represented independently through the same MIDI note mapping.
This is precisely why we developed Playbeat’s alternative MIDI triggering system through the triggering keyboard and remix keys.
Rather than using MIDI notes to reproduce every individual sample event, Playbeat allows you to trigger entire patterns, individual sequencers, combinations of sequencers, and remixes using dedicated MIDI keys.
For example, in Cubase you can arrange these trigger notes on a MIDI track, decide exactly when patterns or individual sequencers should play, switch between variations, and adjust your project’s tempo while Playbeat continues to generate the original sounds and pitch variations internally.
This preserves the full functionality of the Pitch engine without creating conflicts between MIDI notes and sample assignments.
The exported MIDI data serves a different purpose: it captures the note information generated by Playbeat’s sequencers and Pitch engine, allowing you to use those sequences with external instruments and sound sources.
It’s important to clarify that Playbeat itself is designed to be the main editor for your patterns, rather than relying on your DAW’s MIDI editor to modify individual notes.
All editing, including individual steps, rhythms, pitch variations, and other sequencer parameters, can be done directly within Playbeat, where you have full access to its sequencing and sound manipulation features. Once you’ve made your adjustments, you can simply save the updated pattern to a Remix key and trigger it from your DAW using a single MIDI note. You can create multiple variations this way, assigning each one to a different Remix key and recalling them from your DAW whenever needed, without requiring you to export them to audio. All remix variations are saved along with your preset too, so you do not need to shuffle through different presets to trigger pattern variations.
We could certainly explore implementing a more traditional MIDI export and triggering option, where each sequencer is assigned to a fixed MIDI note. However, this would come with a significant trade-off, Playbeat’s real-time pitch-shifting engine, one of its most unique features, would become largely redundant in that mode. That said, we’re always open to improving Playbeat based on user feedback, and if more users express interest in a traditional MIDI workflow, we’d certainly consider implementing it as an alternative option.
Hope this helps!