controller stops working

[mixxxbot]

Reported by: static-warp-shell
Date: 2013-07-18T01:28:11Z
Status: Triaged
Importance: Medium
Launchpad Issue: lp1202452
Tags: controllers
Attachments: mixxx.log

---

my controller is recognized at startup and the appropriate script is loaded, then stops working after a few minutes of use. there is no specific set of actions that reproduce this, it just ceases to function.

i'm using a numark stealth control with the numark total control script, win7 x64, and mixxx 1.11.0 x86.

if i exit and restart mixxx, the controller still does not work. however, if i exit mixxx, unplug the controller and plug it back in, then restart mixxx, the controller works again for a few minutes before becoming unresponsive once more.

[mixxxbot]

Commented by: borfo
Date: 2013-07-20T23:26:33Z

---

I have the same problem with my DJ-Tech Mixer One. It only happens occasionally, and it generally works for an hour or more before it stops responding. I have to exit mixxx, unplug the controller, plug it back in and restart mixxx to get it working again. Because this only happens occasionally, and takes so long to happen, I haven't caught a log of it yet.

[mixxxbot]

Commented by: Pegasus-RPG
Date: 2013-07-21T15:14:11Z

---

This is probably due to one of two things. One is that the controller momentarily attempts to draw more power than the computer/USB hub can supply so it is disabled automatically by the hardware. The other is that somehow PortMIDI (or the HID library) lose track of the device so stop talking to it. In either case, the mixxx.log would be very useful to see what's happening. The next time this happens to any of you, find and copy mixxx.log to somewhere safe (before restarting Mixxx) then attach it to this bug. Instructions for finding it are here: http://mixxx.org/wiki/doku.php/troubleshooting#where_is_the_mixxxlog_file

[mixxxbot]

Commented by: borfo
Date: 2013-07-22T21:38:54Z

---

I'll make sure to grab the log next time it happens - it generally happens when I'm out playing a set somewhere, so it's a bit of a frantic switch-to-a-backup-audio-source-while-i-restart-mixxx sort of thing, and I haven't taken the time to grab the log yet. Maybe I'll leave mixxx running for a few hours at home occasionally and see if I can replicate under those conditions.

Seems unlikely that it's a power issue - the Mixer One is powered - it's got a built in USB hub, but it's just my two scratch controllers plugged into it, and it runs off a DC power adapter, which should supply all the power the controllers could ever need.

[mixxxbot]

Commented by: borfo
Date: 2013-07-22T21:56:12Z

---

...and the scratch controllers attached to the built in USB hub on the Mixer One continue to work even after the Mixer One stops responding.

[mixxxbot]

Commented by: static-warp-shell
Date: 2013-07-24T23:27:44Z
Attachments: mixxx.log

---

here is the mixxx.log from my most recent session. the controller exhibited the same behaviour.

[mixxxbot]

Commented by: static-warp-shell
Date: 2013-07-24T23:30:35Z

---

thanks for your response, pegasus. I should also mention that my controller will continue to function indefinitely with previous versions of mixxx, so it's probably not a power issue, at least in my case. :)

[mixxxbot]

Commented by: borfo
Date: 2013-08-01T23:46:45Z

---

Pegasus - I got a log from last night when my Mixer One failed, but it's huge (22mb of controller script debug messages firing on timers) - anything in particular I should be looking for in there? I've gone through it and there doesn't seem to be anything out of the ordinary in there relating to the Mixer One, except that during the Mixxx shutdown procedure, the connections to the Mixer vumeter leds can't be disconnected, presumably because there was no communication with the mixer at that point:

Debug [Controller]: ControllerEngine shutting down... 
Warning [Controller]: ControllerEngine: No "" object in script 
Warning [Controller]: Could not Disconnect connection "MIXER1.volumeLEDs" 
Warning [Controller]: Could not Disconnect connection "MIXER1.volumeLEDs" 
Warning [Controller]: Could not Disconnect connection "MIXER1.volumeLEDs" 
Warning [Controller]: Could not Disconnect connection "MIXER1.volumeLEDs" 
Warning [Controller]: Could not Disconnect connection "MIXER1.volumeLEDs" 
Warning [Controller]: Could not Disconnect connection "MIXER1.volumeLEDs" 

[mixxxbot]

Commented by: adyj230279
Date: 2014-05-12T13:46:53Z

---

Hi I have similar issues. I use a traktor vinyl and a Behringer CMD micro. I do not restart the mixxx, I unplug, replug the controller then reselect the controller from preferences. This is quicker than restarting mixxx. However I would be interested on a fix. I need most of all the fader from the controller, for the other stuff I can use keyboard shortcuts and vinyl control.

[mixxxbot]

Commented by: daschuer
Date: 2016-01-02T22:38:57Z

---

Is it possible to re-enable the controller by just restarting Mixxx?
Is your effected controller a Midi controller?

If yes, it is likely an handled midi overflow.

We have increased the midi buffer from 64 to 1024 in Mixxx 2.0.0 so the problem might not happen again.
The issue will be finally fixed in #825

[mixxxbot]

Commented by: static-warp-shell
Date: 2016-01-03T03:14:43Z

---

Hi Daniel :) thanks for the reply.

yes, restarting mixxx re-enables my midi controller. i'm glad i saw this
before i sold the thing, and glad to hear about mixxx 2.0.0. i'll retest.

On Sat, Jan 2, 2016 at 5:38 PM, Daniel Schürmann <

wrote:

Is it possible to re-enable the controller by just restarting Mixxx?
Is your effected controller a Midi controller?

If yes, it is likely an handled midi overflow.

We have increased the midi buffer from 64 to 1024 in Mixxx 2.0.0 so the
problem might not happen again.
The issue will be finally fixed in
#825

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1202452

Title:
controller stops working

Status in Mixxx:
Incomplete

Bug description:
my controller is recognized at startup and the appropriate script is
loaded, then stops working after a few minutes of use. there is no
specific set of actions that reproduce this, it just ceases to
function.

i'm using a numark stealth control with the numark total control
script, win7 x64, and mixxx 1.11.0 x86.

if i exit and restart mixxx, the controller still does not work.
however, if i exit mixxx, unplug the controller and plug it back in,
then restart mixxx, the controller works again for a few minutes
before becoming unresponsive once more.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mixxx/+bug/1202452/+subscriptions

[mixxxbot]

Commented by: rryan
Date: 2018-09-20T17:35:41Z

---

Due to lack of progress, marking Triaged and clearing assignee. Feel free to revert if it is in fact still in progress :).

[ronso0]

Since no similiar issues were reported I'll close this as Fixed now.