which buttons are you trying map?
Printable View
which buttons are you trying map?
apc40 grid
specifically...
Deck A
row 3, column 1 = loop decrease
row 3, column 2 = loop increase
row 3, column 3 = loop size 1
row 3, column 4 = loop size 2
row 4, column 1 = loop size 4
row 4, column 2 = loop size 8
row 4, column 3 = loop size 16
row 4, column 4 = loop size 32
i am trying to map it so that when the loop is not active the led is solid green. when the loop is active the led is blinking green.
the loop decrease/increase would be solid orange.
i will then repeat this for Deck B.
You got the APC40 in 'dumb' mode?
hmmm... possibly not... i am on a mac though - i thought that was a windows thing?
I assume it should apply to both. Open Ableton, wait for red rectangle around clips, close Ableton, open Traktor, then try your LED mappings.
Talk to Paddy, his APC40 mapping is godlike!Quote:
Originally Posted by shanefontane
been using it today and I took a look at the mapping section and MY GAWD I see stuff I never seen before:eek: But it all works 100% and getting more and more used to how it's mapped.
he could help ya on getting the loops mapped like ya want
thanks. i guess i decided to change my direction and use loop in/out points with inc/dec size. but now i'm trying to figure out how to work the Slot State parameter.Quote:
Originally Posted by MuzicFreq
yeah. dumb state doesn't seem to apply to mac. the leds load up correctly without having to go to ableton.Quote:
Originally Posted by coolmatic
I'm sharing your pain right now! I'm new to Traktor (just acquired Traktor Scratch Pro 2) and am finding the mappings painful with my APC40.
I had no problems assigning hot cues for Deck A & Deck B so that I get solid green if no cue is assigned and solid red when cue is assigned, but trying to do similar with other actions such as having "beat jump" on deck A set to orange default is near impossible. I actually put in the correct values and it's been turning red! Very frustrating.
I think my biggest frustration is that I can't see the logic in why in some cases I can assign (for example) -1 and -1 as the midi range but in other cases it will force me to be in positive values only (I have -1 / -1 for the controller range with the hot cue state actions).
I feel your pain on this one, I'll let you know if I have any success this weekend, will likely be starting from scratch again to see if I can nail this down.
this is the direction i went...Quote:
Originally Posted by Graham Campbell
http://www.djtechtools.com/forum/sho...d=1#post271443