ruby keyboard

[Loopeytunes]

Ok so I've been messing around with the old selector/droplist arrangement and the new selectors/droplist that's using the new Ruby component. Using the new selectors/droplist seems to stop the audio looping upon interacting with the droplist

I've managed to fix the new Routing Matrix so it updates with preset change and using the selectors in the new routing matrix and the new selector (the one using the ruby code) does NOT cause the audio to loop anymore.

The only problem I am having is implementing the ruby code from the new selectors into the preset manager.

I know this may be a pain for people that already have projects using the old selectors/matrix/preset manager but it may be a possible temporarily work around for now?

[Nubeat7]

thanks nix for reminding me about the polyphonic situations!
i didn't regard to this, so i did a fast update (still without midi in yet) but it is able to show polyphonic playing too,

you can set the piano in latch mode now (turn note on and off with left mouseclick), you can set latch on in the properties..

it will now be possible to show poliphonic incoming midi notes too..

just updated the version in the first post...

[djbrynte]

so this will work now O: ? with old preset selectors?

[Nubeat7]

uploaded a wrong version! fixed now!

@brynte, it still has no midi in yet, and in general you should use ruby selectors.

also note that the keyboard is in early stage atm so no guarant that it is bugfree.. i did the last version here at work in between and its also not tested in reallife situations inside synths or vst's... but just test it

there will also be FS 3.06 very soon so lets see how things are working then

[djbrynte]

I know. And btw your doing great works nubeat. A ruby keyboard who can make that i mean. Thats + bro. I hope we can get it working for original selectors. Or i need to change all selectors even the preset manager

[Exo]

Ok so I've been messing around with the old selector/droplist arrangement and the new selectors/droplist that's using the new Ruby component. Using the new selectors/droplist seems to stop the audio looping upon interacting with the droplist

I've managed to fix the new Routing Matrix so it updates with preset change and using the selectors in the new routing matrix and the new selector (the one using the ruby code) does NOT cause the audio to loop anymore.

The only problem I am having is implementing the ruby code from the new selectors into the preset manager.

I know this may be a pain for people that already have projects using the old selectors/matrix/preset manager but it may be a possible temporarily work around for now?

I had forgot drop lists where added to ruby, if it works then that is a suitable work around. I think using a new thread in green might work too but cannot test that until tomorrow.

[Nubeat7]

midi in also works now, just had no time for testing it a lot

[nix]

awesome, will run it now.
I think it may be possible to live with this selector glitch.
I'm not going to change all my selectors to Ruby I guess.
Anyway, I'm trying to thread and get around it,
does this create a trigger thread?->

thread.png (11.86 KiB) Viewed 27146 times

There's some weird behaviour that will not allow a 'trigger thread' component
to open the old dropdown module

[nix]

little update.
This ruby threading method works!
Here is the working codebox->

thread_working.png (12.87 KiB) Viewed 27146 times

Here is a modified dropdown->

dropdown_fix.fsm

(1.33 KiB) Downloaded 1060 times

Cooool!

[Loopeytunes]

Your "thread" is to prevent loop repeating right?

If so then this doesn't work on any of the midi keyboards I currently have, the looped audio still remains.

So far the new ruby selector and routing matrix (with a little connection fix) works fine with no problems.

I'm near enough finished with the preset manager too, as soon as I have finished them I will upload them all in one schematic.