Custom file extensions for presets
-
Is there a way to change the file extension the preset browser is expecting instead of just .preset? I'm not sure if this would be possible using the built in preset browser or if I'd need to script my own preset loading system.
Thanks for your help
-
@card100 said in Custom file extensions for presets:
Is there a way to change the file extension the preset browser is expecting instead of just .preset? I'm not sure if this would be possible using the built in preset browser or if I'd need to script my own preset loading system.
Thanks for your help
you would need to edit the HISE source I think
-
Would be ge great if that could be a setting
-
This post is deleted! -
@card100 what's wrong with .preset?
-
@d-healey I think having a file extension specific to your plugin comes off as being more professional than a generic file extension that other plugins also use. Also could be confusing to some users as the .preset file type can be opened in a different program that also uses .preset and obviously not work. If two programs are using the same file extension, they should be able to open each other's files (eg a pdf).
-
@card100 said in Custom file extensions for presets:
If two programs are using the same file extension, they should be able to open each other's files
All HISE plugins can load all .preset files made with a HISE project - not that it's a very useful thing to do though.
-
@d-healey Exactly. So if I have a rouge preset file for some reason, I have no idea what plugin it goes with. Let alone a user who doesn't understand what file extensions even are and lets the os just choose a program to open it in. It's just a little small thing to make a user experience a bit better
-
For anyone reading in the future, modifying the source code was pretty straightforward. Literally just replaced every instance of .preset to your file extension across the cpp files and recompiled.
