track analyzed and beatgrid re-created at every load

Bug #1950457 reported by David Nadasi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
New
Undecided
Unassigned

Bug Description

mixxx 2.3.1, Debian 11, x86_64

Since 2.3.1, rhythm analysis is done each time I load a track on a deck.
This is very annoying because I have "assume constant tempo" unchecked because I use a lot of non straight tempo tracks.

With those settings :

- Queen Mary analyzer selected
- Assume constant tempo unchecked
- Re-analyze beats when settings change (...)

The behavior in 2.2 was :

1. Fist load of a track
2. Beat and key analysis
3. Manual tweak of beatgrid if needed
4. Manual check of constant tempo property if needed on track > right-click > properties > BPM
5. No analysis on second track load and beatgrid adjustments preserved.

Now in 2.3.1, the behaviour is :

1. Fist load of a track
2. Beat and key analysis
3. Manual tweak of beatgrid if needed
4. Manual check of constant tempo property if needed on track > right-click > properties > BPM
5. Beat and key analysis at every load and beatgrid adjustments lost, track assumed as non-constant BPM.

I realized this bug during a set, a track I had previously marked as constant BPM was reassumed as non-constant BPM, with a lot of BPM variation in the beatgrid. As BPM sync was enabled on the two decks, the tempo slider started to move a lot to "stay synced" to previous track. Horrible result as you can guess.

As a workaround I have checked "Assume constant tempo" in general settings. The problem is when this is enabled, I can't uncheck it on track properties. I have to uncheck it in general settings, uncheck it in the track properties, then re-check it in general properties. This is odd.

Maybe I should report a bug for this also ?

Tags: beatgrid
tags: added: beatgrid
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/10602

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.