Release Candidate Firmware V1.20 RC5

[Mat]

OK, i just updated to Release Candidate 3 with the following changings/ additions:

*Update RC3 *
- added fine delay for triggers. (Track setup). Triggers, Retriggers and FE (Trigger on) (only from trigger column) can be a bit delayed compared to the CV value. (Please be aware that it is possible that projects already saved with V1.20 might have trigger values filled in. You might have to reset these to 0 manually!!! No issues with old projects, Values of 0 turn the delay off).

Yes great update! Will these values in the future perhaps be mappable in the automation-menu, or maybe controllable through one of the inputs?

[XORadmin]

OK, i just updated to Release Candidate 3 with the following changings/ additions:

*Update RC3 *
- added fine delay for triggers. (Track setup). Triggers, Retriggers and FE (Trigger on) (only from trigger column) can be a bit delayed compared to the CV value. (Please be aware that it is possible that projects already saved with V1.20 might have trigger values filled in. You might have to reset these to 0 manually!!! No issues with old projects, Values of 0 turn the delay off).

Yes great update! Will these values in the future perhaps be mappable in the automation-menu, or maybe through one of the inputs?

No, these are especially for like sample devices where one sound is selected via the CV and fires the sample with a trigger.
You can use the automators already to get different trigger lenghts or delays. But this is for something else and fixed to a track.

[atimbral]

- added User Interface Screen in Setup!!!! Check it out yourself!!

This is truly great! It's so much easier to use with the new fonts. Many thanks for all your hard work on this!!

[StateAzure]

Ran into an issues last night with RC3. Was doing some live recording with MIDI IN, CV OUT (track set to modular). Was live playing Plaits using a CV and Trigger output of Ch.3, when all of a sudden no sound from Plaits..it looked like the gate/trigger got stuck or something because the little red dot on that channel stayed lit. Was ok after a reset though.

[XORadmin]

Ran into an issues last night with RC3. Was doing some live recording with MIDI IN, CV OUT (track set to modular). Was live playing Plaits using a CV and Trigger output of Ch.3, when all of a sudden no sound from Plaits..it looked like the gate/trigger got stuck or something because the little red dot on that channel stayed lit. Was ok after a reset though.

This sounds like a missing Midi Note-Off.(hanging midi notes).

So what is the Midi Master? And is it reproducable? And was it when playing live or when recording?

[grib]

Hi, I installed 1.20 RC2 and loaded a save-file from an older version (1.16 I think).

In the Automate screen there are some un-allowed values for some automation destination slots (see screenshot) and when I try to adjust these values pretty soon I will get an error as shown.  The Nerdseq locks up completely and doesn't respond to any keypresses.

If I clear the slot with DELETE it goes back to -- and I can then adjust it within the legal range with no problems.

Hey Grib,

would you mind sending me the project file so i can test it and fix the issue?

Hey, yes!  Sorry I'm out of town a few days but I will send it to you as soon as I get back to nerd central.

[StateAzure]

Ran into an issues last night with RC3. Was doing some live recording with MIDI IN, CV OUT (track set to modular). Was live playing Plaits using a CV and Trigger output of Ch.3, when all of a sudden no sound from Plaits..it looked like the gate/trigger got stuck or something because the little red dot on that channel stayed lit. Was ok after a reset though.

This sounds like a missing Midi Note-Off.(hanging midi notes).

So what is the Midi Master? And is it reproducable? And was it when playing live or when recording?

I couldn't reproduce it, but then I didn't have much more time to play last night.

I didn't actually record anything, I was just about to before that bug. So yeah, just live playing/practicing at the time. MIDI source Arturia Keystep.

Edit: Sorry. I actually think I did record a short loop of stuff when it happened. Because I remember pulling the trigger out, and I could hear the pitch changes on Plaits, as it doesn't necessarily need the trigger. So it did happen during recording and I was entering a fairly fast sequence of notes.

[Falafel Biels]

Well RC3 fixed my problem, thanks!

[Mat]

Wowow, thanks Thomas! RC3 is just brilliant. Really loving the colours/fonts
Thanks!

[the_cody]

OK, i just updated to Release Candidate 3 with the following changings/ additions:

*Update RC3 *
- added fine delay for triggers. (Track setup). Triggers, Retriggers and FE (Trigger on) (only from trigger column) can be a bit delayed compared to the CV value. (Please be aware that it is possible that projects already saved with V1.20 might have trigger values filled in. You might have to reset these to 0 manually!!! No issues with old projects, Values of 0 turn the delay off).

Yes great update! Will these values in the future perhaps be mappable in the automation-menu, or maybe through one of the inputs?

No, these are especially for like sample devices where one sound is selected via the CV and fires the sample with a trigger.
You can use the automators already to get different trigger lenghts or delays. But this is for something else and fixed to a track.

This is perfect for me! I use the Voltage Block kinda like patch storage and it needs CV just a tad before I send triggers to other stuff to get the right effect (as the CV input on the Voltage Block is a couple of milliseconds slow to change). I'd been doing this manually, but this will speed up my process considerably!! Thank you!!