(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!
Yes, while implementing it and also adding the Midi and Trigger16 features I thought it would make sense. It wasn't like this in the first place.
Still in good hope that there is need anyways for the expander :-)
So sorry it still takes until tomorrow for the release notes. I had a bit of work overload and still plenty of things to do.
(12-04-2023, 10:54 PM)XORadmin Wrote: [ -> ]So sorry it still takes until tomorrow for the release notes. I had a bit of work overload and still plenty of things to do.
Look after your health and get some rest. We can wait another day :-)
(12-04-2023, 06:06 PM)XORadmin Wrote: [ -> ] (12-04-2023, 05:58 PM)st3rk Wrote: [ -> ]I love the encoder, it adds a lot to the ergonomy! I would find very useful to be able to change the note using the encoder; and play it at the same time using the "ok" button. But it seems to trigger wider note jumps. Is it expected?
Thank you again for all you work Thomas, it's crazy how much you expanded the functionalities.
But I think that is what it does. When you hold OK then it trigger each time you turn the encoder (on the note column) in mode X. In Mode Y it triggers only on OK hit.
Indeed! I was trying to push the button repeatedly, but keeping it pressed works perfectly! I love it, it give it a mode hands on interface.
We can also address the CV16 expander in the modulation matrix, it's like christmas
Is it normal for new notes in a pattern to have Ratchet X1 instead of a short trigger by default in the new V2 Firmware? Is anyone else seeing this? Thanks.
(12-05-2023, 01:44 PM)Terekki Wrote: [ -> ]Is it normal for new notes in a pattern to have Ratchet X1 instead of a short trigger by default in the new V2 Firmware? Is anyone else seeing this? Thanks.
Yes, I changed into that as it makes more sense
OK, I found a little bug which slipped in last minute. The Trigger Mapping destination is not completely functional as expected, The TRG* and VAL* should always be executed regardless of a change but they are now executed on change only just like the others without the *.
Will be fixed in the first maintenance update tomorrow.
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?
