I’m mapping 8 hotcue buttons onto my launchpad, I have the actual buttons all mapped and ready to go!
Although there is something missing… Some visual feedback!
I’ve successfully mapped the LEDs for deck A. Unfortunately when I attempt to map deck B usage of the hotcues in deck B light up deck A’s LEDs
I have them all switched to deck B and can’t for the life of me figure out where the reference is coming from beyond them being set as “hotcue 1”
Any thoughts?
Also I’m trying to get a modifier to work in order to have a “shift” key to delete said hotcues, it works ok, but for some reason when I go to delete the hotcue, it also cues it.
I’ve been at this for hours now… Still can’t figure it out… Has anyone else run into the same/similar problems?
I was doing the same thing 2 days ago with my launchpad, except when I pressed a button, the entire row lit up. And I couldn’t figure out modifiers to delete the cue.
A whole row? I can’t even think why that’d happen… As far as I know the MIDI-Out needs to reference an individual key, not sure if there are any commands for rows/columns?
you’re mapping “Hotcue X State”? make sure device focus for the mapping is set to “focus” and you have set “Assignment” correctly for each OUT. should work ok…
sounds like you haven’t added the modifier condition to the store/set that u have to the delete. i.e:
M1=1 delete hotcue
M1=0 select/store hotcue (if this is missing then it will also jump to that hotcue when deleting it)
if you’re mapping the OUT for “select/store hotcue” then i don’t think u can select the individual hotcue number for some reason - so they will all light up. you’d need to set a modifier value to 1-8 that corresponds to which hotcue you press (via the IN for “select/store hotcue”) and then add that as a modifier condition for the OUT
Good man - I’m working on this today, so I’m going to have a go the next few hours and report back.
As a tech-savvy sounding individual who appears to use windows for some things, you haven’t come across the other issue I’m looking into regarding Launchpad sucking power/data transfer from an S4?
never heard of that issue, tho also never had my grubby mits on an s4. you have them plugged into separate usb ports? always seems a wise rule of thumb to plug any soundcard (or controller that has one) into it’s own dedicated usb port.
also the launchpad is usb1.0 so will force (usually) any other devices plugged into that port down to usb1 which i suspect you don’t want for your s4.
As a quick bit of feedback Zestoi - with regards to the LEDs - mapping is set to focus, and I have all of the assignments set to their respective decks, yet I hit hotcue 1 on my deck B area, and the LED for deck A lights up!
With the hot cue issue, AWESOME! Test of concept worked on hotcue 1 deck A. So going to get fired into getting the rest of them done!
cool - sounds good i’ll have a play with your tsi if u still have issues later. you can attach to a forum post. i can even boot my linux machine into windows if needed but i doubt its a mac/windows issue.
Excellent, appreciate it. I’m going to work on getting the rest of these hotcues mapped. Although it’s hard when your testing it works… Far too easy to get distracted…
i know the launchpad used to cause issues in old versions of traktor as it’s leds are so slow to update. enabling multi core support in recent versions of traktor has solved that tho afaik. and yep easy to get distracted mapping/playing with traktor
With regards to the LED feedback… I have no idea what I was doing wrong before (as I checked all of the above) but it’s now working for some bizzare reason across two decks fine. Now to get all four!
i’ll have a play with your tsi if u still have issues later. you can attach to a forum post. i can even boot my linux machine into windows if needed but i doubt its a mac/windows issue.
