DSP Robotics Support

Hi. Flowstone is constantly crashing here, even with the VSTi example from

viewtopic.php?f=79&t=1075

It happens when changing presets.

Here's my Sysinfo:

SaccoSVD wrote:Hi. Flowstone is constantly crashing here, even with the VSTi example from

viewtopic.php?f=79&t=1075

It happens when changing presets.

Here's my Sysinfo:

Hey welcome to the forum. For crashes like this you should really contact support via the email at the top of the forum. The developer don't check the forums that much.

I have already reported this though. Malc is currently on holiday but has his laptop with him so is looking into it.

3.05 running ok here, but some issues..
My tags are stuffed up again...due to crash caused
by infinite loop..
Ive had several unexplainable crashes while just
doing normal stuff. ..no idea on this one...
Had a weird time crashing Exo's free running osc fsm
just by loading 1 module from sm into the fsm...
repeatedly...will re investigate that one...
3.05 did manage to open a 3.04 fsm that had
locked up in 3.04 and I couldnt open.

Some nice new features, but not what I was
really hoping for.

Im not a fan of the current subscription policy.
I think we should we paying around $50 for these
updates, while the price of FS should increase with
every update. FS should be about $400 Atm...
Slugging long time users for $150 a year is a bit much..
just my 2 cents..
Edit...
Note when I installed recently on fresh xp, FS would not
run without the Microsoft 2008 re distributable..

could someone upload a simple schematic where this preset changing issue happens? want to try if it crashes here too, because it seems to work here..

@Nubeat,

* Noted that my crushes occured when used asio out primitive instead of DS in the schematics.

In most cases, PM crash happens when editing a preset, saving it and then switching to another.
And there is also "changing parameter" crash. for instance, exo's "free running osc's" fsm (which does'nt contain PM inside) crashes after switching a waveform (lets say, from sine to saw), when the schematic is connected to asio out primitive.

Last night, I'v sent my all products line fsms (all crashing) to exo so he will give it DSPR for debugging.
Lets hope malc find the problem soon as possible.

Nubeat7 wrote:could someone upload a simple schematic where this preset changing issue happens? want to try if it crashes here too, because it seems to work here..

This is a simple test I sent Malc....

After sending this I realized it still crashed when removing the poly readouts, so I informed him of that too.

kortezzzz wrote:@Nubeat,

* Noted that my crushes occured when used asio out primitive instead of DS in the schematics.

In most cases, PM crash happens when editing a preset, saving it and then switching to another.
And there is also "changing parameter" crash. for instance, exo's "free running osc's" fsm (which does'nt contain PM inside) crashes after switching a waveform (lets say, from sine to saw), when the schematic is connected to asio out primitive.

Last night, I'v sent my all products line fsms (all crashing) to exo so he will give it DSPR for debugging.
Lets hope malc find the problem soon as possible.

I haven't sent them along yet, my simple test case should be enough. Of course if he needs another example I will send them to him.

He is currently on holiday but is looking into it, so hopefully will get a quick update out when he gets back.

Confirmed the crash here - both WinXP - Asio4All and Yamaha mLAN ASIO drivers.

OFF TOPIC: Then I panicked, when I started writing this reply and this happened...
"C6nf5r0ed the crash..."
I thought the crash (with MIDI keys enabled) had messed up my keyboard! Erm, no - I hit num-lock instead of enable audio on my baby netbook's keyboard. Never even noticed the microscopic "num-pad" markings on the keys in the whole five years I had the machine!
What a st66*5d d40bass!!

Then probably i would be better to solve some issues earlier and bring out some patches more often, then to do a whole bunch at once. Like 3.04.1 then 3.04.2 and for a major update with some feature requests in it like a 3.05 or 3.06. So customers are more happy that issues are taken care of and they get more often a year an update.
Then the one update a year there is now. For a yearly update there should also be something interesting in it were also more customers can be attracted to the product.

I didn't renewed yet.
Best bet since no news about any route (even crowdfounded) about x64, and now it's also unstable..