djtriple9
Does VDJ on Mac support the creation of MIDI maps that aren't already in the software? It doesn't create a Devices folder like it does in windows, but I know its looking somewhere because I can use the stock map of Pioneer CDJ 400 with no issue. I have made a map for Stanton DaScratches and want to use it on the mac side and not use Vista/Bootcamp. I have a Mapper folder, but I need to know what to do with my Device xml file.
geposted Tue 08 Sep 09 @ 9:20 pm
Made In Breizh
Hello mjh99ent,
Yes, you can create a MIDI map in VirtualDJ 6.0.2 Pro on Mac.
In VirtualDJ
- click on Config Button,
- go to Mappers tab,
- in the list of connected devices (by default, the field shows the keyboard), switch to Simple MIDI Wrapper
- enter your commands (for each command, click on new in the key list, click on Auto-learn button, push the button on your MIDI controller, type the action in the action field)
- click on OK at the end
The MIDI preset are saved in a file called Generic Midi Mapping.xml stored in Macintosh HD > Users > Your user name > Documents > VirtualDJ > Mappers.
A limit in the system is that VirtualDJ doesn't let any option to save a MIDI map with a name or to load a MIDI map.
VirtualDJ 6.0.2 removal of the list of presets (which were in VirtualDJ 6.0.1) is causing
- bugs of not detection of controllers, (instead od loading the preset file as with other software, if VirtualDJ 6.0.2 doesn't detect the controller, you cannot load the preset file as you cannot get it)
- no way to correct bugged maps (DJ Control Steel map is bugged with a right Stop button not mapped in VDJ 6.0.2 map for Mac OS).
A temporary solution consists in copying by yourself in Mac OS finder this file MIDI xml and rename it with a decent name instead of this mess (instead of 'generic MIDI Mapping', you call it with the name of the controller, of course), and when you want to use it, you rename it with this generic MIDI Mapping.xml name, but of course it is a complicated workaround to correct a limit I fail to understand.
Yes, you can create a MIDI map in VirtualDJ 6.0.2 Pro on Mac.
In VirtualDJ
- click on Config Button,
- go to Mappers tab,
- in the list of connected devices (by default, the field shows the keyboard), switch to Simple MIDI Wrapper
- enter your commands (for each command, click on new in the key list, click on Auto-learn button, push the button on your MIDI controller, type the action in the action field)
- click on OK at the end
The MIDI preset are saved in a file called Generic Midi Mapping.xml stored in Macintosh HD > Users > Your user name > Documents > VirtualDJ > Mappers.
A limit in the system is that VirtualDJ doesn't let any option to save a MIDI map with a name or to load a MIDI map.
VirtualDJ 6.0.2 removal of the list of presets (which were in VirtualDJ 6.0.1) is causing
- bugs of not detection of controllers, (instead od loading the preset file as with other software, if VirtualDJ 6.0.2 doesn't detect the controller, you cannot load the preset file as you cannot get it)
- no way to correct bugged maps (DJ Control Steel map is bugged with a right Stop button not mapped in VDJ 6.0.2 map for Mac OS).
A temporary solution consists in copying by yourself in Mac OS finder this file MIDI xml and rename it with a decent name instead of this mess (instead of 'generic MIDI Mapping', you call it with the name of the controller, of course), and when you want to use it, you rename it with this generic MIDI Mapping.xml name, but of course it is a complicated workaround to correct a limit I fail to understand.
geposted Wed 09 Sep 09 @ 9:10 am
jpboggis
You need to create the Devices folder if it's not present.
geposted Wed 09 Sep 09 @ 1:07 pm
djtriple9
Made In Breizh wrote :
Hello mjh99ent,
Yes, you can create a MIDI map in VirtualDJ 6.0.2 Pro on Mac.
In VirtualDJ
- click on Config Button,
- go to Mappers tab,
- in the list of connected devices (by default, the field shows the keyboard), switch to Simple MIDI Wrapper
- enter your commands (for each command, click on new in the key list, click on Auto-learn button, push the button on your MIDI controller, type the action in the action field)
- click on OK at the end
The MIDI preset are saved in a file called Generic Midi Mapping.xml stored in Macintosh HD > Users > Your user name > Documents > VirtualDJ > Mappers.
A limit in the system is that VirtualDJ doesn't let any option to save a MIDI map with a name or to load a MIDI map.
VirtualDJ 6.0.2 removal of the list of presets (which were in VirtualDJ 6.0.1) is causing
- bugs of not detection of controllers, (instead od loading the preset file as with other software, if VirtualDJ 6.0.2 doesn't detect the controller, you cannot load the preset file as you cannot get it)
- no way to correct bugged maps (DJ Control Steel map is bugged with a right Stop button not mapped in VDJ 6.0.2 map for Mac OS).
A temporary solution consists in copying by yourself in Mac OS finder this file MIDI xml and rename it with a decent name instead of this mess (instead of 'generic MIDI Mapping', you call it with the name of the controller, of course), and when you want to use it, you rename it with this generic MIDI Mapping.xml name, but of course it is a complicated workaround to correct a limit I fail to understand.
Yes, you can create a MIDI map in VirtualDJ 6.0.2 Pro on Mac.
In VirtualDJ
- click on Config Button,
- go to Mappers tab,
- in the list of connected devices (by default, the field shows the keyboard), switch to Simple MIDI Wrapper
- enter your commands (for each command, click on new in the key list, click on Auto-learn button, push the button on your MIDI controller, type the action in the action field)
- click on OK at the end
The MIDI preset are saved in a file called Generic Midi Mapping.xml stored in Macintosh HD > Users > Your user name > Documents > VirtualDJ > Mappers.
A limit in the system is that VirtualDJ doesn't let any option to save a MIDI map with a name or to load a MIDI map.
VirtualDJ 6.0.2 removal of the list of presets (which were in VirtualDJ 6.0.1) is causing
- bugs of not detection of controllers, (instead od loading the preset file as with other software, if VirtualDJ 6.0.2 doesn't detect the controller, you cannot load the preset file as you cannot get it)
- no way to correct bugged maps (DJ Control Steel map is bugged with a right Stop button not mapped in VDJ 6.0.2 map for Mac OS).
A temporary solution consists in copying by yourself in Mac OS finder this file MIDI xml and rename it with a decent name instead of this mess (instead of 'generic MIDI Mapping', you call it with the name of the controller, of course), and when you want to use it, you rename it with this generic MIDI Mapping.xml name, but of course it is a complicated workaround to correct a limit I fail to understand.
I have over 90 commands I'm creating. No way I'm doing that one at a time. I want to be able to drop xml files in the devices and mapper folders like in windows. This lets me not only create my own maps but import other peoples as well.
geposted Wed 09 Sep 09 @ 3:00 pm
djtriple9
jpboggis wrote :
You need to create the Devices folder if it's not present.
I did this, it either did not work or I missed a step. Can you create a test scenario of adding a decive showing where to put your xml files and then how to activate that file in the software?
geposted Wed 09 Sep 09 @ 3:02 pm
jpboggis
First you would browse to your VirtualDJ home folder, which on Mac would be /users/YOURNAME/Documents/VirtualDJ
Next create the folders Devices and/or Mappers (As appropriate if they do not exist.)
Copy your definition file to the Devices folder and your mapping to the Mappings folder.
If the controller is not detected, then there may be a problem with the mapping and/or definition.
If it works on PC, and you are using devicename="Name", it's name may be different on Mac to PC.
Ideally, you should use SysEx if the controller supports it.
Next create the folders Devices and/or Mappers (As appropriate if they do not exist.)
Copy your definition file to the Devices folder and your mapping to the Mappings folder.
If the controller is not detected, then there may be a problem with the mapping and/or definition.
If it works on PC, and you are using devicename="Name", it's name may be different on Mac to PC.
Ideally, you should use SysEx if the controller supports it.
geposted Wed 09 Sep 09 @ 6:01 pm
djtriple9
Tried with device name and with midiin. Also tried with nothing as per the documentation saying it will apply it to all devices that don't match another profile no love dude....
geposted Thu 10 Sep 09 @ 12:17 am
djtriple9
So I got it to show in the menu by not identifying a device (hopefully won't interrupt things when I hook up the CDJ 400's), but it is still useless. After selecting it from the drop down there is no response. revrting back to the simple MIDI it is unresponsive as well. I guess I'll be using bootcamp for now....
geposted Sat 12 Sep 09 @ 2:50 am
jpboggis
If no device ID is specified, it will apply to all unrecognised MIDI devices, so it shouldn't affect a recognised one such as CDJ-400.
It should be possible to ID by name or SysEx ID though - Perhaps there is a bug with this on the Mac version?
One drawback with providing no ID is that it may also apply to your soundcard's MIDI synth, causing piano notes to play as LED's are activated. This can be worked around by muting the MIDI synth or turning its volume down to zero.
NOTE: Selecting it from the list will NOT activate it. It is activated automatically if the hardware is present and detected. For an definition with no device identification, it would be active for all unrecognised MIDI devices, but this might not be working on the Mac version.
It should be possible to ID by name or SysEx ID though - Perhaps there is a bug with this on the Mac version?
One drawback with providing no ID is that it may also apply to your soundcard's MIDI synth, causing piano notes to play as LED's are activated. This can be worked around by muting the MIDI synth or turning its volume down to zero.
NOTE: Selecting it from the list will NOT activate it. It is activated automatically if the hardware is present and detected. For an definition with no device identification, it would be active for all unrecognised MIDI devices, but this might not be working on the Mac version.
geposted Sat 12 Sep 09 @ 1:17 pm
djtriple9
I only run the piano in the studio, the macbook is strictly for DJing so that won't be an issue. I can't figure out why it won't respond to the midi map at all....I would expect something to work...the notes are universal regardless of Windows or Mac, and the map works on Windows flawlessly.
geposted Sat 12 Sep 09 @ 1:25 pm
artofarto
i
geposted Wed 17 Feb 10 @ 6:11 pm
djwalley
Hi,
Has any1 tried mapping using TouchOSC and Osculator on the mac?
Has any1 tried mapping using TouchOSC and Osculator on the mac?
geposted Fri 16 Jul 10 @ 2:12 pm
dacishere
So I just bought some support hardware for VDJ and was hoping someone had some helpful 'getting started' tips.
My system is Mac pro 13", VDJ pro, Akai MPK25 Midi, M-Audio fast track pro AI.
Does VDJ support the Mpk25?
If so, is there specific config I need to do to use the midi properly?
My system is Mac pro 13", VDJ pro, Akai MPK25 Midi, M-Audio fast track pro AI.
Does VDJ support the Mpk25?
If so, is there specific config I need to do to use the midi properly?
geposted Wed 18 May 11 @ 6:38 pm