I want to use the B buttons on my 2 Denon DN-S1200s with a 4 deck skin with those 2 scripts (1) Switch between Deck 1 & 3:
deck 1 select ? deck 3 select & deck 3 leftdeck : deck 1 select & deck 1 leftdeck) for the left side of the 4 decks and (2) Switch between Deck 2 & 4:
deck 2 select ? deck 4 select & deck 4 rightdeck : deck 2 select & deck 2 rightdeck) for the right side of the 4 decks.
I want the B button to act independently on each controller.
Another problem DN-S1200s buttons are not able to act independently if the controllers are set to default decks in a 4 deck skin.
Problem with Denon controllers when they are set to default decks they act as just one deck which is not a good deal when practically speaking each deck should be able to control one side of the decks independently!
deck 1 select ? deck 3 select & deck 3 leftdeck : deck 1 select & deck 1 leftdeck) for the left side of the 4 decks and (2) Switch between Deck 2 & 4:
deck 2 select ? deck 4 select & deck 4 rightdeck : deck 2 select & deck 2 rightdeck) for the right side of the 4 decks.
I want the B button to act independently on each controller.
Another problem DN-S1200s buttons are not able to act independently if the controllers are set to default decks in a 4 deck skin.
Problem with Denon controllers when they are set to default decks they act as just one deck which is not a good deal when practically speaking each deck should be able to control one side of the decks independently!
Posté Thu 03 Feb 11 @ 12:23 pm
This will not work because the Denon DN-S1200 is a player only and does not have PFL/CUE buttons as an all-in-one controller would have. They are also single deck controllers, so by default, left/right deck logic will not work.
You can already switch decks by pressing the EJECT button each player. If you wish to toggle between 1 & 3 on one, and 2 & 4 on the other, try using the following:
action_deck 1 ? on & assign_controller "S1200" 3 : action_deck 2 ? on & assign_controller "S1200" 4 : action_deck 3 ? assign_controller "S1200" 1 : assign_controller "S1200" 2
You may also need refresh_controller for the displays and LED's to update correctly - If so, try:
action_deck 1 ? on & assign_controller "S1200" 3 & refresh_controller "S1200" : action_deck 2 ? on & assign_controller "S1200" 4 & refresh_controller "S1200" : action_deck 3 ? assign_controller "S1200" 1 & refresh_controller "S1200" : assign_controller "S1200" 2 & refresh_controller "S1200"
You can already switch decks by pressing the EJECT button each player. If you wish to toggle between 1 & 3 on one, and 2 & 4 on the other, try using the following:
action_deck 1 ? on & assign_controller "S1200" 3 : action_deck 2 ? on & assign_controller "S1200" 4 : action_deck 3 ? assign_controller "S1200" 1 : assign_controller "S1200" 2
You may also need refresh_controller for the displays and LED's to update correctly - If so, try:
action_deck 1 ? on & assign_controller "S1200" 3 & refresh_controller "S1200" : action_deck 2 ? on & assign_controller "S1200" 4 & refresh_controller "S1200" : action_deck 3 ? assign_controller "S1200" 1 & refresh_controller "S1200" : assign_controller "S1200" 2 & refresh_controller "S1200"
Posté Fri 04 Feb 11 @ 12:15 pm
Thank you for the reply. According to the default eject button with the script holding 1000ms ? play ? nothing : unload : invert_controllers & refresh_controller "S1200" that will switch the decks In the DN-S1200.
I am using a skin with only 4 decks. Why does when I use that script it switches from deck1 thru deck 10. I want that cycle to narrow down to just 4 decks not 10 decks.
I am trying the other scripts you put above no luck yet!
I am using a skin with only 4 decks. Why does when I use that script it switches from deck1 thru deck 10. I want that cycle to narrow down to just 4 decks not 10 decks.
I am trying the other scripts you put above no luck yet!
Posté Fri 04 Feb 11 @ 6:04 pm
The number of decks is determined by the skin that you are using.
Perhaps you are using a custom skin with 10 decks defined (Possibly for samples?) and 4 actually on screen at any time.
The EJECT button will cycle through all available decks in order (E.g: 1 -> 4 for the default 4 deck skins included with VirtualDJ.)
Perhaps you are using a custom skin with 10 decks defined (Possibly for samples?) and 4 actually on screen at any time.
The EJECT button will cycle through all available decks in order (E.g: 1 -> 4 for the default 4 deck skins included with VirtualDJ.)
Posté Fri 04 Feb 11 @ 8:15 pm
Is there an easy way to modify the skin to only cycle thru the 4 decks only?
Posté Fri 04 Feb 11 @ 8:46 pm
Is there a way with this script (holding 1000ms ? play ? nothing : unload : invert_controllers & refresh_controller "S1200") to make one DN-S100 eject button to switch just deck 1 & 3 and the other eject button to switch between deck 2 & 4?
Posté Fri 04 Feb 11 @ 11:14 pm
You can edit the skin XML file and change nbdecks="4", but then the skin may not work correctly any more. It's better to use a skin that's designed for 4 decks only, such as the default 4 deck skin.
invert_controllers will always cycle through all available decks.
invert_controllers will always cycle through all available decks.
Posté Sat 05 Feb 11 @ 12:22 pm
jpboggis, thank you for everything!
Posté Sat 05 Feb 11 @ 7:18 pm
Hi,
can you please tell me if it is possible to map the dennon MC6000 Monitor controls (Cue/Master - Phones Volume) to the corresponding controls in the deafult 4 deck skin? Currently it would seem that they are not.
Also I notice that the main volume control is also not mapped.
I am not sure if the Monitor or Master Volume in the Hardware on the Dennon MC6000 is "midi" controllable.
I guess there is a simple reason for this.
Many thanks,
Mark
can you please tell me if it is possible to map the dennon MC6000 Monitor controls (Cue/Master - Phones Volume) to the corresponding controls in the deafult 4 deck skin? Currently it would seem that they are not.
Also I notice that the main volume control is also not mapped.
I am not sure if the Monitor or Master Volume in the Hardware on the Dennon MC6000 is "midi" controllable.
I guess there is a simple reason for this.
Many thanks,
Mark
Posté Mon 07 Feb 11 @ 11:00 am
The MC6000 is a real hardware mixer and these items are implemented in the hardware of the mixer.
They cannot be mapped, and if they could, you would end up with a doubling of the effect, e.g: Master volume would reduce twice as much because VirtualDJ would first apply its adjustment in software, then the mixer of the MC6000 would also apply its adjustment in hardware.
They cannot be mapped, and if they could, you would end up with a doubling of the effect, e.g: Master volume would reduce twice as much because VirtualDJ would first apply its adjustment in software, then the mixer of the MC6000 would also apply its adjustment in hardware.
Posté Mon 07 Feb 11 @ 12:09 pm