Are my Ruby codes correct?

[nix]

thanks for that 8D!
I would like to send a couple of versions of the sampler to you,
to see if I can get it to work in Live!.
That's cool Fruity is going.
I am now making a project in Orion with multiple instances of the plugs,
to see if they are stable.
Also ta for the Reaper testing,
I wonder what Live doen't like.
I will see if I can make the sampler roadworthy in Orion,
and pm a new schematic for Live.
Certainly there is night and day now that my plugs are using different handles in Orion.
It does help a lot,
and stoked that you might use them.
Chop out the sequencer if you want get into using streams for the clock.

[billv]

that you might use them

It was great, I got this massive wall of sound happening and then kept on changing it and
changing it. Have you thought about building both these plugs into one??

[nix]

hmm, I could.
Thanks for the thought.
I'll think about it.
So I thought the naming thing had stopped the crash,
but you can't rename the event.
So my codes weren't active.
Still crashing,
but it sounds like it might be my host more specifically,
and my plugs.
If it's working OK in FL.
I use Synapse Orion 8.5.
I am still crashing withe RDSP example,
which has the 'custom ticker' in it,
switched on by a 'MIDI mono' prim.
Search me

That's so cool you had a nice session with the plugs Bill.
I'm itching to make some music myself,
but I'd rather use O

edit- I tried turning them into different named classes, no dice

[billv]

Note the ticker is not active. What is it for?

ScreenShot131.png (15.96 KiB) Viewed 16731 times

I didn't get it, so i deleted it.
Re-tested in Live. same thing.
Take another look after work tommorrow........

[nix]

ta for having a look
In that schematic, the example synth--
it doesn't do anything,
just makes Orion crash.
You could hook it up to a trigger counter to see if it is going.

My testbench crash is exporting the RDSP example twice with the timer above,
naming them different things.

I can't use Orion with them, and I tried briefly in eXT, and crashed it there too,
but with the arp being switched on causing it.
So now the arp is not in the testbench either.

I put it into the example, coz there may be no other flaws in that schematic,
whereas my synth has like 150,000 prims

[billv]

In that schematic, the example synth-

Nix, The picture I took was from the Sampler ...... Not the example synth....

[nix]

hmm,
maybe u r not getting the crash coz u took it out.
The timer is the module that causes the crash.
RDSP has reproduced the crash.
I'm fuffing about with 2 ticker methods now.
I'll work on DreamSequence soon.
We can communicate beteween Ruby modules with MIDI links,
like say the note goes beyond 127-
so we can have a sequencer with more than 128 steps over MIDI link.
I had unhooked the timer,
trying to locate the component causing the crash.
That timer gives a tick to the m2f in mod,
which translates the stream into green,
which triggers the random step LFO changing to a new random array, and updates accordingly in the graphic.

[billv]

OK, To do the test, export it as VSTi twice,
with different names.
Load both in host, and give each a MIDI note on.
It should crash then.

Did this with your "Example 2". No crash in FL.
Will try Live and reaper when I get home.

RDSP has reproduced the crash.

What host was used?

[nix]

Thanks for doing the test,
I guess RDSP used Orion.
The arp in the example synth crashes eXT also.
I'll try FL now too I guess.
I think I mightn't be able to fix this myself now,
there may be some environment issue

I'm actually likling Ruby now though,
it's a great step by RDSP IMO

[billv]

Did this with your "Example 2". No crash in FL.

Tried it in Live, and got the same "Refuse to load,screen lock up/have to CPU restart" error,
just like your Sampler Plugin. I worry a bit then, so.......
I make then a new dll called X11 Test.dll....
Same deal again- Ok in FL, Live refuses to load X11 test.dll, locks up again/restart again.
Doing a quick check, I run 2 instances of X11 in live, all good.
Quick test using X11 and your Entrancer Plugin, in Fl and Live, all good, no conflicts.
Searching my old hard drive, I dig out a Demo version of orion 7.62.
It loads every plug.
I load both "Example 2" dlls(named test.dll and test 2.dll).
They both load and run.
( I couldn't get the arp's to stop, I have seen this error a lot in FS while testing Arp module,
but I don't really know Orion, so.......could be user error.....)
But no definate crash.
Hope this helps.
It's good Support knows about the issue, cause it's real.

fix this myself now

Yeh, your dreaming mate...this is serious issue, I need to know the full extent of it.
Still more tests have to be done.
Where is the exact error?
For eg:
This could mean that, I can't take the X11, build say, a "sampler version", and call it another name,
.....WTF is that?????????
But if it did work, I would know that it is this "identical" part that is the cause...
So solution in theory would be to always add at least (1 more part) to a schematic, so they are not read
as identical.......don't know.....more tests........

So, I'd sort of like to question the logic, of wanting to export two identical plugs, with different names??
I'll take it it's just a troubleshooting method....