-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hercules DJ Control Mp3 stops working after exactly 128 midi events #5207
Comments
Commented by: Pegasus-RPG Did you close Mixxx or does it quit on its own after 128 events? |
Commented by: Pegasus-RPG And do you have another MIDI controller you can test with in Mixxx? (Even if it's a virtual keyboard or something.) |
Commented by: groschang Mixxx keeps running, only stops responding to the controller. Unfortunately i don't have another MIDI device to test with. I'm using the 32 bit version. |
Commented by: Pegasus-RPG Have you perchance recently upgraded your Windows Hercules drivers? There's a release on 7/30/09: http://ts.hercules.com/eng/index.php?pg=view_files&gid=2&fid=28&pid=179&cid=1 Please try that, or if you already have that loaded, please try an earlier version. There may be a bug in the driver/firmware, since the SCS.3d and SCS.1m work fine in Windows on 1.7.0 and always have and these are all standard MIDI devices as far as Mixxx sees them. |
Commented by: deftdawg I just hammered Mixxx 1.7.0 on Windows XP w/ 3.HDJS.2009 drivers (the latest) and could not midi crap out after about 7 songs fiddling with just about every control pretty much continuously. Can one of you with an MP3 try clearing the output mappings, close, reopen Mixxx and try again. No LEDs should light on the device but controls should still respond. I'm wondering if this might be the same problem we had with sending too many updates to the outputs (this was a problem during the Linux driver development). |
Commented by: groschang Ok, now i did a clean reinstall of the latest Hercules drivers (just to be sure...) and tested 1.7.0 and the two beta versions. Same thing as before: beta 1 works fine, the other versions behave as i described above. Deleting the output Mappings didn't help anything. |
Commented by: groschang I've tried it with an older driver (2008/4) now. Didn't help. :-( |
Commented by: deftdawg Did you try removing the MIDI (led) outputs as I mentioned earlier? On Sep 6, 2009 10:40 AM, "Groschi" wrote: I've tried it with an older driver (2008/4) now. Didn't help. :-( -- Hercules DJ Control Mp3 stops working after exactly 128 midi events |
Commented by: groschang Yup. I cleared the output mappings and saved the result as a new midi.xml file, because on my machine Mixxx 1.70 doesn't "remember" the mappings of the previous session (as i mentioned above, this still works in beta 1). Then is restarted Mixxx and loaded the new midi.xml with the empty output-table. Nothing changed. |
Commented by: asantoni Hi Groschi, Thanks for continuing to work with us to troubleshoot this. Sean is In the meantime, I've dug up the Herc Control MP3 mappings from beta 1 Beta1: Beta2: Please try each one by placing it in your Mixxx/midi folder, starting Thanks! |
Commented by: groschang Hey, actually i'm the one who has to thank you guys for working on this great software. :-) I tried both files now. It didn't help. |
Commented by: Pegasus-RPG Okay, please try the attached build and let us know how it goes. |
Commented by: groschang It works. No more midi problems. |
Commented by: groschang Also, the log looks a bit different...
|
Commented by: groschang |
Commented by: groschang |
Commented by: Pegasus-RPG Freaky stuff, man. Now try this build & let me know. |
Commented by: groschang Doesn't work, shows the same behavior as in 1.70. |
Commented by: Pegasus-RPG This one oughta do it. Let me know. |
Commented by: Pegasus-RPG Yay! Marking fixed in r2514. Thank you so much for your time on this, Groschi!! So does the MP3 have any LEDs or other outputs? From the log, Mixxx is unable to see it as an output device too (Windows is not reporting it.) |
Commented by: groschang Don't know, is it supposed to work as a midi output device? |
Commented by: groschang
|
Issue closed with status Fix Released. |
Reported by: groschang
Date: 2009-08-08T16:34:05Z
Status: Fix Released
Importance: Undecided
Launchpad Issue: lp410750
Attachments: mixxx.log, [Mixx 1.70 logfile](https://bugs.launchpad.net/bugs/410750/+attachment/704252/+files/Mixx 1.70 logfile), [test build logfile](https://bugs.launchpad.net/bugs/410750/+attachment/704253/+files/test build logfile), mixxx.log, [Test build with some stupidity fixed in midiobjectwin](https://bugs.launchpad.net/bugs/410750/+attachment/705863/+files/Test build with some stupidity fixed in midiobjectwin), mixxx.log
On my Win XP machine this problem occurs with versions 1.70 beta2 & final, beta1 works fine.
The device stops working after the first couple of knob-/fader-movements. In the log i can see, that this always happens after exactly 128 midi-events.
I tested the functionality of the device with "Midi Monitor" and everything works fine, so it's unlikely to be a hardware- or driver-problem.
The text was updated successfully, but these errors were encountered: