KVR Audio

EvilDragon · Post by **EvilDragon** » Wed Jul 13, 2022 5:31 pm

Yes, since VST SDK version 3.6.something, the plugin must be distributed as a bundle. Since Windows doesn't have a concept of bundles, it's just a folder, and this is its specified layout. We cannot change it, nothing we can do about this since it's Steinberg's specification, JUCE already builds VST3 plugins this way. Don't touch it.

vurt · Post by **vurt** » Wed Jul 13, 2022 5:42 pm

EvilDragon wrote: Wed Jul 13, 2022 5:31 pm Yes, since VST SDK version 3.6.something, the plugin must be distributed as a bundle. Since Windows doesn't have a concept of bundles, it's just a folder, and this is its specified layout. We cannot change it, nothing we can do about this since it's Steinberg's specification, JUCE already builds VST3 plugins this way. Don't touch it.

that untidiness is another reason we should all be backing clap where we can!!!

EvilDragon · Post by **EvilDragon** » Wed Jul 13, 2022 6:10 pm

Well, CLAP can also be built as a bundle (but IIRC it's not mandatory).

It's just a folder. You don't need to worry nor care about it (it's in a prescribed path already, which CLAP also has)...

vurt · Post by **vurt** » Wed Jul 13, 2022 6:12 pm

exactly, not enforced!

Chris-S · Post by **Chris-S** » Wed Jul 13, 2022 7:45 pm

I'm creating a Dual patch. After creating Scene A I copied the settings to Scene B.
I expected that Scene B sounds exactly like Scene B, but it sounds very different.
Bug?
Version: latest nightly

Chris-S · Post by **Chris-S** » Wed Jul 13, 2022 8:51 pm

I think I found the reason: The "Absolute" mode of the pitch-slider of a modern-osc is NOT copied when copying the scene from A to B.

EvilDragon · Post by **EvilDragon** » Wed Jul 13, 2022 10:34 pm

Nice catch! Confirmed.

rlared · Post by **rlared** » Wed Jul 13, 2022 10:54 pm

Any chance to get a Flatpak version?

EvilDragon · Post by **EvilDragon** » Wed Jul 13, 2022 11:06 pm

It's alredy there apparently.

https://flathub.org/apps/details/org.su ... m.surge-xt

BTW, we're not handling this at all, it's somebody from Flatpak community doing this.

bagpipe200 · Post by **bagpipe200** » Thu Jul 14, 2022 12:02 am

Would it be possible to have issues regarding Vember Audio Surge (which I love!) created under their own new threads? I'd be happy to skip over many of these recent questions but its kinda difficult when they're all posted under this "Vember Audio Surge is now open-source" thread from ages ago.

Of course I just posted in this same thread with my (new) request!!! D'Oh!

audiojunkie · Post by **audiojunkie** » Thu Jul 14, 2022 12:03 am

Hey @EvilDragon,

While we're at it, could you make your linux binary more distro agnostic? For example, I use Fedora right now, and Fedora uses the RPM packages. You guys package DEBs. If you did like TAL-Software and released a zip file with a quick readme to tell where the folders need to be copied to, more Linux users could have fun with Surge-XT. Please consider it. If you look at the way most developers are releasing their Linux software, you'll see that they try to be as distro agnostic as possible.

Barring that, could you consider switching your Linux binary creation to something like the OBS (Open Build Service) that allows you to compile once but package for many different formats? Either of these would be extremely helpful for us Linux users.

Thanks for listening!

baconpaul · Post by **baconpaul** » Thu Jul 14, 2022 12:18 am

bagpipe200 wrote: Thu Jul 14, 2022 12:02 am Would it be possible to have issues regarding Vember Audio Surge (which I love!) created under their own new threads? I'd be happy to skip over many of these recent questions but its kinda difficult when they're all posted under this "Vember Audio Surge is now open-source" thread from ages ago.

Of course I just posted in this same thread with my (new) request!!! D'Oh!

We would *infinitely* prefer issues are on GitHub or our discord; but if they aren't on GitHub having them on this thread is useful because some of us only subscribe to a limited set of KVR threads. This thread is basically the 'chat with surge team' spot on KVR. As you can see by yesterday me posting a followup to an item opened here in 2019

baconpaul · Post by **baconpaul** » Thu Jul 14, 2022 12:19 am

audiojunkie wrote: Thu Jul 14, 2022 12:03 am Hey @EvilDragon,

While we're at it, could you make your linux binary more distro agnostic? For example, I use Fedora right now, and Fedora uses the RPM packages. You guys package DEBs. If you did like TAL-Software and released a zip file with a quick readme to tell where the folders need to be copied to, more Linux users could have fun with Surge-XT. Please consider it. If you look at the way most developers are releasing their Linux software, you'll see that they try to be as distro agnostic as possible.

Barring that, could you consider switching your Linux binary creation to something like the OBS (Open Build Service) that allows you to compile once but package for many different formats? Either of these would be extremely helpful for us Linux users.

Thanks for listening!

We have had a rpm and zip (well a tar.gz) for linux for about a year now. https://github.com/surge-synthesizer/re ... /tag/1.0.1

audiojunkie · Post by **audiojunkie** » Thu Jul 14, 2022 3:36 am

Fantastic! I hadn’t noticed that before. I had a hard time finding that page, because I saw the message saying there were “no packages” and skipped over “releases”. I didn’t think of the possibility that binaries might be stored in another location. Thank you for creating binaries for your software!

EvilDragon · Post by **EvilDragon** » Thu Jul 14, 2022 7:18 am

bagpipe200 wrote: Thu Jul 14, 2022 12:02 am Would it be possible to have issues regarding Vember Audio Surge (which I love!) created under their own new threads? I'd be happy to skip over many of these recent questions but its kinda difficult when they're all posted under this "Vember Audio Surge is now open-source" thread from ages ago.

Of course I just posted in this same thread with my (new) request!!! D'Oh!

Please, no. It's good that we can always just scan this one thread and notice any issues, rather than thrawling through the whole forum.

Of course, the best way would be reporting directly to our GitHub issue tracker, here.