What is the status of GitHub branches, how do these relate to Ctrlr versions

[Anonymous]

Hi there,
Trying to build Ctrlr yesterday on Linux, I wound up exploring the state of both the master and the stable branch.
I found the master branch build to be somewhat broken – the luabind and laubind-deboostify had backward compatibility issues.
Does master correspond to the Ctrlr v5.3.X stuff?
Am I right in thinking that this has no future – and v6/ a different branch will take over?
The stable branch built (largely without issue) – and the Ctrlr.org standalone shows v6. I’m puzzled about what is to be done to incorporate the VST v2/ v3 stuff, as this appears to be missing from the repository.
Are we to download the VST stuff separately?
If so are there particular versions/dates that have been used?
The messages elsewhere in the forum suggest that v6 has been built as VST…so someone must have succeeded?
Thanks in anticipation.

[Possemo]

I remember that the “vst v2” components had to be deleted in order to comply with Steinbergs new copyrights. They want to get rid of vst v2 in order to push vst v3. You had to fill out a form to be able to contiune to use vst v2 legally until the end of 2017 if I remember well. So this opportunity is gone, but I guess if you publish a complete build of the Ctrlr plugin nobody would care. If you would sell it that probably could change things a bit.

• This reply was modified 4 years, 10 months ago by Possemo.

[Anonymous]

On the VST question…

Went looking on the Steinberg site to find the VST SDK. The V3 SDK specifically makes mention of a GPLv3 possibility provided your “product” is also licensed under GPLv3. I see that Ctrlr source code is currently under GPLv2 – If this were attended to it seems to suggest that the V3 SDK code could be bundled with Ctrlr – which would make the builds easier…

[Possemo]

VST v3 would be nice, but I fear that it could be a lot of work to develop a Ctrlr v3-VSTi plugin. When my work on the Korg 05R/W panel will be finished I will have another try to build Ctrlr for Win. I think the first step would be to try to build the standalone version, then I will maybe try to mess around with the plugin. The VST v2 components should still be available somewhere.

I think another very important thing is the ability to make instances. It just doesn’t feel right when you load Ctrlr and then load a panel into Ctrlr. When you load a dozen panels into the same Ctrlr instance panels interfere, Lua code mixes up, and the whole thing eventually crashes. Moreover, to protect your work from people who are selling panels a restricted instance would be needed.

[Author]

Posts