You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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"
Reported by: kain88-de
Date: 2012-06-09T12:33:42Z
Status: Confirmed
Importance: Wishlist
Launchpad Issue: lp1010869
Tags: autodj
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.
The text was updated successfully, but these errors were encountered: