-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Hardcoded Path in project-files #3810
Comments
Beta = bugs. Tell him sorry. He should be able to open and save with RC4 on the original PC and it should fix the problem. 200 projects is quite high, I would assume only newly created projects with RC1/RC2 would have this bug. If it still happens with RC4 have HIM open a new bug report. On a side note... @musikBear STOP filing bugs for other people please. Just send them to discord (lmms.io/chat) or directly here. Being a translation layer between the problem and the description is kind, but unnecessarily complex. Describe the problem and move on without dramatics. Closed via |
Don't talk about "another user". Stop, stop, stop acting as a surrogate. If you have a a bug with midi import, open a new bug report. There's no "relaying bugs", there's no "experiments". Either the software works or it does not and exact steps are required to reproduce. There are rare exceptions to this where intermittent bugs can't be 100% reproduced, but this is not that case. Please offer value or stop using our tracker. |
Tresf - you need to read what is written.
It does exists in RC5, So this is a request to reopen the issue. |
Steps to reproduce and we'll reopen. I'm not sure how much clearer I have to be here. |
There are two named settings that pertain to soundfonts and your most recent post makes this confusing (as is your original bug report) but I'll specify, clearly. Please consider this in the future to avoid this back and forth which is a waste of developer time.
Unfortunately the software doesn't really make use of either of these when calculating relative paths, and I'm not sure we ever will, but I agree this is a bug. Soundfonts were decided to be stored inside What seems to be the missing puzzle piece here is that we added an option for a "SF2 DIRECTORY" folder, but we ignore it. I think it simply needs to be removed. I'm sure there will be a few people asking to have their SF2 directory outside their |
Edit: So please ask the users to start using "LMMS HOME DIRECTORY" (Edit2: Specifically, In regards to the 200 projects in the original bug report that are now "unusable", have the user drop over to Unfortunately at this time, batch conversion of |
No that is not relevant. What i did is to simulate using a different pc:
|
@musikBear if you read the above reply, you can see the soundfonts must reside within the If you'd like all files to be relevant to the project path, then you've opened a duplicate of #2982. This has never been supported. |
Closing marking as duplicate of #2982. |
I now see why i havent had this issue. I do not have 'stand-alone' soundfonts. 'All' (I have 5..) are embedded in Lmms-soundfont-player and saved as *.XPFs. |
There's no such thing as "embedding" a soundfont in an XPF file. It's theoretically possible (e.g. base64 blob) but it won't ever happen because soundfonts are generally very large in size.
A In an LMMS project file, all instruments are still saved in XPF format, just internal to the project. XPF files are actually the one file that is never cross-references inside an LMMS project, it's copied directly into the project. This means it's not that common nor that useful for an XPF to contain a soundfont patch. There are use-cases where this makes sense, but most people will simply drag a soundfont into a new track and not rely on preset information although you're free to use it how you wish so as long as you keep things organized properly. Organization is as follows... if there is a specific combination of XPF preset and SF2 sample you would like to re-use in your projects, you will need to save your presets inside the proper You may also consider talking through these bugs in our #support channel on Discord. We're answering questions just like these all day long there. |
Ok, that is how i have my 5 SF2, and all as .XPF. I will then ofcause not have any SFs in samples library, and no issues loading them. 👍 |
Again, storing samples relative to projects/presets is not yet supported, they must reside inside |
I wonder why lmms has hardcoded path information in project-files. The reason is a forum-user that has bought a new pc.
His former pc was quite weirdly partitioned -dont ask why, i dont know
But he had a folder structure
D:/a/b/c/d/
And then a folder with soundfonts
That was his default sf path, and the one he had in his lmms settings
So ~200 projects had this information in each project:
Now he got a new pc
He now installed lmms as default in C
None of his 200 projects can load
Why is the
src=
not just a reference to the path made in lmms-settingsIs there a special reason, that the information must be added to the project-file as a hardcoded string, and not as a reference to the directory in lmms-settings
The same goes for all other
src=
It would be best if they were references to just one constant namely the strings in lmms-settings
The text was updated successfully, but these errors were encountered: