Can't override Auto-DJ once fading has stated

Bug #1010869 reported by Max Linke
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Confirmed
Wishlist
Unassigned

Bug Description

There are some cases where Auto-DJ should be turned off automatically.

For one create a loop at the end of a track when it's starting to fade to the other deck.
The other deck is started and plays normally but the first deck will always restart the fading event in the loop and prevent auto-Dj from loading the next song into the deck.

I think it might be a good idea to disable Auto-Dj as soon as the user manually starts/stops a deck or creates a loop on it.

Tags: autodj
Changed in mixxx:
status: New → Confirmed
tags: added: autodj
RJ Skerry-Ryan (rryan)
Changed in mixxx:
importance: Undecided → Wishlist
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

I don't think deck transport events (seeks / loops / etc.) should necessarily disable AutoDJ but I think that once a fade starts it should not be connected to the play position of the deck we are fading away from (as it is now).

That way once the fade starts you can set a loop if you want to prevent the left deck from fully going out.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

It is a good Idea to make the fading independent from the track position.
This allows also some kind of transport transition effects like spin-down.

The request to "disable Auto-DJ" seams to be already a solution for the underlying bugs
"Can't override fade form AutoDJ"
And
"Can't override transport when AutoDJ starts to fade"

We have recently discussed in the forums not to disable Auto DJ at all:
https://bugs.launchpad.net/mixxx/+bug/1391630

@rryan: What do you think about that?

summary: - Auto-DJ should be disabled automatically for some events
+ Can't override Auto-DJ once fading has stated
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/6517

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.