Flash mode clips don't end if you scroll away and release the button in flash mode

Bug reports
1

Summary: Flash mode clips don’t end if you scroll away and release the button in flash mode

Submit Date: 7/2/2024
Reporter: Moodyak

Platform: Windows
Operating System Version: Windows 11
Details of laser DACs connected (number, type, connection method): 2 Helios DAC. Ilda → DAC → USB

Description

I’m using an Akai APC40 Mk.1 to control clips. I’ve noticed that if I turn each group into flash mode (so I can hold down the clip I want firing), if I then scroll to a different section of clips while holding down a button, that previous clip is then stuck on - and it seems to also stop flashing so it becomes very difficult to scroll through and find the clip that’s playing to stop it.

I’ve also noticed that when selecting effects using the “record ARM” button sections, it only selects every second effect. Would be nice if we could map effects to buttons rather than arbitrarily select them

Steps to reproduce

  1. Set each group to flash mode
  2. Use Akai APC40 to select a clip, hold the button down
  3. Using Cue Level knob, turn to another section of clips
  4. Release the first clip button

Expected result

First clip should end

Actual result

First clip continues to play

Screenshot

image
image1720×1214 196 KB

Notes

2

Thanks for the report @moodyak, good catch! And welcome to the forum :blush:

Re the “record ARM” buttons, those effects are part of MX group 1, (Mutually eXclusive), so only one of those can be on at the same time. The MX group is set via each effect’s right click menu; set the group to 0 to disable this function and make the effect completely independent of the others.

(All of the colour effects in the default set up are assigned to MX group 1 so that you can easily switch between colours)

3

This issue with scrolling away isn’t exactly fixed - it proved a bit complicated - but I have disabled scrolling while any button is pressed, so you can’t get this bug any more. I hope to fix this properly in future but at least for now the issue is resolved.

Thanks!

Seb