macOS: Error with SixSines VST3

Help, Support & Bugs
1

Hi,

install https://github.com/baconpaul/six-sines/releases/download/Nightly/six-sines-macOS-2025-02-04-633146d.dmg

Do a rescan. The below message will appear (I guess due to an error in the nightly build). The problem is now, if you press [OK], Renoise will force quit. I think that should not happen. Also the message is a bit vague, and I already did a rescan.

grafik
grafik980Ɨ260 16.3 KB

2

Weird, it loads just normally in Buttwig. And in Unabletonā€¦ maybe it uses an feature which Renoise misinterprets or something?

3

BaconPaul has no idea how to fix it, so I assume itā€™s a Renoise problem:
https://www.kvraudio.com/forum/viewtopic.php?p=9039043#p9039043

4

@taktik baconpaul mentioned that there actually might be a bug in Renoise then (I donā€™t fully understand it):
https://www.kvraudio.com/forum/viewtopic.php?p=9039175#p9039175

5

Yeah hi @taktik good to chat again. Even if it is about oddities in VST3.

This is definitely a renoise problem with VST3 support, caused by the nightly six sines vst3 having (1) two plugins inside one vst3 file and perhaps (2) those have different topologies.

So hereā€™s what happens

  • The nightly six sines vst3 has two internal plugins. That is, when you scan the single vst3 file you get a pair of vst3s, one called ā€œSix Sinesā€, the other called ā€œSix Sines, Seven Outsā€. The first is the stereo synth, the second is a synth with seven outputs (main plus one per operator)
  • When renoise scans this
    • for the AU it shows both
    • but for the VST3 it doesnt
  • Then when you load the VST3 it says that the synth is an effect, I think because it is confused about which plugin to use and which topology it has

The solution to this is probably supporting multi-plugin cases properly. They are becoming more common (u-he, waves have them and increasingly Iā€™m using them in surge-adjacent land).

But to get ffx back in the water and give you an a b test Iā€™ve just pushed a change which makes two nightlies on mac and windows, one with the full feature set and one with just a single plugin. In my testing when I built the nightly with the single plugin only version, renoise loaded it just fine.

If you want that binary, grab the single-plugin- version of the installers here Release Nightly Ā· baconpaul/six-sines Ā· GitHub

let me know how to help!

1 Like
6

Oh also if there was some reliable cross-platform way for me to know at scan and load time that i was in renoise I could work around this problem without a separate build (which would be great for me).

In my dev area, for instance, I did this

uint32_t clap_get_plugin_count(const clap_plugin_factory *)
{
    bool isRenoise{false};
#if __APPLE__
    if (strstr(getprogname(), "Renoise") != nullptr)
        isRenoise = true;
#endif

    return isRenoise ? 1 : 2;
};

and then the ā€˜regularā€™ vst3 loads in renoise (because it becomes the single-plugin version). Obviously I donā€™ want to do that and i donā€™t want to do a registry or filesystem wide trick either but if, say, renoise consistently set an env variable like IS_RENOISE across platforms I would happily do that and then I could retire my split build pipeline.