The Launchpad Thread

[Tenebris]

Nerds,

I just bought a Mini mk3. It is showing patterns and triggers, however I cant enter of remove triggers on the Launchpad? Pressing the trigger just moves the cursor to that trigger?

[XORadmin]

Nerds,

I just bought a Mini mk3. It is showing patterns and triggers, however I cant enter of remove triggers on the Launchpad? Pressing the trigger just moves the cursor to that trigger?

You got 3 different modes on the multi-io buttons for that. It’s a combination of the modes and buttons and ‘dial’ with the grid.

[deziben]

Dear fellow nerds,

I guess I may have found a bug in the Launchpad integration:

The NerdSEQ is running V3. My Launchpad Mini MK3 is configured as Pro Mk3-Host * and is working pretty well this way.
I have connected a Acid Rain Navigator fader to CV Input 1 in order to control the distribution of triggers using euclid. So I have made a mapping like this:
CV IN1 > TRCK TRK6 ECLD

The track is an ordinary Modular track where I only use the triggers.

In the following "sequencer page" and "patterns page" directly relate to the corresponding functions on the NerdSEQ that the Launchpad reflects.

In the initial state just after starting up the NerdSEQ the Launchpad still correctly shows the patterns on the sequencer page and the euclidian triggers when in the corresponding pattern page. Controlling the triggers also works as expected using the Navigator, and is also correctly reflected by the Launchpad when the pattern page is active. But The feedback from the Launchpad goes a bit havoc when the Launchpad is showing the sequencer page and the NerdSEQ starts playing (starting on the NerdSEQ itself).
In this case the sequencer page on the Launchpad is overlaid by the triggers from the patterns page as soon as I start to move the fader on the Navigator. I don't know if this is intended behaviour but this way, I cannot really identify anymore where my patterns are on the sequencer page. When stopping the NerdSEQ (stopping on the NerdSEQ itself), the patterns on the sequencer are not visible anymore but only the triggers, just if I where in the patterns page.

Note, that is only happens when external voltage is applied to CV Input using the fader to change the triggers. When controlling directly on NerdSEQ, the feedback is fine.

I think the expected behavior should be that the sequencer page does not overlay the triggers as soon as triggers where changed by external input. However, I could be an interesting idea to only do that temporarily as long the the external voltage is changing so there is some feedback how the triggers changed when on the sequencer page.

If additional information is needed to track this down just let me know.

[XORadmin]

Dear fellow nerds,

I guess I may have found a bug in the Launchpad integration:

The NerdSEQ is running V3. My Launchpad Mini MK3 is configured as Pro Mk3-Host * and is working pretty well this way.
I have connected a Acid Rain Navigator fader to CV Input 1 in order to control the distribution of triggers using euclid. So I have made a mapping like this:
CV IN1 > TRCK TRK6 ECLD

The track is an ordinary Modular track where I only use the triggers.

In the following "sequencer page" and "patterns page" directly relate to the corresponding functions on the NerdSEQ that the Launchpad reflects.

In the initial state just after starting up the NerdSEQ the Launchpad still correctly shows the patterns on the sequencer page and the euclidian triggers when in the corresponding pattern page. Controlling the triggers also works as expected using the Navigator, and is also correctly reflected by the Launchpad when the pattern page is active. But The feedback from the Launchpad goes a bit havoc when the Launchpad is showing the sequencer page and the NerdSEQ starts playing (starting on the NerdSEQ itself).
In this case the sequencer page on the Launchpad is overlaid by the triggers from the patterns page as soon as I start to move the fader on the Navigator. I don't know if this is intended behaviour but this way, I cannot really identify anymore where my patterns are on the sequencer page. When stopping the NerdSEQ (stopping on the NerdSEQ itself), the patterns on the sequencer are not visible anymore but only the triggers, just if I where in the patterns page.

Note, that is only happens when external voltage is applied to CV Input using the fader to change the triggers. When controlling directly on NerdSEQ, the feedback is fine.

I think the expected behavior should be that the sequencer page does not overlay the triggers as soon as triggers where changed by external input. However, I could be an interesting idea to only do that temporarily as long the the external voltage is changing so there is some feedback how the triggers changed when on the sequencer page.

If additional information is needed to track this down just let me know.

Hey, 

I reproduced the issue and it'll be fixed in the upcoming version.