pattern sequencer; possible with Ruby?

[tulamide]

I don't see why we need more than 1 midi to poly module. each 1 note sequencer has it own midi out. they all can be sent to the same midi to poly module, don't they?... am i missing something?

I'm not sure if we're talking of different situations. It's just that in my tests with 'Note Event' two notes of the same midi key (but different lengths/velocities) were cut to the shortest of both. And it didn't make a difference if they were sent on different midi cables connected to that one 'Midi to Poly', or on one midi cable. It only worked with two midi cables going to two 'Midi to Poly' modules. But maybe it is of no relevance for this project.

[kortezzzz]

And it didn't make a difference if they were sent on different midi cables connected to that one 'Midi to Poly', or on one midi cable. It only worked with two midi cables going to two 'Midi to Poly' modules. But maybe it is of no relevance for this project.

Ok, Thanks for the info tulamide. Maybe Its not relevant in this project, which is GREAT just as it is.

billv
Thanks, Thanks for the fix. Works really great. Wish I could code to help you, guys, but this Ruby stuff looks harder than chinese to me maybe the next update will deliver some midi surprises that will make life easier. According to exo, there is a bunch of them coming soon' so maybe midi is in the list.

[billv]

It only worked with two midi cables going to two 'Midi to Poly' modules. But maybe it is of no relevance for this project.

Yeh, that works. But to be avoided.
We cant mix those signals downstream, until we get to mono..so
we got 16 seq's, into 16 midi to poly...followed by ..you guesed it...16 synths...until
you can maybe bus them into one fx unit......so it's back to square one.
It's 1 midi to poly or ..... .

[trogluddite]

It's just that in my tests with 'Note Event' two notes of the same midi key (but different lengths/velocities) were cut to the shortest of both.

Yes, that's perfectly normal - it's not an FS limitation, just how the (very old!) specification for MIDI works. It was designed with keyboard playing in mind - to play a second note of the same pitch, you can't do it without releasing the key first, so MIDI does not allow for two overlapping notes with the same note number.

It only worked with two midi cables going to two 'Midi to Poly' modules

Unfortunately, this has difficulties too. It works OK if your M2Ps are feeding two completely separate poly synths and then mix the audio at the output (i.e. a 'blue mono' mixer after the voices are summed). But if you join their 'poly' sections together it can lead to problems with the voice and envelope management.

Trouble is, MIDI has been too successful - there are other standards like OSC that could be adopted, but no universal standard for sending over hardware has ever been agreed - so we're stuck with a nearly 30 year old, low resolution and relatively slow standard to work with. It really holds back sequencer and DAW development

[kortezzzz]

Yes, that's perfectly normal - it's not an FS limitation, just how the (very old!) specification for MIDI works. It was designed with keyboard playing in mind - to play a second note of the same pitch, you can't do it without releasing the key first, so MIDI does not allow for two overlapping notes with the same note number.

Agreed about the format limitations. That's bad, but this is what we got right now, and we should win with it.

billv, would be great if we could have also a custom note duration that rises from 0 to 1 in steps smaller than 1\1,1\2,1\4 and etc. can it be done? Another interesting feature would be porting MyCo's midi file player to this sequencer somehow

And had i said that I realy love this sequencer?

[billv]

custom note duration that rises from 0 to 1 in steps smaller than 1\1,1\2,1\4 and etc. can it be done?

I take it your thinking about 'quantization'..???..not sure yet..will have to be looked at
eventually. I think PPQ is more important at the moment, while I can sort of work around it,
by automating the process a little, most people don't, and require proper PPQ.
I think/hope Trog/nubeat7 or someone will have to bail us out in the end...

MyCo's midi file player

...yeh,that was great...havn't re-downloaded though since my last crash... ..
Hope he's still working on it....

And had i said that I realy love this sequencer?

Cheers mate.

[billv]

Agreed about the format limitations

But your other idea still works... .. Here's an alt version,
16 one-note seq with independent timing, velocity, duration and octave.
Some master controls to help manage it all...
...now we got CHORDS...much more musical...
I did it horizontal to help me think piano roll

Test_Ruby Sequencer_Alt Design.fsm

(378.46 KiB) Downloaded 844 times

There were some high cpu spikes...but they seem to be gone....

[kortezzzz]

WOW man. Excellent! ported a nice drumkit to it, and it sounds great!

Still would like to say few words about the advantages of using a single note sequencer inside a schematic, instead of full notes range sequencer (what we actually have now):

1) When I use a single note sequencer in the project, although i have to copy-paste it 12 time (or whatever number of note i desire to use) and connect it with the same number of midi wires to the midi2poly, I GET A FULL MIDI CONTROL ON EACH NOTE SEPARATELY. I can for instance filter its midi channel output and by that, send the kick sequence to channel 1, the snare sequence t channel 2 and so on, and viola! we have a multichannel instrument!

2)I can determine velocity, duration, "mute mote", "solo mode", keyboard split mode" and more by manipulating each note's midi section.

3) I can decide how many notes to use (by copy-pasting some more sequencers) and also to decide where to sent it's midi signal instantly. (makes life much easier when working on new concept).

billv, I know you worked hard for this, but please, would you try to make a "reduced version" of only one note sequencer? in that case, velocity and duration modules are not even necessary! .

Thanks!

[kortezzzz]

And almost forgot: the single note sequencer needs the ability to edit the note's pitch (for example, to change it from note 36 to note 39. can be done by porting to it a simple string input).

[billv]

Here's a stripped down 1 note seq, that might help to get you started.
Check properties panel for controls...

One note Seq.fsm

(7.57 KiB) Downloaded 879 times