You are here
Home › Forum home › VirtualMIDISynth › Wishlist › Paths to added soundfont files is saved as relative in config file ›Paths to added soundfont files is saved as relative in config file
Please let our ADS show!
This sites offers only FREE software and it's supported by a few advertisement boxes (no intrusive popups).
Please:
- disable your AdBlocker by adding CoolSoft website to whitelist
- give the proper cookie consent
- enable JavaScript for this website
This seconds wait is to let you update your browser configuration...
Ok, I've done the required changes... now show me your content!- LenweSaralonde
- Posts: 9
- Joined: April 28, 2020 - 12:12
- coolsoft
- Posts: 1979
- Joined: March 25, 2012 - 01:19
LenweSaralonde wrote:I noticed the soundfont files are stored in the VirtualMIDISynth.conf configuration file using the relative path from the vmssf file
No, it's not (and I agree it shouldn't).
Exported file contains the filenames format as shown in the soundfonts list, which must be (and it's supposed to be) an absolute path.
Maybe it all started after importing the wrongly saved .vmssf file at first.
Should be great to know how did you came into that condition...
Could you try to add/remove SF2 files from the list and check that each one is shown with its full path?
(do not load an already wrong .vmssf file, because there's actually no check on file paths)
- LenweSaralonde
- Posts: 9
- Joined: April 28, 2020 - 12:12
My .vmssf file has been generated by hand with relative paths because it's intended to be bundled within a pack of .sfz files so we can't predict the full path of the folder the end user will save them.
- Soundfont files added by the .vmssf file with relative paths show as relative
- When adding a soundfont file by drag and drop or using the + button, the full absolute path is shown
- Relative and absolute paths described above are reflected in the VirtualMIDISynth.conf file and the exported .vmssf file
IMO it would make sense to me to allow relative paths in .vmssf (so they can be distributed in packs) and convert them into absolute path during the import process.
- Attachments (Only registered users)
- Screenshot from 2020-05-04 16-26-16.png
- coolsoft
- Posts: 1979
- Joined: March 25, 2012 - 01:19
Ok, now I understand.
I thought this was a bug report (since you've posted it in Bug reports section), but this is much more a feature request, so I'll move it to the Wishlist section.
Now, I could try to "fix" paths relative --> absolute (if they're not) on import, but export will always contain absolute paths...
Can you confirm that this is what you're asking for?
- LenweSaralonde
- Posts: 9
- Joined: April 28, 2020 - 12:12
coolsoft wrote:Now, I could try to "fix" paths relative --> absolute (if they're not) on import, but export will always contain absolute paths...
Can you confirm that this is what you're asking for?
Yes
- LenweSaralonde
- Posts: 9
- Joined: April 28, 2020 - 12:12
Hi
Will this feature be implemented soon ? I don't see it in the TODO list.
This feature would be helpful for my project. I have a dirty workaround for now (generating a .bat file that generates the config file with absolute paths) but allowing to rewrite relative paths to absolute during import would be much more cleaner.
- coolsoft
- Posts: 1979
- Joined: March 25, 2012 - 01:19
I'm really sorry, I've somehow missed this thread.
Or rather, I thought I've already posted a version with this feature... 🙄.
Looking back to my source repository log I've found that... it was never included, so I dit it now 😉.
Version 2.10.2 is now available and includes this new feature.
Please check it out and report your thoughts.
- LenweSaralonde
- Posts: 9
- Joined: April 28, 2020 - 12:12
It works great now, thanks a lot !
Navigation
Login
Support me
Click here if you want to support CoolSoft using PayPal