Play button on Hercules MK2 does not get released

Bug #197460 reported by surfed
4
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Undecided
Unassigned

Bug Description

When starting a Song Mixxx behaves like the Play button is being held down going back between play and pause at a fast rate. Changing Audio drivers during this behavior enables smooth playback until play is pressed again. Also Mixxx seems to pick up the sliders slowly, ie when i move a slider very fast from max to min it will register as lets say 15% or so, this makes rapid cross fading impossible.

System:
2x 2.4Xeons, 2gb Ram, Ubuntu Gutsy with RT kernel, Nvidia prop., M-Audio delta 1010LT, Hercules MK2 Console.

Surfed

Revision history for this message
ironstorm (ironstorm-gmail) wrote :

I'm not sure if the packages are built against libDJConsole or the legacy code...

That set of symptoms sounds like the legacy code switch (which works with MP3 Controllers).

We are waiting on Hercules to create MIDI drivers for Linux which we'll eventually use to replace our existing Hercules Console implementation.

-G

Revision history for this message
surfed (surfed) wrote : Re: [Bug 197460] Re: Play button on Hercules MK2 does not get released

For some reason i was under the impression that beta2 uses libDJConsole,
can somebody confirm?
Surfed

"I have noticed even people who claim everything is predestined, and that we can do nothing to change it, look before they cross the road."

ironstorm wrote:
> I'm not sure if the packages are built against libDJConsole or the
> legacy code...
>
> That set of symptoms sounds like the legacy code switch (which works
> with MP3 Controllers).
>
> We are waiting on Hercules to create MIDI drivers for Linux which we'll
> eventually use to replace our existing Hercules Console implementation.
>
> -G
>
>

Revision history for this message
ironstorm (ironstorm-gmail) wrote :

try:

ldd -r `which mixxx`

That should tell you what libs it's linked against.

Revision history for this message
surfed (surfed) wrote :

So it seems it uses libdjconsole.....

$ ldd -r `which mixxx` | grep libdj

libdjconsole.so.0 => /usr/lib/libdjconsole.so.0 (0xb6f38000)

"I have noticed even people who claim everything is predestined, and that we can do nothing to change it, look before they cross the road."

ironstorm wrote:
> try:
>
> ldd -r `which mixxx`
>
> That should tell you what libs it's linked against.
>
>

Revision history for this message
ironstorm (ironstorm-gmail) wrote :

Yup, that's libDJConsole

Try starting mixxx with this script:
http://mixxx.org/wiki/doku.php/compiling_on_an_asus_eeepc#slowmixxx

it should increase the priority of mixxx, it will cause mixxx to hog one of your cpus, but it should be more responsive.

Revision history for this message
ironstorm (ironstorm-gmail) wrote :
Revision history for this message
surfed (surfed) wrote :

i dont think hardware resources are an issue, i am running dual xeons
2.4 here and oddly the slider problems are only in on direction. When i
flick a volume slider from min to max with my finger it gets there but
if i go from max to min it stops 2/3 of the way. Anyhow i cant use it as
i cant play any tracks :)
 I have tried the script but the results are identical. Thanks for trying.
Surfed

"I have noticed even people who claim everything is predestined, and that we can do nothing to change it, look before they cross the road."

ironstorm wrote:
> Yup, that's libDJConsole
>
> Try starting mixxx with this script:
> http://mixxx.org/wiki/doku.php/compiling_on_an_asus_eeepc#slowmixxx
>
> it should increase the priority of mixxx, it will cause mixxx to hog one
> of your cpus, but it should be more responsive.
>
>

Revision history for this message
ironstorm (ironstorm-gmail) wrote :

> i dont think hardware resources are an issue, i am running dual xeons
> 2.4 here and oddly the slider problems are only in on direction. When i
> flick a volume slider from min to max with my finger it gets there but
> if i go from max to min it stops 2/3 of the way. Anyhow i cant use it as
>i cant play any tracks :)

The crossfader is one place where I could see you going from 0 to Middle or other side, however min to max on the volume is not something I'd ever do...

Anyway, there are a couple things... moving too quickly, the hercules may not generate all of the events or the combo of libUSB + libDJConsole + Mixxx may not receive all the events.

There is one more thing you can try:
* minimize Mixxx and then play with the volume sliders, etc, while it is minimized using your Herc Mk2... (this will cause the app to skip the step of painting the UI updates)

If you find that things are much more responsive then the problem lies with Mixxx (or Mixxx + Nvidia drivers) and it's inability to keep the UI updated on very fast input events.

-G

Revision history for this message
surfed (surfed) wrote :

minimizing does not help, maybe my dual screen setup is at fault ? But
then i have no problems with the console in Windows. I am running a Real
Time kernel (Ubuntu Studio) could that have something to do with it?

Surfed

"I have noticed even people who claim everything is predestined, and that we can do nothing to change it, look before they cross the road."

ironstorm wrote:
>> i dont think hardware resources are an issue, i am running dual xeons
>> 2.4 here and oddly the slider problems are only in on direction. When i
>> flick a volume slider from min to max with my finger it gets there but
>> if i go from max to min it stops 2/3 of the way. Anyhow i cant use it as
>> i cant play any tracks :)
>>
>
> The crossfader is one place where I could see you going from 0 to Middle
> or other side, however min to max on the volume is not something I'd
> ever do...
>
> Anyway, there are a couple things... moving too quickly, the hercules
> may not generate all of the events or the combo of libUSB + libDJConsole
> + Mixxx may not receive all the events.
>
> There is one more thing you can try:
> * minimize Mixxx and then play with the volume sliders, etc, while it is minimized using your Herc Mk2... (this will cause the app to skip the step of painting the UI updates)
>
> If you find that things are much more responsive then the problem lies
> with Mixxx (or Mixxx + Nvidia drivers) and it's inability to keep the UI
> updated on very fast input events.
>
> -G
>
>

Revision history for this message
b2ag (thomas-b2ag) wrote :

maybe you noticed, that you can't get 0-position (most left for crossfader).
if you move to fast in this direction you got the last event which than could have 15% offset.

see https://bugs.launchpad.net/mixxx/+bug/198400

Revision history for this message
ironstorm (ironstorm-gmail) wrote :

> maybe you noticed, that you can't get 0-position (most left for crossfader).
> if you move to fast in this direction you got the last event which than could have 15% offset.
> see https://bugs.launchpad.net/mixxx/+bug/198400

Yes, I saw that and agree that you found a bug there...
I'm not sure it is related to the first part of this issue (which should have been 2 bugs btw)... i.e. "Play button on Hercules Mk2 does not get released".

Revision history for this message
ironstorm (ironstorm-gmail) wrote :

I can play/pause pretty quickly on my eeePC, but I can't seem to get this stuck behaviour you describe, maybe my eeePC is just to slow to reproduce it...

Let me know if the fix for 198400 does anything to help with this one on your set-up...

Revision history for this message
surfed (surfed) wrote :

just compiled r1874 and it does fix the slider problem but playback
still oscillates between pause/play when Hercules console is connected.
Alex

"I have noticed even people who claim everything is predestined, and that we can do nothing to change it, look before they cross the road."

ironstorm wrote:
> I can play/pause pretty quickly on my eeePC, but I can't seem to get
> this stuck behaviour you describe, maybe my eeePC is just to slow to
> reproduce it...
>
> Let me know if the fix for 198400 does anything to help with this one on
> your set-up...
>
>

Revision history for this message
ironstorm (ironstorm-gmail) wrote :

Both play buttons to this eh? Do the play button LEDs also blink while this is happening?

Revision history for this message
surfed (surfed) wrote :

No, Play Button LED only lights up when i push play. Playback returns to
normal if i change audio device in prefs during playback, but only until
i press play/pause again.
Alex

"I have noticed even people who claim everything is predestined, and that we can do nothing to change it, look before they cross the road."

ironstorm wrote:
> Both play buttons to this eh? Do the play button LEDs also blink while this is happening?
>
>

Revision history for this message
Albert Santoni (gamegod) wrote :

You don't have "Enable vinyl control" checked, do you?

(It's a long story, but if you have that enabled and no timecode signal going into your soundcard's input, it's possible the software preamp is amplifying noise making the vinyl control go bonkers.)

Revision history for this message
surfed (surfed) wrote :

nope.

"I have noticed even people who claim everything is predestined, and that we can do nothing to change it, look before they cross the road."

Albert Santoni wrote:
> You don't have "Enable vinyl control" checked, do you?
>
> (It's a long story, but if you have that enabled and no timecode signal
> going into your soundcard's input, it's possible the software preamp is
> amplifying noise making the vinyl control go bonkers.)
>
>

Revision history for this message
Tom Jennings (tomj-wps) wrote :

> When starting a Song Mixxx behaves like the Play button is being held down going back between play and pause at a fast rate.

I too run a Hercules, Control MP3 (via djconsole_legacy). This behavior occurred to me when I compiled a recent svn version that added Bheringer MIDI controller support -- it changed prefs for Input Controller to Behringer. I put it back to Evolution_Xsession or whatever it is, quit and restarted mixxx, back to full Herc functionality (minus LEDs of course).

(For some reason setting Input Controller to Hercules Control MP3 does not work.)

Revision history for this message
surfed (surfed) wrote :

Evolution_Xsession does not work for me (i have mk2 not mp3 console), no
behringer support in my svn install (svn 1874) but leds work :)
Now i must note that i get this behavior even when starting playback by
pressing play in mixxx with the mouse as long as the console is
connected... anyhow i somehow get the feeling i will have to wait for
hercules to release some drivers unless someone gives me a crash course
in coding :)

"I have noticed even people who claim everything is predestined, and
that we can do nothing to change it, look before they cross the road."

Tom Jennings wrote:
>> When starting a Song Mixxx behaves like the Play button is being held
>>
> down going back between play and pause at a fast rate.
>
> I too run a Hercules, Control MP3 (via djconsole_legacy). This behavior
> occurred to me when I compiled a recent svn version that added Bheringer
> MIDI controller support -- it changed prefs for Input Controller to
> Behringer. I put it back to Evolution_Xsession or whatever it is, quit
> and restarted mixxx, back to full Herc functionality (minus LEDs of
> course).
>
> (For some reason setting Input Controller to Hercules Control MP3 does
> not work.)
>
>

Revision history for this message
Albert Santoni (gamegod) wrote :

Should be fixed in SVN with r1988 because this sounds like it was related to the MIDI-feedback bug (LP 209365)

Changed in mixxx:
status: New → Fix Committed
Changed in mixxx:
status: Fix Committed → Fix Released
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issue/4927

lock status: Metadata changes locked and limited to project staff
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/4927

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.