DSP Robotics Support

Sean wrote:This, I think, is the issue- cant be all things to all people! May have been better selling very basic pack and then adding the modules as paid extras (Maybe even free basics and then pay $99 for audio pack...); anyway, don't want to hijack the upgrade thread...I'm off back to the SM forum to find some cool audio modules

Spliting modules/extras would not work. Imagine. You created a schematic and would like to share with someone. Will their app load these extra modules? It should, because the environment itself is uniform. It opens too many issues.

tester wrote:Start doing serious things

ruby is slow for serious thing.

tester wrote:And keep in mind, that the company listened to regular users too; they changed their initial phiilosophy after our requests.

changed his philosophy after realizing that he had not users.

tester wrote: So there is a balance between going into profitable directions, and listening to customer needs. Isn't it?

the only direction that I realized that follow, is to sell licenses to schools for teaching,
small users are out of the game.

Congrats!
I think reading the intro, this is a very good step dev has made.
I even think it might be become better then Labview in a while. (allthough labview exports to C which is fast)

But i love SM and FS.
Also people who talk about synthedit, that is allready in development for more then 2 years and really nothing is brought to the light so far.

SM is stalling rightnow, read FS as Futuristic Software !

(@Tronic). Well - it's your point of view.

And yes - ruby is slow for certain serious things.
Therefore I don't use it for them.

Better check what requires fixing in the next update. Sean pointed that there is something that crashes new release. I'm curious whether two 3x versions can be installed/working side by side correctly (sharing issues?).

jjs wrote:Congrats!

But i love SM and FS.
Also people who talk about synthedit, that is allready in development for more then 2 years and really nothing is brought to the light so far.

SM is stalling rightnow, read FS as Futuristic Software !

but the SE community is strong and still don`t complain.. absolutely my mind jjs i think this is just the beginning, 3 updates in 7 months, so another 5 or 6 during the next year.. looks like a big future

This is great news on the 3.0.3 release !!!

I see a fix on the mouse cursor in there. I think I ran into that bug a couple times [had to return to the old SM pull down menu].

Another point of interest is the possibility for FS apps to share info ... this could be very useful !

The mention in the new way that RUBY is enclosed with are exports is both interesting ... and raises a few questions.

I've not yet had the chance to do much testing with the latest release ... but maybe we could get some info/clarification, please.

For projects that have been made [and released] prior to this upgrade ... what happens with those 'installs' that have gone out ? Do we need to inform customers about this change ?? [I'm thinking of the RUBY component that gets called on 'their' computer].

Again ... I may be just confused on how this may impact us ... if at all.

Thanks for any clarification, or heads-up we should be aware of.

Thanks

oh ... second question ...

As with any new release [or update] ... I was wondering, can we install this newest version and keep our current version ???

I am right in the middle of several projects and I'm hesitant to do an upgrade in the middle of all this !

Thanks again!

Malc, I do not understand why you have opted for this solution,
at the end to have multiple instances of the interpreter,
just change the name Msvcr90-ruby191.dll,
then include it, as he did.
giving the opportunity to the user,
change the name of Msvcr90-ruby191.dll,
be able to extrapolate a specific folder on \Roaming\My_Folder,
and when run the vst, it point to this folder.

FS can continue to use his Msvcr90-ruby191.dll.

When you want to use external libraries,
you compile the ruby from source,
and specify the name to use for the ruby interpreter, istead of Msvcr90-ruby191.dll,
the your file name, es. ruby_core_tronic.dll
also because it is not that there are many libraries already supplied.

in this way, each user has his ruby interpreter.

so why not do so?
something I'm missing?

P.S. I tried it and it works.

Edit:
and also
With a nice panel of options for the user where you can set:
- The name to use for the interpreter. [Ex. my_ruby_core.dll]
- The name of the folder where you extract it. [Ex. \Roaming\My_Folder_Ruby_Core]
- Specify the folder of the library that you want to embed. [Ex C:\my_ruby_src \lib\ etc.etc]
- Extrapolate the library in the same folder as the ruby_core when loading.

we hope for a response.

i had a crash while opening the first time, but when you click ignore it goes on fine

RJHollins wrote:oh ... second question ...

As with any new release [or update] ... I was wondering, can we install this newest version and keep our current version ???

I am right in the middle of several projects and I'm hesitant to do an upgrade in the middle of all this !

Thanks again!

I asked the same question to devs earlier, so here is reply on that I received:

It's not really set up for that but you can do it if you're careful.

When you install FlowStone it makes a note of the install folder in the registry and uses this to determine where to look for files to do export to VST and EXE. So if you install one version to folder A and then another to folder B then exporting using the version in A will use the files in B. You need to be aware of this.

Also, the modules are installed to the same folder no matter what version you install. This means that if you run an older version you have to be careful not to drag in any modules from the toolbox that were updated or came with the newer version.

Ignoring the module issue, one way to have two versions in use is to install one to folder A and then rename the folder and install the second one to folder A. To switch between them for exporting just swap the folder names.

If you're not exporting then it's only the potential module conflict you have to deal with. In 3.0.3 we only changed the Bitmap module so you should be fine.

Hope this helps,

Note thatr devs refer to changed prims/modules, not new ones (like HID).