Tres Finocchiaro

> Not sure if this is the right place to comment for this Thanks. It's not, really. This thread is for software workflow (not developer workflow). Probably better for the...

> Presets saved as xpf-files has path to the instrument hard-coded in the file. It does not matter for LMMS-instruments, but it does for VST-presets plugin="H:/LMMS/presets/VST/DSK techsynth PRO/DSK TechSynth PRO.dll"...

I wrote it a while ago because the relativize logic was already written for samples, scaled well to SF2 and and there was no dedicated "plugins" folder yet so we...

Tagging @DomClark -- our resident expert with VSTs. :)

@DomClark excellent investigation. Can you please open a bug at JUCE describing the issue?

> I'm not forcing the MIT onto anyone. It's compatible with the GPL and thus MIT files can be relicensed under the GPL. @jasp00 is correct. Future contributions to this...

> Thanks. Double standard will make my life easier. As indicated, we already have this exception on CMake files. Assuming "double standard" means "two standards", and not the proverbial English...

> Possible culprits: https://github.com/LMMS/lmms/pull/3940 and https://github.com/LMMS/lmms/pull/3987 #3940 was essentially a direct clone of 0.60 and a partial rename (from `calf.so` to `veal.so` to avoid namespace conflicts with the ones from...

Each time this was [proposed in the past](https://github.com/LMMS/lmms/pull/2118), I've been an opponent. I've always felt that it proposes inflation to the code for what I would consider a small chance...

> Calf has been been bumped from Calf 0.18 -> Calf 0.90 since stable-1.2 . @zonkmachine just for clarification, when you say "since `stable-1.2`", I assume you're referring to builds...