CV Recording and Inputs

[Terekki]

With regard to CV recording and inputs, is there a way to preview/passthru the cvs that are coming into the inputs, so you can decide when to hit record? Kinda the same way that a midi keyboard works with the NerdSeq? I would like to record 4 channels of note CV from my ornament and crime into patterns to create variations that would be then sequenced. Have tried anything I could find in the manual with no luck.

thanks, T

[Marizu]

I'm on V1.21A

I don't think so. NerdSeq only seems to pass the notes through when record has been pressed.
You also have Live Quantise to consider, so Nerdseq wouldn't necessarily start recording as soon as you pressed record. I think that it would wait until the next Live Quantise point is passed.
I tend to create a 64 step pattern and record it until it loops. Then I remove notes from the beginning of the recorded pattern (and shift the following notes up) and set the pattern length to a length that I actually wanted. That way, my pattern starts at the correct place and has the appropriate length.
It would be handy if I could rotate the rows (eg. on a 16 row pattern, if you rotated down, then row 1 would go to row 2, row 2 would go to row 3 until row 16, which would go to row 1).

This approach works okay in some cases, but there are some problems with it.
Nerdseq doesn't seem to have an overwrite mode. This would be very handy for recording. If Nerdseq encounters a 0V it assumes that there is no note to record, so it leaves the existing note value in place. The same happens for recording triggers (the reliability of my trigger recordin depends on whether I have the NerdSeq synced to the other sequencer, or vice versa. Nerdseq master works best for me).
If I am recording a pattern in from my Generator+ sequencer and the NerdSeq pattern loops then some of the note and mod voltages will get overwritten as it loops, but triggers that were left over from the previous loop get left there. This means that the number of triggers becomes denser on each loop and my rhythms are wrong.

[Terekki]

I'm on V1.21A

I don't think so. NerdSeq only seems to pass the notes through when record has been pressed.
You also have Live Quantise to consider, so Nerdseq wouldn't necessarily start recording as soon as you pressed record. I think that it would wait until the next Live Quantise point is passed.
I tend to create a 64 step pattern and record it until it loops. Then I remove notes from the beginning of the recorded pattern (and shift the following notes up) and set the pattern length to a length that I actually wanted. That way, my pattern starts at the correct place and has the appropriate length.
It would be handy if I could rotate the rows (eg. on a 16 row pattern, if you rotated down, then row 1 would go to row 2, row 2 would go to row 3 until row 16, which would go to row 1).

This approach works okay in some cases, but there are some problems with it.
Nerdseq doesn't seem to have an overwrite mode. This would be very handy for recording. If Nerdseq encounters a 0V it assumes that there is no note to record, so it leaves the existing note value in place. The same happens for recording triggers (the reliability of my trigger recordin depends on whether I have the NerdSeq synced to the other sequencer, or vice versa. Nerdseq master works best for me).
If I am recording a pattern in from my Generator+ sequencer and the NerdSeq pattern loops then some of the note and mod voltages will get overwritten as it loops, but triggers that were left over from the previous loop get left there. This means that the number of triggers becomes denser on each loop and my rhythms are wrong.

did a bit of experimenting, it appears the live input to CV1 setting does pass notes through, but there has to be triggers defined in the pattern.

[Marizu]

did a bit of experimenting, it appears the live input to CV1 setting does pass notes through, but there has to be triggers defined in the pattern.

That's interesting. I haven't been using the Input 1 LIVE (except for transposition). I've only been using the Input 1 Record.
NerdSeq does tend towards equating voltages with triggers in a conventional note based approach.
In many cases, I just want to work with voltages. If I have a moving voltage coming into the sequencer, then recording that is not going to damage the recorded sequence. It is going to replicate it correctly. In fact, some of the most beautiful blips and nuances that I get out of pure analogue step sequencers come from changing the voltage during the note.

I wonder if my use case is in the minority. I rarely enter notes into NerdSeq manually. I tend to create sequences traditional analogue sequencer and then record the output into NerdSeq for performance, refinement or arrangement.

I need to write this up as a feature request.

[Terekki]

Same here, I tend to experiment with other more hands on sequencers, and record multiple takes/variants that can further be explored by clip launching on the Nerdseq kind of like how Ableton session view works.

[zerius]

Plug your cv/gate sources into each inputs, set up each ones of those into the input recorder menu on the set up / projet menu.
Then switch to ON the Live input.
You will be able to listen to your external keyboard / sequencer / sources without recording.
Then if you wanna record, the easiest way would be to set the Nerdseq as your Master clock then press record when you feel it right.
However I'm on the latest firmware, I don't know it you are on the same as mine.

[joesh]

Hi, we're way into the future (from when this thread started in 2020), talking about CV recording. I'm also trying to record my CV input, which I've done in the past by simply setting the CV input (as the above comment) with ON, and the CV1 input to QUANTIZE, and then I think just pressing play, if I remember correctly. However, I've just been trying this yesterday, and nothing seems to be recording on the chosen track/pattern!

Just to add that I can see the CV is coming in on the meters on the right hand side, so there should - I would have though - be some notes recorded, surely?

What have I forgotten to set up (in test version 1.28)?

[joesh]

Whoops, I forgot to switch on the Input 1..4 Recording .... now it works