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

DrumSynth presets (.ds) export incorrectly, losing important information. #7721

Open
1 task done
Capewearer opened this issue Feb 19, 2025 · 1 comment
Open
1 task done
Labels
bug stable branch This issue applies to the latest stable

Comments

@Capewearer
Copy link

System Information

Windows 10 (Huawei distribution), x86-64 (Intel CPU)

LMMS Version(s)

1.2.2-stable (sorry, I'm not into nightly builds)

Most Recent Working Version

No response

Bug Summary

This bug is reproducible, the export works weird no matter the file format (.wav, .ogg, .mp3) is chosen, sample rate, bitrate doesn't matter at all. Simple project for reproduction and exported file are posted in zip-archive (because Github can't post .mmp files).
....
I am aware about #6335, but original poster complains about difference between versions, including the playback and export, I am complaining about difference between real-time sound and export itself on that one LMMS version. Please, feel the difference.

Expected Behaviour

Have highest overtones to be heard and proper volume. My hearing is average, if not worse. I know there always will be a difference between "pure" real-time generated sound and baked one, but it shouldn't be that different.

Steps To Reproduce

1.Open the project.
2. Listen the loop.
3.Export.
4.?????
5.PROFIT!!111

Logs

Click to expand
  

Screenshots / Minimum Reproducible Project

I know that's another export bug, but please, take it into consideration, because it would be a pity to write track with excessive usage of drumsynth and get bad export. A one of overcomings is to record audio with screen capture.

export_test.zip

Please search the issue tracker for existing bug reports before submitting your own.

  • I have searched all existing issues and confirmed that this is not a duplicate.
@Capewearer Capewearer added the bug label Feb 19, 2025
@qnebra qnebra added the stable branch This issue applies to the latest stable label Mar 1, 2025
@rubiefawn
Copy link
Contributor

I know there always will be a difference between "pure" real-time generated sound and baked one, but it shouldn't be that different.

Ideally there should be no difference whatsoever between real-time sound and "baked" sound. If there is any difference between the two, it's a bug.

I tested this on Windows 10 x86_64 using the SDL backend, but unfortunately wasn't able to replicate it. I rendered out the provided project file in both 1.2.2 as well as nightly 9159533 (msvc), and also recorded the live playback using OBS to compare. I can't hear any substantial difference, and they all look close enough when manually lining them up and comparing waveforms.

Image

Here are the audio files for comparison: exports.zip

Is this still happening for you? In LMMS's settings, what are your audio interface settings?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug stable branch This issue applies to the latest stable
Projects
None yet
Development

No branches or pull requests

3 participants