setting hotcue_X_activate to 1 while paused makes deck unable to stop playback

Bug #1466606 reported by Be
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Medium
Daniel Schürmann

Bug Description

If a script sets hotcue_X_activate to 1 while a deck is paused, the deck will play from that hotcue but hitting play/pause will not stop the track. The only way to fix this is to restart Mixxx. This does not occur with hotcue_X_gotoandplay.

Be (be.ing)
tags: added: hotcue
Revision history for this message
Be (be.ing) wrote :

Setting hotcue_X_activate to 0 solves the issue.

Changed in mixxx:
status: New → Invalid
Be (be.ing)
Changed in mixxx:
status: Invalid → New
Revision history for this message
Be (be.ing) wrote :

Well, setting hotcue_X_activate to 0 makes the deck able to be paused again, but it has a side effect. When hotcue_X_activate is set to 1 by a script while the deck is paused, setting it to 0 jumps back to the hotcue and stops. The user may want to press play to let playback continue before letting go of the hotcue button. Strangely, this works if the hotcue button is pressed in the GUI then play is set to 1 by a controller or the keyboard. It also works if hotcue_X_activated is mapped to a MIDI signal with the MIDI Learning Wizard. It only does not work when a script sets hotcue_X_activate to 1.

Be (be.ing)
tags: added: scripting
Revision history for this message
Daniel Schürmann (daschuer) wrote :

@Be:
Do you have fun and time to adopt it yourselves?
Do you need help?

Changed in mixxx:
status: New → Confirmed
importance: Undecided → Critical
milestone: none → 1.12.0
Revision history for this message
Be (be.ing) wrote :

Well, I guess it is about time for me to start learning C++ then.

Revision history for this message
Be (be.ing) wrote :

I figured out that play must be set to 0 while hotcue_X_activate is 1 to continue playback after hotcue_X_activate is set to 0. This behavior is counterintuitive for script writers, so I'll make a note of it on the wiki. So, this bug is not crucial for mapping my controller, but it is still a serious issue in the event that a script fails to set hotcue_X_activate to 0.

Revision history for this message
Owen Williams (ywwg) wrote :

Script bugs are hard to quantify. We can't necessarily prevent all bad behavior that a script might do.

Changed in mixxx:
importance: Critical → Medium
Changed in mixxx:
status: Confirmed → Fix Committed
assignee: nobody → Daniel Schürmann (daschuer)
Revision history for this message
Daniel Schürmann (daschuer) wrote :

The bug is fixed in the current 1.12 (tested in git 5609)

* set sets hotcue_X_activate 1 == press the hotcue 1 button and keep ti pressed
* set play -> latching play, the would keep playing if you release hotcue 1
* reset play = pause, track stops.

Now it works reasonable, but keeping the hotcue_X_activate 1 is a script bug and should not happen.

RJ Skerry-Ryan (rryan)
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/issues/8104

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.