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
This may be related to #14089 or #14359 but I couldn't find an issue that suggested that 2.5 would be affected. I have a track (ffprobe output attached) where the beatgrid re-loads every time I load the song. Since it detects the beatgrid wrong, I have to hit "Reanalyze (variable BPM)" every time or it's incorrect and off the beat.
I initially thought this might have something to do with it being an m4a file, which I rarely use, and in the first of those related issues the same suggestion is made (this is a non-stem file, FWIW), but if I convert the track to opus with ffmpeg the same behavior is present.
Not related to #14089 since STEM didn't exist in 2.5.
After a quick look at the log, I can see you are using Serato metadata (SeratoBeatGrid), does it happen on tracks which aren't known in Serato?
Unfortunately my experience with the Serato feature is very limited... I only know it sometimes cause trouble with beat grid offset, but I'll have to leave it to other Mixxx members to help here!
Bug Description
This may be related to #14089 or #14359 but I couldn't find an issue that suggested that 2.5 would be affected. I have a track (ffprobe output attached) where the beatgrid re-loads every time I load the song. Since it detects the beatgrid wrong, I have to hit "Reanalyze (variable BPM)" every time or it's incorrect and off the beat.
I initially thought this might have something to do with it being an m4a file, which I rarely use, and in the first of those related issues the same suggestion is made (this is a non-stem file, FWIW), but if I convert the track to opus with ffmpeg the same behavior is present.
ffprobe.txt
Here are the logs for starting mixxx, searching for the track in the library view, and loading it:
load_track_mixxx_logs.txt
Version
2.5.0
OS
Arch Linux 6.13.4-arch1-1
The text was updated successfully, but these errors were encountered: