PB4.0.3 very unstable in Logic Pro 11.1.2 and other questions #playbeat4

Hi I upgraded to PB4 couple of days ago and I started reading and using it in my DAW Logic Pro.

Playbeat 4.0.3 and Logic Pro 11.1.2

In PB 3, I was able to set up multi-output and export MIDI files for each track into my DAW, but since only the kick sound played on all tracks, it was practically unusable. As a result, I have always relied on exporting the “All Tracks” MIDI file and then using the “Track In Place” function to convert it into audio.

Now, in PB 4, when I export the “All Tracks” MIDI file and turn off PB4 Sync, clicking the play button in Logic Pro does not play the MIDI file at all. The reason I turn off the sync button is to prevent Playbeat from duplicating the sound playback. (This is also a common practice I follow with several other drum machine plugins I own.)

However, turning on the sync button does not fix the issue either. In fact, when the sync button is enabled, the Sounds, Sequence, Remix sections at the bottom react unpredictably to the MIDI file, completely disrupting the patterns I have set. I attempted to stop them from responding to exported MIDI notes by clicking “Hold” in the Sounds, Sequence, Remix sections, but this did not seem to work properly either.

This issue occurs not only with the “All Tracks” MIDI file but also with individually exported MIDI track files.

At first, I thought I might be misunderstanding something, so I checked the manual again, but I couldn’t find any helpful information. Restarting Logic Pro and trying again sometimes makes it work as expected, but soon after, it behaves unpredictably again.

Additionally, after restarting Logic Pro, if I load a user preset where I modified the Knock 01 expansion and changed the rate of two tracks to 1/8, they randomly switch to 1/16 during playback. After some time, they might revert back to 1/8, as originally set. Also, I have experienced situations where the Track Lock button gets disabled on its own or where the Swing value is randomly changed to 70%, yet the actual sound remains unaffected and plays with the original settings.

Exporting MIDI files is essential for introducing variations in patterns over different sections, but currently, this functionality is practically unusable, making it very inconvenient. If the Bank (snapshot) function from version 3 were still available, it would at least allow for some flexibility in applying variations through audio exports, but unfortunately, it seems to have been removed.

Through these repeated issues, I have concluded that PB4 is very unstable in my Logic Pro setup. I sincerely hope a quick update will improve stability and usability.

Additionally, I have a question regarding the manual. Normally, drum machine virtual instruments are loaded through the Instruments panel. I also used PB3 in this way. However, in the PB4 manual, it mentions MIDI Routing and suggests loading PB4 in the MIDI FX panel while loading another instrument in the Instruments panel. When and how exactly should this method be used?

These also happen in standalone mode as well. In stand alone it even does not play any sound while it is play if I choose my own preset which is modified from Knock expansion.

I really can not understand now.

It would be incredibly helpful if you could upload detailed guides on your YouTube channel explaining how to export and use MIDI files in different major DAWs, as well as how to use PB4 as a MIDI FX plugin.

Hi @sourcreembeat ,

For use with Logic Pro, Playbeat 4 includes a complimentary MIDI FX version that can be loaded into a track’s MIDI FX slot. This is designed to send MIDI from Playbeat to your other plugin(s) loaded in the same track, not the other way around.

Feeding MIDI data into Playbeat won’t work, but there’s a better solution. You can trigger any sequencer -or the full mix- using the bottom keyboard section in the ‘Sequencers’ area, either from your MIDI keyboard or by placing a MIDI note in your track.

(In this case, ensure that keyboard triggering is enabled instead of automatic mode. You can do this using the two buttons at the top left of the menu—one is a play button, and the other is a keyboard button.)

Are you looking to control another app using MIDI from Playbeat, or looking to arrange patterns and variations in your DAW timeline?

To summarize, what I want to do is export and arrange MIDI patterns and variations in my DAW timeline.

Structuring beats with pattern variations in sections like Verse, Chorus, and Bridge is crucial to avoid monotony, and audio export alone is far too restrictive for this. Multi-output track arrangement and exporting an “All Tracks MIDI” file to edit MIDI notes along the timeline is an essential feature. This is a common function in other virtual drum machines I own, and I used it the same way in Playbeat 3.

However, in Playbeat 4, this function does not work at all. Individual track MIDI export also does not function properly.

Additionally, audio export is also problematic. When exporting either “All Tracks” or individual tracks and dragging them into the timeline, the files do not snap correctly to the grid, despite the DAW’s snap function being enabled. This makes proper usage impossible.

To verify if this issue was caused by modifying presets or changing samples, I tested it using a paid expansion pack, but the same problems persisted. Furthermore, when I close and reopen my DAW, any track rates I adjusted (e.g., 1/4, 1/8, etc.) revert to 1/16, and some tracks even change to different samples.

In short, this is a complete disaster. The top priority should be restoring basic functionality. I will wait for a new update.

Finally, to reiterate, what I want to achieve is export and arrange MIDI patterns and variations in my DAW timeline, with Playbeat 4 playing the drums according to my edited MIDI files.

Thanks for the explanation! First, Playbeat’s MIDI output is not designed to be fed back into Playbeat. Instead, you can arrange your patterns, remixes and track arrangement using the bottom keys in the ‘Sequencers’ section.

For instance, pressing C2 (or a C2 midi note in the midi clip) will trigger the full mix, but you can also trigger individual sequencers. (C#2 being the Kick and so on…)

For this, please ensure that the triggering mode is enabled, which can be found by clicking the small piano icon at the top left corner of the UI.

About exporting audio, are you dragging from the ‘All Stems’ button into an audio track? This should produce perfectly cut loops of what the sequencer is playing as it renders in real-time.

If not, may I please ask that you share with us a full Stems export as an audio file and the preset name so we can check?

So, does this mean that Playbeat 4 is designed for sequencing using a MIDI controller rather than MIDI export for editing the performance patterns? Is it similar to how ChordJam triggers full chords when a single MIDI note is played?

Then, what is the purpose of MIDI export in Playbeat 4? Is it intended to use the exported MIDI notes with other drum machines or the DAW’s built-in drum sequencing, along with Playbeat 4’s sample sounds?

All triggering in Playbeat 4 can be done from the bottom keyboard. You can trigger these keys using a MIDI keyborad / controller or MIDI notes in the Playbeat track, just like any virtual instrument.

From this section, you can trigger single sounds (one shots), the full mix, individual sequencers 1-8, as well as custom or auto-generated variations (remixes).

The MIDI output is designed to capture what the pitch tab (if enabled) is generating in real time, this real-time pitch-shifting engine is one of Playbeat’s most unique features. It’s not intended to be fed back into Playbeat, as the triggering options mentioned above offer much more flexibility.

Instead, it allows you to use the MIDI from the pitch tab with other modules and to integrate it with other plugins, just as you would when using Playbeat’s MIDI to control other plugins in real-time.

I fully understand that Playbeat 4 is designed for sequencing primarily through its internal keyboard section or via a MIDI controller.

I have tested this approach, but I found it to be overly cumbersome and inconvenient. These days, even melody and chord generators tend to offer direct MIDI export rather than relying on such an indirect workflow.

While this approach is undoubtedly beneficial for users who focus on live performance or finger drumming, it feels extremely limiting (and, in my case, nearly useless) for those like me who prefer editing MIDI notes to refine and modify drum patterns. While I recognize the uniqueness of this design choice, it’s difficult to support an approach that completely disregards a widely used workflow among producers.

Additionally, the 3 expansion packs I purchased separately contains a wealth of high-quality MIDI patterns. However, the fact that they can only be effectively edited within Playbeat 4—or through cumbersome workarounds—feels like a significant drawback. If I have to go through the tedious process of manually exporting MIDI as audio each time I want to make adjustments, it defeats the very purpose of using a sequencing plugin. Furthermore, this contradicts the inclusion of MIDI export functionality—if sequencing is intended to be done via the keyboard, under what circumstances is MIDI export actually meant to be used?

For me, plugins are meant to enhance workflow efficiency and convenience. Unfortunately, Playbeat 4 feels like a disappointing upgrade because it removes features I appreciated in version 3 while prioritizing uniqueness over practicality. This disappointment is further compounded by the various issues I outlined earlier. I believe Audiomodern could have mitigated much of this frustration by providing more in-depth video tutorials to properly explain these changes to users.

I already understand that I won’t be able to work the way I prefer, so at the very least, I just hope the stability issues and bugs get fixed.

With this approach, you can trigger any of the eight sequencers, spanning from C-2 to G8, using a single key or MIDI note, something that most drum machines without a pitch shifting module can’t achieve.

This works similarly to triggering an arpeggiator on a virtual instrument and offers several advantages over traditional MIDI editing, where achieving the same results would take significantly more time compared to the ease of a few clicks.

The included patterns can be used directly in Playbeat or, if preferred, routed to your chosen MIDI output for use with another drum module. Both options are possible.

All adjustments can be made directly in Playbeat, and all variations can be saved in the remix slots along with your preset, offering a level of flexibility that few modules provide.

Also, no features have been removed from the previous version. The earlier version did not include the ability to trigger anything using key notes, it relied solely on your DAW’s start/stop function.

Posted some info about MIDI scenarios in another thread - is this of any assistance?