Release Candidate Firmware V3.0 RC5

[robs]

When playing a midi track in firmware V3.0RC2 to an external synth, the notes keep playing after stopping the track.
(it doesn't do this when previewing a note). It sounds a bit like the sustainpedal is active. When I switch back to V2.02A it works as expected.

[XORadmin]

When playing a midi track in firmware V3.0RC2 to an external synth, the notes keep playing after stopping the track.
(it doesn't do this when previewing a note). It sounds a bit like the sustainpedal is active. When I switch back to V2.02A it works as expected.

OK I got to test that again. Is there any special situation when that happens ( like transpose, scale ...). Do you press stop once and let it stop or do you stop it directly?

[robs]

When playing a midi track in firmware V3.0RC2 to an external synth, the notes keep playing after stopping the track.
(it doesn't do this when previewing a note). It sounds a bit like the sustainpedal is active. When I switch back to V2.02A it works as expected.

OK I got to test that again. Is there any special situation when that happens ( like transpose, scale ...). Do you press stop once and let it stop or do you stop it directly?

Thanks for the response. The track has CC's in the FX1 one colomn. And an LFO is modulating the note 3 probabilty. 
I do a restart and than press play on the sequence. After I hear the synth playing I press shift-stop. In firmware 3.0 it keeps playing the last note (the sequence contains long sustained notes) in firmware 2.02 it stops and fades out. In case it matters, the synthesizer is a Waldorf Blofeld.

[XORadmin]

When playing a midi track in firmware V3.0RC2 to an external synth, the notes keep playing after stopping the track.
(it doesn't do this when previewing a note). It sounds a bit like the sustainpedal is active. When I switch back to V2.02A it works as expected.

OK I got to test that again. Is there any special situation when that happens ( like transpose, scale ...). Do you press stop once and let it stop or do you stop it directly?

Thanks for the response. The track has CC's in the FX1 one colomn. And an LFO is modulating the note 3 probabilty. 
I do a restart and than press play on the sequence. After I hear the synth playing I press shift-stop. In firmware 3.0 it keeps playing the last note (the sequence contains long sustained notes) in firmware 2.02 it stops and fades out. In case it matters, the synthesizer is a Waldorf Blofeld.

Can you send me the project file please. In my situation the notes do stop as expected.

[robs]

When playing a midi track in firmware V3.0RC2 to an external synth, the notes keep playing after stopping the track.
(it doesn't do this when previewing a note). It sounds a bit like the sustainpedal is active. When I switch back to V2.02A it works as expected.

OK I got to test that again. Is there any special situation when that happens ( like transpose, scale ...). Do you press stop once and let it stop or do you stop it directly?

Thanks for the response. The track has CC's in the FX1 one colomn. And an LFO is modulating the note 3 probabilty. 
I do a restart and than press play on the sequence. After I hear the synth playing I press shift-stop. In firmware 3.0 it keeps playing the last note (the sequence contains long sustained notes) in firmware 2.02 it stops and fades out. In case it matters, the synthesizer is a Waldorf Blofeld.

Can you send me the project file please. In my situation the notes do stop as expected.

This is the file. It's just a testproject with different patterns. it concerns track 6, pattern 08 (named WALDORF)

  RS-02.NRD (Size: 442,41 KB / Downloads: 1)

[flel]

I am not sure if this got introduced at the RC, but when having the Launchpad connected and trying to navigate "up" using the "pattern >" button on the launchpad (Pro MK3) does not allow the cursor to go higher than the original position and I need to resort to the NerdSeq keypad to do this. Once I "reposition" the cursor to a higher position, this becomes the new "zero point" for the launchpad and its not possible to navigate higher beyond it. Unsure if a bug or intentional?

Also, the "top right button" on the launchpad does not take you back to the sequencer screen from the pattern screen (and the only way to exit the pattern screen seems to be using the nerdseq controls)

[robs]

When playing a midi track in firmware V3.0RC2 to an external synth, the notes keep playing after stopping the track.
(it doesn't do this when previewing a note). It sounds a bit like the sustainpedal is active. When I switch back to V2.02A it works as expected.

OK I got to test that again. Is there any special situation when that happens ( like transpose, scale ...). Do you press stop once and let it stop or do you stop it directly?

Thanks for the response. The track has CC's in the FX1 one colomn. And an LFO is modulating the note 3 probabilty. 
I do a restart and than press play on the sequence. After I hear the synth playing I press shift-stop. In firmware 3.0 it keeps playing the last note (the sequence contains long sustained notes) in firmware 2.02 it stops and fades out. In case it matters, the synthesizer is a Waldorf Blofeld.

Can you send me the project file please. In my situation the notes do stop as expected.

This is the file. It's just a testproject with different patterns. it concerns track 6, pattern 08 (named WALDORF)

I got the same issue when I sequence a VST piano instrument. When I play a midi sequence (in 3.0) al lot of the played notes stay on. You can see this illustrated in the VST. This explaines the sustained like sound.  I have to reset midi in the vst to undo this. But this only happens when there is note offset active in the track setup. When I use firmware 2.02 the notes don't "hang" and the note-offset doesn't matter. Hope this helps?

[DriesG]

OK I got to test that again. Is there any special situation when that happens ( like transpose, scale ...). Do you press stop once and let it stop or do you stop it directly?

Thanks for the response. The track has CC's in the FX1 one colomn. And an LFO is modulating the note 3 probabilty. 
I do a restart and than press play on the sequence. After I hear the synth playing I press shift-stop. In firmware 3.0 it keeps playing the last note (the sequence contains long sustained notes) in firmware 2.02 it stops and fades out. In case it matters, the synthesizer is a Waldorf Blofeld.

Can you send me the project file please. In my situation the notes do stop as expected.

This is the file. It's just a testproject with different patterns. it concerns track 6, pattern 08 (named WALDORF)

I got the same issue when I sequence a VST piano instrument. When I play a midi sequence (in 3.0) al lot of the played notes stay on. You can see this illustrated in the VST. This explaines the sustained like sound.  I have to reset midi in the vst to undo this. But this only happens when there is note offset active in the track setup. When I use firmware 2.02 the notes don't "hang" and the note-offset doesn't matter. Hope this helps?

I get those hanged notes as well, using Multio IO trs out.

Midimonitor (using Midihub) shows Note Off at vel127 for all notes on all channels. Seems like note off message always resets the velocity to 127, regardless of any value passing before that note off message. Not sure though if this is what’s causing those hanging notes.

Empty project, no mapping, offset or automation going on.

[XORadmin]

Thanks for the response. The track has CC's in the FX1 one colomn. And an LFO is modulating the note 3 probabilty. 
I do a restart and than press play on the sequence. After I hear the synth playing I press shift-stop. In firmware 3.0 it keeps playing the last note (the sequence contains long sustained notes) in firmware 2.02 it stops and fades out. In case it matters, the synthesizer is a Waldorf Blofeld.

Can you send me the project file please. In my situation the notes do stop as expected.

This is the file. It's just a testproject with different patterns. it concerns track 6, pattern 08 (named WALDORF)

I got the same issue when I sequence a VST piano instrument. When I play a midi sequence (in 3.0) al lot of the played notes stay on. You can see this illustrated in the VST. This explaines the sustained like sound.  I have to reset midi in the vst to undo this. But this only happens when there is note offset active in the track setup. When I use firmware 2.02 the notes don't "hang" and the note-offset doesn't matter. Hope this helps?

I get those hanged notes as well, using Multio IO trs out.

Midimonitor (using Midihub) shows Note Off at vel127 for all notes on all channels. Seems like note off message always resets the velocity to 127, regardless of any value passing before that note off message. Not sure though if this is what’s causing those hanging notes.

Empty project, no mapping, offset or automation going on.

Can you share the sequence that causes the hanging notes?

I fixed the reported issue which was related mostly to the note offset (Fixed also the note off 7f which is more a beauty thing). The 7f note off is by the way totally valid and not the issue for sure. In fact they are rarely any synths that do react on the note off velocity value. A Note on with velocity 0 is also a note off and many sequencer and midi keyboards use that instead to save precious communication bytes.

[XORadmin]

I am not sure if this got introduced at the RC, but when having the Launchpad connected and trying to navigate "up" using the "pattern >" button on the launchpad (Pro MK3) does not allow the cursor to go higher than the original position and I need to resort to the NerdSeq keypad to do this. Once I "reposition" the cursor to a higher position, this becomes the new "zero point" for the launchpad and its not possible to navigate higher beyond it. Unsure if a bug or intentional?

Also, the "top right button" on the launchpad does not take you back to the sequencer screen from the pattern screen (and the only way to exit the pattern screen seems to be using the nerdseq controls)

I can't reproduce the issue to go higher than the former position. In fact that was something that has been fixed in earlier versions. (Using a mini mk3 here)

The top right button in the Modular screen seem to be gone since after V2.0 when the whole launchpad and midi part was refactored. I did include it now for the release but this is still subject to change in the future.