Auto DJ Fails in win10-64

Bug #1893197 reported by Peter Burg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Critical
Daniel Schürmann

Bug Description

Leaving the app overnight broadcasting, I twice noticed Mixx hangs without playing.
One player loaded, the other one empty.
mixxx-2.4.0-alpha-pre-master-git7498-release-x64

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

Which transition mode did you use? With which time?
Did you define into and outro regions?

Can you recall which two track where affected?

Please attache the mixxx.log file from this session.
https://github.com/mixxxdj/mixxx/wiki/Finding-the-mixxx.log-file
by luck it is still there with a suffix number.

Changed in mixxx:
importance: Undecided → Critical
milestone: none → 2.3.0
Revision history for this message
Peter Burg (wunjo) wrote :

Hi Daniel,

transition; Fade at Outro Start, 4 sec
defined; intro start, outro start and outro end.(most tracks)

I see in the log section there are 3 minidumps (with mixxx-settins) so there were 3 instances with malfunctions.

Now playing vs.7491, playing well:-)

Revision history for this message
Peter Burg (wunjo) wrote :
Revision history for this message
ronso0 (ronso0) wrote :

@wunjo Please let us know if you encouter that bug again and provide a backtrace in case Mixxx crashes.

Changed in mixxx:
status: New → Incomplete
Revision history for this message
Peter Burg (wunjo) wrote :

Hi Ronso0,

Still happens here. Still using mixxx-2.4.0-alpha-pre-master-git7491-release-x64 for broadcast.
Mixxx didn't crash it just stopped the autoDJ for some reason.

From time to time I tried newer versions of 2.4 alpha, they didn't work for me, same story.
These include:
Mixxx-main-r7730-b7e72bf826.msi
Mixxx-main-r7786-eff873a190.msi
Mixxx-main-r7803-f1c2947989.msi
Mixxx-2.3-r8090-9f259f8fef.msi

Win10 20h2 64
AMD A8-3870 APU with Radeon(tm) 8Gb
I run Mixxx in developer mode due transfer from A=440 to A=432

Revision history for this message
ronso0 (ronso0) wrote :

hmm.. So playback stops but AutoDj still appears to be engaged?

Revision history for this message
Jan Holthuis (holthuis-jan) wrote :

Please post log output, maybe AutoDJ encountered some debug assertion and disabled itself.

Revision history for this message
Jan Holthuis (holthuis-jan) wrote :

Hmm, or maybe not. DEBUG_ASSERT does show up in the logs, not just on the terminal, right?

Does it always happen for the same track?

Revision history for this message
Peter Burg (wunjo) wrote :

Jan, no, at random.

Logic tells me it is caused by a change between mixxx-2.4.0-alpha-pre-master-git7491-release-x64.exe witch runs 7/24, and mixxx-2.4.0-alpha-pre-master-git7498-release-x64.exe where the stops occur.

Revision history for this message
Peter Burg (wunjo) wrote :

last try log

Revision history for this message
Peter Burg (wunjo) wrote :

also last try

Changed in mixxx:
milestone: 2.3.0 → none
status: Incomplete → New
tags: added: autodj windows
Revision history for this message
Daniel Schürmann (daschuer) wrote :

Does this still happen? There is no violated assertion visible in your logs.

I have prepared a Mixxx version with more debug output when using auto DJ.
Can you please try to reproduce the issue with the build found at the bottom of this page?
https://github.com/daschuer/mixxx/actions/runs/1907115706

(You need to log in on GitHub for download)

Revision history for this message
Peter Burg (wunjo) wrote :

Hi Daniel,

I'm using now the standard edition 2.3.1
No problems sudden stops now.
The only problem now is Mixxx sometimes skipping the fade out, after changing the fade out in the next track. But i have to rapport this as a new bug, I guess..

I will try the prepared version, report back on it.

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

The jump cut issue is already tracked here:
https://bugs.launchpad.net/mixxx/+bug/1948975

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

I have prepared here another build with more debug messages and merged with 2.4
The original link was 2.3 based.

I am curious if this issue is a 2.4 regression.
The main difference is that we have replaced the sample based cue point API by a frame based one.
Maybe there is a factor 2 missing somewhere.

Revision history for this message
Peter Burg (wunjo) wrote :

Daniel,
The download on the link you provided on 27-2 has no issues. Runs now 55 hours.
I'll check on the other bug report 1948975
Thanks

Changed in mixxx:
status: New → Confirmed
status: Confirmed → In Progress
assignee: nobody → Daniel Schürmann (daschuer)
milestone: none → 2.3.3
Revision history for this message
Daniel Schürmann (daschuer) wrote :
Revision history for this message
Daniel Schürmann (daschuer) wrote :

@wunjo: Please test the build found here: https://github.com/mixxxdj/mixxx/actions/runs/1981955789

Changed in mixxx:
status: In Progress → 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/issues/10093

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.