Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

waveform and transport out of sync for mp3 #7794

Closed
mixxxbot opened this issue Aug 22, 2022 · 8 comments
Closed

waveform and transport out of sync for mp3 #7794

mixxxbot opened this issue Aug 22, 2022 · 8 comments

Comments

@mixxxbot
Copy link
Collaborator

Reported by: daschuer
Date: 2015-01-04T09:39:35Z
Status: Fix Released
Importance: High
Launchpad Issue: lp1407394
Tags: soundsource


Waveform and transport are out of sync.

My test track has according to Audacity 0,4 s silence at the beginning.

This is displayed in Mixxx correctly, the waveform starts, when the track time is on 0,40.

But the sound output starts actually starts at 0,36 and the first beat marker of the non const beat grid is at 0,36

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2015-01-04T11:54:06Z


The original issue appears using a mp3 file. If I save the same file as wave using Audacity, it sound output aligns perfectly with the waveform.
This was tested with 64 bit Linux build of 1.12.0-alpha (build master r5041) on Ubuntu Trusty.
the original track is an an mp3float.

I have also recoded the file in 192 kbps variable and fixed rate.
Now the Audio starts at 0:45 according to the waveforms im Mixxx and according to Audacity, but the sound starts later at 0.47 for both tracks in Mixxx.

Is that regression?

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2015-01-04T14:00:44Z


Is that regression?
Tested with 1.11 release and it suffers the same issue.

@mixxxbot
Copy link
Collaborator Author

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2015-01-11T22:49:16Z


Have you discovered the root cause? What's your planned fix?

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2015-01-12T01:01:38Z


#461

On cause are simple bugs in seek calculations.
An other cause are mad_frame_decode calls that to not advance to the next frame.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2015-06-03T06:18:59Z


The fix is now in Master. Not in 1.12 alpha :-(

@mixxxbot
Copy link
Collaborator Author

Commented by: Be-ing
Date: 2017-11-12T15:49:32Z


Fixed by Uwe: #411

@mixxxbot
Copy link
Collaborator Author

Issue closed with status Fix Released.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
@mixxxbot mixxxbot added this to the 2.1.0 milestone Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant