Thanks for sending these over! So, when we open the audio files in Ableton we get this. Which is the part you’re noticing the timing is off-grid?
On the screenshot you shared, it’s not clearly noticeable. On my end, I also opened the same file as you in Ableton and zoomed in on certain parts. Then, you can see that sometimes PB4 is perfectly on the beat, while other times it’s slightly off. Of course, it’s not a significant gap—just a matter of milliseconds—but when I add the PB4 demo to one of my projects and choose a preset, over time, I can hear that PB4 is not in sync with the rest of my sounds.
Also, when listening to the files I sent, you’ll notice that the kick doesn’t always align perfectly with the metronome.
Thanks for the explanation. We believe this is due to how audio is processed within the same audio block/buffer, which is about 10 ms long. If a MIDI message is received at the end of a block, its output (whether playing a sample, generating a MIDI note, or starting the playhead) is added at the beginning of the next block. However, this difference is only 0-10 ms, which isn’t audible. That said, we’ll work to reduce it even further.
Thank you for your message!
I ran several tests again today in hopes of finding a solution, and here are the results I’d like to share with you:
When I set PB4 to synchronization mode (play icon), it remains perfectly on time, which is excellent.
However, once I switch it to trigger mode (keyboard icon), PB4 stays on time during a clip, whether it’s 4 measures or more (I tested it with a 16-measure clip using the note C2 ALL, and throughout the entire clip, PB4 remained on time).
So, even though I’m not a programmer and have no understanding of how your plugin functions, I would think that the issue might possibly stem from PB4’s internal clock, which doesn’t always synchronize perfectly with the DAW.
I have other drum plugins like Triaz, Algonaut Atlas, Seepdrum 2, etc., and their sequencers are always perfectly in sync.
I discovered PB4 and was ready to purchase it along with all the expansion packs, but since I’m experiencing this issue with the demo, I’ll hold off and wait to see if you’re able to find a solution to resolve the problem.
If the issue gets fixed, PB4 will be an instant buy for me because I absolutely love this plugin, its concept, and the functionality I find truly amazing—being able to launch a complete sequence with the C2 key and individual sequences for each track starting from the C#2 key. 
I’m eagerly awaiting your response, and if you release an update, I’ll test it out immediately!
By the way, when I discovered PB4, I sent you an email through your support form on your website on March 18th and never received any reply. However, I did receive the following message:
“Your request (19918) has been received and is being reviewed by our support staff. To add additional comments, reply to this email.”
This makes me wonder if something went wrong with my email. Could there have been an issue with the response or follow-up?
I also forgot to mention that during the tests I conducted today, in trigger mode (keyboard icon), when I place multiple clips of 1 bar one after another, that’s when PB4 is no longer perfectly in sync.
However, when I create a 1-bar clip, I make sure the note length is not 1.0.0 but 0.3.3+ to prevent overlap when transitioning from one clip to another. (I’ve already encountered issues with plugin arpeggiators at 1.0.0, so I always shorten them to 0.3.3+.)
If you’d like me to run additional tests with PB4, feel free to ask—I’d be more than happy to help! If it contributes to identifying and resolving the issue, it’s my pleasure to assist.
Hi Audiomodern Team,
As I have not received any response to my recent messages, I am wondering if you are currently working on PB4 to address the synchronization issue, or if I should let go of the idea of purchasing your plugin?
I would like to mention that I have installed the demo version 4.0.7, and the issue is still present.
Thank you in advance for your attention to this matter.
Best regards
Yes, this is related to the buffer settings. The difference is around ~10 ms, which isn’t noticeable. We’re working to refine it even further.
Ok great, I’ll wait for the update.
If the problem is fixed I will buy PB4.
Hello Audiomodern team,
It’s been almost a year since I wrote my last message, and I’m reaching out again with some positive news.
I tried PB4 once more with the latest version of Ableton, and the issue is still there.
However, I recently switched to a new DAW and moved over to FL Studio.
And there, like magic, everything works perfectly!
No matter which mode I try, PB4 stays perfectly in sync with the tempo 
So I was finally able to purchase the full PB4 bundle!
And now that I can import my own samples, I love PB4 even more!
Since it works flawlessly in FL Studio, I still wonder why there’s this small issue with Ableton Live 12.
I just have a quick question regarding the expansion packs. I remember seeing someone on the forum mention the older packs being available separately instead of being grouped together in the factory library.
Is it possible to get those packs and install them so the samples and presets remain separated?
That would be great!
Thanks in advance, and now I can finally start working with PB4 in FL Studio
Best regards
That is a specific issue, but it might be worth checking your Plugin Delay Compensation settings in Ableton’s preferences. Sometimes if there are heavy plugins on other tracks, it can cause MIDI trigger offsets on subsequent loops even if the first one hits correctly.
Thanks a lot for the information, I’ll give that a try and see if it fixes the issue!
Even though I’ve switched to FL Studio, I still have Ableton, so it’s worth testing it there!