Second, let's say the original author had his soundfont in some a weird absolute path. We don't do that with missing sound samples, right? Simply opening and saving a project shouldn't break it if some paths are missing. Saving it will save the "broken" version.įirst of all the broken paths should be left alone. Look at it as a compromise solution.Ĭurrently: When opening a project that contains references to a SF2 that doesn't exist, the invalid paths are replaced by the default soundfont path. This is not to be confused with storing samples relative to project files, which is outlined in #2982.
HOW TO OPEN SF2 FILES IN LMMS PATCH
If you can point me to a regression that occured between 1.1.0 and 1.2.0, I'll consider writing a patch for this, but at a glance it appears the bug was adding this location to the UI to begin with. I'm sure there will be a few people asking to have their SF2 directory outside their samples directory, but still relocatable, but it's simply not something we support. What seems to be the missing puzzle piece here is that we added an option for a "SF2 DIRECTORY" folder, but we ignore it. Soundfonts were decided to be stored inside samples/sf2, discussed in #1807 and implemented in #1908 and then renamed to samples/soundfonts in #3895.
HOW TO OPEN SF2 FILES IN LMMS SOFTWARE
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 feel this is a bug.
0 kommentar(er)
