Flowstone crashing

[Exo]

I tried both Flemming's and Nubeat7's example schematic and they work completely flawlessly in Flowstone 3.0.2 Firefly free version - never had a single crash even after several dozen tries. So the bug must've been introduced after that update.

Yes was introduced in the latest release 3.0.5.

[Tronic]

I think that the problem is in the primitive Poly to Mono.

[Flemming]

I think that the problem is in the primitive Poly to Mono.

Interesting! Especially since none of the schematic files in this thread even uses Poly to Mono primitive. How come you think that this specific primitive is the culprit?

[Tronic]

this one
from Nubeat7 post
audioselector bug.fsm

i think you call it Combiner? Inside you can found the primitive Poly To Mono.
I suppose that is related,
because if you disconnect it an connect an readout in Poly, it work without crash, even if you use the selector, so no selector bug, but another intricate misture of poly->mono->asio, as I remember Malc have apported some update for the Asio primitive, to prevent the crash when you open more schematic in the preview version.

[Flemming]

this one
from Nubeat7 post
audioselector bug.fsm

i think you call it Combiner? Inside you can found the primitive Poly To Mono.
I suppose that is related,
because if you disconnect it an connect an readout in Poly, it work without crash, even if you use the selector, so no selector bug, but another intricate misture of poly->mono->asio, as I remember Malc have apported some update for the Asio primitive, to prevent the crash when you open more schematic in the preview version.

Arrrgh, stoopid me. I was thinking of the Midi to Mono prim....

You're making sense. I will try to do some testing with your discovery in mind to see if i get same results here.

Thanks for investigating with us

[Flemming]

Damn, i'm at work. Only able to install the demo version of Flowstone, also no Asio device, and when i insert DirectSound Out and select a sound output it crashes immediately (caused by our phones, which connects to PC via USB and acts like a 'pseudo' soundcard - it's not a Flowstone bug). So no testing for me before i get home

Though, i can add, 'KG_is_back' posted a DSP coded Multiplexer yesterday, and even with the Poly to Mono inside the schem, it still worked just by replacing the Multiplexer prim with the code that KG posted. I am kinda determined to pinpoint the bug, so i can work around it, but also to make the life of DSPR a little easier, hehe

Anyways, regardless of where the bug may be found - since FS3.0.5 is fairly new, will it not be long before we can hope for a new bugfixed release?

[Flemming]

This one is very simple. No Poly to Mono, and it still crashes I replaced the Asio Out with Direct Sound but still i can make it crash.

[Flemming]

Ok ok, one last post and then i'll shut up, i promise

I got really tired of clicking that Selector dropdown. I mean, like, reeeeealy tired. So i built an auto selector

Capture.PNG (18.73 KiB) Viewed 16379 times

It can crash any schem from this thread except if KG_is_back's code snippet is used. I opened my revised delay schem which uses the code Multiplexer. Then I connected the auto selector and went to have a smoke. When i came back it was still going strong. The schem uses both Poly to Mono and Asio Out prims. I could play notes happily and toggle Midi/sound IO on/off with no problems at all.

[Tronic]

Flemming, I think the bug is more extensive, since even without selector or multiplex, occur crash,
try connecting only two green float to two mono readout and enables and disables the Asio driver,
you'll see that the crash happens the same, so it is not directly connected to the selector or multiplex primitive,
but a driver error at compile time.
In fact, the primitive and multiplex selector,
always cause the recompilation of the schematic,
so it's like when you enable and disable your sound drivers.

[Walter Sommerfeld]

Just tested Aliasant's Wave Player II (Poly):

1. Left Levelmeter shows always max
2. press Pause sometimes crashes FS immediately
3. My own App works fine in FS but crashes compiled as EXE...

v3.0.5 win8 64 bit 16GB Ram