musescore / musescore/MuseScore

MP3 and WAV exports are out of sync

Open
#27,501 0 comments 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Apr 4, 2025.

P3 playback
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Import/export issue

Description with steps to reproduce
  1. Open a score
  2. Export it as MP3 with default settings (Sample rate 44100Hz, Bitrate 128 kbit/s)
  3. Export it as WAV with default settings (Sample rate 44100Hz)
  4. Run ffprobe -i <filename> over the two exports
  5. Observe a slight duration difference
Supporting files, videos and screenshots

Here's a score file that reproduces the issue:

drumbeats-4-4.zip

I also tested with OGG and FLAC, here's the list of the exported files durations:

  • FLAC 00:02:29.68
  • MP3 00:02:29.73
  • OGG 00:02:29.00
  • WAV 00:02:29.67

Regardless of the duration, the MP3 export seems to be significantly shifted from the other three.

Here there's a screenshot of Audacity after importing all four (FLAC, MP3, OGG, WAV respectively):

Image

What is the latest version of MuseScore Studio where this issue is present?

MuseScore Studio version (64-bit): 4.5.1-250800846, revision: github-musescore-musescore-603eca8

Regression

I was unable to check

Operating system

OS: Arch Linux

Additional context

I'm using the AppImage release using the i3 window manager (X11).

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.