Release Candidate Firmware V1.20 RC5

[XORadmin]

Sorry if this has already been covered, but I have a bit of quick feedback that is hopefully easy to fix for the next release.

Launchpad Integration:
- No way to stop a pattern from playing via the Launchpad.
- Pressing an empty pattern below a non-empty pattern, in an attempt to stop the pattern, queues up the pattern above it.
- Default color for each track should be set to a dim gray, so it shows up on the launchpad by default. I had mentioned this earlier, but am just jotting it down again.  

Sequencer:
- Pressing OK on an existing pattern, replacing it with a blank, should be disabled while playing.  I have accidentally clicked ok a couple times during a set and had to scroll back and find what pattern was there before.

Launchpad Question:
- I am using multiple channels of MIDI out on my nerdseq, and noticed if I have the launchpad set to channel 1, channels 1-5 should also not be used as outputs as they interfere with the UI.  Not sure what to do about this, maybe it is a documentation thing.  Should these channels be avoided?

Thanks for the feedback...and just in time before my next (and hopefully final) release candidate which i wanted to upload tomorrow.
About your info:

- No way to stop a pattern from playing via the Launchpad.

Hmm, are you sure? The third button from the Bottom combined with a track should mark the track to stop. Doing it twice stops the track directly. That works with the other launchpads and i don't know why it shouldn't work with the LP Pro. Shift+STOP+a track, stops the sequencer.

- Pressing an empty pattern below a non-empty pattern, in an attempt to stop the pattern, queues up the pattern above it.

This is not a stop pattern situation. I don't remember that it would queue up, but i will test it tomorrow. I think it is a general question how it should behave. In my opinion i want to keep it mostly the same as nerdSEQ own behaviour.

- Default color for each track should be set to a dim gray, so it shows up on the launchpad by default. I had mentioned this earlier, but am just jotting it down again.  

I will give used patterns a DIM grey, but only if they didn't get a colour yet. I still think and say that it only makes real sense if using with colours.

- Pressing OK on an existing pattern, replacing it with a blank, should be disabled while playing.  I have accidentally clicked ok a couple times during a set and had to scroll back and find what pattern was there before.

Thats not the behaviour in the new version anymore. There is a thread about it and i took over the ideas so this can't happen anymore. I think the new approach is now much better and these issues are solved with it. But also, i advise to disable edit when playing a set. This also brings the direct jump function then which i always use intensively when playing live.

- I am using multiple channels of MIDI out on my nerdseq, and noticed if I have the launchpad set to channel 1, channels 1-5 should also not be used as outputs as they interfere with the UI.  Not sure what to do about this, maybe it is a documentation thing.  Should these channels be avoided?

I don't know. As mentioned before, i don't have a Launchpad Pro so i can't confirm the behaviour. (Still waiting for Novation to provide me one, so i can also give support for that one) The only thing the NerdSEQ does is to use Midi Channel 1 which seem to be channel-fixed in the Launchpad to control it. All other Midi channels i don't know about and you might refer the Launchpad midi integration manual for it to find out. With the LP integration i totally depend on what a LP can do and what not and keep in mind that this is still Beta and will also be beta until i make a proper USB expander for it.