-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Problems with Reloop Digital Jockey 2 Master edition #6556
Comments
Commented by: isra |
Commented by: isra
|
Commented by: Pegasus-RPG I see the problem. Disable the MIDI Through device, then reload the Reloop preset and let us know if that solves it. |
Commented by: isra Sorry, I am afraid you are going to have to be more detailed. I am not a Mixxx experienced user, I just bought the Reloop device, installed Mixxx and have not been able to use it yet, to my great frustration:
Next attempt:
When I click OK, then another popup almost identical, just with different script functions, like 'DigitalJockey2Controller.EnableHeadPhone1', 'DigitalJockey2Controller.LoopIn' and many others that "will not be bound". Was this what you wanted me to try? Thank you for your help |
Commented by: rryan Hi iLugo, What Sean means is that you should disable the MIDI Through Port (uncheck the 'Enabled' box) and leave it disabled. The MIDI-through port is not a valid MIDI device. Do you see a device in the preferences representing the Reloop device? The fact that the MIDI-through port can crash Mixxx is a serious problem we've had for a while though. We really should either blacklist it or pin down the race conditions that allow it to crash Mixxx. |
Commented by: isra Hi Ryan, Thanks a lot for the explanation. Now I understand that the Midi Through port is something that I do not want enabled in any case until the bug is fixed. How this is supposed to appear? I have tried connecting and reconnecting the Reloop device USB connector to different USB ports. Is there anything else that I need to do to get this device recognized by Mixxx? am I doing/missing something incredibly stupid?
...although the Through port has been disabled (and the program restarted and the Reloop reconnected since that). So, could this mean that there is still some configuration that forces the Reloop device to be associated to Midi through port, perhaps as a result of a previous configuration where the port was enabled? could this be reseat/eliminated to see if the program will finally detect the Reloop device? or, again, perhaps I am failing to do a basic thing? I have to say that the Reloop device is working under Windows/Traktor, so I have to exclude a hardware failure from the Reloop device itself or its cable. Once again, thank you for your interest . The Reloop device is a "Top Seller" in conrad.de, so I am sure this could help others who, like me, want to use this wonderful Mixxx program in Linux and avoid the Windows system completely. |
Commented by: rryan Hi iLugo, If the device doesn't show up in Mixxx then it is likely that it is not Could you run these two commands and paste the output? The first one lists On Wed, Jul 4, 2012 at 12:56 PM, iLugo wrote:
|
Commented by: isra Hi Ryan, I am attaching the requested output for the commands listed below in the next comments immediately. Interestingly, lsusb output (see attachment lsusb_-v.txt) will state: "libusb couldn't open USB device /dev/bus/usb/002/003: Permission denied." for all devices. For this reason, I run it with sudo (see sudo_lsusb_-v.txt). It shows now at least the iManufacturer, iProduct and few additional lines. This is different than lsusb as regular user. |
Commented by: isra |
Commented by: isra |
Commented by: isra |
Commented by: isra |
Commented by: isra |
Commented by: isra |
Commented by: isra By the way, the Reloop Digital Jockey 2 Interface Edition is reported to work in Ubuntu 10.10 amd64 http://permalink.gmane.org/gmane.comp.multimedia.mixxx.devel/3727 -- and previously also working on Ubuntu 9.10 in http://www.digipedia.pl/usenet/thread/15448/754/
I will try again creating the /etc/udev/rules.d/15-mixxx-usb.rules and see if this yields any significant differences. Any suggestions/advices are most welcome. |
Commented by: isra FYI: |
Commented by: rryan Hmm. It looks like the Reloop device is this one: Bus 002 Device 003: ID 200c:1009 The device class is "Vendor Specific" which means that it is not a class-compliant MIDI device and Linux needs a driver to speak to it. Have you already tried creating a udev rule? Could you paste the contents of what you're trying here? |
Commented by: isra I have done as instructed in the last entry of http://www.mixxx.org/wiki/doku.php/troubleshooting , i.e., created a udev rules file: /etc/udev/rules.d/15-mixxx-usb.rules with the following contents:
Then: "sudo chmod 644 /etc/udev/rules.d/15-mixxx-usb.rules" I disconnected the Reloop device, then reconnected it. Then did dmesg, and the relevant line (last) is: Then: "amidi -l", "aseqdump -l" and "aconnect -i" yield exactly the same output as the original experiment above (see attachments). Then "lsub -v" (no sudo) yields (for the Bus 002 Device 003: ID 200c:1009 ) exactly the same output as the above attachment sudo_lsub_-v.txt - at least now it is not necessary to do sudo, thanks to the above udev rule. Then if I run Mixxx, all remains the same: the Reloop controller is not shown in the Preferences -> MIDI Controllers section, and I can use Mixxx, but no controller (as long as I do not enable the midi Through port, then Mixxx crashes). Running out of ideas.... so far it would seem as if Linux does not recognizes it and needs a driver, even in Ubuntu 12.04 with kernel 3.2.0-23.... unless I have something wrong with my PC's hardware (but in dualbooting in Windows/Traktor it works). I still find strange that the Interface Edition would be recognized but not the Master Edition... I would like to know what is the driver that the Interface Edition is using, or by which mechanism that version works. I have seen posts in the forum like this http://mixxx.org/forums/viewtopic.php?f=7&t=1226&p=14638&hilit=reloop#p7754 where the user Jones seems to know about the Master edition. |
Commented by: Pegasus-RPG HID controller support is new as of Mixxx v1.11.0. Please download the latest beta from the forums and see if it appears (though I'm doubtful given that lsusb output.) Apparently, despite the similar names, the two controller editions have very different interface hardware. |
Commented by: Pegasus-RPG If it doesn't appear in v1.11.0, a contributor is working on bulk USB device support for v1.12.0 so that might help you. (Keep an eye on the forums as we'll post a test build there when the feature is ready to test.) |
Commented by: isra Thank you very much Sean, |
Commented by: rryan Since the crashes were related to the midi-through-port (which is a known issue) I'm renaming this bug to just focus on supporting the reloop device. |
Commented by: donato-troccoli Hi everyone, I've got the same hardware and the Reloop Digital Jockey 2 Master edition isn't working at all with Mixxx in Ubuntu 13.10 Saucy distr. |
Commented by: donato-troccoli I think the difference between the others edition of the reloop digital jockey 2 is this (Master Edition) has a built-in audio interface or sound card. D/A sample audio conversion is made by the Reloop device and then sent to the outputs Balanced /Unbalanced /Booth RCA. |
Commented by: donato-troccoli In the manual is written the device can work also in standalone mode, this means it can get inputs by external CDJ or turntables. Also it can work in midi mode with pc. |
Commented by: donato-troccoli What does "No Linux MIDI Driver" mean? |
Commented by: rryan Re-posting what I wrote on the forums: Hi Donny, That means that somebody needs to develop a MIDI driver for the reloop on Linux before Mixxx can use it. This typically involves reverse engineering the USB implementation to figure out how the device sends MIDI data over USB and then writing a Linux USB driver (or alternatively a user-space driver with libusb) that would present the device as a MIDI device. It's totally possible but nobody on the Mixxx team has this device to build the support for it. Mixxx is created by volunteers so in a sense there is no time or money for developers to work on this :). If you find someone who has the device and is good at writing Linux drivers then that might be a good person to convince to work on it :). Not having the device makes it very very difficult to do this work. |
Commented by: isra Hi Donny, Ryan,
|
Commented by: isra By the way, I wanted to --once again-- thank so much Ryan and the Mixxx team for their excellent and very friendly support and congratulate them for the amazing work they do. The world needs more people like you guys. |
Commented by: donato-troccoli Thanks Sean for the answer. |
Commented by: donato-troccoli Building this kind of driver implies costs? I don't mean the cost of the developer writing and reverse engineering work. |
Commented by: rryan @donny -- the costs I was referring to are the developer purchasing a Reloop Digital Jockey 2 Master Edition and then spending many hours of their time reverse engineering it. Presumably once they have written the driver they will contribute it to the Linux kernel so it will be available to all as FLOSS. If you'd like you could start a campaign on a site like Pledgie. We have had success doing fundraising for small projects on Pledgie (such as this one: https://pledgie.com/campaigns/13624 ). You could use this to raise money to buy a willing developer a unit and compensate them for their time. |
Commented by: donato-troccoli
|
Commented by: rryan Ah, sorry I misunderstood you. No there is no permission necessary from Reloop since the reverse engineering is for compatibility purposes. It would be ideal if Reloop were to develop the driver themselves but I imagine they have little interest in this. |
Commented by: esbrandt @donny |
Commented by: donato-troccoli Thanks everyone for helps :). |
Commented by: donato-troccoli @jus
|
Commented by: donato-troccoli Happy Xmas to y'all!! Donny |
Reported by: isra
Date: 2012-07-02T23:58:40Z
Status: New
Importance: Low
Launchpad Issue: lp1020338
Tags: crash
Attachments: [Three Backtrace sessions: with “gdb mixxx” and with "pasuspender mixxx"; Mixxx program failed with Segfault and Sigabrt.](https://bugs.launchpad.net/bugs/1020338/+attachment/3211359/+files/Three Backtrace sessions: with “gdb mixxx” and with "pasuspender mixxx"; Mixxx program failed with Segfault and Sigabrt.), [Preferences snapshot](https://bugs.launchpad.net/bugs/1020338/+attachment/3213339/+files/Preferences snapshot), mixxx.log, [lsusb -v](https://bugs.launchpad.net/bugs/1020338/+attachment/3213374/+files/lsusb -v), [sudo lsusb -v](https://bugs.launchpad.net/bugs/1020338/+attachment/3213376/+files/sudo lsusb -v), [amidi -L](https://bugs.launchpad.net/bugs/1020338/+attachment/3213377/+files/amidi -L), [amidi -l](https://bugs.launchpad.net/bugs/1020338/+attachment/3213384/+files/amidi -l), [aseqdump -l](https://bugs.launchpad.net/bugs/1020338/+attachment/3213385/+files/aseqdump -l), [aconnect -i](https://bugs.launchpad.net/bugs/1020338/+attachment/3213387/+files/aconnect -i)
Using a Reloop Digital Jockey 2 Master Edition with Mixxx software, the Mixxx program crashes when I just press one of the play buttons (on the Mixxx GUI) after loading a music. Sometimes it gives Segfault, sometimes gives SIGABORT.
The debug information will contain several "PortMidi: `Buffer overflow'", "QMutex: cv destroy failure", "QMutex: mutex destroy failure" and finally "Segmentation fault" after many "Requested control does not exist" and ControlObject::getControl returning NULL" debug messages.
(See: http://www.mixxx.org/forums/viewtopic.php?f=3&t=3861)
As requested by D.J. Pegasus in the forum, I have created a couple of backtraces (attached). I do not have debug symbols for Mixxx, thus I decided to at least install the Qt symbols (ubuntu package: libqt4-dbg) to provide as much information as possible.
I would be glad to rerun the test if someone would provide the debug symbols for Mixxx.
Attached backtraces: Note that since I could not find a way to attach more than one file, I was forced to concatenate three backtraces in ONE file, separated by few lines full of asterisks '*********************'
Backtrace_without_pasuspender.txt : This was obtained by running “gdb mixxx” as per "http://mixxx.org/wiki/doku.php/creating_backtraces" . The Mixxx program failed with Segfault.
Backtrace_with_pasuspender_sigabrt.txt: This was obtained by running "pasuspender mixxx" and letting it generate a core dump, then loaded it in gdb. The program here failed with SIGABRT.
Backtrace_with_pasuspender_sigsegv.txt: This was obtained by running "pasuspender mixxx" and letting it generate a core dump, then loaded it in gdb. The program here failed with SIGSEGV.
Note that in all tests, the way to crash the program is to: 1) Load a music in one or the two sides, and 2) Click a Play button on the GUI.
The text was updated successfully, but these errors were encountered: