pattern sequencer; possible with Ruby?

[billv]

Thanks for updating your fsm Nubeat7.
Its got pro seq behavior. ..will be fun challenge for me
one day...have to change my clocking system from int
to floats, to handle custom note lengths & pos.
Have to change the whole way Im doing things.
Please don't be offended if I keep building 'toys' just
a little while longer.

[kortezzzz]

which kind of values would be needed here

@Nubeat,

played with it half an hour before going to work, and I have some highlights to share:

1)I thought about that again and realized that the when you cover few cells with a long note, for instance, the first note covers the 3 first cells, then it should be forbidden to draw a new note in cell no. 2 and no.3, and this is for avoiding overlapping of the same note in the sequence. even if the long note doesn't covers a cell completely, but only partially, the partially covered cell would be forbidden to draw!. You can overlap 2 different notes (lets say, note 54 and 72),but never overlap the same note (let say, long 54 note with short 54 notes during it). So the best solution would be limiting the drawing according to the notes length.

2)When outputing array that should be sent to midi, the array must contain the zero's as well that represent the gaps between played notes. As I see now, your code outputs an array with the played notes only, with no gaps.

3)To implement the arrays in midi, we need the pitches and the velocities only. duration doesn't needed to be sent to midi because its determined in the ruby code and comes as is. there is nothing useful that midi can use duration information for. But... we should output the duration for only one reason: to keep it's array in a preset.

[Nubeat7]

have to change my clocking system from int
to floats

yes i was taking care of this, the note start positions are always int values as long as you use quantization which works with 128 (128/16, 32, 8 ....) the tricky part is to use rythms like 3/4 in this case the output resolution would be needed to changed to a multiple of 12 (which would be 96 for 16th notes then instead of 128 - if i`m right, this always confuses me) also the clock needs to be setted to 96 ticks per round then..

about the length, this needs to be converted to sec, which also shouldn`t be a big thing...

this is just one way to extract values you can change them however you need them with the 'getNoteParam' methode where you transform the note Areas values to usable note Parameters...


i didn`t thought to much about all this, because the focus was on getting the gui to work, the rest is just transforming values as you need it to fit your needs

this is also why i dind't implement the preset sysztem yet, as you need to transform it back into areaValues then using some methode like getNoteAreas or so...

the next challenge would be to make the gui for more then one note (pitch), i will see when i will find time for this

[Nubeat7]

@ kortezzz
1) overlapping the same note doesn't make any sense at all because both notes will be stopped with the first note off signal and if i'm right if one note is played you cannot trigger it a second time anyway (or does it do? )

2) this is depending on the system you follow, you also can trigger the note if it's equal to the counter or clock position, like this you need only the notes which should be played in the array and not the fulll pattern length which would get really big if you have 128 notes * 256 (for 64th resolution) its a size of 32768 for one pattern which need to be saved in a preset!

anyway you easily can integrate the array in a 'full sized' array if you need it this way..

3)just add the the pitch to the array this dont need to be done inside the gui as long as it is just for one note, you can name each 'note line' with its pitch nr for example...
and you will need the duration after it marks the noteoff event!

so including the pitch you have all parameters you will need to generate notes in a timeline system...
you are welcome to improve and / or change the schematic as you like or need it, its free to use

you also can pm me if you need customized ready solutions

[kortezzzz]

cannot trigger it a second time anyway (or does it do? )

You can't. Trog said that at my other thread. Midi format has it's limitations, so it better to avoid that kind of "adventures". As i said before, there is a the "velocity sliders" challenge as well: if you desire to tweak the whole octave's velocity ranges, you end up with "overlapping velocity sliders" as well, that sit on each other...
so that why, IMO, velocity should be set with (somehow) dragging the mouse on the cell itself. in that way, no sliders needed anymore.

you also can trigger the note if it's equal to the counter or clock position

Oh, sorry. didn't know about this method. Was sure that the only way to make it work is with a full array.
This only strengthen my conclusion: I never be able to code...

you are welcome to improve and / or change the schematic as you like or need

I can only dream about it

you also can pm me if you need customized ready solutions

put an eye on your massage box

[billv]

i didn`t thought to much about all this, because the focus was on getting the gui to work, the rest is just transforming values as you need it to fit your needs

this is also why i dind't implement the preset sysztem yet, as you need to transform it back into areaValues then using some methode like getNoteAreas or so...

the next challenge would be to make the gui for more then one note (pitch), i will see when i will find time for this

thanks mate...don't hurry/rush yourself on my part..
.

the note start positions are always int values as long as you use quantization

that's why I'm focusing on float...get that human feel...i figure int will be no issue

[billv]

Hey guys, here's my new Seq.
This is a quick mock-up..
Working great in host, but still lots to do...
Bear in mind ruby/draw modules in this are not finished....please ignore them...

Test_Main timing system_v2.fsm

(343.67 KiB) Downloaded 1033 times

[gvalletto]

I wish ruby was a little more approachable tool or at least graphically formed. There are so many beneficial
uses to this language that would cause to many amazing projects birth (mainly midi projects) but it seem like
most of us will never devise them and they will remain an unattainable dreams.

Hi kortezzzzz,
I think the same as you. If you are interested yet, you can post in this topic:
viewtopic.php?f=2&t=3234

Regards,
Gustavo