Extension-less exports always become WAVs

[yohannd1]

System Information

Linux core2 6.18.2-arch2-1 #1 SMP PREEMPT_DYNAMIC Thu, 18 Dec 2025 18:00:18 +0000 x86_64 GNU/Linux

LMMS Version(s)

LMMS 1.3.0-alpha.1.950

Most Recent Working Version

No response

Bug Summary

When exporting, typing in an extension-less filename always results in a WAV export regardless of the selected filetype.

Expected Behaviour

It should follow the selected filetype.

Steps To Reproduce

1. Press Ctrl+E or go to File > Export...
2. Type an extension-less filename on the dialog that appears, and select a file format that isn't wav.
3. Click save
4. The export dialog filetype will go to wav.

Logs

No response

Screenshots / Minimum Reproducible Project

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.

[musikBear]

would not call that a bug. It would be a bug if it crashed when there was no extension or if it wrote to file anonymously without an extension

[yohannd1]

What do you mean by "anonymously"?
By "bug" here I mean "behavior that does not seem intentional and causes unexpected results" - if I recall correctly, most programs I've used add the currently selected filetype to the save filename if it doesn't have one. And LMMS seems to be trying to do the same, except it's always .wav.

[musikBear]

What do you mean by "anonymously"?

without extension. Then a user would not know that the file was a sound/ media-file, but you have a fix for it, and thats fine. 👍

[rdrpenguin04]

I'd say that feels unexpected; though, I don't know the code well enough to know if we know what file type is selected when the dialog is closed.

[yohannd1]

There is a selectedNameFilter method on the file dialog that the code parses to figure that out. The confusion that happens is because of the default extension (set through setDefaultSuffix) which does not take such filter into account.
(Also, what are you referring to as unexpected? Not sure if I got it)

[sakertooth]

Nice, this bug was reported! I noticed it for quite awhile but never got around to fixing it. I can try something maybe today.