Bhajan
Hello friends,
I am undergoing the task of mapping the Vestax VCI-400 Ean Golden Edition to Virtual DJ Pro 7. I am relatively new at mapping so I was hoping to get some assistance from more experienced mappers. This is a non-HID device, by the way.
Question:
Why would I need a "definition" xml ? Is there stuff that the definition file can do, that the wrapper cannot? If so, do i still use both? Or does everything just go in the definition file. I'm hoping someone can clear this up for me.
Thanks in advance. :)
I am undergoing the task of mapping the Vestax VCI-400 Ean Golden Edition to Virtual DJ Pro 7. I am relatively new at mapping so I was hoping to get some assistance from more experienced mappers. This is a non-HID device, by the way.
Question:
Why would I need a "definition" xml ? Is there stuff that the definition file can do, that the wrapper cannot? If so, do i still use both? Or does everything just go in the definition file. I'm hoping someone can clear this up for me.
Thanks in advance. :)
geposted Wed 11 Jul 12 @ 4:14 pm
synthet1c
the definition file is where you tell vdj what the control is "potentiometer, encoder, led" and you can add different modifiers to change how the midi messages are recieved "invert, steps, restrictions", if you use the simple midi wrapper everything is treated as standard 128 step midi and you can't control midi out messages for leds.
geposted Wed 11 Jul 12 @ 5:47 pm
Bhajan
Thanks for the reply synthet1c.
I guess for now, rather than over-complicating things, I'll just keep using the simple MIDI wrapper until I stumble upon the inherent limitations.
Would you mind taking a look at this?
I'm trying to map jog fx.This is one command but I've split it into multiple lines for improved readability.
# This is called when you spin the jogwheel
<map value="2-CC19" action="
deck 1 param_greater 50% ? deck 1 effect slider 1 +0.2% : deck 1 effect slider 1 -0.2% &
deck 1 param_greater 50% ? deck 1 effect slider 2 +0.2% : deck 1 effect slider 2 -0.2%"
/>
In this example slider 1 functions perfectly. Slider 2 decreases normally, but increases with a strange jumpiness. Also, when slider 2 reaches zero, it will not increase at all after that. It seems to have something to do with whichever command comes after the '&' sign. If I swap them and put slider 2 first in the command line, it functions perfectly, but slider 1 exhibits the same strange behavior.
I guess for now, rather than over-complicating things, I'll just keep using the simple MIDI wrapper until I stumble upon the inherent limitations.
Would you mind taking a look at this?
I'm trying to map jog fx.This is one command but I've split it into multiple lines for improved readability.
# This is called when you spin the jogwheel
<map value="2-CC19" action="
deck 1 param_greater 50% ? deck 1 effect slider 1 +0.2% : deck 1 effect slider 1 -0.2% &
deck 1 param_greater 50% ? deck 1 effect slider 2 +0.2% : deck 1 effect slider 2 -0.2%"
/>
In this example slider 1 functions perfectly. Slider 2 decreases normally, but increases with a strange jumpiness. Also, when slider 2 reaches zero, it will not increase at all after that. It seems to have something to do with whichever command comes after the '&' sign. If I swap them and put slider 2 first in the command line, it functions perfectly, but slider 1 exhibits the same strange behavior.
geposted Wed 11 Jul 12 @ 6:49 pm
synthet1c
you have the syntax wrong... When you use variables the syntax is
query ? action if true : action if false
what you have is this which is missing out on the second variable.
param_greater 50% ? deck 1 effect slider 1 +0.2% : deck 1 effect slider 1 -0.2% & deck 1 param_greater 50% ? deck 1 effect slider 2 +0.2% : deck 1 effect slider 2 -0.2%
this is the correct way to script it so it will change the two effect sliders at the same time.
param_greater 50% ? deck 1 effect slider 1 +0.2% & deck 1 effect slider 2 +0.2% : deck 1 effect slider 1 -0.2% & deck 1 effect slider 2 -0.2%
...btw definition files mean you don't need to specify the deck in each script, and only need to do it once per control pair/group, and you can name them to make it easier in the mapper, eg. if you add these lines in a definition file
<jog cc="0x13" channel="2" full="128" zero="0x40" deck="1" name="jog"/>
<jog cc="0x??" channel="?" full="128" zero=0x40" deck="2" name="jog"/>
then in the mapper you just need to map this for both decks
param_greater 0% ? effect slider 1 +0.2% & effect slider 2 +0.2% : effect slider 1 -0.2% & effect slider 2 -0.2%
Or if you want to really uncomplicate things you can simply map "effect slider 1 & effect slider 2" if both effect sliders are to go the same direction. Personally I like to separate forwards and backwards as sometimes I may want two effect sliders to move in opposite directions.
*also full is jog resolution, so would be more like 2000, but you would need to use a program like chackl's vdj definer that counts the steps, unfortunately this is only available to registered pro users.
query ? action if true : action if false
what you have is this which is missing out on the second variable.
param_greater 50% ? deck 1 effect slider 1 +0.2% : deck 1 effect slider 1 -0.2% & deck 1 param_greater 50% ? deck 1 effect slider 2 +0.2% : deck 1 effect slider 2 -0.2%
this is the correct way to script it so it will change the two effect sliders at the same time.
param_greater 50% ? deck 1 effect slider 1 +0.2% & deck 1 effect slider 2 +0.2% : deck 1 effect slider 1 -0.2% & deck 1 effect slider 2 -0.2%
...btw definition files mean you don't need to specify the deck in each script, and only need to do it once per control pair/group, and you can name them to make it easier in the mapper, eg. if you add these lines in a definition file
<jog cc="0x13" channel="2" full="128" zero="0x40" deck="1" name="jog"/>
<jog cc="0x??" channel="?" full="128" zero=0x40" deck="2" name="jog"/>
then in the mapper you just need to map this for both decks
param_greater 0% ? effect slider 1 +0.2% & effect slider 2 +0.2% : effect slider 1 -0.2% & effect slider 2 -0.2%
Or if you want to really uncomplicate things you can simply map "effect slider 1 & effect slider 2" if both effect sliders are to go the same direction. Personally I like to separate forwards and backwards as sometimes I may want two effect sliders to move in opposite directions.
*also full is jog resolution, so would be more like 2000, but you would need to use a program like chackl's vdj definer that counts the steps, unfortunately this is only available to registered pro users.
geposted Thu 12 Jul 12 @ 12:44 am
jusblaze246
Wow, Syn, that's all I can say.....What is this "Programming Witchcraft " you speak of?........You are a truly gifted man and everyone's go-to guy for VDJ script!......lololol
geposted Thu 12 Jul 12 @ 1:06 pm
Bhajan
Absolutely! :) I really appreciate it synthet1c. It makes complete sense to me now (i.e. what I was doing wrong syntactically). I have some mapping concepts that I hope to implement here that I think could be really awesome, so I may be seeking your wisdom in the future.
Also, if anyone would like to tinker with my mapping, go to:
forum.djtechtools.com/showthread.php?t=54693
Also, if anyone would like to tinker with my mapping, go to:
forum.djtechtools.com/showthread.php?t=54693
geposted Fri 13 Jul 12 @ 8:35 am
gogliko7
where can i download mapping for vci 400 on mac for virtual DJ? this site is giving me error every time i download it. is there any other sources?
geposted Wed 05 Dec 12 @ 1:15 pm
jusblaze246
Mappings are only available to Pro level licensed users and above, unfortunately.
geposted Wed 05 Dec 12 @ 1:32 pm