Entra:     

Forum: Old versions

Topic: Ion Discover DJ: Jogwheel Mapping confusion - Page: 1

Questa parte dell'argomento è obsoleta e potrebbe contenere informazioni obsolete o errate

I recently got the Ion Discover DJ for Christmas. It comes with Mixvibes which is a decent program, but I would rather use VirtualDJ.
I've tried doing the simple midi mapping and I get all the buttons and sliders to work, except the crossfader is inverted (when I slide the real crossfader to the left, the VDJ crossfader moves to the right).

My main issue, however, is that I cannot get the jog wheels to scratch. They are touch sensitive, I believe. When I map them myself I can get them to fast forward the song or rewind it, but not scratch. When I use the auto-learn function, it says my jog wheel has one key name, whether I spin it forwards or backwards.

Any help?

Here is my miditrace info:

Left:
90 4D 7F 00
B0 19 7F 00
B0 19 7F 00

Right:
90 4D 7F 00
B0 19 01 00
B0 19 01 00
 
Inviato Fri 25 Dec 09 @ 4:33 pm
And here is my right jog wheel miditrace info:

Left:
90 4E 7F 00
B0 18 7F 00
B0 18 7F 00

Right:
90 4E 7F 00
B0 18 01 00
B0 18 02 00
 
I will attempt to help, but jogs are notoriously difficult.

If mapping through"learn" is working & if you're moving the track at all with the jogs, at least it's a start.

if you can track down the data that the jogs send, using simple midi wrapper works, you'll need two commands with that data. one command to turn scratch on and one to calculate the movements. You'll need to build these into the mapper and the device def.

for instance, in the device definition, you create a button called "jog_touch", it will be activated by the message the the jog sends. This one gets NOTE data

In the definition
you'll also have a "jog", this one will need CC data & its variables(min/max)

the mapper will need commands that correspond to those? /\
|

Hope this doesn't sound like I know what I'm talking about, I don't, but I have spent many hours attempting.
Good luck
 
Usually a touch sensitive jogwheel will send a MIDI note for touch on/off and a CC for the jogwheel movement.

The note needs to be mapped to touchwheel_touch and the CC to touchwheel.

NOTE: A controller definition http://www.virtualdj.com/wiki/ControllerDefinition.html is usually required for a jogwheel to work correctly - Simple MIDI only supports basic buttons, sliders and knobs with min/max.
 
can the inverted crossfader be fixed?
 
Yes, if you add param_invert, e.g:

param_invert & crossfader
 
Thank you so much for the help. I still don't understand the jog wheel parameters, could you post a sample midi wrap command that I could compare to?
 
I can't get my jog wheels to work at all. I've tried to learn how to write a definition and xml file but its way to con fusing. can someone please help
 
It's unlikely that you will be able to map a jogwheel properly using Simple MIDI Wrapper. It does not support jogwheels - A definition that describes how the jogwheel functions is required for it to work correctly and optimally.

However, the following might work:

Map the touch sensor button to (Hold jogwheel still using a non-sensitive part, click learn and then touch it):

touchwheel_touch

Map the jogwheel movement to (Turn it using a non-sensitive part):

param_greater 50% ? touchwheel : param_invert & touchwheel

...Or possibly:

param_greater 50% ? touchwheel +0.1% : -0.1%
 
I can get the touch set, but it just stops the song both touch sensors work with "scratch_wheel_scratch" and I can set the movement note to "scratch_wheel" but can only move it forward or backward :( this just seems way harder than it should be. any help at all would be awesome!
Thanks!!
 
i think the ion is sending a note for movement? check how many note values there are. Outer rim, inner rim. Its like djtech imix reload.

1 note for touch
1 note for forward
1 note for backward
1 note for pitch forward
1 note for pitch backward

you need values for both decks. they might change if you have a "scratch/search" button.

then, in the definition and mapper put the following, but only with your midi notes (!)

<button note="0xXX" name="SEARCH" deck="1" />
<button note="0xXX" name="SEARCH" deck="2" />
<toggle note="0xXX" name="JOG_TOUCH" deck="1" />
<toggle note="0xXX" name="JOG_TOUCH" deck="2" />
<button note="0xXX" name="JOG-" deck="1" />
<button note="0xXX" name="JOG-" deck="2" />
<button note="0xXX" name="JOG+" deck="1" />
<button note="0xXX" name="JOG+" deck="2" />
<button note="0xXX" name="JOG-" deck="1" />
<button note="0xXX" name="JOG-" deck="2" />
<button note="0xXX" name="JOG+" deck="1" />
<button note="0xXX" name="JOG+" deck="2" />
<button note="0xXX" name="JOG-" deck="1" />
<button note="0xXX" name="JOG-" deck="2" />
<button note="0xXX" name="JOG+" deck="1" />
<button note="0xXX" name="JOG+" deck="2" />

MAPPER:

<map value="SEARCH" action="vinyl_mode" />
<map value="JOG-" action="touchwheel -0.01" />
<map value="JOG+" action="touchwheel +0.01" />
<map value="JOG_TOUCH" action="touchwheel_touch" />

i hope this helps.
 
this sounds like it should work
my only problem is how many midi trace codes I get when moving the wheel

Moving slightly forward gives me the code(B0 19 01 00) and reverse(B0 19 7f 00)
but the faster I move the wheel the code counts up 1. For example forward counts B0 19 01 00, B0 19 02 00, B0 19 03 00..... the third set of numbers depends on how fast I'm moving the wheel.
which do i use?????

*this is all just the left wheel moving forward*
 
sounds like slowly moving is pitch-bend, a button note, and fast moving is scratching, a control change.

on a second thought, it sounds like a encoder.

If the encoder sends messages for increments and decrements of its position (+1/-1), you can defines it with a <encoder> element, with the following properties:
- cc: the MIDI cc (second number in miditrace)
- inverted: (optional) set to "true" if the jog is inverted
- zero: set the cc value that represents zero. For a jog that sends 0x01 for forward movement and 0x7F for rewind, set this to "0" (default). For a jog that sends 0x41 for forward movement and 0x3F for rewind, set this to "0x40".
- max: (optional) specifies the value at which the encoder wraps

<encoder cc="XX" name="jogwheelLEFT" zero="0">

try to give the notes the jogwheel+0.01 action, and the touch-note and cc as jogwheel_touch and jogwheel

how does this work?
 

@VDJAK47

This controller is nothing like the DJ-Tech controllers ... you are giving poor advice ... please don't confuse the situation here. There are several different ways the manufactures implement MIDI and that is why we need to build definitions. The ION actually correctly implements MIDI unlike the i-Mix. The CC/Note is for 1 element of the controller, with the velocity/value controlling direction. Unfortunately the i-Mix used separate CC/Notes to identify direction ... which is more complex than it has to be.
 
-SENT-
I don't think any of its right but thanks
 
 
 
You will have to wait until we include the mapping in the next trial version release ... OR, you can purchase a Pro license and have access to the download.
 
i just downloaded it and it doesnt seem to work, any suggestions or instructions?
please and thanks
 
You ran the installer after you downloaded it - right ?

Did the installer put the files in the right place ? Check the My Documents\VirtualDJ\Devices for the ION Discover DJ definition file.

What O/S are you running ?
 
54%