LMMS / LMMS/lmms

differences in play times of exported tracks with exactly same notes

Open
#8,137 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
10.4k
Forks
1.3k
Avg merge
2d 13h
Merged PRs (30d)
7

Description

When you "export tracks" and check the time lengths for same notes, bpm and output format settings, you will find that the artifacts are with different play time lengths and other attributes.

Open the attached sample, export the tracks, and load all .ogg files in Audacity.
Then see the ending times. In my opinion, they should contain equal amount of playtimes.

How to reproduce? Please consider the project: [exports.zip](https://github.com/user-attachments/files/23597248/exports.zip)

Updates: [exports-with-automation-bar.zip](https://github.com/user-attachments/files/24019535/exports-with-automation-bar.zip) does not cause this issue.

Copy some notes, eg 2 bars long to some default instruments.
Image

- Then apply same channel number to ensure they have common effects, if any.
- Export all tracks using the File > Export Tracks menu.
- Open all artifacts together in a stack using Audacity or MP3Tag

They have different play times! causing overlapping sounds.

Image

Each instrument seems to have a different bitrate output
Image

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start with the File > Export Tracks workflow and reproduce the issue using exports.zip, then load the generated .ogg files together in Audacity to compare their ending times and output attributes. The fix is complete when tracks with identical notes, BPM, format settings, and channel effects export with matching play times without overlapping playback.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.