(12-07-2023, 03:35 AM)proxemics Wrote: [ -> ]Hi Thomas,
A question on pattern row and NRPNs. I'm just trying to understand what I'm seeing, because I think it would help me to see into how mappings work.
I have pattern with a BRK 000 on row 03.
In mappings I have TRCK TRK1 PTRW > MCON D-16 N--0
The values I'm getting look like:
[0, 0, 0, 0]
[0, 0, 0, 40]
[0, 0, 0, 84]
[0, 0, 0, 124]
[0, 0, 1, 40]
[0, 0, 1, 84]
[0, 0, 1, 124]
[0, 0, 2, 40]
[0, 0, 2, 84]
[0, 0, 2, 124]
[0, 0, 3, 40]
[0, 0, 3, 84]
[0, 0, 3, 124]
[0, 0, 4, 40]
[0, 0, 4, 84]
[0, 0, 4, 124]
[0, 0, 5, 40]
[0, 0, 5, 84]
[0, 0, 5, 124]
[0, 0, 6, 40]
[0, 0, 6, 84]
[0, 0, 6, 124]
[0, 0, 7, 40]
[0, 0, 7, 84]
In every case PTRW seems to yield about double the number of the actual pattern row in the MSB, and some ticks in the LSB. Row 00 shows four initial 0s, every normal row shows up three times, and whatever is the last row shows twice. So if BRK is on row 07, before reset the last numbers are:
[0, 0, 14, 40]
[0, 0, 14, 84]
[0, 0, 14, 124]
[0, 0, 15, 40]
[0, 0, 15, 84]
This all seems to be BPM independent. If you have a moment, can you give a hint as to what's happening here?
To start with, check out what values the command is generating. In that case the current row is scaled to the full range. Row 0-63 equals to the values 0 - FFF. But the rows are generated by the ticks which means that you would get also in between values instead of only 64 different ones. (you can scale that down of course if you prefer that)
Next is the output and what you see in your midi data is the NRPN Data which is 7 bit encoded per byte. It needs some bit shifting to decode whats going out there. In fact what it generates is the following: Row 0-63 equals the NRPN Data of 0 - 16336 (it's actually normally 16383 at max but the source precision is lower than that and this is the scaled value next to it). [0,0,126,36]
Thank you! It was the scaling that I was missing. I knew that CC scaled when converted to NRPN but somehow I didn't expect that a small, absolute number (0-63) would be scaled. That makes this easy!
Just a note, I had a blast last night playing with some turing-machine like functionality. The mappings logic is perhaps a bit esoteric (somehow reminds me a bit of programming in Forth!) but so, so powerful. What's great is to have this incredibly powerful tracker/sequencer for composition mixed with programability. I was able to build an improv on top of an already-composed base that sounded fantastic; doing the same thing either through DROID's approach or through modular setup would be essentially impossible. I don't know when you decided to add mappings, but that you were able to do it on top of what we all thought was a mostly-complete project shows that you must have a very well-organized code base, in addition to genius. Thanks so much for this work! I am indeed nerding out here. Hope to post some videos soon.
(12-07-2023, 03:37 PM)proxemics Wrote: [ -> ]Thank you! It was the scaling that I was missing. I knew that CC scaled when converted to NRPN but somehow I didn't expect that a small, absolute number (0-63) would be scaled. That makes this easy!
Just a note, I had a blast last night playing with some turing-machine like functionality. The mappings logic is perhaps a bit esoteric (somehow reminds me a bit of programming in Forth!) but so, so powerful. What's great is to have this incredibly powerful tracker/sequencer for composition mixed with programability. I was able to build an improv on top of an already-composed base that sounded fantastic; doing the same thing either through DROID's approach or through modular setup would be essentially impossible. I don't know when you decided to add mappings, but that you were able to do it on top of what we all thought was a mostly-complete project shows that you must have a very well-organized code base, in addition to genius. Thanks so much for this work! I am indeed nerding out here. Hope to post some videos soon.
Thanks!
I got basic mappings in my mind since many years actually, but was never happy with my ideas so far and the way how the workflow should be. I also had already since quite a while in my mind to add some coding possibilities...like smaller 16 lines codes which could be chained and executed from the sequence. When I started to sketch the mappings I wanted to have some features to put mapping values into a range. But that wouldn't fit into one screen and I wanted to stay in the screen for the overview. So I decided to combine the 2 ideas of mapping and code which results now in a much more flexible thing. Of course it can be complex, I am totally aware of it. But basic mapping is very easy and doesn't involve any programming skills.
My hope is actually to have some kind of a share base of cool mapping 'maps'. So if someone needs a functionality which could be made with the mappings, someone else could make and share it. Surely over the time some useful functions will pop up which I will add to the mappings. I am pretty sure it is able to make some cool generative stuff, too.
That said, getting back to work!
I just updated to V2.00A which includes these small fixes:
- fixed: execution of Trigger mapping destinations and screen glitch
- added: Midi Note + Pitchbend to mapping destinations
- added: force value to destination command for mappings so selected values will always be passed to the destinations
Also the release notes are now in the first post.
THOMAS, DUDE!! You are from another planet! .. The customisation of the new I2C/MULTI tracks are pure joy! .. and mapping the nerdseq is like building max for live devices for ableton!
And every nerdsequer: get the MULTI-IO. It's worth it, even without using i2c!
This thing is so sick, my brain is freezing!!
this is great.
the secret gem: cloning all marked patterns.
(12-04-2023, 07:35 PM)yrn1 Wrote: [ -> ]So it seems you can configure the i2c/multi expander even if you don’t own it, and then use the drum matrix with the old 2hp midi expander! Niiiiice!
Hi. Could you maybe explain a little closer how that is configured?
Is it thru "Mapping" or how do you connect the triggers in the drum matrix to midi?
(12-09-2023, 06:35 PM)Morim Wrote: [ -> ] (12-04-2023, 07:35 PM)yrn1 Wrote: [ -> ]So it seems you can configure the i2c/multi expander even if you don’t own it, and then use the drum matrix with the old 2hp midi expander! Niiiiice!
Hi. Could you maybe explain a little closer how that is configured?
Is it thru "Mapping" or how do you connect the triggers in the drum matrix to midi?
Just configure a track as multi io. Then you can map midi notes to the drum matrix in the track setup.
(12-09-2023, 06:58 PM)yrn1 Wrote: [ -> ] (12-09-2023, 06:35 PM)Morim Wrote: [ -> ] (12-04-2023, 07:35 PM)yrn1 Wrote: [ -> ]So it seems you can configure the i2c/multi expander even if you don’t own it, and then use the drum matrix with the old 2hp midi expander! Niiiiice!
Hi. Could you maybe explain a little closer how that is configured?
Is it thru "Mapping" or how do you connect the triggers in the drum matrix to midi?
Just configure a track as multi io. Then you can map midi notes to the drum matrix in the track setup.
Ahh, thnx
Just got it to work with my Mutantbrain, so now I have 11 drum tracks *yeay*