Traktor Pro: Cue Buttons? Can someone tell me what combination of midi mappings I need for cue buttons?
I have "Select Hotcue" and "Jump to Act Cue" setup for each cue button... It seems to work fine except the first time I switch cue points. I have to hit the cue button twice. The first press so that the Select Hotcue takes effect for the new cue point and the second press to actually trigger the new cue point.
As you can imagine, this bug makes cue juggling impossible. Please help! |
Fidel Toupin
25.06.2012 |
Originally Posted by JAC
Are you not over-complicating things? For my nanopad I assigned select hotcue and cue play/pause to each trigger pad and it works just as you described above. I order them with 1 on the left and 6 on the right and when i press a trigger pad, the track jumps to the corresponding hotcue and plays.
Why not just do this? Or am i mis-understanding the problem?
Hi Im having the same issue using a Korg NanoKontrol2. I followed the different tutos : its like the mapped button act with an "hold" function, I have to "dehold" it first in order to play the hot cuepoints. So in a live mix I have to push my button once in order to launch the cuepoints, repush it in order to "dis-engage my hotcue" and only then im able to repush the button in order to relaunch the cuepoints. (Weird isnt it?).
By the way B33SON I wasnt able to find the functions "select hotcue" and "cue play/pause" in traktor mappings sections... |
Roberto Viccione
28.01.2009 |
Originally Posted by BentoSan
*confused look* can you elaborate on that ? im not quite sure i know what your getting.
If you use 80 instead of 90 it's a Note Off signal. So you can use different commands for different velocities of the "Off" message, which can cause interesting effects. It's just how I send my off messages. |
Jean Marc Lopez
28.01.2009 |
Originally Posted by B33SON
What I really want is just to be able to cue juggle with one click. I want playback to remain the same. If playback was started, then it continues. If it's stopped then it remains stopped. Seems like it's simple, but for some reason it's buggy for me.
Are you not over-complicating things? For my nanopad I assigned select hotcue and cue play/pause to each trigger pad and it works just as you described above. I order them with 1 on the left and 6 on the right and when i press a trigger pad, the track jumps to the corresponding hotcue and plays.
Why not just do this? Or am i mis-understanding the problem? |
Xavier Emanuels
28.01.2009 |
Originally Posted by DvlsAdvct
Also, you can use 80 instead of 90 for note offs.
*confused look* can you elaborate on that ? im not quite sure i know what your getting. |
Xavier Emanuels
28.01.2009 |
Originally Posted by B33SON
Yes!!!! It works! Thanks to both of you for your help with this. Finally getting expected behavior!
No problem dude. glad to hear you got it working how you like. |
Hannes Deburchgraeve
28.01.2009 |
Originally Posted by BentoSan
a note release is a 00 message - 127 = note on - 0 = note release aka note off
Yes!!!! It works! Thanks to both of you for your help with this. Finally getting expected behavior! |
Xavier Emanuels
27.01.2009 |
Originally Posted by B33SON
This sounds exactly like what I'm doing wrong. So, you're saying, for each button, I'll have one translation that sends out the "Select Cue" midi on the key down event... and a second translation that sends out a "note release" on key up?
What is a note release message? Sorry, Google didn't help me.
a note release is a 00 message - 127 = note on - 0 = note release aka note off |
Hannes Deburchgraeve
27.01.2009 |
Originally Posted by BentoSan
Nothing except that you might be forgetting to translate the key up message into a note release.
This sounds exactly like what I'm doing wrong. So, you're saying, for each button, I'll have one translation that sends out the "Select Cue" midi on the key down event... and a second translation that sends out a "note release" on key up?
What is a note release message? Sorry, Google didn't help me. |
Xavier Emanuels
27.01.2009 |
Originally Posted by B33SON
It is weird! And yes, I am using Bomes to translate a keyboard key press to a midi note and send it to Traktor. I just hooked up a M-Audio 02 and set the same mapping... and the Select Cue works fine. For this I'm using the Midi Thru to send out of Bomes. Why the difference between a real controller and a generated midi message?
Nothing except that you might be forgetting to translate the key up message into a note release. |
Hannes Deburchgraeve
27.01.2009 |
Originally Posted by DvlsAdvct
that's... really weird...
Are you sending the messages through Bomes? Does it work the same if you set a hotkey IN Traktor?
It is weird! And yes, I am using Bomes to translate a keyboard key press to a midi note and send it to Traktor. I just hooked up a M-Audio 02 and set the same mapping... and the Select Cue works fine. For this I'm using the Midi Thru to send out of Bomes. Why the difference between a real controller and a generated midi message? |
Fidel Toupin
25.06.2012 |
Originally Posted by JAC
Are you not over-complicating things? For my nanopad I assigned select hotcue and cue play/pause to each trigger pad and it works just as you described above. I order them with 1 on the left and 6 on the right and when i press a trigger pad, the track jumps to the corresponding hotcue and plays.
Why not just do this? Or am i mis-understanding the problem?
Hi Im having the same issue using a Korg NanoKontrol2. I followed the different tutos : its like the mapped button act with an "hold" function, I have to "dehold" it first in order to play the hot cuepoints. So in a live mix I have to push my button once in order to launch the cuepoints, repush it in order to "dis-engage my hotcue" and only then im able to repush the button in order to relaunch the cuepoints. (Weird isnt it?).
By the way B33SON I wasnt able to find the functions "select hotcue" and "cue play/pause" in traktor mappings sections... |
Roberto Viccione
28.01.2009 |
Originally Posted by BentoSan
*confused look* can you elaborate on that ? im not quite sure i know what your getting.
If you use 80 instead of 90 it's a Note Off signal. So you can use different commands for different velocities of the "Off" message, which can cause interesting effects. It's just how I send my off messages. |
Jean Marc Lopez
28.01.2009 |
Originally Posted by B33SON
What I really want is just to be able to cue juggle with one click. I want playback to remain the same. If playback was started, then it continues. If it's stopped then it remains stopped. Seems like it's simple, but for some reason it's buggy for me.
Are you not over-complicating things? For my nanopad I assigned select hotcue and cue play/pause to each trigger pad and it works just as you described above. I order them with 1 on the left and 6 on the right and when i press a trigger pad, the track jumps to the corresponding hotcue and plays.
Why not just do this? Or am i mis-understanding the problem? |
Xavier Emanuels
28.01.2009 |
Originally Posted by DvlsAdvct
Also, you can use 80 instead of 90 for note offs.
*confused look* can you elaborate on that ? im not quite sure i know what your getting. |
Roberto Viccione
28.01.2009 | haha yeah, if I hadn't overslept I'd have said the same thing.
I was doing this a bunch and trrying to figure out why it wouldn't work.
Also, you can use 80 instead of 90 for note offs. |
Xavier Emanuels
28.01.2009 |
Originally Posted by B33SON
Yes!!!! It works! Thanks to both of you for your help with this. Finally getting expected behavior!
No problem dude. glad to hear you got it working how you like. |
Hannes Deburchgraeve
28.01.2009 |
Originally Posted by BentoSan
a note release is a 00 message - 127 = note on - 0 = note release aka note off
Yes!!!! It works! Thanks to both of you for your help with this. Finally getting expected behavior! |
Xavier Emanuels
27.01.2009 |
Originally Posted by B33SON
This sounds exactly like what I'm doing wrong. So, you're saying, for each button, I'll have one translation that sends out the "Select Cue" midi on the key down event... and a second translation that sends out a "note release" on key up?
What is a note release message? Sorry, Google didn't help me.
a note release is a 00 message - 127 = note on - 0 = note release aka note off |
Hannes Deburchgraeve
27.01.2009 |
Originally Posted by BentoSan
Nothing except that you might be forgetting to translate the key up message into a note release.
This sounds exactly like what I'm doing wrong. So, you're saying, for each button, I'll have one translation that sends out the "Select Cue" midi on the key down event... and a second translation that sends out a "note release" on key up?
What is a note release message? Sorry, Google didn't help me. |
Xavier Emanuels
27.01.2009 |
Originally Posted by B33SON
It is weird! And yes, I am using Bomes to translate a keyboard key press to a midi note and send it to Traktor. I just hooked up a M-Audio 02 and set the same mapping... and the Select Cue works fine. For this I'm using the Midi Thru to send out of Bomes. Why the difference between a real controller and a generated midi message?
Nothing except that you might be forgetting to translate the key up message into a note release. |
Hannes Deburchgraeve
27.01.2009 |
Originally Posted by DvlsAdvct
that's... really weird...
Are you sending the messages through Bomes? Does it work the same if you set a hotkey IN Traktor?
It is weird! And yes, I am using Bomes to translate a keyboard key press to a midi note and send it to Traktor. I just hooked up a M-Audio 02 and set the same mapping... and the Select Cue works fine. For this I'm using the Midi Thru to send out of Bomes. Why the difference between a real controller and a generated midi message? |
Roberto Viccione
27.01.2009 | that's... really weird...
Are you sending the messages through Bomes? Does it work the same if you set a hotkey IN Traktor? |
Hannes Deburchgraeve
27.01.2009 |
Originally Posted by DvlsAdvct
Do you need "Jump To ACtive Cue"? I've never set this before in relation to selecting a new Cue point.
I shouldn't right?! But if I don't have it, Traktor seems to just ignore the midi message telling it to select the cue point. If I repeatedly press the button and send the midi message, Traktor will ignore it and but if I keep pressing it randomly about 16-24 beats later it'll finally do it. |
Roberto Viccione
27.01.2009 | Do you need "Jump To ACtive Cue"? I've never set this before in relation to selecting a new Cue point. |
Hannes Deburchgraeve
27.01.2009 |
Originally Posted by DvlsAdvct
So, just to make sure I understand the problem.
You load a track and hit "Select Hotcue" and it jumps to the hotcue and doesn't play? You want it to start playing when you press the button, right?
When the track is playing, though, it should act normally, so you can cue juggle, correct?
No, it doesn't play... because I would have to hit the play button first.
For loading and playing from a cue point, I'm fine with selecting my cue point via my cue select button and then hitting play. I don't have a problem with this behavior.
What's not working right now (because I'm using the "Jump to Active Cue") is that I have to hit the cue select button twice... The first time causes the current cue point to reselect... the second press makes the jump to the correct cue point.
What I really want is just to be able to cue juggle with one click. I want playback to remain the same. If playback was started, then it continues. If it's stopped then it remains stopped. Seems like it's simple, but for some reason it's buggy for me. |
Roberto Viccione
27.01.2009 |
Yes, please take a look. I thought Select Hotcue would be the only thing needed, but without "Jump to Active Cue" nothing happens after the first time I send the midi for "Select Hotcue". In other words, it will only cue to that point once.
So, just to make sure I understand the problem.
You load a track and hit "Select Hotcue" and it jumps to the hotcue and doesn't play? You want it to start playing when you press the button, right?
When the track is playing, though, it should act normally, so you can cue juggle, correct? |
Xavier Emanuels
27.01.2009 |
Originally Posted by B33SON
Yes, please take a look. I thought Select Hotcue would be the only thing needed, but without "Jump to Active Cue" nothing happens after the first time I send the midi for "Select Hotcue". In other words, it will only cue to that point once.
Are you sure about that ? because i was just testing it before i posted and the only thing i have my cue buttons mapped to at the moment is select hot cue / hold and it works as i described above.
Im personally putting more thought into how i want my cue points to react and ill be reworking the system that i use at the moment in the near future.
Originally Posted by B33SON
Secondary, when the track is stopped, I want to be able to move to the cue point to begin playing. Multiple taps aren't necessary for this of course.
You could have a modifer that changes depending on when the track is playing. If it isnt playing and you hit a cue button it could also innitiate the play button with a double macro.
This way they allways act as cue plays if the deck is paused or not.
I need to get some sleep now, if you havent sorted this out by tommorow ill continue to help out |
Hannes Deburchgraeve
27.01.2009 |
Originally Posted by BentoSan
If you just use select hot cue then when the deck is playing they will act as cue plays and if the deck is paused it will act as cue pauses.
Yes, this part works fine.
Originally Posted by BentoSan
How you map them depends on how you want them to react - could you be bit more specific in how you wish them to function ?
I want to be able to tap each cue button when it's playing and have it cue to the cue point and continue playing. I want to be able to use it for jumping while the track is playing... I like to do this after tightening a loop for a buildup. I also want to be able to do a bit of beat juggling.
Secondary, when the track is stopped, I want to be able to move to the cue point to begin playing. Multiple taps aren't necessary for this of course.
Originally Posted by DvlsAdvct
You should just be able to use "Select Hotcue" and not use "Jump to Act Cue"
If no one can answer by the time I get home I can reference my TSI.
Yes, please take a look. I thought Select Hotcue would be the only thing needed, but without "Jump to Active Cue" nothing happens after the first time I send the midi for "Select Hotcue". In other words, it will only cue to that point once. |
Roberto Viccione
27.01.2009 | You should just be able to use "Select Hotcue" and not use "Jump to Act Cue"
If no one can answer by the time I get home I can reference my TSI. |
Xavier Emanuels
27.01.2009 | If you just use select hot cue then when the deck is playing they will act as cue plays and if the deck is paused it will act as cue pauses.
How you map them depends on how you want them to react - could you be bit more specific in how you wish them to function ? |
