djDecks

Test build:
http://djdecks.be/macos/djDecksMac.zip

In the new build some very basic MIDI support is included.
I am thinking about a new system for this that will eventually replace the MIDI support in the windows version as well.
The idea is that custom MIDI mapping will have the same flexibility and possibilities of the native support for controllers.
Support for a new controller will then be easier to create and share, since it will just be a simple XML file.

Also, HID devices and Keyboard mappings could use the same system, and the format is very similar to how the current skin system works.

You can see an example that maps the first two buttons of a VCI-100 or VCM-100 in the devices folder.
The current build will only open 'vestax_vci100.xml', so if you want to experiment with your own midi controller, you have to edit that file.

To help you get the correct name of your midi controller and get the button/slider numbers, you can use the following helper program:
http://djdecks.be/macos/midiecho.zip

Manufacturer and Model are currently used to find and connect to the correct midi device.

Objects are either defined as <input>, <output> or <input_output>
<bytes_down> are the bytes sent from the controller when the key is pressed.
<bytes_up> are the bytes sent when the key is released.
<bytes> is used for sliders. The byte that indicates the current position should be 'VV'

If the controller also has leds to indicate the status, an output object can be used.
<bytes_down> are the bytes that will be send to the controller when the object is active,
<bytes_up> are the bytes that will be send to the controller when the object is inactive.

Since on many controllers, the input and output bytes are the same, an input_output object combines the two.

Type, value, valuespecifier and player are similar to how they work in skins, so the can be used to look them up.

In future versions it will be possible to use <TABS> sections with <TAB> sections in them.
These can be used to have the same buttons act differently when an effect is selected or while another key is pressed for example.

A new build that improves the MIDI support.
TABS sections are now possible, and a Tab can be selected with TabSelect objects, similar to how it works for skins.

MIDI Objects can now also have a <condition> field, so that the action is only performed if the condition is met.
I've used them in the VCI-100 mapping for the Sync button to make a short press match BPM's, but holding the button pressed for a while resets the pitch.

A MIDI Object can also have flash_length, flash_offset and flash_ratio fields, which will be used for output buttons to flash the led when it would otherwise just be off.
I used these in the VCI-100 mapping to make it clear that while the 'KEY' button is pressed you can press one of the 4 small buttons at the top.

I think the way this new system currently works it is already possible to create most of the functionality that required native support in the windows version.

the behringer bcd 2000 has no midi Support with a mac.
But I find a intresting driver:
http://bcd2000dj.blogspot.com/2007/01/m ... -2000.html
so with this driver i can use the bcd in ableton and other programms.

The VCI-100 is now almost complete.
In the new beta I've also started with the Denon HC-4500 controller.
The display was of course the hard part that makes it different from other controller, but the new midi mapping is now also capable of mapping such displays.

New beta with improvements for the HC-4500 mapping, and better quality scratching with any midi controller.

Good work. I see there are TODO inside the xml file and you have got some more midi commands working. But wouldnt it be easier for the non-tech non-programmer like myself to be able to read the script with Deck A and Deck B in the script? All the midi commands are listed for both decks with the LED functions. The only benefit I see for this, is when I want to use Effects 1,2,3 on Deck A and Deck B to be customized midi commands. How about a built in mini options from the HC4500 like that in what jpboggis does for his advanced midi mapper for VDJ?

Yo!
just playin with djdecks on my new 13" MB....
so fast...

anyone working on the Hercules midi support?
i love how the PC version natively supports the hercules mk2... any chance that map can be imported?

thanks

rowan

New beta which fixes the hc4500 not working anymore in previous beta.

Mappings for other controllers such as the dj consoles will be added, but it's not possible to just copy the native mappings from the pc version so the mappings have to be created from scratch.

Thanks, HC4500 is back working again.

Does anyone here own an Evolution UC-33e, and have a djDecks mapping for it?

I've taken a look at the XML files in the 'devices' folder, and I don't think I could really create one myself... Or is there any newbie-guide?

I basically want to control the effects, channel volume faders and EQ with it..

you could start here http://djdecks.be/index.php?module=docs

all the info about the skinning and scripting should be very helpful when reading the currently existing .xml
when you finally understand them, and you have written down all your buttons midi values (or found info about this in their manual or on their site)
then you can start creating a mapping...

New beta available.
MIDI Devices are no longer automatically loaded, you are now free to select a matching xml file with your device from Preferences.

Documentation on the new MIDI XML Format is also available now:
http://djdecks.be/index.php?module=docs ... di_xml.php

Thanks!!! with midiecho and skin helper i just started creating a device xml file for Behringer's BCR2000. It works great with djDecks mac version. I will upload the file when mapping is complete.

Anyone got BCD2000 working on OSX version of DJDecks?

There's a new beta online now which includes a bcd-2000 mapping.
Most things work, but it isn't as complete as the windows mapping yet.

btw, your signature seems quite large, would you mind putting some things on a single line so it doesn't distract from the discussions