-
-
DJTT Mapping Ninja Moderator
It's changed like many commands in 2.5
Add out > Track deck > Cue > Hotcue # type
-
Hi Stewe,
That's exactly what I did but it doesn't work, that's what drives me nuts.
Here's one of the versions I've tried. Can you see what I've done wrong ?
Schermafbeelding 2012-09-02 om 13.47.23.png
-
DJTT Mapping Ninja Moderator
Hm.. Try adding M1=0 as condition for LED type same as you did for store hotcues.
-
Done that... nope. Not working. Arrrgghh..... I've seen it working so it must be something that I'm doing wrong.
-
DJTT Infectious Moderator
Try deleting the commands and mapping them again.
-
DJTT Mapping Ninja Moderator
Also make sure to set midi In/Out port to your controller.
-
DJTT Mapping Ninja Moderator
Did you set range for hotcue type?
Controller range 0-0
Midi range 0-127
No blend checked.
-
Tech Guru
try adding a sending monitor state command twice, one normal, one set to invert.
Latest mix
There’s also an almost hermetic community that exists in many areas of dance music, where serious hobbyists feed off each other’s expertise but barely connect to the industry – despite many of those involved actually working in it.
-
DJTT Mapping Ninja Moderator
My hotcues are assigned to buttons which doesn't support LED output so I didn't actually mess with hotcue outputs in 2.5 but I knew it was renamed.
So i tried to troubleshoot it and see what is the problem there. I added only one output for "hotcue # tupe" and it worked. Thing was with controller range, I started from 0-0 and it lite properly.
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
Bookmarks