DSP Robotics Support

kortezzzz wrote:Attached a very simple schematic using the stock multi-sample module and added a switch button to turn on\off the "NoSav" feature for easy testing. Also attached the SFZ patch. The schematic saved the SFZ samples and its 4.6 mb now (Had to upload it to an external server since DSPR's site supports only 2 mb files maximum). After downloading, All you have to do is to use 3.0.6 ver. or newer and save the schematic while the "NoSav" switch is on. If it remains 4.6 mb, then its probably a bug that needs a fix.

That's not exactly a "simple test schematic"

kortezzzz wrote: All you have to do is to use 3.0.6 ver. or newer and save the schematic while the "NoSav" switch is on. If it remains 4.6 mb, then its probably a bug that needs a fix.

If nosav is "true" the schematic size is 207 KB... so I guess it's working just fine then. (tested in 3.0.9b1 but I guess it's same for 3.0.8)

If nosav is "true" the schematic size is 207 KB... so I guess it's working just fine then. (tested in 3.0.9b1 but I guess it's same for 3.0.8)

Well, its probably fixed already. Thanks
Wish DSPR could at least let us test the new beta for few days, as nubeat7 mentioned. Each gang member here, including those with the expired license, dealing with different aspects of FS in details and may help with finding new bugs. Anyway, cool to see you guys making serious efforts to fix things.

Releasing a beta is a great move for DSPR. Should have happened long ago.
Great to see them looking at 'Synthesis ' again, which means they're comfortable
with how the robotics section is sitting, which in turn puts a bigger eye on the
timeline for 64bit delivery.

Again, awsome to see people like myco now can nut out the issues from
every new update.

I remember once, after a recent release, myco was finding bugs straightaway.
This should never happen with a community of 20 000+ members.
Thanks DSPR for letting the Guru's inside...great news for everyone.

MyCo wrote:

Spogg wrote: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.

Thanks for responding MyCo.

If I install Firefox or Chrome on a new installation of Windows I get the option to import bookmarks/favourites. This is the principle I had in mind. Also the import process could highlight any tools or toolbox modules which would be incompatible, thus saving problems later. I do think that this would be useful as Flowstone progresses and its compatibilities change with newer versions.

Cheers

Spogg

MyCo wrote:

MyCo wrote:

Walter Sommerfeld wrote:BUG: Touch-Screen R-Click simulation on EXE Compiled GUI and in FS... v309b1 disables this feature...

I don't think FS can disable that in any way (as it just sees a right click). Else all I can say is that the right click behaviour wasn't changed at all in this version.

Update for that: It was caused by a library update. I think we fixed it... at least it's working on my old tablet again.

Great - because it worked until v3081

Bump again: Multi-Touch... Multi-Touch...

@Spogg:
i use the Rename Installed Path version (manually but could be a .bat or .cmd file)
for years now w/o any probs...


btw: thanks 4 the info about the leftover "*pid=nnn.fsm"

One issue I've often had with Flowstone MIDI handling is stuck notes. This can happen with live playing when the sustain (hold) pedal is used to sustain and then release some notes as a piano player would tend to do.
I see that some MIDI points have been addressed but I wondered what the state of play is with this unfortunate behaviour.

Cheers

Spogg

Can't test this and it's the first time I heard about that.

I would've expected some more bug reports for the stream section, in the meantime I found some bugs myself... seriously, is no one really testing the beta?

Did not have sufficient time yet, but summarizing one of the first things I found:

While trying to convert some 'old' 32-bit stream code into 64-bit, changing a streamin into streamdoublein doesn't seem to work and the same for changing a streamout into streamdoubleout (please note that the links to the connectors have been removed first).