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.
Posts made by card100
-
RE: Custom file extensions for presets
-
RE: Custom file extensions for presets
@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
-
RE: Custom file extensions for presets
@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).
-
RE: Custom file extensions for presets
Would be ge great if that could be a setting
-
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
-
RE: Building a Panic Button
@ustk I don't know why I didn't think of that... Thanks!
-
Building a Panic Button
What would be the best way to implement a panic button that cuts off processes going on? I've seen this post but that is only cutting off the midi notes. However, the "send all note off message" button in the HISE controller (the (!) button) does kill all processes going on like a delay chain or reverb tail. Is there a way to call this in my code? I couldn't find anything in the docs about it
Thanks for your help