Quick Sign In:  

Forum: Old versions

Topic: midisport 4x4

This topic is old and might contain outdated or incorrect information.

Hi, i'm trying to connect my Behringer DDM4000 + my Akai S20 with a midi hub M-box MIDISPORT 4x4, have all the mapping files but, connected to the hub all midi channels are mixed! thanks for helping!
 
Posted Sat 26 Dec 15 @ 12:36 am
djrickmhaiti wrote :
Hi, i'm trying to connect my Behringer DDM4000 + my Akai S20 with a midi hub M-box MIDISPORT 4x4, have all the mapping files but, connected to the hub all midi channels are mixed! thanks for helping!
 
Posted Sat 26 Dec 15 @ 12:41 am
When there is no vid/pin in the mappings the first aphabetic mapping will display 5 times instead of having the 4 chanmels o of my midisport A.B.C.D and empech the other mapping to work.
I'm having difficulty to find the vid / pid of the akay s20 , was told to unable the midilog in virtualdj but it gave me a bunch of numbers and don't know wich one to pick.
I Think the midilog displays the sysexid also but I'm not sure which one it is.
 
Posted Sat 26 Dec 15 @ 12:49 am
VID and PID (and therefore the ability for VDJ to identify hardware) is only for USB devices.

Hardware that has 5 pin DIN MIDI connections won't be indentifiable to VDJ. It will only see the MIDI hub, because that has a USB connection.
 
Posted Sat 26 Dec 15 @ 1:19 am
thanks for the info.
Now what is my option if I want to use several midi devices with the midisport?
 
Posted Sat 26 Dec 15 @ 8:27 pm
Here is a log report :

--- 2015/12/20 - 19:28 (2587)
Audio device found: name="Realtek High Definition Audio" vid="0x10EC" pid="0x0269" hardwareID:"{0.0.0.00000000}.{6a8efe62-0a4f-48ba-aadf-00d98a4544bf}"
Audio device found: input name="Realtek High Definition Audio" vid="0x10EC" pid="0x0269" hardwareID:"{0.0.1.00000000}.{19084a2c-d2e0-46d5-a714-0a78a9a5a754}"
Audio device found: asio="ASIO4ALL v2" hardwareID:"232685C6-6548-49D8-846D4141A3EF7560"
Audio device found: asio="SL 1 Driver" hardwareID:"EA8BDD96-1C34-46FE-887AD55749ED1F23"
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
MIDI Device Identifying: \\?\usb#vid_0763&pid_1021#5&65407c9&0&1#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midisport4x4ina (in:0 out:1)
MIDI Device Identified by catch-all: \\?\usb#vid_0763&pid_1021#5&65407c9&0&1#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midisport4x4ina
Assigned Behringer DDM4000 V2, type:0, index:1
MIDI Device Identifying: \\?\usb#vid_0763&pid_1021#5&65407c9&0&1#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midisport4x4inb (in:1 out:2)
MIDI Device Identified by catch-all: \\?\usb#vid_0763&pid_1021#5&65407c9&0&1#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midisport4x4inb
Assigned Behringer DDM4000 V2, type:0, index:1
Assigned Behringer DDM4000 V2, type:0, index:1
MIDI Device Identifying: \\?\usb#vid_0763&pid_1021#5&65407c9&0&1#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midisport4x4inc (in:2 out:3)
MIDI Device Identified by catch-all: \\?\usb#vid_0763&pid_1021#5&65407c9&0&1#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midisport4x4inc
Assigned Behringer DDM4000 V2, type:0, index:1
Assigned Behringer DDM4000 V2, type:0, index:1
Assigned Behringer DDM4000 V2, type:0, index:1
MIDI Device Identifying: \\?\usb#vid_0763&pid_1021#5&65407c9&0&1#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midisport4x4ind (in:3 out:4)
MIDI Device Identified by catch-all: \\?\usb#vid_0763&pid_1021#5&65407c9&0&1#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midisport4x4ind
Assigned Behringer DDM4000 V2, type:0, index:1
Assigned Behringer DDM4000 V2, type:0, index:1
Assigned Behringer DDM4000 V2, type:0, index:1
Assigned Behringer DDM4000 V2, type:0, index:1
MIDI Device Identifying: Microsoft GS Wavetable Synth (in:-1 out:0)
MIDI Device Identified by catch-all: Microsoft GS Wavetable Synth
Assigned Behringer DDM4000 V2, type:0, index:1
Assigned Behringer DDM4000 V2, type:0, index:1
Assigned Behringer DDM4000 V2, type:0, index:1
Assigned Behringer DDM4000 V2, type:0, index:1
Assigned Behringer DDM4000 V2, type:0, index:1
Assigned Behringer DDM4000 V2, type:0, index:1
Assigned Behringer DDM4000 V2, type:0, index:1
Assigned Behringer DDM4000 V2, type:0, index:1
Assigned Behringer DDM4000 V2, type:0, index:1
Assigned Behringer DDM4000 V2, type:0, index:1
[19:32] Midi Out Closed (\\?\usb#vid_0763&pid_1021#5&65407c9&0&1#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midisport4x4ina)
[19:32] Midi Out Closed (\\?\usb#vid_0763&pid_1021#5&65407c9&0&1#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midisport4x4inb)
[19:32] Midi Out Closed (\\?\usb#vid_0763&pid_1021#5&65407c9&0&1#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midisport4x4inc)
[19:32] Midi Out Closed (\\?\usb#vid_0763&pid_1021#5&65407c9&0&1#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midisport4x4ind)
[19:32] Midi Out Closed (Microsoft GS Wavetable Synth)
 
Posted Sun 27 Dec 15 @ 3:44 pm
Hi guys, things are moving forward here! i got the Akai s20 and the DDM4000 to work on the midisport 4x4 !
(BUT the DDM4000 is not receiving data for the LEDs)
I added the lines :
<?xml version="1.0" encoding="UTF-8"?>
<device author="Pierrick_Madsen" drivername="MIDISPORT 4x4 In B" drivernameout="MIDISPORT 4x4 Out B" name="akai_S20" type="MIDI" >
for the S20 and :
<?xml version="1.0" encoding="UTF-8"?><device name="BEHRINGER_DDM4000_V2" author="Yannick.J" type="MIDI" description="Behringer DDM4000 V2" decks="4">
for the DDM4000.
virtual DJ did not see the DDM4000 when i added the (drivername="MIDISPORT 4x4 In A drivernameout="MIDISPORT 4x4 Out A" )
VDJ still displays the "Behringer DDM4000 V2" 5 times in the setup menu and none will "CONNECT" to the mixer for the LED display.
other problem is VDJ will not close, it will close the windows but continue to run as a process and and even prevent the laptop to shutdown
We can say we're half way there!! learning VDJ script and programming MIDI ... VDJ such a powerful tool !!
 
Posted Sun 27 Dec 15 @ 10:05 pm
still at the same stage .. Midi is still one way . and Virtual DJ don't want to Exit even if the window is close it still runs in processes !
 
Posted Sun 10 Jan 16 @ 6:39 pm
Hi, still no solution working with the MIDISOPORT 4x4 hub...one major problem is that Virtualdj don't want to close when the hub is connected .. even if I force to close VDJ when I go to the task manager VDJ is still there and the only option is to shutdown.
thanks for your help!
 
Posted Mon 04 Apr 16 @ 1:45 am
Hi everyone, I downloaded VDJ 7 and all controllers work perfectly LEDs on the DDM4000 lights are all on etc....with VDJ 7.. on the other hand VDJ 8 sees only the Akai with the right mapping, the DDM400 is not defined but VDJ8 sees it.
the last problem I'm facing now is that when I want to close either VDJ 7 or 8 it freezes and even if the software appear to close they remain working in the background. but if I disconnect the hub before I close VDJ 7 or 8 they will close normally.
so.. VDJ 7 sees both MIDI devices but won't close.
VDJ 8 only see the Akai 's mapping only and won't close.
Thanks for any help to solve the closing problem.
 
Posted Sun 10 Apr 16 @ 11:08 pm
Hi, I finally have a hand on the Midisport 4x4 ... if you have one .. know that you need to change the number in the definition file ex: "X- MIDISPORT..." X = the number you get in VDJ mapping menu.
Every time you connect to a different USB port, the PORT # number will change and you will have to do the same to the DEFINITION file .
Hope that info can help someone!


Now I still have an unsolved problem with the Midisport 4x4 driver that will keep VDJ from shutting down.
I'm currently using Windows 10 and the latest Midisport 4x4 original driver.
Any one who could help me with this problem, I would appreciate it!
THANKS!
 
Posted Sun 11 Dec 16 @ 2:40 pm


(Old topics and forums are automatically closed)