Find missing (dll) files in LMMS
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
It's hard (impossible?) to collaborate casually on lmms projects.
I'm trying to edit https://lmms.io/lsp/?action=show&file=15367
I downloaded the dlls listed in the error report (see https://github.com/LMMS/lmms/issues/5176 )
I placed the DLLs in one folder and told LMMS that it is the VST folder.
LMMS reports the same error.
I suppose if the project file was edit-able, I could modify XML paths to fix this. However the file is shared as mmpz https://lmms.io/forum/viewtopic.php?t=4727#p15089
Blender and Video editing software is no stranger to this kind of problem. Blender has a nice "find missing files" feature, which asks to find a folder and auto-searches recursively https://blender.stackexchange.com/questions/5368/why-are-all-the-textures-in-my-file-pink
Olive video editor for example marks missing media and allows to manually "replace" it

Shotcut video editor has a warning pop-up that allows to resolve in a similar manner:

The big problem with LMMS is that if I open an mmpz with missing files and save it, the saved mmp will forget about the missing files and assume all the VeSTige instruments are just supposed to be empty.
"users should use standardized VST folders" is an anti-beginner workaround I'm afraid.
(Considering samples the issue currently is probably unsolveable when moving between unix/windows?)
For the time being: perhaps there is a mmpz to mmp converter that doesn't change the content?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source files, tests, or entry points. Start by tracing LMMS project loading and VeSTige instrument path handling with the linked mmpz example and the missing-DLL report in issue 5176. Done would require an agreed design and implementation for finding or replacing missing files without losing them when the project is saved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- audio-video-rtc, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100