Ingreso rápido:  

Forum: VirtualDJ Technical Support

Tema: Issues applying definition file....

Este tópico es antiguo y puede contener información incorrecta para la nueva versión.

New guy here, first post.
Trying to create a definition, no issues with that, however the log report shows it's being detected as a general midi device.
--MIDI Device Identifying: \\?\bomebus#bomemidi#02#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\bomemidiin (in:0 out:-1)
--MIDI Device Identified by general midi: \\?\bomebus#bomemidi#02#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\bomemidiin

In monitoring the midi port on the device, VDJ isn't sending the sysex identity request...
Definition file:
<?xml version="1.0" encoding="UTF-8"?>
<!-- file name DN500BD.xml -->
<device name="DN500BD" description="Denon DN-500BD" version="8.xx" author="djMightyMaxx" type="MIDI" decks="1" sysexid="F07E??060200020BF7">
<!-- out commands -->
<sysex value="F0 7F 01 06 02 F7" name="PLAY" />
<!-- this may be wrong -->
<sysexin sysexid value="F0 7F 01 07 02 F7" name = "PLAY"/>
<!-- alternate form can use wild cards as in the device section
<sysexin sysexid="F0 7F 01 07 02 F7" name = "PLAY"/>
<sysexin value="F0 7F 01 07 02 F7" name = "PLAY"/>
-->
</device>

Any help would be much appreciated...



 

Mensajes Wed 24 Aug 16 @ 12:07 am
It's a Blu-Ray player - with no MIDI.
 

Mensajes Wed 24 Aug 16 @ 9:11 am
I'm building a midi to serial converter using Bomes midi translator pro...
So vdj it talking to Bomes virtual midi port, which I can monitor on that end, that's how I know it's not sending any sysex discovery on vdj startup....
 

Mensajes Wed 24 Aug 16 @ 12:30 pm
Seems that device identification only works by using the midi port name, at least that's the only way I've gotten it to apply the def file.
 

Mensajes Tue 30 Aug 16 @ 12:45 pm


(Los tópicos y foros antiguos son automáticamente cerrados)