I tested 306 side by side with 309b2 and 306 is completely useless to me. Every single plugin that was exported with 306 is overloading the CPU way more than 309b2. Just look at the CPU load generated by QX7 and then compare it with Dexed. Both are supposed to be the same thing, as in, DX7 emulators ...

I looked at that file called "EasySyncSeqTest.fsm" and it's doing some sync I just don't understand that complication at the moment. Why does it have to be so complicated ? Can that example be simplified somehow ? I guess I will have to play with it for a while to understand that complication.

Can you guys figure out what's wrong with mine ? Sometimes the tempo gets initialized properly but other times it keeps the wrong tempo. Here is a version made with 309b2 because 306 is not exporting any 64bit plugins and it's also overloading the CPU in a gigantic way. And yet Tulamide keeps ...

Here is one example of a broken tempo where the ARP is mostly in sync by pure coincidence. I need a module that gets/sets the tempo on transport change (stop/play/record) and also when the ARP speed is modified or the tempo is modified manually. There is no module that does that and the hard coded ...

The plugin, when it gets exported, is memorizing the FlowStone tempo of 120 and is not going to initialize it again when it gets loaded in the host unless you change the tempo manually. It only happens because the Tempo module is hard coded and is not editable and it has no trigger input. Why is the ...

It is a 306 problem because 306 is broken and is not able to export VST2 64bit. Why do you pretend 306 is better when in fact it's not ? How exactly is that Slack group any different ? It's the exact same people behind it. Is that Slack group fixing all bugs instantly or something ? No. Of course ...

Why don't you blame Microsoft and DSP Robotics for that scam ? I never said that versions should be incompatible with each other. If the Firefox browser is still compatible with the internet even at version 85.0.2 then I expect the same from Windows and FlowStone and everything else. Why do you ...

306 might be the most stable version in Windows 7 but it's not the most stable version when it comes to Windows 10. I already tried it. It's also not able to export 64bit plugins therefore there is no way for me to test with Reason 10 since it needs 64bit plugins. It's in the user examples because ...

It looks like I kind of forced it to trigger the tempo reading by attaching an AfterLoad and AfterDup trigger to a Tempo multiplier but that doesn't really give proper control of the get/set tempo. How can I convert them to 306 when they were made with 309 ? It's in Reason 10 because 306 is not able ...

Here a few ones that work Reason 10.