DSP Robotics Support

That looks like a Windows Message to me, maybe something from DirectSound? We'll have to somehow reproduce it, to find the cause for the message.

Well - never had these before... my project only uses Midi I/O...
Will investigate further!

Keep on doing!

Any news on the non-beta release date?

My subscription ran out last November, and I'm prepared to pay to upgrade, but paying for a Beta seems a bit of a sting.

Thanks

Nat.

MyCo wrote:Interresting! I can reproduce it in 3.0.9 and there seems to be something wrong with gridStep and one redraw. I'll have a look.

It's actually not exactly "wrong" but could be confusing for the user. There is a redraw for the navigator that's getting called with a different ZoomFactor (=gridstep) and this gets forwarded to the user drawing section so that the preview in the navigator somehow resembles the real schematic. I might have a workaround but you'll have too keep in mind that the gridstep is still used for the navigator as well. For the same reason you see multiple redraws when you click on the schematic background BTW.

@natbuk:
No release date yet.

Two nice addictions would be:

1 - refresh modules button; when you add a custom module in a instance of FlowStone and you want to open it in another one. At the moment you need to close both and restart, so it refresh the list.

2 - Multi Audio Output prim. When making a VST, would be nice be able to route audio on different DAW mixer channels (Wrapper settings in FL Studio, for example).

What do you think? I'm going to buy FlowStone standalone when 3.0.9 is official (I'm with the FL one) I've found a true new love...

MyCo wrote:

MyCo wrote:Interresting! I can reproduce it in 3.0.9 and there seems to be something wrong with gridStep and one redraw. I'll have a look.

It's actually not exactly "wrong" but could be confusing for the user. There is a redraw for the navigator that's getting called with a different ZoomFactor (=gridstep) and this gets forwarded to the user drawing section so that the preview in the navigator somehow resembles the real schematic. I might have a workaround but you'll have too keep in mind that the gridstep is still used for the navigator as well. For the same reason you see multiple redraws when you click on the schematic background BTW.

@natbuk:
No release date yet.

Sorry, MyCo, I missed this one! I can follow your explanation. If it doesn't influence the use of .gridstep, it can stay as it is. For exported plugins it should be safe, since you don't change the zoom settings there. But, if you make modules that are of use within Flowstone, .gridstep will be used to keep the redrawing at the right zoom level. If the navigator then doesn't reset gridsteps to the real value, it would be an issue, wouldn't it?

As long as you only use it in the draw method, it shouldn't be an issue. You would draw to the right surface (schematic view / Navigator view) with the corresponding gridStep. The only reason why you see the "wrong" gridStep in the watch output is because the last draw method call was for the navigator.

MyCo wrote:As long as you only use it in the draw method, it shouldn't be an issue. You would draw to the right surface (schematic view / Navigator view) with the corresponding gridStep. The only reason why you see the "wrong" gridStep in the watch output is because the last draw method call was for the navigator.

Yes, you're right. It doesn't influence drawing, it is just irritating if you inspect values during development. Once used to it, there shouldn't be any issues. You should leave it as it is (and work on the more important things )

why the beta version is not available for everyone to try out like the demo?

Hello gang,

I really agree with father here, being a FS user via Fl Studio I would really like to try 3.09 and I bet many other Fl Studio users would to.

Later then, BobF.....

as the full version is still not here, i thought i make some wish, maybe it would be possible to add this:

integrate a getHostProductString primitive to identify the actual DAW,
like this we could react to DAW specific specialcases (like the sync problems with FL Studio)