Synthmaker forum DB?

[RJHollins]

Gee ... did my post take down the forum ??!?

if so ...... sorry

[trogluddite]

Gee ... did my post take down the forum ??!?

Oh, it was you was it, was it? Phew - I thought it might have been me!

What just wonder why 3.07 is being ignored/avoided ?

I just went with what Spogg and co. suggested, so I'm kinda curious myself.

[tulamide]

Gee ... did my post take down the forum ??!?

Oh, it was you was it, was it? Phew - I thought it might have been me!

What just wonder why 3.07 is being ignored/avoided ?

I just went with what Spogg and co. suggested, so I'm kinda curious myself.

At least it wasn't me this time! -phew-

3.0.7 and 3.0.8 introduced a lot of bugs, including frequent crashings without noticable reason. On top of it 3.0.6 is the last version where Ruby runs in its own thread without interfewrence. 3.0.7+ introduced a timeout detection that runs in Ruby's main thread, making Ruby effectively only half as fast. This comes especially into play when constantly drawing, for example a scope fed from blue streams, and overall the responsiveness of 3.0.6 in the editor is noticably better.

[RJHollins]

Gee ... did my post take down the forum ??!?

Oh, it was you was it, was it? Phew - I thought it might have been me!

What just wonder why 3.07 is being ignored/avoided ?

I just went with what Spogg and co. suggested, so I'm kinda curious myself.

At least it wasn't me this time! -phew-

3.0.7 and 3.0.8 introduced a lot of bugs, including frequent crashings without noticable reason. On top of it 3.0.6 is the last version where Ruby runs in its own thread without interfewrence. 3.0.7+ introduced a timeout detection that runs in Ruby's main thread, making Ruby effectively only half as fast. This comes especially into play when constantly drawing, for example a scope fed from blue streams, and overall the responsiveness of 3.0.6 in the editor is noticably better.

I glad to be asking about this ...

Even though 3.07 has not crashed on me ... You bring up important 'internal' details that I've not heard mentioned before. [if there is a link to 3.07 issue ... that would be nice to read].

Anyway ... least me to debate any of this ... I just want the least issues available. If 3.06 is that one ... ok.

I only hope that my current project [from 3.07] will load up into 3.06.

[Spogg]

I only hope that my current project [from 3.07] will load up into 3.06.

I was very reluctant to go down to 3.06 but tulamide beat me into submission.

Since I went to 3.06 I haven’t had one single instance of a problem loading previous 3.08.1 projects and modules. That would probably have been a deal breaker for me, but it hasn’t happened. So happily I’ll stay with 3.06.

Cheers

Spogg

[trogluddite]

@tulamide
Thanks for explaining the various "issues" with the FS versions. I wonder if there will ever be a day where we don't have to wring our hands over which version we use?!

[Phil Thalasso]

Here are all the old attachments from the SM forum

http://www.naiant.com/SM/index.php

Adam, thank you bunches for this link. There is so much to learn from all those examples that I haven't been doing much else in FS since your post came up.

Best Regards
Phil

[Phil Thalasso]

Trog, thank you so much for that historical background.

I still have a certain nostalgia for the SM days. The move into a new market was seen as a death-knell for the DSP/VST side of things by a lot of the old SM regulars, and was the impetus for many of them to move on to new pastures. We lost a lot of the SM gurus who taught me my chops and that I later collaborated with on optimisations, tutorials, and filling the gaps in the official documentation. I have nothing but gratitude for the members who salvaged and made available so much of the work from those days.

I do think it was the wrong decision.

There was a lot of talk about trying to maintain some kind of continuity - even if only by continuing the name as a specialist bundle of FS with VST export and audio DSP module included. Whatever might be said, my years of regularly corresponding with Malc always led me to believe that, if he could set aside commercial considerations, he does have a genuine passion for music-making tools.

In a way, I almost see the move to the educational market as underselling FlowStone. I used to work for a company in that market and, if you can get a toe in the door, it's a large reservoir of users who, for the most part, will have little need for the kind of advanced features that we hanker for (and as with the customers of the company that I worked for, they rarely seem to join in with user forums.) I've always thought that with the right investment, FS could become a class-leading general purpose programming platform, because it's interface is still by far the best graphical coding environment that I've found. It could be so much more - a creator of mobile-phone apps, website scripter, Arduino programmer, etc.; and of course, a specialist version for us DSP freaks! Sadly, it's all down to the numbers; making plugins is just too niche an application to be a big money-spinner, I think.

Hey all, with humble respect, there might be a classical solution that makes sense money-wise and advances the product.

1. Fork the product into a regular and a pro version that offers an sdk. Maybe switch Pro to a subscription model, which provides regular and somewhat steady income.

2. Incentive: Organize an online cottage market for developers and their modules, much like adobe does or compare with small-scale projects, like VCV Rack.

3. Collect a commission from any sales on above market.

I am pretty sure that this would work extremely well. Marketing could be limited to the usual suspects (KVR, stack, vstplanet, etc.). To put my money where my mouth is: I'd pitch in in a project like that.
A counter-argument would be that you can't prevent from others sharing stuff via warez-sites. True. You can't. But normal people most likely don't go for illegal copies, if there is an adequate price-schedule.
Most paid modules on VCV cost between 5 and 25 bucks, with lots of free stuff too. I have probably spent 250$ there on gear that would cost me a fortune in hard-ware. There is zero copy-protection on the modules and guess what? I haven't seen anybody complaining about their work being nicked from torrents and the like.
So, that is just a thought and I'd appreciate any comment on this that points out another view.

Have a great sunday + Best Regards
Phil

[wlangfor@uoguelph.ca]

3.0.6 ? Hey? No Ruby error. And no mousewheel support... Hmm...

My reasoning was due to mention of some RUBY 'fix' [?}

Hi there! Yes, it's a problem that was introduced with 3.0.8, when Ruby "time-outs" were changed to be per-RubyEdit. You can read all about it on this thread - in summary, it makes Ruby events create lots of new threads which then leak memory when Ruby doesn't clean them up properly. As Spogg and others have pointed out, going back to 3.0.6 has definitely made FS feel more responsive, too.

[jon_stoppable]

wow n1 thx guys! and especially thx Youlean for still hosting this!
didn't know that dump existed...

It's hosted on my site although I had little to do with that other than giving smarter people FTP access to set it up. That was seven years ago, which also means it's been about seven years since I did anything with SM I've gotten FS now though and I'm planning on doing something with it later in the year, to control audio gear via serial port. Hopefully someday with a 64 bit app. Sure that doesn't need FS, but for me it's easier than learning to code!