Firmware V2.0C

[XORadmin]

Hi Everyone and Thank you for all the hard work Thomas!

I'm only scratching the surface of what's possible with V2.0A but still, it's very exiting. If you know of any resources / threads to help explore what's possible please give us some pointers below.

Just few things I am noticing that don't work as one would expect, perhaps a bug or something missed ( possibly by me...)


Thank you !

1. I have another sequencer patched into trs midi in (Note and gate) on multi I/O, mapped to CV - Note - CV 3 and gate on trk3 as well. What comes out of track 3 is 2 octaves down and only sound like original sequence when I transpose the track 24 semitones up.

That is what your sequencer patched to the Midi in does. It sends the sequence 2 octaves down (which limits it also to less available notes).
The NerdSEQ can compensate these. See manual page 123. This applies to the general Midi -> Track assignment. Mapping Midi data is passed 1:1 and a C-0 is the Midi mode number 0 received into the mappings. If you need to offset that you use the calculation functions.

Side note: How would I go about applying some logic or adding / substracting if I had another sequence on TRK 3 in Nerdseq ? it plays nerdseq step only if nothing is present on midi in atm.

If there is something playing on the track it will just play as well or the part you play over it through midi.

2. Transposing a track also affects MOD output not just CV out as one would expect. It was very handy to have C3 being 0volt so that one could use negative values for something else then positive such as send levels to two diferent fx. When Mapping MOD output to i2c however what comes out seems to be only positive voltage. also If I send a value on the same port from my fader bank it get's stuck on whatever faderbank sent last as oposed to updating when reaching a step with different value in a sequence.

Transpose affects notes from the CV/MOD which is what I would expect. I don't know what you mean by negative values. Do you mean negative values if you have the offset switch to the left? Those are not recognized by the NerdSEQ and doesn't generate negative values. All the data created is always positive (eg. MOD from 0-10V / 0-FFF) and the offset switches just subtract 5 volt hardwarewise from it.
I2C uses positive values and if you need to offset it somehow then you either use the add/subtrack functions or the destination would be the one which should take care of this.
Please explain your issue with the fader bank vs the updates.

3. i2c port B doesn't seem to have option to send TR ( trig) as you get on port A. What that means is that if want to trig stuff using i2c and plug faderbank to the front (port A) I can't control internal parameters on nerdseq from faderbank at the same time as i2c port A needs to be set up to OUT to send information to er-301 in my case. If I could use port B at the back to trig drums it wouldn't be a problem but merge or any other option on port A doesn't seem to do it.

Oh yes I missed that one. Integrated with the maintenance release. It suppose to be there of course. A and B should be equal.
Merge is for the incoming data merged to the other output.

4. new i2c track type would be even better if first column was a regular trig colum with all ratchet options etc. otherwise it's just like more cv track / not very useful if you want to trig and seuence notes and control few parameters from one track... it gets confusing having stuff accross different tracks.

You can send basic triggers but adding the use of the full trigger commands is surely a possibility. You could define also some trigger types with the matrix and should be able to fire them from the columns.

5. I might be missing something and it's not really new FW thing but is it possible to have trigs disapear when I delete a note value ( autofill in reverse) it gets reall frustrating to jump columns to get rid of trigs when writing a sequence...

It was requested before but I got to see how I would implement this. Because I think this shouldn't be a standard setting and maybe it would also be a thing to clear the whole row directly. On my list to find a good solution.