Beachy03
Hello,
Recently when I connected my BCD3000 via USB it made me update the driver software (approx 2 weeks ago, was working perfectly the previous day - months before). With the new drivers installed (which match the latest updates from Behringers website) my controller is no longer recognized. I've been working at this for a little over 2 weeks, maybe 3 now and I cannot find a resolution here. I know I'm going to get referred to buy a different controller but that's not an immediate resolution for me right now, I would really like to get this BCD back in action.
Any assistance here would be greatly appreciated, I haven't mixed in a while and it's killing me!
Recently when I connected my BCD3000 via USB it made me update the driver software (approx 2 weeks ago, was working perfectly the previous day - months before). With the new drivers installed (which match the latest updates from Behringers website) my controller is no longer recognized. I've been working at this for a little over 2 weeks, maybe 3 now and I cannot find a resolution here. I know I'm going to get referred to buy a different controller but that's not an immediate resolution for me right now, I would really like to get this BCD back in action.
Any assistance here would be greatly appreciated, I haven't mixed in a while and it's killing me!
Posté Sun 13 Jul 14 @ 7:27 pm
djdad
We dont have a unit to see what the latest drivers changed (if anything has). so please do the following...
Open VirtualDJ, goto Config->OPTIONS tab
Change the setting CreateMidiLog to Yes (Show Advanced Option - checked)
Close VirtualDj.
Connect the BCD (if not connected already) and launch VirtualDJ.
close again.
Post here the content of the Log Report.txt file you will find in /Documents/VirtualDJ folder.
Open VirtualDJ, goto Config->OPTIONS tab
Change the setting CreateMidiLog to Yes (Show Advanced Option - checked)
Close VirtualDj.
Connect the BCD (if not connected already) and launch VirtualDJ.
close again.
Post here the content of the Log Report.txt file you will find in /Documents/VirtualDJ folder.
Posté Mon 14 Jul 14 @ 3:09 am
Beachy03
Thanks, and so sorry for the slow response. When it comes to this kind of stuff I'm technically challenged so I can't really read this:
Audio device found: name="2- Behringer BCD3000WDM V1.3.4.0" vid="0x1397" pid="0x00BF" mid="0xFFFFFFFF"
Audio device found: name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: input name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: input name="2- Behringer BCD3000WDM V1.3.4.0" vid="0x1397" pid="0x00BF" mid="0xFFFFFFFF"
Audio device found: asio="ASIO for Generic USB Device"
Audio device found: asio="ASIO4ALL v2"
Audio device found: asio="BCD3000 ASIO"
Audio device found: name="2- Behringer BCD3000WDM V1.3.4.0" vid="0x1397" pid="0x00BF" mid="0xFFFFFFFF"
Audio device found: name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: input name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: input name="2- Behringer BCD3000WDM V1.3.4.0" vid="0x1397" pid="0x00BF" mid="0xFFFFFFFF"
Audio device found: asio="ASIO for Generic USB Device"
Audio device found: asio="ASIO4ALL v2"
Audio device found: asio="BCD3000 ASIO"
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
MIDI Device Identifying: \\?\behringer#bcd3000wdm#7&2eae60d0&2&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midi1 (in:0 out:1)
MIDI Device Identified by general midi: \\?\behringer#bcd3000wdm#7&2eae60d0&2&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midi1
MIDI Device Identifying: Microsoft GS Wavetable Synth (in:-1 out:0)
MIDI Device Not Identified: Microsoft GS Wavetable Synth
Audio device found: name="2- Behringer BCD3000WDM V1.3.4.0" vid="0x1397" pid="0x00BF" mid="0xFFFFFFFF"
Audio device found: name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: input name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: input name="2- Behringer BCD3000WDM V1.3.4.0" vid="0x1397" pid="0x00BF" mid="0xFFFFFFFF"
Audio device found: asio="ASIO for Generic USB Device"
Audio device found: asio="ASIO4ALL v2"
Audio device found: asio="BCD3000 ASIO"
Audio device found: name="2- Behringer BCD3000WDM V1.3.4.0" vid="0x1397" pid="0x00BF" mid="0xFFFFFFFF"
Audio device found: name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: input name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: input name="2- Behringer BCD3000WDM V1.3.4.0" vid="0x1397" pid="0x00BF" mid="0xFFFFFFFF"
Audio device found: asio="ASIO for Generic USB Device"
Audio device found: asio="ASIO4ALL v2"
Audio device found: asio="BCD3000 ASIO"
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
MIDI Device Identifying: \\?\behringer#bcd3000wdm#7&2eae60d0&2&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midi1 (in:0 out:1)
MIDI Device Identified by general midi: \\?\behringer#bcd3000wdm#7&2eae60d0&2&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midi1
MIDI Device Identifying: Microsoft GS Wavetable Synth (in:-1 out:0)
MIDI Device Not Identified: Microsoft GS Wavetable Synth
Posté Sun 27 Jul 14 @ 6:00 pm
djdad
Could you please repeat the same procedure , but this time, dont connect the BCD 3000. So we ll need again the same Report log but without the BCD 3000.
Sorry for the troubles, but it seems that the Midi of BCD doesnt offer vid/pid so we are looking for a safe identifier. thank you
Sorry for the troubles, but it seems that the Midi of BCD doesnt offer vid/pid so we are looking for a safe identifier. thank you
Posté Mon 28 Jul 14 @ 12:00 am
Beachy03
Audio device found: name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: input name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: asio="ASIO for Generic USB Device"
Audio device found: asio="ASIO4ALL v2"
Audio device found: asio="BCD3000 ASIO"
Audio device found: name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: input name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: asio="ASIO for Generic USB Device"
Audio device found: asio="ASIO4ALL v2"
Audio device found: asio="BCD3000 ASIO"
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
MIDI Device Identifying: Microsoft GS Wavetable Synth (in:-1 out:0)
MIDI Device Not Identified: Microsoft GS Wavetable Synth
Audio device found: name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: input name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: asio="ASIO for Generic USB Device"
Audio device found: asio="ASIO4ALL v2"
Audio device found: asio="BCD3000 ASIO"
W/out the BCD connected - No need to apologize, you're trying to provide assistance and it's greatly appreciated!
Audio device found: input name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: asio="ASIO for Generic USB Device"
Audio device found: asio="ASIO4ALL v2"
Audio device found: asio="BCD3000 ASIO"
Audio device found: name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: input name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: asio="ASIO for Generic USB Device"
Audio device found: asio="ASIO4ALL v2"
Audio device found: asio="BCD3000 ASIO"
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
MIDI Device Identifying: Microsoft GS Wavetable Synth (in:-1 out:0)
MIDI Device Not Identified: Microsoft GS Wavetable Synth
Audio device found: name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: input name="IDT High Definition Audio CODEC" vid="0x111D" pid="0x7605"
Audio device found: asio="ASIO for Generic USB Device"
Audio device found: asio="ASIO4ALL v2"
Audio device found: asio="BCD3000 ASIO"
W/out the BCD connected - No need to apologize, you're trying to provide assistance and it's greatly appreciated!
Posté Tue 29 Jul 14 @ 8:12 pm
djdad
We have updated the default mapping files with an addition that could make the detection possible with version 8.
You will need the latest available beta build 1901.751 (or you can wait for that to become public).
You will need the latest available beta build 1901.751 (or you can wait for that to become public).
Posté Thu 31 Jul 14 @ 4:36 am
Beachy03
Thanks, I appreciate the help. Is there anywhere I can find more information on this?
Posté Thu 31 Jul 14 @ 7:38 pm
djdad
If you wish to get and try the beta build before it becomes public (in order to test the above), open VirtualDJ, goto Config->OPTIONS tab and change the GetBetaBuilds setting to Yes (in the Advanced Options)
Posté Thu 31 Jul 14 @ 11:50 pm