ClayDJ
Hi Everyone,
I'm a noob on this site.
I have a Denon 5500 and would like to map the FX knob on my controller to change the cue points (similar to a cue point browser).
Here's how I would like it to work:
When a track is currently playing, and without interruption, I would like to turn the FX knob to select another cue point on that track. I would then push the FX knob to load/trigger the newly selected cue point. Each push of the knob should trigger that cue point. Normal turning the FX knob (not push and turn) one click should advance or go back to the next cue point depending on which way knob is turned.
FX knob should trigger cue on the down push. Holding down the FX knob for more than one second will give normal FX control for this knob.
If a track is not playing, then turning FX knob will browse/select a cue point then push to trigger cue start.
I tried using 'goto_cue' for the FX knob but that is for going to a specific cue point. It won't allow for scrolling through (browsing) cue points.
A plus would be to have the Hot Cue button(s) change their cue point number and color accordingly when triggered.
If possible please show the exact syntax string that I would need to put in the mapper 'Action' box to enable this action.
Also; Any way to save samples for each individual track (each track would have its own set of samples)?
Hopefully the above not to confusing.
Thanks for your input and a great forum.
DJClay
I'm a noob on this site.
I have a Denon 5500 and would like to map the FX knob on my controller to change the cue points (similar to a cue point browser).
Here's how I would like it to work:
When a track is currently playing, and without interruption, I would like to turn the FX knob to select another cue point on that track. I would then push the FX knob to load/trigger the newly selected cue point. Each push of the knob should trigger that cue point. Normal turning the FX knob (not push and turn) one click should advance or go back to the next cue point depending on which way knob is turned.
FX knob should trigger cue on the down push. Holding down the FX knob for more than one second will give normal FX control for this knob.
If a track is not playing, then turning FX knob will browse/select a cue point then push to trigger cue start.
I tried using 'goto_cue' for the FX knob but that is for going to a specific cue point. It won't allow for scrolling through (browsing) cue points.
A plus would be to have the Hot Cue button(s) change their cue point number and color accordingly when triggered.
If possible please show the exact syntax string that I would need to put in the mapper 'Action' box to enable this action.
Also; Any way to save samples for each individual track (each track would have its own set of samples)?
Hopefully the above not to confusing.
Thanks for your input and a great forum.
DJClay
Inviato Mon 25 Jul 11 @ 2:11 pm
ClayDJ
OK, reworded in simpler terms;
Is there a way to map a knob to select the various cue points?
Thanks in advance.
Is there a way to map a knob to select the various cue points?
Thanks in advance.
Inviato Tue 26 Jul 11 @ 10:14 am
synthet1c
sure you could do it, but you would need to modify a skin so you can see what cue your going to on the next press. something like...
encoder button
deck 1 play ? deck 1 load & goto_cue 1 : holding 1000ms ? toggle 'fx_butt' & var 'fx_butt' 1 ? deck 1 effect active : var 'cue_jump 1' ? deck 1 goto_cue 1 : var 'cue_jump' 2 ? deck 1 goto_cue 2 : var 'cue_jump' 3 ? deck 1 goto_cue 3 : var 'cue_jump 4 ? deck 1 goto_cue 4 : var 'cue_jump' 5 ? deck 1 goto_cue 5 (etc... just finish on var 'cue_jump' 0)
knob
deck 1 play ? param_greater 50% ? browser_scroll +1 : browser_scroll 11 : var 'fx_butt' 1 ? param_greater 50% ? deck 1 effect slider +1 : deck 1 effect slider -1 : param_greater 50% ? cycle 'cue_jump' 6 : cycle 'cue_jump' -6
you need to make skin panels that show when one of the following variables are activated... don't know how to do it though... your better off asking in the skin forum for that...
var 'fx_butt' 1 ?
var 'fx_butt' 2 ?
var 'fx_butt' 3 ?
var 'fx_butt' 4 ?
var 'fx_butt' 5 ?
var 'fx_butt' 0 ?
encoder button
deck 1 play ? deck 1 load & goto_cue 1 : holding 1000ms ? toggle 'fx_butt' & var 'fx_butt' 1 ? deck 1 effect active : var 'cue_jump 1' ? deck 1 goto_cue 1 : var 'cue_jump' 2 ? deck 1 goto_cue 2 : var 'cue_jump' 3 ? deck 1 goto_cue 3 : var 'cue_jump 4 ? deck 1 goto_cue 4 : var 'cue_jump' 5 ? deck 1 goto_cue 5 (etc... just finish on var 'cue_jump' 0)
knob
deck 1 play ? param_greater 50% ? browser_scroll +1 : browser_scroll 11 : var 'fx_butt' 1 ? param_greater 50% ? deck 1 effect slider +1 : deck 1 effect slider -1 : param_greater 50% ? cycle 'cue_jump' 6 : cycle 'cue_jump' -6
you need to make skin panels that show when one of the following variables are activated... don't know how to do it though... your better off asking in the skin forum for that...
var 'fx_butt' 1 ?
var 'fx_butt' 2 ?
var 'fx_butt' 3 ?
var 'fx_butt' 4 ?
var 'fx_butt' 5 ?
var 'fx_butt' 0 ?
Inviato Tue 26 Jul 11 @ 3:36 pm
ClayDJ
Thanks a million Synthet1c!
I assume that the encoder button string is actually 'pushing and holding' the FX knob to retain its normal FX settings?
Thanks again for your help.
I assume that the encoder button string is actually 'pushing and holding' the FX knob to retain its normal FX settings?
Thanks again for your help.
Inviato Tue 26 Jul 11 @ 4:31 pm
synthet1c
yep if you hold it, it will toggle on/off, but you need to deactivate it before you can cue again, there was a couple of errors, this should work properly... well hopefully
just read your post in the skins forum... mapping the leds on the controller would be easy, leave out the deck # as you assign that in the mapper anyway..
encoder button
stop ? load & goto_cue 1 : holding 1000ms ? toggle '%fx_butt' & var '%fx_butt' 1 ? effect active : var '%cue_jump' 1' ? goto_cue 1 : var '%cue_jump' 2 ? goto_cue 2 : var '%cue_jump' 3 ? goto_cue 3 : var '%cue_jump' 4 ? goto_cue 4 : var '%cue_jump' 5 ? goto_cue 5 : var '%cue_jump' 0 ? goto_cue 6
knob
stop ? param_greater 50% ? browser_scroll +1 : browser_scroll 11 : var '%fx_butt' 1 ? param_greater 50% ? effect slider +1 : effect slider -1 : param_greater 50% ? cycle '%cue_jump' 6 : cycle '%cue_jump' -6
for the leds you only have three to choose from so you could either use blinking or binary for visual feedback... for blinking map
led 1
var '%fx_butt' 1 ? on : var '%cue_jump' 4 ? blink 250ms : var '%cue_jump' 1 ? on : off
led 2
var '%fx_butt' 1 ? on : var '%cue_jump' 5 ? blink 250ms : var '%cue_jump' 2 ? on : off
led 3
var '%fx_butt' 1 ? on : var '%cue_jump' 0 ? blink 250ms : var '%cue_jump' 3 ? on : off
also sorry I gave you the wrong variable in the last post... its not 'fx_butt' you want to query its 'cue_jump'
just read your post in the skins forum... mapping the leds on the controller would be easy, leave out the deck # as you assign that in the mapper anyway..
encoder button
stop ? load & goto_cue 1 : holding 1000ms ? toggle '%fx_butt' & var '%fx_butt' 1 ? effect active : var '%cue_jump' 1' ? goto_cue 1 : var '%cue_jump' 2 ? goto_cue 2 : var '%cue_jump' 3 ? goto_cue 3 : var '%cue_jump' 4 ? goto_cue 4 : var '%cue_jump' 5 ? goto_cue 5 : var '%cue_jump' 0 ? goto_cue 6
knob
stop ? param_greater 50% ? browser_scroll +1 : browser_scroll 11 : var '%fx_butt' 1 ? param_greater 50% ? effect slider +1 : effect slider -1 : param_greater 50% ? cycle '%cue_jump' 6 : cycle '%cue_jump' -6
for the leds you only have three to choose from so you could either use blinking or binary for visual feedback... for blinking map
led 1
var '%fx_butt' 1 ? on : var '%cue_jump' 4 ? blink 250ms : var '%cue_jump' 1 ? on : off
led 2
var '%fx_butt' 1 ? on : var '%cue_jump' 5 ? blink 250ms : var '%cue_jump' 2 ? on : off
led 3
var '%fx_butt' 1 ? on : var '%cue_jump' 0 ? blink 250ms : var '%cue_jump' 3 ? on : off
also sorry I gave you the wrong variable in the last post... its not 'fx_butt' you want to query its 'cue_jump'
Inviato Tue 26 Jul 11 @ 4:45 pm
ClayDJ
Thanks again Synthet, I will let you know how I make out.
Clay
Clay
Inviato Tue 26 Jul 11 @ 5:23 pm
ClayDJ
OK Synthet, I tried your suggested mapping and had problems.
1- The rotary fx knob does nothing when rotated (should change cue points).
2- On every other push of the FX knob, it will only trigger cue 1, and only when released (should trigger selected cue on push).
3- It takes 2- one second pushes (hold button down) to enter FX mode, and 2 -one second pushes to get the button back in cue mode (should be 1 - one second push of the fx button to enter or exit fx mode).
A few observances with your strings (I'm a noobe with this stuff so bear with me);
Encoder button:
4- You have 'cue_jump', and 'fx_butt' listed but these scripts (verbs) are not listed in the verb sheet?
Knob:
5- You have 'browser_scroll' listed. This command should scroll cues. I'm guessing this 'browser' command can also be used for cue selection? (script shows it's for folders/files selection etc.)?
6- Line 1 - 'Browser_scroll 11' (typo)?
7- 'Effect slider' - can this be used with a knob?
Can you please check through the strings and see if there's a typo or something else wrong?
Thanks again for your help!
Clay
1- The rotary fx knob does nothing when rotated (should change cue points).
2- On every other push of the FX knob, it will only trigger cue 1, and only when released (should trigger selected cue on push).
3- It takes 2- one second pushes (hold button down) to enter FX mode, and 2 -one second pushes to get the button back in cue mode (should be 1 - one second push of the fx button to enter or exit fx mode).
A few observances with your strings (I'm a noobe with this stuff so bear with me);
Encoder button:
4- You have 'cue_jump', and 'fx_butt' listed but these scripts (verbs) are not listed in the verb sheet?
Knob:
5- You have 'browser_scroll' listed. This command should scroll cues. I'm guessing this 'browser' command can also be used for cue selection? (script shows it's for folders/files selection etc.)?
6- Line 1 - 'Browser_scroll 11' (typo)?
7- 'Effect slider' - can this be used with a knob?
Can you please check through the strings and see if there's a typo or something else wrong?
Thanks again for your help!
Clay
Inviato Tue 26 Jul 11 @ 10:39 pm
synthet1c
1. the knob changes the shift which the button activates the cue for depending on the shift, but the lights should change depending on the shift and therefore the cue that will be activated
3. the fx overides the cue so you need to hold it again to switch off the fx mode so you can cue again, but the fx isn't for selecting the effect it is changing the parameter of the first slider, It can be changed to "param_greater 50% ? effect select +1 : effect select -1"
4. fx_butt and cue_jump are shifts I have named you can call them anything
5. when the track is stopped the knob will scroll through the browser, this overides both effects and cues
6. yep typo, it should say browser_scroll -1
7. yep that is the way it was mapped
8... the leds sequence is all on for effects 1,2,3 on individually for cues shift 1,2,3 and for 4,5,6 blinking individually
9. it's untested, Im at work so don't have access to test it I'll give it a look when I get home on a controller
encoder button
stop ? load & goto_cue 1 : holding 1000ms ? toggle '%fx_butt' & var '%fx_butt' 1 ? effect active : var '%cue_jump' 1' ? goto_cue 1 : var '%cue_jump' 2 ? goto_cue 2 : var '%cue_jump' 3 ? goto_cue 3 : var '%cue_jump' 4 ? goto_cue 4 : var '%cue_jump' 5 ? goto_cue 5 : var '%cue_jump' 0 ? goto_cue 6
knob
stop ? param_greater 50% ? browser_scroll +1 : browser_scroll -1 : var '%fx_butt' 1 ? param_greater 50% ? effect select +1 : effect select -1 : param_greater 50% ? cycle '%cue_jump' 6 : cycle '%cue_jump' -6
for the leds you only have three to choose from so you could either use blinking or binary for visual feedback... for blinking map
led 1
var '%fx_butt' 1 ? on : var '%cue_jump' 4 ? blink 250ms : var '%cue_jump' 1 ? on : off
led 2
var '%fx_butt' 1 ? on : var '%cue_jump' 5 ? blink 250ms : var '%cue_jump' 2 ? on : off
led 3
var '%fx_butt' 1 ? on : var '%cue_jump' 0 ? blink 250ms : var '%cue_jump' 3 ? on : off
3. the fx overides the cue so you need to hold it again to switch off the fx mode so you can cue again, but the fx isn't for selecting the effect it is changing the parameter of the first slider, It can be changed to "param_greater 50% ? effect select +1 : effect select -1"
4. fx_butt and cue_jump are shifts I have named you can call them anything
5. when the track is stopped the knob will scroll through the browser, this overides both effects and cues
6. yep typo, it should say browser_scroll -1
7. yep that is the way it was mapped
8... the leds sequence is all on for effects 1,2,3 on individually for cues shift 1,2,3 and for 4,5,6 blinking individually
9. it's untested, Im at work so don't have access to test it I'll give it a look when I get home on a controller
encoder button
stop ? load & goto_cue 1 : holding 1000ms ? toggle '%fx_butt' & var '%fx_butt' 1 ? effect active : var '%cue_jump' 1' ? goto_cue 1 : var '%cue_jump' 2 ? goto_cue 2 : var '%cue_jump' 3 ? goto_cue 3 : var '%cue_jump' 4 ? goto_cue 4 : var '%cue_jump' 5 ? goto_cue 5 : var '%cue_jump' 0 ? goto_cue 6
knob
stop ? param_greater 50% ? browser_scroll +1 : browser_scroll -1 : var '%fx_butt' 1 ? param_greater 50% ? effect select +1 : effect select -1 : param_greater 50% ? cycle '%cue_jump' 6 : cycle '%cue_jump' -6
for the leds you only have three to choose from so you could either use blinking or binary for visual feedback... for blinking map
led 1
var '%fx_butt' 1 ? on : var '%cue_jump' 4 ? blink 250ms : var '%cue_jump' 1 ? on : off
led 2
var '%fx_butt' 1 ? on : var '%cue_jump' 5 ? blink 250ms : var '%cue_jump' 2 ? on : off
led 3
var '%fx_butt' 1 ? on : var '%cue_jump' 0 ? blink 250ms : var '%cue_jump' 3 ? on : off
Inviato Tue 26 Jul 11 @ 11:20 pm
ClayDJ
Synthet, still no luck with the fx rotary knob. Rotating it does nothing, pushing it activates the fx on second push.
Let's try and keep it simple for now;
Can you only map the fx knob to:
1- Rotating the fx knob will select cues.
2- Pushing the fx knob (button) once will set/trigger the selected cue on release.
I can do without the 'push and hold' for the fx knob right now (at least until the cue select is working :) ).
Thanks again,
Clay
Let's try and keep it simple for now;
Can you only map the fx knob to:
1- Rotating the fx knob will select cues.
2- Pushing the fx knob (button) once will set/trigger the selected cue on release.
I can do without the 'push and hold' for the fx knob right now (at least until the cue select is working :) ).
Thanks again,
Clay
Inviato Wed 27 Jul 11 @ 1:33 pm
synthet1c
encoder button
var '%cue_jump' 1' ? goto_cue 1 : var '%cue_jump' 2 ? goto_cue 2 : var '%cue_jump' 3 ? goto_cue 3 : var '%cue_jump' 4 ? goto_cue 4 : var '%cue_jump' 5 ? goto_cue 5 : var '%cue_jump' 0 ? goto_cue 6
param_greater 50% ? cycle '%cue_jump' 6 : cycle '%cue_jump' -6
for the leds you only have three to choose from so you could either use blinking or binary for visual feedback... for blinking map
led 1
var '%cue_jump' 4 ? blink 250ms : var '%cue_jump' 1 ? on : off
led 2
var '%cue_jump' 5 ? blink 250ms : var '%cue_jump' 2 ? on : off
led 3
var '%cue_jump' 0 ? blink 250ms : var '%cue_jump' 3 ? on : off
var '%cue_jump' 1' ? goto_cue 1 : var '%cue_jump' 2 ? goto_cue 2 : var '%cue_jump' 3 ? goto_cue 3 : var '%cue_jump' 4 ? goto_cue 4 : var '%cue_jump' 5 ? goto_cue 5 : var '%cue_jump' 0 ? goto_cue 6
param_greater 50% ? cycle '%cue_jump' 6 : cycle '%cue_jump' -6
for the leds you only have three to choose from so you could either use blinking or binary for visual feedback... for blinking map
led 1
var '%cue_jump' 4 ? blink 250ms : var '%cue_jump' 1 ? on : off
led 2
var '%cue_jump' 5 ? blink 250ms : var '%cue_jump' 2 ? on : off
led 3
var '%cue_jump' 0 ? blink 250ms : var '%cue_jump' 3 ? on : off
Inviato Wed 27 Jul 11 @ 4:54 pm
ClayDJ
Still no luck mapping the fx knob/button on the Denon 5500.
Using the last string that you sent me, the rotary knob still does nothing when remapped to select cues. Pushing the fx button only activates the fx as it should.
What DOES work to a small degree is one of the VDJ script examples:
param_greater 0 ? goto_cue 1 : goto_cue 2
Notice that I modified the above script example to read: "param_greater 0" which worked. The actual script example: "param_greater 50%" did NOT work. It did not like the %, and no other number would work except 0.
Using the string above I CAN toggle only between cues 1 and 2 using fx the rotary knob. Cue 1 can only be selected by turning the fx knob clockwise, cue 2 only selected by turning counter clockwise.
I would actually like to advance one cue point for each click when fx knob is rotated clockwise, and the opposite for counter clockwise rotation, then push to trigger. Current playing track should continue while searching cues until triggered.
The button push for the fx knob was not remapped for this test, and left as normal map (push for effects).
Any idea's or other strings to try?
Clay
Using the last string that you sent me, the rotary knob still does nothing when remapped to select cues. Pushing the fx button only activates the fx as it should.
What DOES work to a small degree is one of the VDJ script examples:
param_greater 0 ? goto_cue 1 : goto_cue 2
Notice that I modified the above script example to read: "param_greater 0" which worked. The actual script example: "param_greater 50%" did NOT work. It did not like the %, and no other number would work except 0.
Using the string above I CAN toggle only between cues 1 and 2 using fx the rotary knob. Cue 1 can only be selected by turning the fx knob clockwise, cue 2 only selected by turning counter clockwise.
I would actually like to advance one cue point for each click when fx knob is rotated clockwise, and the opposite for counter clockwise rotation, then push to trigger. Current playing track should continue while searching cues until triggered.
The button push for the fx knob was not remapped for this test, and left as normal map (push for effects).
Any idea's or other strings to try?
Clay
Inviato Wed 27 Jul 11 @ 10:22 pm
synthet1c
I think the reason you use param_greater 0 is you have a 14bit knob which is more sensitive
knob
param_greater 0% ? cycle 'cue_jump' 6 : cycle 'cue_jump' -6
button
var 'cue_jump' 1' ? goto_cue 1 : var 'cue_jump' 2 ? goto_cue 2 : var 'cue_jump' 3 ? goto_cue 3 : var 'cue_jump' 4 ? goto_cue 4 : var 'cue_jump' 5 ? goto_cue 5 : var 'cue_jump' 0 ? goto_cue 6
knob
param_greater 0% ? cycle 'cue_jump' 6 : cycle 'cue_jump' -6
button
var 'cue_jump' 1' ? goto_cue 1 : var 'cue_jump' 2 ? goto_cue 2 : var 'cue_jump' 3 ? goto_cue 3 : var 'cue_jump' 4 ? goto_cue 4 : var 'cue_jump' 5 ? goto_cue 5 : var 'cue_jump' 0 ? goto_cue 6
Inviato Wed 27 Jul 11 @ 10:50 pm
ClayDJ
It works! Great troubleshooting Synthet!
The fx rotary and button works as mapped to your last post.
If possible, can we backtrack now and add the fx button hold feature (trigger effects) to work with your last set of strings?
Any new string changes that I should let them know in the 'skins' threads (selected cue number to be illuminated in the UI).
Any changes to your last LED strings for the controller display?
Thanks again for all your help!
Clay
The fx rotary and button works as mapped to your last post.
If possible, can we backtrack now and add the fx button hold feature (trigger effects) to work with your last set of strings?
Any new string changes that I should let them know in the 'skins' threads (selected cue number to be illuminated in the UI).
Any changes to your last LED strings for the controller display?
Thanks again for all your help!
Clay
Inviato Thu 28 Jul 11 @ 8:46 am
synthet1c
nope, just take the % symbol out, other tan that it should work, I think maybe the feature of localizing shifts for duplicate controllers has been taken away
Inviato Thu 28 Jul 11 @ 9:09 am
ClayDJ
I'll try the full combination of strings and let you know how I make out.
Are these strings good for two controllers or do I have to add the $ sign anywhere?
Will this work with both layers of the Denon 5500?
Thanks,
Clay
Are these strings good for two controllers or do I have to add the $ sign anywhere?
Will this work with both layers of the Denon 5500?
Thanks,
Clay
Inviato Thu 28 Jul 11 @ 4:04 pm
synthet1c
$shift is for global shifts, as in it shifts both devices with one button
%shift, is meant to localize the shift to the individual deck you press the button on, so what I think you are after, but try it without the % sign and see if it works, also the first script that starts with "play ?" is wrong use the one that starts with "stop ?"
Not sure if it will work for both decks so you may need to change the midi channel of one of the decks to use channel 2 then copy the entire mapper xml, paste it in notepad and use find and rename and replace channel and the 1 with 2 for the decks, paste it all together and you should be good to go
%shift, is meant to localize the shift to the individual deck you press the button on, so what I think you are after, but try it without the % sign and see if it works, also the first script that starts with "play ?" is wrong use the one that starts with "stop ?"
Not sure if it will work for both decks so you may need to change the midi channel of one of the decks to use channel 2 then copy the entire mapper xml, paste it in notepad and use find and rename and replace channel and the 1 with 2 for the decks, paste it all together and you should be good to go
Inviato Thu 28 Jul 11 @ 6:25 pm
ClayDJ
Not too much luck so far adding the fx knob/button full strings. (full string = your previous fx knob and button strings with the 'stop' command).
It still works fine as newly mapped for the cue select and trigger. The second half of both the knob and button syntax strings work fine (which is what I am using now), but when I add in the first half of the strings that you suggested with the 'stop' command, the strings do not work.
Due to the Denon 5500 14bit knob/button;
The full strings will not work either with or without the %. It also does not matter what number I use with param_greater (50%, 50, 0%, 0) does not work using the full string (see previous post in this thread for more 5500 14bit info).
Since the Denon 5500 may have a 14bit knob/button then maybe the knob/button strings need some tweaking because of this?
If you have any other idea's on making the full strings work then please let me know.
I will try and tinker around with it a bit more otherwise.
Clay
It still works fine as newly mapped for the cue select and trigger. The second half of both the knob and button syntax strings work fine (which is what I am using now), but when I add in the first half of the strings that you suggested with the 'stop' command, the strings do not work.
Due to the Denon 5500 14bit knob/button;
The full strings will not work either with or without the %. It also does not matter what number I use with param_greater (50%, 50, 0%, 0) does not work using the full string (see previous post in this thread for more 5500 14bit info).
Since the Denon 5500 may have a 14bit knob/button then maybe the knob/button strings need some tweaking because of this?
If you have any other idea's on making the full strings work then please let me know.
I will try and tinker around with it a bit more otherwise.
Clay
Inviato Fri 29 Jul 11 @ 2:42 pm
ClayDJ
Hi Synthet1c (or anyone else that can help),
I have a denon 5500.
A few months back, you assisted me with setting up my FX knob/button to change/select cues.
This setup works great. It allows me to use the FX knob on my controller to cycle through the cues then push to select the cue.
Notice in the button syntax: var 'cue_jump' 0 ? goto_cue 6
It seems that in this scenario, cue 1 is actually cue 0, and cue 2 is actually cue 1, etc...
Is what I just mentioned correct?
The "cue_jump 0" works great for the controller but, I am now modifying a VDJ skin.
Using the various VDJ script language when programming, in some instances the skin wants to see cue 1= cue 0, and in other instances it wants to see cue 1= cue 1.
It can get pretty confusing.
Is there a way to write a default for either the skin or controller so that both the controller and skin see cue 1= cue 1, OR is there another way to write the above knob/button string so that cue 1 = cue 1 to the skin?
Thanks again for your help,
ClayDJ
I have a denon 5500.
A few months back, you assisted me with setting up my FX knob/button to change/select cues.
synthet1c wrote :
I think the reason you use param_greater 0 is you have a 14bit knob which is more sensitive
knob
param_greater 0% ? cycle 'cue_jump' 6 : cycle 'cue_jump' -6
button
var 'cue_jump' 1' ? goto_cue 1 : var 'cue_jump' 2 ? goto_cue 2 : var 'cue_jump' 3 ? goto_cue 3 : var 'cue_jump' 4 ? goto_cue 4 : var 'cue_jump' 5 ? goto_cue 5 : var 'cue_jump' 0 ? goto_cue 6
knob
param_greater 0% ? cycle 'cue_jump' 6 : cycle 'cue_jump' -6
button
var 'cue_jump' 1' ? goto_cue 1 : var 'cue_jump' 2 ? goto_cue 2 : var 'cue_jump' 3 ? goto_cue 3 : var 'cue_jump' 4 ? goto_cue 4 : var 'cue_jump' 5 ? goto_cue 5 : var 'cue_jump' 0 ? goto_cue 6
This setup works great. It allows me to use the FX knob on my controller to cycle through the cues then push to select the cue.
Notice in the button syntax: var 'cue_jump' 0 ? goto_cue 6
It seems that in this scenario, cue 1 is actually cue 0, and cue 2 is actually cue 1, etc...
Is what I just mentioned correct?
The "cue_jump 0" works great for the controller but, I am now modifying a VDJ skin.
Using the various VDJ script language when programming, in some instances the skin wants to see cue 1= cue 0, and in other instances it wants to see cue 1= cue 1.
It can get pretty confusing.
Is there a way to write a default for either the skin or controller so that both the controller and skin see cue 1= cue 1, OR is there another way to write the above knob/button string so that cue 1 = cue 1 to the skin?
Thanks again for your help,
ClayDJ
Inviato Mon 26 Sep 11 @ 9:31 am
synthet1c
hi clay, sorry I must not have thought about it properly when figuring it out, it would pobably work better if "'cue_jump' 0 " was "hot cue 1" that way it will default on cue 1, to make it work on a skin you should just need to make the panels with the other cues hidden, just leaving the first cue panel visable
var 'cue_jump' 1' ? goto_cue 2 : var 'cue_jump' 2 ? goto_cue 3 : var 'cue_jump' 3 ? goto_cue 4 : var 'cue_jump' 4 ? goto_cue 5 : var 'cue_jump' 5 ? goto_cue 6 : var 'cue_jump' 0 ? goto_cue 1
var 'cue_jump' 1' ? goto_cue 2 : var 'cue_jump' 2 ? goto_cue 3 : var 'cue_jump' 3 ? goto_cue 4 : var 'cue_jump' 4 ? goto_cue 5 : var 'cue_jump' 5 ? goto_cue 6 : var 'cue_jump' 0 ? goto_cue 1
Inviato Mon 26 Sep 11 @ 9:47 am
ClayDJ
Ok, thanks for your response Andrew!
Just to clarify:
The last syntax string that you listed in your previous note was for my controller knob (correct?).
Also, you mentioned:
"It would probably work better if cue_jump' 0 was "hot_cue 1".
Should I substitute "hot cue 1" in place of "cue_jump 0" in the controller FX button syntax (example: var hot cue 0 ? goto_cue 1), or substitute the "hot cue 1" within my skin XML for switching cues?
Thanks,
Clay
Just to clarify:
The last syntax string that you listed in your previous note was for my controller knob (correct?).
Also, you mentioned:
"It would probably work better if cue_jump' 0 was "hot_cue 1".
Should I substitute "hot cue 1" in place of "cue_jump 0" in the controller FX button syntax (example: var hot cue 0 ? goto_cue 1), or substitute the "hot cue 1" within my skin XML for switching cues?
Thanks,
Clay
Inviato Mon 26 Sep 11 @ 2:50 pm
