+- XOR Userforum (https://forum.xor.eu)
+-- Forum: Products (https://forum.xor.eu/forumdisplay.php?fid=3)
+--- Forum: NerdSEQ (https://forum.xor.eu/forumdisplay.php?fid=6)
+---- Forum: General Questions (https://forum.xor.eu/forumdisplay.php?fid=17)
+---- Thread: Sending LFO/Envelopes out i2c (/showthread.php?tid=2111)
Sending LFO/Envelopes out i2c - skylab001 - 09-23-2026
I have an ER301 connected to the Nerdseq via i2c A bus. I've can send triggers from the Drummatrix tracks and Note on/off from the i2c tracks, so that is working. What I can't seem to figure out is how to get an LFO/Envelope/Automation or other continuous cv out of the Nerdseq via i2c. Can anybody walk me through the process? I feel like I've scoured the manual and YouTube but still can't get it working.
RE: Sending LFO/Envelopes out i2c - XORadmin - 09-23-2026
(09-23-2026, 05:31 PM)skylab001 Wrote: I have an ER301 connected to the Nerdseq via i2c A bus. I've can send triggers from the Drummatrix tracks and Note on/off from the i2c tracks, so that is working. What I can't seem to figure out is how to get an LFO/Envelope/Automation or other continuous cv out of the Nerdseq via i2c. Can anybody walk me through the process? I feel like I've scoured the manual and YouTube but still can't get it working.
Mapping screen:
Automator X -> I2C ..... Automator X is the LFO
Envelope X -> I2C.....
Keep in mind that I2C communication is just like Midi limited in bandwidth so you want to limit continuous signals as much as possible. They are ways to do that.
RE: Sending LFO/Envelopes out i2c - skylab001 - 09-29-2026
Thanks! got it working. Do you mind elaborating on ways to limit the amount of continuous data? I can see how the i2c bus can get overloaded.
RE: Sending LFO/Envelopes out i2c - XORadmin - 09-29-2026
(09-29-2026, 07:35 PM)skylab001 Wrote: Thanks! got it working. Do you mind elaborating on ways to limit the amount of continuous data? I can see how the i2c bus can get overloaded.
They are multiple ways, basically you could skip (have a counter and do skip if counter < 3 or something like that) the output to the I2C row multiple times which would reduce the data flow. You can go as high as your resolution is fine.
In the upcoming firmware version there is a dedicated mapping command for this, so you wouldn't need to build this with the function blocks.
ER301 got also own LFOs and Envelopes but you know that already ;-)