Hi! I'm still playing around and experimenting with this wonderful software that is PlugData, and I've noticed a strange behavior regarding object priority using [scale] on Windows 10.
When running PlugData Standalone or Instrument VST, [scale] defaults to the Cyclone implementation. However, when running PlugData FX VST, the same patch defaults to Gem's [scale] object. I fixed it by setting it explicitly as [cyclone/scale], but I'm curious about this behavior.
Is there a specific reason why the library search priority changes between the FX and Instrument versions? I hope this is useful for someone else. Thanks!
Hi! I'm still playing around and experimenting with this wonderful software that is PlugData, and I've noticed a strange behavior regarding object priority using [scale] on Windows 10.
When running PlugData Standalone or Instrument VST, [scale] defaults to the Cyclone implementation. However, when running PlugData FX VST, the same patch defaults to Gem's [scale] object. I fixed it by setting it explicitly as [cyclone/scale], but I'm curious about this behavior.
Is there a specific reason why the library search priority changes between the FX and Instrument versions? I hope this is useful for someone else. Thanks!