[ Following up with @Mickey from previous thread. ]
I confirmed that the velocity / level slider works from TR mode. This is a huge deal in terms of usability and appreciate the bug fix.
In this mode, however, I ran into a weird screen that I’ve never seen before and cannot reproduce. In BankE, TR-Mode, hitting shift-[desired step] I can reliably switch between the sequencer view (all tracks and a few bars) or the step tweak menu (list view of midi parametres). That is the behavior described in the manual, all good.
Somehow I got to a screen that looked like the step edit page for the sampler tracks. Envelope was a dashed line with no cross bar, though level and pitch worked really nicely. Filter and Slice sliders appeared to be functional, but I didn’t tweak on them. This seems like a cool feature if that is something you’re playing with behind the scenes? If that is part of the OS, I would love to know how to reliably get back there.
The weird bit was that the green led steps turned red, only for the steps that had seen this window. I clicked in and out of TR mode and this was gone, and I couldn’t get back.
I will take photos / video if I’m able to reproduce this. Thank you.
Hey @Mickey - I have some time set aside tonight to play with a soundfont drum kit controlled with a MIDI track. I’ll report back if I see it.
I did see red and orange TR triggers last night that appeared in the mute/solo HW row, but not in the piano roll. That seems related to at least some of the above. I’ll capture what (if) I see tonight.
Hey @Mickey - I encountered the sample step edit screen from bank F again. I couldn’t get back to it. I was entering steps using TR mode and the level fader. I’m on the first DSP fw and will update this week hopefully (had thirty minutes to mess around today). This is FYI, hitting back got me out of the screen, and may be gone in more recent fw.
The updated MIDI TR sequencer looks like it will play nicely with my Nord Drum. Having the CC on the knobs and faders really wakes it up.
The step edit screen has not changed in a while. Whatever this bug is, it likely has nothing to do with DSP and has been in the firmware for a long time.
