Timing

[billv]

After a few days getting dodgy timing results, i went back to the start.

I first tested the "Is playing" module, to see if i can get at least get the first note on the money.
Using Green it fails everytime
Using Ruby it nails it everytime
(Note: the midi note is generated in Ruby for both tests)

ScreenShot102.png (44.92 KiB) Viewed 75767 times

Here's the one note test.

ScreenShot103.png (34.21 KiB) Viewed 75767 times

Attached to the stock "Arp" module, it's 100% accurate every time, just like (FL Studio)SM

ScreenShot104.png (50.05 KiB) Viewed 75767 times

So for me the Timing issue is finally dead.

So Support, after about a week on FS, instead of rambling on about how much I'm loving this FS thing,
I'll just say "THANKS".

[trogluddite]

Nice detective work Billy - another piece of the jigsaw falls into place!

[billv]

Thanks Trog.
Note in the example I'm using Midi note 60 for the first hit. This is wrong, as it will always
give you the wrong note on the first hit. ie: not the user selection.
The user selection in the ARP Module should be routed into this "midi note 60" position.
Should not be an issue. Its there waiting in green at the "Preset string" module.
Just need to extract it and route it back into the ruby "is playing code".

[nix]

I'd say you'll be making sequencers with Ruby,
but if any of the timing is turned into green, you can stop graphical changes glitching the audio by using a trigger thread.
I mean a notorious one of these for me was clicking on the VST's header or window.
Thanks for letting me know about this, I will be synced to host better.
All success

[billv]

using a trigger thread.

Never used it. Often wondered about it. Thanks for the tip. I'll stick it on a back-burner for now. Cheers.

[trogluddite]

Its there waiting in green at the "Preset string" module.
Just need to extract it and route it back into the ruby "is playing code".

Yes, the Ruby prim' behaves a little differently there - it stores the input/output state at save, and re-loads it at startup (like a green sample and hold). So Ruby never creates a "backwards trigger" to request values - you always need a trigger to 'push' the value into the input.

[billv]

So Ruby never creates a "backwards trigger" to request values

ha ha, that's probably why i failed with all attempted mods in last nights shift. Thanks
Trog, Did you keep working on your "PPQ" idea mentioned in the "accurate midi" thread?
A "Guru" version would be nice to help clarify this area completly

[trogluddite]

Not got far so far - too many new toys, I need to trim my list of ongoing projects a little bit!!

[billv]

too many new toys

I see what you mean. I'm just looking forward to getting this X11 2.0 update out of the way so i can start
mucking around. Malc and his mates have really done it this time with this ruby thing- just huge-enough to
keep us all very busy for years.......

[philton]

hey that are indeed great news billv- and one more BIG reason for me to get into that ruby stuff finally....
100 % Accurate VST timing....how many nights have i dreamed of that