relying on engine.softTakeoverIgnoreNextValue() assumes that physical control is moved every time it switches to controlling another value

Bug #1564644 reported by Be
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Confirmed
Medium
Unassigned

Bug Description

The recently introduced soft takeover mechanism requiring a call to engine.softTakeoverIgnoreNextValue() when a physical control such as a fader is switched to manipulating a different value in Mixxx generally works well. However, it does not work well when the physical control is switched between different modes without being moved. For example, a volume fader controlling [Channel1] could be moved all the way down, then the script switches it to controlling [Channel3] and calls engine.softTakeoverIgnoreNextValue('[Channel1]', 'volume'), then the script switches it back to controlling [Channel1] without the user moving the fader. In this situation, to use the fader to move the value of [Channel1], volume back up from 0, the fader on the controller has to be moved up, then down, then up again.

Be (be.ing)
description: updated
Changed in mixxx:
status: New → Confirmed
importance: Undecided → Medium
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/8504

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.