search

CodeKill3r / BCD2000HIDplus

Behringer BCD2000 custom firmware to use w/o driver
BSD 2-Clause "Simplified" License
6 stars 5 forks source link

Device issues after flashing. #5

Open charliecrash opened 1 year ago

charliecrash commented 1 year ago

Hi. I got myself a usb-burner and a clamp, and dumped the original rom and burned the tusboot.bin. Verify was ok. Device shows up as BCD2000+Midi and BCD2000+Audio. Midi works flawless, but audio is clicky and buggy. Restart didn't help. I also couldn't figure out what notes on what channel turns on the LED's. Do you know or should I keep looking?

I don't need the audio part so I just disabled it in device manager (win10pro 21H2). But it would be nice if it worked :)

I added my original dump, if that might differ from other versions. BCD2000ORIGINAL.zip

CodeKill3r commented 1 year ago

For audio try changing the buffers/use with asio4all/set other output format (should be 44100Hz 16bit only). Maybe try another USB port?

The MIDI commands for the LEDs should be the same as in the BCD2000 manual (MIDI channel 1 / CC 1-25 ---value 0-63= off / 64-127= on)

xd2 commented 1 year ago

I didn't notices any issue with audio using Mixxx (MacOs).
Nevertheless, as @charliecrash experienced, MIxxx here is unable to put the LEDs on.
Did anyone succeed in lightning LED with any dj software ?

xd2 commented 9 months ago

I Understood why it's not working with Mixxx 2.3 (i'm using Mac Os X).

Debug [Controller]: ControllerManager: Setting up devices
Debug [Controller]: Scanning PortMIDI devices:
Debug [Controller]:  Found output device # 1 BCD2000HID+  BCD2000 MIDI IN  
Debug [Controller]:  Found input device # 0 BCD2000HID+  BCD2000 MIDI OUT 
...
Debug [Controller]: MidiPresetFileHandler: Output mapping parsing complete.
Debug [Controller]: Opening controller: "BCD2000HID+  BCD2000 MIDI OUT "
Debug [Controller]: PortMidiController: Opening BCD2000HID+  BCD2000 MIDI OUT  index 0 for input
Debug [Controller]:   Starting engine
Debug [Controller]: Controller in script engine is: "BCD2000HID+  BCD2000 MIDI OUT "
Debug [Controller]: Applying controller preset...

As discussed in the forum, if the name of the midi in and midi out ports is not the same, Mixxx will only map the input device.
Consequently, no CC messages will reach the BCD input, LEDs won't light up :-(

@CodeKill3r, would it be possible to update firmware to get the same name for midi IN and OUT ?
I can't find this naming labels in the asm code, could it be that names are assigned by the operating system ?

CodeKill3r commented 8 months ago

@xd2 It is very possible, but I'm not sure if this is the right path, instead of bugging the Mixxx team to add support for split MIDI devices.

But if you want to experiment with them however they are here: aBcd2000mdi and aBcd2000mdo