VDJ Rob G
I am experimenting with both Bitfocus Companion and Chataigne connecting them to both Virtual Dj and MaestroDMX. The MaestroDMX communicate very well with both bridges using OSC. The midi connection with VDJ is causing a few headaches. Firstly, I have disabled midi2. Im using loopMIDI to set up the virtual ports. I have created device and mapper xml's and had some success.
My main issues concern intermittent connections and multiple device tabs showing up. I also managed to map some custom buttons for midi notes, but much more difficulty with cc mapping. Again, it seems intermittent, and only works usjng internal commands (such as sampler_volume_master), variable originate values seem impossible.
Questions:
Are there known limitations regarding virtual midi devices? Can I use variables to map cc values? Any pointers greatly appreciated :)
My main issues concern intermittent connections and multiple device tabs showing up. I also managed to map some custom buttons for midi notes, but much more difficulty with cc mapping. Again, it seems intermittent, and only works usjng internal commands (such as sampler_volume_master), variable originate values seem impossible.
Questions:
Are there known limitations regarding virtual midi devices? Can I use variables to map cc values? Any pointers greatly appreciated :)
Posted 8 hours ago
VDJ Rob G
Ultimately my idea is to create a remote skin with tabs to control basic functions from MaestroDMX, OBS, Synesthesia.live, and cantabile lite.
Posted 8 hours ago
locoDog
Done similar in the past [about 30 times] midi out [loopmidi, or loopbe] to lamping software, [live button press or action poi placed] worked fine, I haven't read up on the whole M$ midi thing and where that is at with those VirtMidiCabs,
honestly using 2.0 and the native M$ solution might be easier
I have mapping, definition and skin as a thing I sell with some initial training(hand holding)
The definition is easy but laborious, mapping isn't much different
the skin, script and the action poi placer are the clever bit
ripping out the commands from my skin and placing on a remote skin would be trivial for a skinner.
honestly using 2.0 and the native M$ solution might be easier
I have mapping, definition and skin as a thing I sell with some initial training(hand holding)
The definition is easy but laborious, mapping isn't much different
the skin, script and the action poi placer are the clever bit
ripping out the commands from my skin and placing on a remote skin would be trivial for a skinner.
Posted 7 hours ago