• Fixed: Corrected the issue with mono to stereo audio file conversion upon importing.
• Fixed: Resolved an issue where samples were not saved with expansion packs during export on certain iPadOS versions.
Desktop users, you can download the app from your account -or- from our updates page here: Latest Software Updates | Audiomodern
iOS users, kindly check for updates manually if you haven’t automatic updates turned on.
Happy composing! 
Any of the user feature requests coming soon? Or are they gonna be in version 4?
V4 Will come with many new features including almost all additional feature requests by users.
Greetings!
Will PlayBeat v4 have the option to:
a) relocate the library folder?
b) choose a custom sample folder?
thx!
Hi Pete,
a) Relocate the Library folder is available on our upcoming V4.
b) Choosing a custom sample folder should already be available in the current version. Do you mean the folder in which we use to randomize samples from? Once you select a sample on your sample slot, the randomization will then use the same folder to pick a new sample when you click on randomize.
Not sure who to let know, but I installed playbeat 3.2.8 yesterday and Reason 12 (win10) no longer starts as there is error with the VST ( I installed both PB vst2 and vst3 so not sure if it affects both). Reason went into VST protection mode.
I reinstalled to 3.2.6 that I previously had installed and that fixed the issue.
PB 3.2.8 looks like it needs some urgent TLC.
FWIW, in 3.2.6 there is a midi export issue within Reason, where the drag and drop “combined” midi might be malformed (compared to other product VST exports e.g. XO) and PB creates new instruments for each drum channel (and also appears to export each drag and drop midi twice )
Hi noiseboys,
Thanks for reaching out. It seems that your OS is missing the last C++ Redistributable update, we will need to include this with our next 3.2.9 installer to avoid any confusion, meanwhile you may download it directly from Microsoft here:
Thanks. Think I’ll wait then.
Is there a changelog for PB at all (to see what has been added)? I couldn’t find one.
If you need assistance with the midi export in Reason, let me know. Its a real pain 
Sent you a DM with a video showing the behaviour.
Versions 3.2.7 & 3.2.8 correct a minor UI issue when using the app with Studio One.
I can confirm that 3.28 does NOT correct the midi export issue.
Hi noiseboys,
I assume you mean in Reason DAW? Are you able to open the Playbeat UI and go to the export tab and export your MIDI from there?
as discussed in DM, when I drop in the exported PB midi file (from desktop) , it exhibits the same split behaviour rather than the neat combined operation as per XO (or Atlas etc).
Sorry I didn’t see that included in the video that you shared, in any case the exported MIDI should be combined in one midi file. If you export as a MIDI file (Export as a MIDI file button) and import to Reason, will it still be imported in multiple MIDI files/tracks?
Yes it does import as multi instrument single lane midi rather than 1 instrument and multilane midi.
Playbeat 3.2.8: Reason 12’s new nemesis. Back to 3.2.6, yet MIDI’s still causing chaos. Audiomodern, over to you.
Reported this a while back “PB creates new instruments for each drum channel (and also appears to export each drag and drop midi twice )”
Yes, and each drum channel does not have Playbeat in them. It defaults to Reasons RE ID8 device (sry if you have stated that already).
Reason’s Midi may also be a possible problem. The sequencer doesn’t seem to allow VST midi player with only a few exceptions hence why Reason has their own RE Midi players.
Playbeat’s Seq is 8 separate Seq… and I presume this is where the problem may be, no?
Buuuuuuuuttttttt like you mention about XO works fine and I can confirm Microtonic, Triaz and the UJAM plugins work as well.
I bet Pooh Bear’s Reason channel on YT will have an answer or fix for this… I may ask him 
Radio silence on this issue from the Audiomodern speaks volumes sadly.
Initially they were responsive and it was encouraging. I provided videos of the issue, so couldn’t be much more help, other than coding a fix myself.
This was the last meaningful DM update I got from AudioModern back in August 2024:
"Exporting a MIDI file into separate stems has been changed since version 2.0 and since then all sequencers MIDI data are included in one single midi file.
So I’m a little confused as to why this is handled this way in Reason.
Am I right to assume that there must be a setting which separates the notes based on their pitch?
Is every midi stem including one pitch value only, therefore the separation?
In any case, our team is looking at this today. Thank you for your patience."
@jakasspeech50 @Ch1mpact :
Good (or rather not good) to know its a general issue with Reason and only Audiomodern.
Agreed that XLN XO have had midi export working properly since day 1.
Likewise for me, 3.2.8 wasn’t a fix (infact it 3.2.8 didnt even have the right MS VC distribution executable/checks for it to install properly for me at the time)
I would have assumed they would have grabbed R+ to test as required.
Sorry for the delay! This issue occurs because Reason’s sequencer doesn’t utilize MIDI channels. Could you try setting all MIDI outputs to Channel 1 in the settings tab and then re-export?
Yes, that is a work around. It still creates an ID8 but at least it’s workable and includes all notes in the single clip, albeit slight pain. Perhaps add a new button set set all to midi channel x ?
Shame it can’t bounce the variations to the track, but Reason doesn’t support midi out from vst natively.
