apc40 midi channels

[ectoplasm]

So feel free to flame me if I've been looking in the wrong places for answers, but it seems like I'm experiencing midi mapping issues with my APC40 and Traktor Pro 2

As many APC users know the clip grid sends the same midi messages across different channels in every column.

I'm trying to map two clip launch buttons (same midi note, different channel) to trigger hotcue 1, the first button for deck A and the other for deck B... when triggering the hotcues they work as normal, but when deleting or resetting hotcues it occurs on both deck A and B simultaneously, regardless which deck its mapped to... I feel like there is some sort of conflict between the duplicate midi notes, even though they are on seperate midi channels...

I've noticed other peoples APC40 mappings don't seem to encounter this problem, what am I doing wrong?

[ectoplasm]

also is there a way to make it so that traktor sends hotcue state to light up LEDs everytime I load a song?

I programmed it so that when there is no hotcue it is lit up green, and when there is a hotcue on the grid it lights up red, but when I load a track with a bunch of hotcues already in it the grid doesnt change color to correspond...

[ectoplasm]

oh hey it magically works now and recognizes all the different midi channels as seperate messages : ] win!

[Onimode]

Glad you figured it out, sir. o:
By the way, are you using generic mode or "dumb" mode?

[ectoplasm]

Using dumb mode for everything, I like my mapping to have full LED response, and I've put it all in there accordingly. The 8 banks of encoders in generic mode I would never really use, I feel like the APC has plenty of faders/knobs to suit my style of mixing already.

For one example of useful LED response... my play/pause button flashes when a track is playing on that deck, when I have a loop active its the same deal... helps me remember to not leave a track playing too long or leave a loop on by accident.

At this point you might be convinced I suck at DJing, but weve all accidentally left an EQ off or a filter on by accident right? this mapping helps me avoid those silly mistakes with lots of LED feedback. I just spent the past 4 hours working on this .tsi and I feel like it's at a point where I'm happy with the level of control and feedback.

[C-Lab]

After writing and out message to control your LED's its always a good idea (usually with buttons) to also add a "send monitor state" IN command. This will make sure that your LED's are always giving your up-to-date feedback.