DSP Robotics Support

No FS 3.0.2 Free Edition? The download is still 3.0.1.

jjs wrote:@support Now how can you see if one of the packs is updated ?? Like the dsp, audio and robotics pack. There is no info but the download link. Thanks!

None of them have changed but when we do change them we'll add something to show that they have.

Morph wrote:No FS 3.0.2 Free Edition? The download is still 3.0.1.

Thanks for pointing this out - should be correct now. Also the user guide has been uploaded now.

support wrote:None of them have changed but when we do change them we'll add something to show that they have.

Okidoki ! Thanks Support !

Cool update.

One problem though.. Plugins created with FS 3.0.1 won't work at the same time on the same system as plugins created with FS 3.0.2. Crashes every host I've tested so far. Rebuilding all plugs with FS 3.0.2 fixes the issue..

I thought FS was never going to go Mac. This is clearly Mac behaviour.

Thanks for the heads-up, matti.
I just tested in Reaper and VSThost on two different machines, and it is exactly as you describe - instant death to the VST host unless all plugins are made with the same FS version.

Yep-thanks for the heads up.
I have some issue here though.
I deleted all the plugs that had been built before 3.02.
So I just have these 2 in my DSPR VST folder->

http://www.sendspace.com/pro/dl/k9f5jv

They run fine by themselves,
but if you put both in the same project it crashes.
They are both built this morning with 3.02.
Is it something to do with the way I am initializing Ruby,
or have we got an environment issue here?
I'd really appreciate if anyone would test by trying to load both in one host project.
Cheers, Nick
I am using a default init for all Ruby modules,
the pins are called different things, even when the module is the same.
I can't seem to call checkInited though, it says it is an invalid command->
NameError

edit- hmm, doesn't crash Acid, but without fail on loading Entrancer after the sequencer in Orion
edit2-It's my novice initialising of Ruby for sure. Got it not to crash,
and I see that checkInited is defined in each Ruby window,
it's not a built in function, sorry for my user error callling into question the environment.

Maybe pick different VST identifiers (plugin ID) for different plugins when exporting?

And by the way. Just recently I had to reexport some plugins with different IDs anyway, because the host locked them up, and did not wanted to let go (neither re-cache). After changing the IDs - everything came back to normal.

I wonder if that crashing has anything to do with the Ruby issue?

tester wrote:Maybe pick different VST identifiers (plugin ID) for different plugins when exporting?

And by the way. Just recently I had to reexport some plugins with different IDs anyway, because the host locked them up, and did not wanted to let go (neither re-cache). After changing the IDs - everything came back to normal.

The id's are different. The problem is most likely Ruby.

hmm
I just had a break from this coz I got a tummy bug.
Now trying to lock down exactly what's going on.
It has something to do with this module->
viewtopic.php?f=2&t=1260
...and using similar switches.
So for now I have taken it out of the sequencer,
and I have 2 in the synth.
They are for switching on the synth's arp manually,
and playing on host play.
So I am looking at the way checkInited is set up by RDSP.
I'm pretty sure it is my Ruby modules.
When changing the codes I am getting different crashes.
So now, I can load the synth first, and it's fine.
If I load the seq first, I can load both.
Then hit play on host transport,
still fine, but changing a control value on Entrancer causes the crash.
Hopefully I can solve this.
Will let yous know what it is.
Cheers
edit- I chopped out all the Ruby that is lesss neccessary,
and I am still left crashing. So it must be this:-

def init
@in_id = 0
@samples = 5512.5
@samplerate = 44100
end
def event
init
off = Midi.new 128,1,60,127
if @in_id = 0
delay = @samples/@sample_rate
output 0,off,time+delay
end
end

This my timer, the output gets fed back into the input.
It sends a MIDI note from which the trigger is extracted from a MIDI split.
So hmm, can anyone see what is wrong with this snippet?
Cheers

edit2- OK, something else is wrong than my Ruby implementation.
Now I have exported them without any Ruby. Crash on load of the synth.
What's going on here?

edit3- I found a Ruby component I had forgotten about. I deleted it and it has helped. Will have a look what is wrong with that one. I suspect it is Ruby again, and my use of it