(04-25-2019, 04:04 PM)XORadmin Wrote:

(04-25-2019, 03:23 PM)LostForWords Wrote:

(04-25-2019, 02:55 PM)XORadmin Wrote:

(04-25-2019, 02:49 PM)LostForWords Wrote: How do you set the note lengths in a MIDI pattern? I'm probably being an idiot but I can't see any settings like the trigger value on a modular track. I'm setting up some notes and each one plays until the next note in that lane.

Just like with all the other tracks with either a note off or via the kill command. While Kill is in the FX section, note off can be archieved by deleting an empty field or the lowest note that you can set (One below C-0).

Please check the manual for it. This is stuff you really need to know to get everything out of the NerdSEQ. Using the trigger commands for the CV/Gate tracks is just one possibility to decide for Note / Gate length.

I'm fairly new to Nerdseq and to date have been using trigger length with my style of music. I will brush up on the other options. In this case I'd recorded some notes in from Marbles with just the CV-note input and manually added velocity values. I missed one so there was a note with no velocity. It was stealing and holding one of the Peak's voices each time it hit that note so I was getting never ending notes. Should a velocity be forced in such a recording case where note values are being recorded in over CV not MIDI? I can't add a note manually without a velocity value. MIDI appears to treat such a note (no velocity) as a forever note.

OK i see, i think it doesn't really make sense to record without using the gate. Midi doesn't know such a thing like note change. And thats what you actually do with only CV changings. However, i expect it to fill in a 7f as velocity anyway, but it seems like it doesn't do it.

Also with Midi (and thats with Midi in general), a note value has always also velocity information. Thats why you can't fill in a note manually without a velocity value. However, it looks like a missing velociy causes a illegal Midi note which causes to steal a peaks voice. I will fix that.

So for proper use: Record best with the gate, because then you get the note-off automatically. When recording from CV into midi, you manually got to fill in your velocity values until i fixed it. Thanks for the little bugreport 

(04-25-2019, 04:07 PM)LostForWords Wrote:

(04-25-2019, 04:04 PM)XORadmin Wrote:

(04-25-2019, 03:23 PM)LostForWords Wrote:

(04-25-2019, 02:55 PM)XORadmin Wrote:

(04-25-2019, 02:49 PM)LostForWords Wrote: How do you set the note lengths in a MIDI pattern? I'm probably being an idiot but I can't see any settings like the trigger value on a modular track. I'm setting up some notes and each one plays until the next note in that lane.

Just like with all the other tracks with either a note off or via the kill command. While Kill is in the FX section, note off can be archieved by deleting an empty field or the lowest note that you can set (One below C-0).

Please check the manual for it. This is stuff you really need to know to get everything out of the NerdSEQ. Using the trigger commands for the CV/Gate tracks is just one possibility to decide for Note / Gate length.

I'm fairly new to Nerdseq and to date have been using trigger length with my style of music. I will brush up on the other options. In this case I'd recorded some notes in from Marbles with just the CV-note input and manually added velocity values. I missed one so there was a note with no velocity. It was stealing and holding one of the Peak's voices each time it hit that note so I was getting never ending notes. Should a velocity be forced in such a recording case where note values are being recorded in over CV not MIDI? I can't add a note manually without a velocity value. MIDI appears to treat such a note (no velocity) as a forever note.

OK i see, i think it doesn't really make sense to record without using the gate. Midi doesn't know such a thing like note change. And thats what you actually do with only CV changings. However, i expect it to fill in a 7f as velocity anyway, but it seems like it doesn't do it.

Also with Midi (and thats with Midi in general), a note value has always also velocity information. Thats why you can't fill in a note manually without a velocity value. However, it looks like a missing velociy causes a illegal Midi note which causes to steal a peaks voice. I will fix that.

So for proper use: Record best with the gate, because then you get the note-off automatically. When recording from CV into midi, you manually got to fill in your velocity values until i fixed it. Thanks for the little bugreport 

No problem, I was just typing an edit to say when I go to edit the velocity from -- it starts at FE and works down so also when left at a value higher than 7F it causes problems. I'll know to avoid this now and the fix will sort it later.

---

Another small related bug : when CV input 1 and 2 (note and trigger) are directed to a Midi track the note value is going in to Note 1 and the trigger value is going in on Note 3! I know you'll fix Have a good Superbooth!

(05-24-2019, 06:41 PM)sascha12 Wrote: Hi oI iI’ve been wondering about the envelopes as well. That’s one of the main reasons I chose the Nerdseq, among others of course.

(08-06-2019, 02:09 PM)XORadmin Wrote: You can simply transpose all from the project menu. Shift up/down as usual for an octave and left/right for a semi-note.
Though, this update is already several months old :-)

(08-06-2019, 02:33 PM)Mat Wrote:

(08-06-2019, 02:09 PM)XORadmin Wrote: You can simply transpose all from the project menu. Shift up/down as usual for an octave and left/right for a semi-note.
Though, this update is already several months old :-)

Thanks! That one I know, although it would be mighty handy if it would be possible to transpose per octave. Then a simple precision adder could be patched into any of the inputs, and this way it would be incredibly easy to manually transpose separate tracks one octave up/down.

(08-06-2019, 02:46 PM)XORadmin Wrote:

(08-06-2019, 02:33 PM)Mat Wrote:

(08-06-2019, 02:09 PM)XORadmin Wrote: You can simply transpose all from the project menu. Shift up/down as usual for an octave and left/right for a semi-note.
Though, this update is already several months old :-)

Thanks! That one I know, although it would be mighty handy if it would be possible to transpose per octave. Then a simple precision adder could be patched into any of the inputs, and this way it would be incredibly easy to manually transpose separate tracks one octave up/down.

I think you’d try the latest V1.20 release candidate then. Because with it you could do this i think.