Get Tempo And Set Tempo

[deraudrl]

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 blame me for compatibility scams that have nothing to do with me ?

You seem to be using rather non-standard definitions for "scam" and "compatible".

I prefer version v3.0.9b2-3319-gd51130b because at least it's trying to export some 64bit caricatures. All other versions are suck in 32bit mode which is not going to work for me. Here is another buggy example where the preset manager is not saving the patterns of the arpeggiator.

And, like I said, you and Spogg are not talking about the same "3.0.9" version. Since you're using the FS4 alpha (not sure if the one you cite is the latest iteration or not), you should be reporting bugs (or "scams") on the Slack forum, NOT HERE.

[Spogg]

... you and Spogg are not talking about the same "3.0.9" version. Since you're using the FS4 alpha (not sure if the one you cite is the latest iteration or not), you should be reporting bugs (or "scams") on the Slack forum, NOT HERE.

Ahh I shouldn’t have been so lazy and checked before commenting.

Just to confirm what’s been said many times, any issues with the so-called “alpha” versions should be posted on Slack.
It’s best to make a minimum schematic to demo a problem, and then ask on Slack in the Help section. Then when at least one other person has confirmed a bug the issue can be posted in the alpha section for Maik to address. Sometimes what appears to be a bug is actually a misunderstanding and the guys will likely point you in the right direction so we don’t burden Maik with false positives.

[newdsp]

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 not. It's just another excuse. Or just another scam.

[tulamide]

We really need a better way to refer to various versions. There are three distinct sets in play:

1. 3.0.6, generally agreed to be the last stable official release. It works well with all currently-viable versions of Windows, including Win10 20H2.

2. 3.0.7/8/9/whatever (available on dsprobotics.com), which are 32-bit, buggy, and incompatible in obscure ways with 3.0.6. AFAIK, they can NOT export 64-bit VSTs or standalones in any way, shape, or form.

3. FS4 Alpha, available only on the Slack development channel, which is 64-bit, still in development but getting ever-closer to release. The real problem is that, at least for now, it is horribly and misleadingly misnofficial amed: it officially carries a version number beginning with "3.0.9", which it most certainly is not. And the place to discuss problems with it is on the Slack forum, not here.

Failing to distinguish between #2 and #3 seems to be causing a great deal of confusion and people talking around each other. I realize there is some logic (or OCD) in reserving "4.0.0" as the first release of the 64-bit rewrite, but the day "FS4 Alpha" starts using a version number beginning with "4" cannot come soon enough. I fear that at some point it will advance from "alpha" to "beta" status and make the situation even worse.

Thus endeth the rant.

[tulamide]

Two remarks:

1) The comment about 3.0.6 being worse is simply wrong. It is the most stable version of Flowstone to date, and works just fine with Win 10. (Stay away from buggy 3.0.9 betas. The version number says nothing about improvements. It's misleading.)

2) Why is this question in user examples? It should be in general.

[deraudrl]

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 ?

Well yes, actually, they are, for some value of "instantly". Are they actively working to solve your particular bug? I have no idea, but I suspect not, because apparently you have not reported it to them. That's how alpha testing works: the people testing the newly-developed code find bugs and report them so the developer can fix them. Throwing tantrums here does not advance that effort.

Note: it is NOT the "exact same people" there as here. Yes, there is some overlap, but only on the "tester" side of the process. The developer of the 64-bit version isn't reading this. And calling his efforts a "scam" certainly won't get your particular issues to the front of the bug-fix queue.

[newdsp]

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 get tempo module so hard coded and not editable and without a way to trigger it on load or on duplication ? These are issue that were supposed to be solved in version 1.0. It's not something that started with 306 or 309. Is it coded by amateurs ? Or is the tempo module hard coded strictly for scam ? What is it ?

[newdsp]

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 tempo is not doing it properly. I tried the midi cc 121 (reset all controllers) but it's not clear if it's forcing a tempo refresh or not. Probably not.

[Spogg]

Moderator comment @newdsp

FS 3.06 in NOT broken. I’ve been using it for some years and made many projects, as have many others, some of whom sell their professional grade plugins.

There is no scamming or scammers.

You have been given ample advice and guidance from me and others to date, but seem determined not to follow any of it.

You accusations are not only unfounded but irritating and offensive.

You have been banned before for similar behaviour (under a different user name) and we will ban you again without further warning if you don’t desist making false claims.

[newdsp]

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 but the CPU load is 5 times worse on the QX7 compared directly to Dexed. Plus, if it's not exporting VST2 64bit then it's completely broken. And it's not exporting any 64bit plugins. We all know that. You guys should keep using 306 if you want but I can't deal with that broken thing. Just look at all the synths made by Laszlo and how much they overload the CPU. Those were all made with 306. All buggy, broken and useless. You can thank 306 for that.