The following warnings occurred:
Warning [2] Undefined property: MyLanguage::$archive_pages - Line: 2 - File: printthread.php(287) : eval()'d code PHP 8.1.24 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/printthread.php(287) : eval()'d code 2 errorHandler->error_callback
/printthread.php 287 eval
/printthread.php 117 printthread_multipage



XOR Userforum
Firmware V1.28 Test Version - Printable Version

+- XOR Userforum (https://xor-electronics.com/forum)
+-- Forum: Products (https://xor-electronics.com/forum/forumdisplay.php?fid=3)
+--- Forum: NerdSEQ (https://xor-electronics.com/forum/forumdisplay.php?fid=6)
+---- Forum: Firmware / Manual (https://xor-electronics.com/forum/forumdisplay.php?fid=11)
+---- Thread: Firmware V1.28 Test Version (/showthread.php?tid=1604)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13


RE: Firmware V1.28 Test Version - mgd - 08-09-2023

I've been playing around a bit with feeding MIDI CC from my Keystep Pro into the Mapping and stumbled over two things:
- the Keystep Touch Stripe (Modwheel, CC#9) is automatically mapped to CC#1 (could select Velocity) by the NerdSEQ
- all 7 bit controllers (#9, #74-#78) are shifted to the left by 5 bits (1 -> 20, 2 -> 40, etc.)

Am I supposed to fix this via the mapping, i.e. CC#9 actually being on #9 and all values RSFT by 5 or DIV by 0x20/32 (no problem, it's easy enough) or is that something the NerdSEQ will eventually "correct"?

Kind regards,
Michael


RE: Firmware V1.28 Test Version - XORadmin - 08-09-2023

(08-09-2023, 07:00 PM)mgd Wrote: I've been playing around a bit with feeding MIDI CC from my Keystep Pro into the Mapping and stumbled over two things:
- the Keystep Touch Stripe (Modwheel, CC#9) is automatically mapped to CC#1 (could select Velocity) by the NerdSEQ
- all 7 bit controllers (#9, #74-#78) are shifted to the left by 5 bits (1 -> 20, 2 -> 40, etc.)

Am I supposed to fix this via the mapping, i.e. CC#9 actually being on #9 and all values RSFT by 5 or DIV by 0x20/32 (no problem, it's easy enough) or is that something the NerdSEQ will eventually "correct"?

Kind regards,
Michael

The keystep and standard mod-wheel cc is #1. (as specified in the midi specs)

All values (if not notes) are suppose to be scaled to 12 bit aka 0-4095 and so also the midi cc values. Do the right shifts and you get the original value.
I think it is better and easier to work with scaled values as much as possible (except for notes), do for example max automator values, max CV in, max midi cc. etc is all 4095 and you can all replace them 1:1 as a source


RE: Firmware V1.28 Test Version - mgd - 08-10-2023

(08-09-2023, 08:44 PM)XORadmin Wrote:
(08-09-2023, 07:00 PM)mgd Wrote: I've been playing around a bit with feeding MIDI CC from my Keystep Pro into the Mapping and stumbled over two things:
- the Keystep Touch Stripe (Modwheel, CC#9) is automatically mapped to CC#1 (could select Velocity) by the NerdSEQ
- all 7 bit controllers (#9, #74-#78) are shifted to the left by 5 bits (1 -> 20, 2 -> 40, etc.)

Am I supposed to fix this via the mapping, i.e. CC#9 actually being on #9 and all values RSFT by 5 or DIV by 0x20/32 (no problem, it's easy enough) or is that something the NerdSEQ will eventually "correct"?

Kind regards,
Michael

The keystep and standard mod-wheel cc is #1. (as specified in the midi specs)

All values (if not notes) are suppose to be scaled to 12 bit aka 0-4095 and so also the midi cc values. Do the right shifts and you get the original value.
I think it is better and easier to work with scaled values as much as possible (except for notes), do for example max automator values, max CV in, max midi cc. etc is all 4095 and you can all replace them 1:1 as a source

Scaling all values to 12 bit does indeed make a lot of sense. I'll do RSFT when I need it Smile
[I already did and it works like a charm - I love the mapping table Wink ]

W/r to Keystep Pro Modwheel Stripe being CC#1 or CC#9:
If I read the documentation correctly it does send on CC#9. There's also the Arturia MIDI Control Center which allows to change the CC# of the Touch Stripe (aka the Modwheel; again if I understand correctly). However when I change that the NerdSEQ still reacts on CC#1 only. So there's obviously something I do not yet understand Smile


It really is great fun to play with these mappings. They open up a vast range of options to play the NerdSEQ and to interact with it in a live situation.

Kind regards,
Michael


RE: Firmware V1.28 Test Version - XORadmin - 08-10-2023

Modwheel is per midi definition always CC#1, believe me, also for the arturia ones (I just checked the keystep manual).
And beside the mapping the modwheel functions with midi input and recording are using always only #1.


RE: Firmware V1.28 Test Version - Cyber_Imp - 08-11-2023

VERY EXCITED TO TRY THIS THANK YOU!


RE: Firmware V1.28 Test Version - trevormeier - 08-11-2023

I'm having lots of fun with 1.28 so far. It's a huuuuuuuge leap forward for how usable NerdSeq is with the rest of my rack.

I'd like to see more MIDI options in the mapping screen - for example gates (note on/off) and pitch bend. I often use MIDI to send gates, and pitch bend would allow some interesting things with MPE controllers.

In the interim I've been using the four CV inputs to receive triggers/gates... but I've noticed that the CV inputs have between 1-3ms of jitter when mapping them to trigger outputs. That's fine for most CV but quite a bit for gates & triggers (there's also ~1ms latency which is expected). The issue compounds with the 1.28 mapping screen: converting gates at the CV input to MIDI CC seems to add a little bit of jitter, and MIDI receivers tend to prioritize gates over MIDI CC data, so even more jitter is added on the other end of the chain.

All that to say: if note on/off (& pitchbend!) were available on the mapping screen it would make the most of the limitations of MIDI.

This firmware is really a big leap for the NerdSeq. I'm having so much fun playing with it. Thanks for letting us use it before it's 100% ready!!


RE: Firmware V1.28 Test Version - vidret - 08-15-2023

Is this meant to take the place of the CV I/O in automators?


RE: Firmware V1.28 Test Version - Cyber_Imp - 08-15-2023

Is there going to be a way to save and load these sheets of mappings? Does this already exist and i'm missing it?


RE: Firmware V1.28 Test Version - Labrioche - 08-16-2023

Tried this firmware for a couple of hours and I must admit that I’m little bit confused. I’ve owned a Teletype for a while and was expecting some similarities with the Matrix Mapping. But I can’t figure how to do anything expect for listening CV in and send them to any outs. 
Anyone manage to do something musical with it? Here is some idea I can’t succeeded:
- sample and hold listening to a lfo and sending note based on a clock division
- same but based on trigger/CV ON of a pattern
- condition to launch a pattern once
That was some easy thing to make with the TT but maybe I’m totally wrong in my expectations on this feature. Anyway it looks promising but I’ll stick to 1.27 for a bit, waiting for more clever folks than me to share some recipes / tips on how to use this. 

Cheers


RE: Firmware V1.28 Test Version - mgd - 08-16-2023

(08-15-2023, 11:01 PM)Cyber_Imp Wrote: Is there going to be a way to save and load these sheets of mappings?  Does this already exist and i'm missing it?

You have read the very first post in this thread?

Thomas explicitly write:
Quote:- there will be mappings import/export in the final version (before you ask)
HTH,
Michael

(08-16-2023, 06:03 AM)Labrioche Wrote: Anyone manage to do something musical with it? Here is some idea I can’t succeeded:
- sample and hold listening to a lfo and sending note based on a clock division

Assuming the LFO is in Automator Slot 0:
Left side (Source) AUTM SLT0
Right side (Destination) wherever you want it to go, e.g. SETV V  A or CV [PTCH|NOTE] <output>
The logic for clock division is a bit trickier. You can trigger it from inside your pattern via XMAP or you need to do clock management "by hand" which probably is less desirable.

(08-16-2023, 06:03 AM)Labrioche Wrote: - same but based on trigger/CV ON of a pattern

Left side (Source) CV <whevever that pattern is writing to>
Rest see above

(08-16-2023, 06:03 AM)Labrioche Wrote: - condition to launch a pattern once

I haven't tried this but I guess it is
TRCK TRK1 PROW on the destination side and whatever provides a proper value, e.g.
VAR  #  A SRC as the source an VAR A would hold the pattern row number

In general playing around does help a lot. Don't forget, this isn't the released product, i.e. there's not yet a written manual etc.

HTH,
Michael