Hello Thomas,
I notice a strange behavior when I map Midi-Notes and Gates to i2c Note- and Trigger-Ports on the ER-301
My Mapping text is
MIDi TC5 NOTE > I2C ACVS # 1
MIDI TC5 GATE > I2C A TR # 7
to send from Midi-Channel 5 from my Keyboard CV-Note and Gate-Information to a Synth on the ER-301
...it seems that the triggers do not work on MIDI-Note-On/Gate but on -Off and on Aftertouch and the Gate stays high after releasing the Note.
The Note-CV also does every here and there some very big jumps. Is this a known issue, you are working on, or am I missing something?
When (TR)igger is off, either '00' or '--', the CV change is still outputted as CV and Trigger are 'decoupled'.
This means when a sound has longer release than the step is long, the CV is also send and the pitch has changed.
My feature request would be (per track) setting, that when the trigger step if 'off' (either '--' or '00') that the CV out is also not changed. Not to break current pattern behaviour.
This mimics the settings of sequencers (like The Doepfer Dark Time), that the step is still part of the sequence, but the setting 'turns off' the output of new CV and Trigger together.
I'm aware deleting both will do the trig, but I'm looking for a quick way to 'turn off' a step in the sequence.
On the other hand, I also realize 'pre-programming' is more the way of NerdSeq than performance live and make changes.
Should these examples directly translate to ‘Groove’ setting in Nerdseq? From the looks of it, ‘6’ appears to be standard groove for both M8 & Nerdseq… not sure if this is common for all trackers? If so, I’m curious if others have found creative uses of ‘Groove’ that work well in tracks. Thanks!
When i map a CV Out to a CV16 Out, the tuning is not correct.
When i use the CV out (from the nerdseq), it's fine. Even when i patch the CV Out to a CV IN and map that CV IN to a CV16 track it's also totally fine.
So, it's not a calibration issue, but something else..
I’m greatly enjoying using my NerdSEQ with the More Video IO expander. An external keyboard really makes interfacing with the NerdSEQ a breeze.
It does appear that of all the keyboard bindings listed in the manual, one of them seems to be not working on my keyboard: Shift-F5 (load project). My keyboard seems to be fine, and unshifted F5 (current values) works as it should, so I’m wondering this is firmware based.
I actually noticed this a while ago, but using “print screen” for “load project” works fine, so it never bothered me.
I wanted to share my thoughts and concerns regarding the readability of the Nerdseq Manual, particularly from the perspective of someone diagnosed with ADHD. Please understand that this feedback is personal and may not be applicable to everyone, but I believe it's worth discussing for potential improvements.
Firstly, I'd like to express that I've found the Nerdseq Manual to be more challenging to read compared to some other manuals I've encountered. My intention is not to criticize for the sake of it but to provide constructive feedback that could potentially enhance the overall user experience.
One significant issue I've noticed is the absence of clear paragraphs throughout the manual. This lack of structure makes it difficult for me to focus on the information presented within a given sentence. As someone with ADHD, maintaining focus can be a challenge, and the absence of distinct paragraphs exacerbates this difficulty.
I've observed a notable number of RTFM responses within the forum, and it has raised the question of whether others in the community share similar concerns about the manual's readability. It's important to note that RTFM responses can be discouraging, especially if users genuinely find it challenging to navigate the manual effectively.
In my case, I've resorted to copying and pasting the necessary chapters into a word processor to manually add spaces and paragraphs. While this workaround helps, I believe a revision of the manual to improve readability could be a worthwhile investment of time. It may not only assist individuals with ADHD but also contribute to reducing the frequency of RTFM questions.
I understand that this feedback is subjective and may not apply to everyone. If my experience is an isolated case, I apologize for any inconvenience. However, if others in the community share similar sentiments, I believe addressing these concerns could lead to a more accessible and user-friendly manual.
Thank you for considering my feedback. I appreciate the effort that goes into creating and maintaining the Nerdseq Manual, and I believe that small adjustments could make a significant difference for users like myself.
I have my Nerdseq set up to trigger each pad of Lyra-8 using an external trig to s-trig converter.
Doing this works great with Nerdseq Trig expander, using Ext trig 1-8. On an external trigger track, FE then 00 starts and stops the gate correctly. After FE, stopping the sequence also stops the gate.
However, when I use a Patch to try and stop the gate, applied to the same row as FE, Kill Note 0001 through 0FFF does not work to stop the gate during playback. In the Patch, Trigger set to 0000 also does not stop the gate.
I feel there’s something I’m missing to stop the gate without using 00 gate off in the main pattern, as I’d like to randomize the pattern.
I’m looking to have a pattern full of FE in different lanes, randomize, and use Patch each time FE is triggered to stop the gate say after 3 seconds. Any help is appreciated. Thanks!
Cause I'm recording a lot into patterns, it would be cool to have a button combo to clear the whole content of the selected pattern. Maybe shift+mark+delete ..
I can do shift+mark+down+delete and that's fine, but then when i change the pattern the cursor is always at row 63 and i have to go back to the beginning. It's not the end of the world, but when jamming it's a little slow..
Here's my idea for some conditional funkiness / generative beats. Where a typical beat will play with a chance of the kick or snare deviating to an adjacent step.
A counter is being clocked by the global clock output.
I'm using Trig 4 to reset the counter every 8 steps (but it's cool to mess around with different lengths/rhythms for different meters/variations).
Kick will trig on step 1 with a probability of instead trigging on step 8.
Snare will trig on step 5 with a probability of instead trigging on step 4.
The sum of these two trigs will choke another trig, in this case a breakbeat that's cycling between slices on each trig, and there is some probability on it.
I'll eventually explore mapping the probabilities to midi cc. but this was enough to wrap my head around.
The attached mapping does (since the update to V2 ) create arbitrary Lucas Sequences, or more precisely the modulo values of such sequences.
The possibly well known Fibonacci series is one of many different Lucas Sequences.
In general a Lucas Sequence is created by the following formulas:
U(n) = P * U(n-1) - Q * U(n-2)
V(n) = P * V(n-1) - Q * V(n-2)
and U(0) = 0, U(1) = 1, V(0) = 2 and V(1) = P, P and Q are whole numbers.
U(n) and V(n) are the n-th members of the series and U(n-1), U(n-2) and V(n-1), V(n-2) are the two preceding values.
Both U(n) and V(n) very quickly can get very big. One way to limit these numbers is applying the modulo function (MOD) to them. For this mapping I'm computing a slightly modified version of the above formulas. It can be shown that if
a = b + c => mod(a) = mod(mod(b) + mod( c ))
and
mod(a) = mod(m + a) and m being the divisor of the modulo function
[the last line means, you can add the divisor m to a number w/o changing the result of the modulo function; that trick is used in the mapping to save a few lines of code]
The mapping makes use of 3 sliders from a F8R, Sweet Sixteen mkII or a 16N (whatever is available) connected via I2C to the Multi I/O Expander:
Slider 1 sets P from -32 to +31
Slider 2 sets Q from -32 to +31
Slider 3 sets m from +1 to +61
This results in 64*64*61 = 249856 different pairs of U(n)/V(n) series.
Using larger ranges for P and/or Q would require to reduce the range for m (and vice versa) because these are multiplied and the math in mappings is at most 12-bit.
The mapping is invoked by placing one of
XMAP 004 for a set of new U(n) and V(n)
XMAP 005 for a new V(n)
XMAP 007 for a new U(n)
in the FX column of a pattern.
Attached is the mapping file in its current and to the best of my knowledge functional state as well as an annotated listing of all the commands. The previous annotated listing contains a few rows that don't have a Row number in front of them. These are the lines that were missing from the initial V1 to make it functional as intended. V2 has these lines included and removes all the code that did compute MODS.
I tried to explain the algorithm. Feel free to ask any questions.
I also tried to make it as dense as I could. If you spot places where the mapping could be shortened I'm eager to hear about them. Last not least while I did do some testing (and I do think the mapping works) there obviously might be some undetected errors. If you spot any errors please notify me about them.
Update for NerdSEQ Firmware V2.01:
Thanks to the new MODS function I could reduce the number of lines by 24!!!
It is now working. For those interested in the evolution of the script I left the initial and non functional commented version attached to this post. Version 2 leaves quite a few lines that could be used to add additional generative functionality. Feel free to improve on the code (and I'm happy to hear if it is useful for you one way or another).
) create arbitrary 