FlowStone 3.0.9 Beta1

[MyCo]

Even an empty Modul created with v309b1 dragged from the toolbox let FS v306 to v3081 crashes

As I said:

The saved files are not downward compatible due to the new assembler and the editor features (eg. bookmarks).

Toolbox modules are saved files too... sorry for not explicitly stating that

[MyCo]

Bug: when you hover your mouse over the poly to mono, in the popup info it says ...into onesingle channel signal. there is a space missing from one and signal. Its the only bug I found

Weird, can't see that.

[adamszabo]

Yeah strange indeed, its like this for me.

[tulamide]

Even an empty Modul created with v309b1 dragged from the toolbox let FS v306 to v3081 crashes

As I said:

The saved files are not downward compatible due to the new assembler and the editor features (eg. bookmarks).

Toolbox modules are saved files too... sorry for not explicitly stating that

MyCo,

this needs a change. Maybe using a file format that keeps a version number and therefore doesn't load the critical elements new in 3.0.9
I say this because the biggest advantage of developing with Flowstone is the ability to share modules across versions. Without this module sharing it becomes less and less community driven. That would be sad. Really, I think this is the big issue.

[MyCo]

Well, it was always like that... and I can't change all previous versions to not crash when they try to load newer versions.

[MyCo]

Yeah strange indeed, its like this for me.

That might be a Windows thing. It's probably just the font stretching in combination with white-space.
See, it's even a different font on my system:

[Perfect Human Interface]

This looks like a great update. Personally I'm welcoming the continued updates to usability with Poly streams. Of course I am also waiting on 64 bit before I attempt any more serious work in Flowstone, and unfortunately I believe the FL Studio team may not be interested in supporting Flowstone any more until a 64 bit version is in place anyways. But it IS coming... right??

This may be a stupid or impossible request but do you think that future releases could allow multiple versions to be installed?

Well, that's not that easy... we would have to duplicate your whole toolbox for every new version that you install.

I don't see how that's a problem. Unless the toolbox is gigabytes large. Or you could possibly use a shared folder.

Working with the FL Studio versions of Flowstone I can revert to older versions simply by loading up an older version of FL, and I will note that my toolbox has always remained intact. Although this is dependent on which version of FS is attached to which version of FL.

(Alternatively, I've recently just kept multiple installer files on my desktop for different updates to FL12 Flowstone (3.0.7 and 3.0.8) since the FL version of 3.0.8 has bugged exports. I've had no trouble switching back and forth between the versions simply by running the installers.)

Of course the FL version is different in its implementation but I think it demonstrates that multiple version installs are possible without having to rig it up manually.

[TheAudiophileDutchman]

well, you can't connect streams to double streams or vice versa. You'll have to use the converter primitives. And then your assembler code has to get updated as well to use instructions for double precission.

I know, but the point is that double variable declarations and double streams are not (yet) supported in the DSP code module, only in the assembler module. Not sure if that's a bug or a lacking feature (at least this limitation cannot be concluded from the release notes).

[MyCo]

DSP Code only supports floats. I thought about adding doubles but we would run into a lot of type conversion problems. And then you would also have to deal with multichannel issues, eg. doubles are not single SSE-Mem-Variables they are a pair to support 4 channels, making them effectively 256 Bit wide while SSE only supports 128Bit. It would be quite an effort to hack that in, and there's only a minor benefit.

[tulamide]

Well, it was always like that... and I can't change all previous versions to not crash when they try to load newer versions.

That's not what I want you to do - and it isn't true. Or we talk past each other.
Let me give you an eample of what is possible now and not possible with 3.0.9

Person A has v3.0.8.1
He creates a module. Inside the module he places a mgui connected to a RubyEdit. He writes some code to draw and manage a knob. He saves the schematic and publishes it on User Examples.

Person B has v3.0.5
He downloads the fsm, opens it with his version and no crash occurs. The modules just works. He copies it to the toolbox and that works as well, without any crash.

Why? Because all the elements used are present in both versions. But with 3.0.9, as you stated, not even schematics that contain elements that are available in older version as well, can be opened in older versions or added to the toolbox. And that is new. It was NOT that way before.