Are my Ruby codes correct?

[billv]

Hi Nix,
Took a look at your midi timer.
I'm sort of worried by the way you intend to generate the midi notes, with that Split module there.
Notes must be generated in ruby. You need to route your midi notes back to the very start
of the chain, like this

ScreenShot116.png (49.61 KiB) Viewed 16385 times

I had a look at Dream Sequence yesterday, in the hope of doing a quick fix for you, went looking for
the green notes, but got a bit lost with all the arrays. just got to find those notes and punch them out
properly at the start of the chain.Will have another look when time allows.
Cheers

[nix]

Here is my example that shows the user's operations affecting a pure Ruby tick.
It is the stock custom ticker I have used,
versus the custom ticker outputting a MIDI note off,
which is modified by the MIDI splitter back into a tick->
http://www.sendspace.com/pro/dl/c2sfvc
It is the polyphonic sequencer as a VSTi
The difference in usability is telling.
Thanks a bundle man fer checking it out.
There is a 4096 entry array for each of the 128 MIDI notes.
So the array is 32 128 note patterns, which is repeated for c,c#....
Cheers mate, hope tomorrow's off work for you 8D
I am interested in the method u would use to make a pianoroll
I am not sure if we need to generate note data in Ruby,
perhaps we can use regular memory.
Like you can read the faulty timed green system array with sample accuracy,
as long as the index is sound.
I was looking at the loop I rendered using a ruby tick,
there were 7 samples before the note became visible,
on all bar divisions.

[billv]

Here is my example that shows the user's operations

Will check it out.

hope tomorrow's off work

Nah, bummer, back on.

MIDI splitter back into a tick

I did get , 100%, using a midi split tick to push a green note. It is possible.
Found the method "un-friendly" gave up on it pretty quick.

[trogluddite]

The difference in usability is telling.

Cheers nix, interesting that it makes such a difference. I would guess that it helps because A) When going Ruby->MIDI, the timing accuracy is kept. B) MIDI triggers might get slightly higher priority than other green, so that poly voices etc. get good timing for live playing.

user's operations affecting a pure Ruby tick.

That's the root of your problem though - it's not a "Pure Ruby tick" because it's being converted to green.
To be sure of keeping totally accurate timing, everything has to remain Ruby right up to the point of sending the final MIDI data. Once you have anything going via green, all bets are off - because you are then back in the land of the low-priority green CPU thread.
It might be accurate if the ticks can be processed quickly enough, but the more green primitives you add, the more it could start lagging behind. We've seen that before with the old "ticker 1000" threads back in SM - many people made stuff that looked accurate when they were testing inside SM. But the timing usually went nuts as soon as they were in a host with loads of other processes trying to use the CPU at the same time.
The difference is that green ticks are just commands that get queued up and then done whenever the CPU is free - wheareas Ruby/MIDI are properly time-stamped events that always check with the clock before doing anything.
That's why my PPQ timer gadget has only Ruby outputs for the timing signals - and to guarantee keeping that timing, any sequencer that you connect it to would also have to be written in Ruby. You might get very close with green ticks, but it would be a matter of luck rather than design.

[nix]

Well it's my design anyway!
After noodling about with these schematics for a couple of days,
I've come to think my VSTs are more twitchy than they used to be.
Like not as solid in the host.
Possibly I'm imagining things,
but I have lots of weird stuff going on.
I have some results of timing tests.
I got my seq to render out as intended now.
It looks like this method is 50 to 130 samples out at 44.1k,
in the render.
My feedback timer was 7,
but ur right folk,
it was a bad idea to do it that way.
Used to stream counters I guess.
Maybe I will go for a rebuild in Ruby with the seq,
but I feel like making some music,
if only my plugs would hang in there.

[trogluddite]

Like not as solid in the host.

Hmm, I'm certainly more paranoid with my testing now.
I haven't had any problems once plugin are actually loaded, but it seems to take a couple of re-boots of Reaper sometimes before the plugin scan will accept them as valid - and if it doesn't want to accept the plugin, it just hangs and requires a CTRL-ALT-DEL to close Reaper down.
Hard to say if that is a FS only thing, but it's not something I ever saw before.

[nix]

OK,
I'm still battling with my 2 vsts,
some success.
hmm this issue of Ruby triggers pooling,
I wonder if it's causing some crashes for me.
For one thing which is undesirable,
when I open a list box, audio hangs.
The list box is the old one,
no Ruby.
I think my Ruby counters/triggers may be accumulating triggers when this happens,
leading to a crash when u have selected from the list.
This issue seems better with triggers which are not generated as MIDI.
I'm not really sure what's going on,
but audio is definitely hanging on my synth when I open a list box in the host.
hmm

[billv]

open a list box, audio hangs

If the list box is the "stock" sm selector, this may help.
If its the "custom' List Box then dis-regard post.
In the X11, there is not one drop down list selector or drop down
menu type selecter. I think i had that issue ever since the X1 prototype,
with audio glitch's happening when those drop down's get used.
There's are probably easy fixes for this, but I just by-passed the issue and used some other way.

[nix]

I set the preset mangaer mode to 7,
and that seems to have fixed it.
We'll see about the crash,
fingers crossed

[nix]

Yeah my stock list boxes are making the audio hang,
at whatever setting in the preset manager.
This is only on the sequencer, synth is running pretty good.
Also I discovered that if using a trigger thread on the sequencer index,
it will generate red links,
but only if the list box is opened.
It runs fine until touching the list box.
The thing that sets the 2 projects apart,
is the generation of played MIDI notes.
The sequencer is all green logic, creating MIDI.
I would like to use the stock list box,
but if there is no fix-
I'll maybe make my own control.

edit-actually the dropdowns are broken in the synth too. This is an environment issue, not something I have done.
Could we get a fix?