PG-8X (2.0) released
- KVRAF
- 23102 posts since 7 Jan, 2009 from Croatia
It's not yet 100% confirmed that PG-8X will go fully under SST wings (however nothing prevents us to just fork Martin's repository and see what happens!), but we have discussed about various things with Martin and he's open for collaboration.
GUI is going to be updated with resizeable interface for sure, for this I think both Martin and myself would like to touch base again with ENV1 who did the current skin for it!
GUI is going to be updated with resizeable interface for sure, for this I think both Martin and myself would like to touch base again with ENV1 who did the current skin for it!
- Banned
- 10732 posts since 17 Nov, 2015
EvilDragon wrote: ↑Fri Jan 22, 2021 9:05 pm VST3 was released in 2008, the transition to 64-bit was still kinda in process back then...
That said, many plugin developers simply decided once they went to VST3 they would also go 64-bit only, so that kinda skews perception I suppose!
sure, but the transition to vst3 is much slower.... I know most devs won't give up vst2. 4(?) are some have been vocal (privately and publicly) about not liking it/being forced to use it (I don't code, but they obviously prefer the old way)
i guess most devs have gone 64bit only to save time on a tiny part of the market, cant argue with that
- KVRAF
- 23102 posts since 7 Jan, 2009 from Croatia
Yeah for sure already established devs who signed a contract with Steinberg for the SDK prior to 2018 can continue to build VST2 just fine. It just doesn't apply for any new developers after 2018, including any open-source development.
It's true that VST2 is a much, much, MUCH simpler spec, but such is the way the cookie crumbles...
It's true that VST2 is a much, much, MUCH simpler spec, but such is the way the cookie crumbles...
- Banned
- 10732 posts since 17 Nov, 2015
yeah, i guess everyone has to move with the times.... shame when it's forced tho....
i dont like change!
i will literally have to buy a new pc soon just to keep up with modern spec, even tho it's a great pc that works fine.... but no AAX etc
oh well....
i dont like change!
i will literally have to buy a new pc soon just to keep up with modern spec, even tho it's a great pc that works fine.... but no AAX etc
oh well....
-
- KVRAF
- 2802 posts since 31 Aug, 2011
This shouldnt be a problem.EvilDragon wrote: GUI is going to be updated with resizeable interface for sure, for this I think both Martin and myself would like to touch base again with ENV1 who did the current skin for it!
I have countless WIPs for a larger version already done, (which Martin rejected at the time because he thought theyre too big), so i pretty much just need to finish one of these, and i can always make them even bigger.
rightclick and select View Image for fullsize
You do not have the required permissions to view the files attached to this post.
-
The Nerdy Music Guy The Nerdy Music Guy https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=475847
- KVRist
- 172 posts since 7 Oct, 2020
- KVRAF
- 18561 posts since 16 Sep, 2001 from Las Vegas,USA
ENV1 wrote: ↑Fri Jan 22, 2021 11:44 pmThis shouldnt be a problem.EvilDragon wrote: GUI is going to be updated with resizeable interface for sure, for this I think both Martin and myself would like to touch base again with ENV1 who did the current skin for it!
I have countless WIPs for a larger version already done, (which Martin rejected at the time because he thought theyre too big), so i pretty much just need to finish one of these, and i can always make them even bigger.
That's great news! I came here to recommend ENV1 do the GUI for any future versions. Love the style.
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe
-
- KVRer
- 14 posts since 18 Aug, 2020
I used this synth a lot the new one looks exciting
- KVRAF
- 23102 posts since 7 Jan, 2009 from Croatia
ENV1 wrote: ↑Fri Jan 22, 2021 11:44 pmThis shouldnt be a problem.EvilDragon wrote: GUI is going to be updated with resizeable interface for sure, for this I think both Martin and myself would like to touch base again with ENV1 who did the current skin for it!
I have countless WIPs for a larger version already done, (which Martin rejected at the time because he thought theyre too big), so i pretty much just need to finish one of these, and i can always make them even bigger.
However I think the current GUI is perfectly fine in every way. We would only need it rendered at multiple zoom levels (HiDPI support etc.).
-
- KVRian
- Topic Starter
- 960 posts since 27 Jun, 2009 from Germany
Hi, sorry to participate only sparsely. As for the vst2.4 version: first of all, the current version will still be around and can be used. I want that the new version will be patch compatible, so that there is no problem to transition. Secondly, I still do have the vst2.4 license, so I should be able to do a binary release of a vst2.4. However, I need to double check that this is in fact allowed. As far as I understand, we just cannot ship it with a vst2.4 sdk in source form, but it should be possible to compile a vst2.4 if you have the license.
As for the GUI, it is great to see that ENV1 is interested, as his GUI is simply stunning. I also do not want to change much, aside from different zoom levels.
I am currently experimenting with JUCE, but it is still some way to go. I might first try it on the chorus effect plug-in, and then take it from there...
Cheers,
Martin
As for the GUI, it is great to see that ENV1 is interested, as his GUI is simply stunning. I also do not want to change much, aside from different zoom levels.
I am currently experimenting with JUCE, but it is still some way to go. I might first try it on the chorus effect plug-in, and then take it from there...
Cheers,
Martin
- KVRAF
- 23102 posts since 7 Jan, 2009 from Croatia
You can compile VST2 for your own use (if you've signed the VST2 SDK contract with Steinberg before 2018, which you did) but you cannot distribute it if your plugin is open sourced under GPL3 license (because this requires also shipping the source code along with your binary). VST2 SDK license is not compatible with open source in any way - only VST3 is, and ONLY through GPL3.
-
- KVRian
- Topic Starter
- 960 posts since 27 Jun, 2009 from Germany
What about dual licensing by the author? I thought that is always possible?
-
ReleaseCandidate ReleaseCandidate https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=476930
- KVRian
- 620 posts since 19 Oct, 2020
That's possible, you (the Surge team) have to ensure that every contributor to the source code allows distributing his GPL code under the closed license too.
But please don't ask mé about details, INAL.
- KVRAF
- 23102 posts since 7 Jan, 2009 from Croatia