Command keys and midi

Don't do this via command keys - use Hog's MIDI maps, then assign a macro to kick off what you want. Unlimited MIDI assignments that way

I appreciate the reply, it seems kinda vague tho, care to elaborate? Ope, I see what you meant. I wanted to use command keys as they actually listen to release time 

I've been mapping the apc40 to a few virtual playbacks and have started mapping cues to some of the buttons as well.

You wouldn't happen to know anything about master flash buttons not listening to release time would you? That's my biggest gripe right now

I agree with Chris’s explanation.

Since you already know how to map the APC40’s buttons to notes, the next step is to use the comment macro in the midi map editor column to link a button press to a cuelist. From there, you’ll need to build the cuelist that the MIDI note will trigger. The command buttons are limited to pages of 12 so don’t waste time mapping them.

If you want a release time, open the cuelist and edit the release settings. You then create a second cue that uses a comment macro to release the cuelist. The manual explains comment macros in more depth, and I’d recommend starting there — they’re quite powerful once you get comfortable with them. 

To my knowledge, the timing of all flash buttons (except the command button) is fixed at zero and can’t be changed — but if someone knows otherwise, I’d be glad to be corrected.

the Hog V5 layout killed the command buttons for me. Using them looks to me like I need to learn the Vulcan salute, so I grabbed a MIDI fighter 64.

Clarifyingmy statement above— command buttons are limited to 12 buttons on one page so to map them would be the same on the midi controller and on the console.

Thank you so much for taking the time to explain it all. I've been using comment macros since day one and keystroke macros not too long after that but I had no idea I had to create a second cue that releases the first in order to see release time. Does this mean I'll have to make each of these cues chases? Otherwise I'd be hitting the button twice, right? I've started to use single cycle chases for one shots and have figured out how to make those look how I want for sweeps.

The flash keys not being able to fade out is kinda annoying as I come from MA2/3 but I'll get over it. 

Does it even get annoying that you have to have alllll of your dimming effects on one cuestack if you want all of their bpms to match? I find the lack of speed masters to be a nuisance, our drummer just spins a dial for the click track so it's never the same bpm when we do the song so I can't even program set bpms for effects. I've resorted to using bump buttons to keep everything in time.

Again thank you for the help! 

Thank you so much for taking the time to explain it all. I've been using comment macros since day one and keystroke macros not too long after that but I had no idea I had to create a second cue that releases the first in order to see release time. Does this mean I'll have to make each of these cues chases? Otherwise I'd be hitting the button twice, right? I've started to use single cycle chases for one shots and have figured out how to make those look how I want for sweeps.

The flash keys not being able to fade out is kinda annoying as I come from MA2/3 but I'll get over it. 

Does it even get annoying that you have to have alllll of your dimming effects on one cuestack if you want all of their bpms to match? I find the lack of speed masters to be a nuisance, our drummer just spins a dial for the click track so it's never the same bpm when we do the song so I can't even program set bpms for effects. I've resorted to using bump buttons to keep everything in time.

Again thank you for the help!