DSP Robotics Support

what exactly doesn't work?
left double click = create note, left down and drag = set notelength

works on both of my machines...

This is that 'double slider" type of control i was dreaming about.
great stuff nubeat7...thanks a lot mate....
Works good....interesting code too....Lots to learn from it...

works on both of my machines...

Ok, got it. My mistake. Its does work, but in a little tricky way. You have to set the length right at the time you draw the new note. Its cool! would love to test it in action.
A small suggestion: you could for instance to let the left mouse knob to control drawing\deleting (one click for draw, one click for delete) and let the right knob to set velocity and length (draging from left to right, set the length. draging up and down, set the velocity. it can even change color when setting velocity, lets say from light blue to dark blue )

Nice job here guy's. Really enjoying at the forum lately!

you are welcome billv, would make me happy if it could find a place in your x series

@kortezz
you always can set the length of the note not only when it is created, just create it with double left click (when creating the note the length is set to 1 quantization length by default) and then just set the length with holding left mouse button and drag it left or right...

about velocity with colors, i was thinking about this too, to set the colors individual for each note in relation to value would be a bit tricky and the user would't see the value very well only from the color, specially for colorblind people this wouldnt be very useful i think..

so i think special faders for vel are more useful and also more common, anyway you can use the x values from the noteAreas to generate your velocity faders with default values its no big difference to this code..

Nubeat7 wrote:would make me happy if it could find a place in your x series

no doubt it will...like a lot your other stuff...(i took a look at your ppq seq lfo again and
your advanced coding techniques done my head in ..still too hard to process and
I had to bail out again.)
Similar problem this morning when looked into this thing...
I spent half an hour with it...I still can't get an output happening.
I put a watch on lots of stuff to see what was going on....
I'll work it out .....it should fit nice into that alt design seq...
I've been looking at a grid idea , a 12 x 16 grid in one ruby module, programming wise
would give simple x,y co-ords to work with ...
And up top, for user control, I was thinking a "matrix trigger" type
( remember the old one myco re-built for me), so the user can can draw and 'splash' notes
all around real quick....buttons under all x and y arrays for quick rand, ect, ect ,.ect,
So many detours....what was i working on in the first place...

And in the meanwhile, continuing here the shape the "one note seq". Still no advanced midi between the midi out-midi to poly as I had some problems to understand the ruby clock, but finally, did it and put separate 3\4 beat support and simpler preset method based on integer arrays.

Having some problem here with the preset manager: when saving schematic and closing FS, the preset manager never saves the "before closed" preset to the memory. so, for instance, I always have to set it to preset 24, just to take care the first presets won't deleted.

Attaching the new schematic. It starts on preset 24, but please set it to preset 1 and you'll find nice guitar strumming in both 3\4 and 4\4 modes

kortezzzz wrote:some problem here with the preset manager

it's not the pm....it's my switches(that arn't finished) that your still using.
I deleted that timer set up i found in your preset modules..not needed..
You just need to push the sample and hold via index change from pm, and a afterload.

it's not the pm....it's my switches(that arn't finished) that your still using.

Thanks for the fix, mate. Works great here

Well, continuing riding a head! :

Two new features I'd like to add are:
1) increasing the cells amount from 16 (and 12) to 32 (and 24). I already realized how to increase it, but I will have to decrease the note cells graphic's size to make it usable. Couldn't find the exact part in the ruby code that is in charge of the size. any help would be appreciated.

2) The velocity-duration dilemma again: Each 1 note seq' has it's global velocity and duration that cannot be changed for each cell by midi manipulation. It must be determined at the ruby code only (like in the very first billv's schematic). So...
seems like I will have to port billv's sliders anyway to each note, but make a "edit" knob for each note that will show it's velocity and duration edit screen when chosen (kind of set of radio knobs maybe...). That's until Nubeat's routine becomes more functional (i have no idea how to port it my existing schematic as it has no outputs yet).

kortezzzz wrote:That's until Nubeat's routine becomes more functional (i have no idea how to port it my existing schematic as it has no outputs yet).

the output is not the big problem, but to get it alltogether..

i did some little fixes, added velocity faders which was a pain in th a... as i built it in a second module, so i had to update the velocity values in the note sequence too.. maybe it would have been easier to do all in one module.. anyway like this the overview is maybe better.

i still haven't built in some preset solution but it outputs some useful values, after i didn't study billv's sequencer too much i'm not sure which kind of values would be needed here but they could be converted or changed easily,

atm the sequence spits out the note position (notestart) in a 128th resolution - so you could use a counter with different speeds, and the resolution can be changed easily - the same goes for note duration or length (which is the length of the note and not the note off position)
and finally the velocity

so now you have an output and you can use and change it as you need

i did some little fixes, added velocity faders which was a pain in th a... as

atm the sequence spits out the note position (notestart) in a 128th resolution

Man, you've just kicked cubase's piano roll in the damn a...ss with this! Wow, this is explosive stuff! thanksss!
Must say, this seq's post, for me, is one of the best posts in both FS-SM forums. opens so many possibilities,
so many options and ideas. Unlike many other thing, very "beefy"! Wish it continue forever (or at least get a real DAW quality range piano-roll )

maybe it would have been easier to do all in one module.. anyway like this the overview is maybe better.

Yes. I can see the difficulties. Likewise, relaying velocity on color change instead of sliders (as I'v mentioned few threads a go) could leave the whole tweaking mambo jumbo in same window. Why is it good? because when the user is dealing with overlapping notes, he get overlapping velocity sliders as well... And any DAW user knows how annoying it is to tweak overlaping velocity\pitch\modulation sliders, when one is lying on the other. Color based velocity tweaking that can be performed by draging a mouse click on the note itself, could resolve this. Or... you know what? let's abandon the colors: the value it self (for instance 72, or any value from 0-127) will be shown inside the turned on note. How about that?

i'm not sure which kind of values

The sequence array values (1 output), velocity array values (1 output), duration array values (one output). This is the most important. In my opinion, tempo changes (for instance from 1\4 to 1\8) are overkill.