I have completed an initial release of the vst3-opcodes plugin opcode
for Csound.

The vst3-opcodes plugin enables Csound to host VST3 plugins. VST3 is
the current version of the VST protocol from Steinberg. It offers some
advantages over the earlier VST2 protocol: sample accurate scheduling
of parameter updates, more flexible parameter naming and arrangement,
and real-time control of individual notes.

The VST3 SDK from Steinberg is hosted on GitHub and is GPLv3 for
non-commercial uses, such as Csound and the vst3-opcodes. The
vst3-opcodes project, also hosted on GitHub, is also GPLv3. That means
the vst3-opcodes are compatible with Csound's LGPLv2.1 license, thanks
to that clause permitting re-licensing Csound code to "any later
version" of the GPL. Therefore, the vst3-opcodes are fully and legally
licensed according to both the Steinberg license and the Csound
license.

I have attached a copy of the documentation for these opcodes to this
email. The major differences with the earlier vst4cs opcodes, which
are still the only way for Csound to host VST2 plugins, are that the
vst3-opcodes do not provide a way to open a plugin's user interface
window, and that the vst3init opcode requires an additional parameter
to specify the name of the plugin within its loadable module (AKA
shared library, DLL, or bundle).

I have only tested these opcodes on Linux. However, I scrupulously
followed the guidelines of the VST3 SDK and used its CMake build
system, which is cross-platform. So, with very little work, it should
be possible to build and use the vst3-opcodes also on Windows and
macOS.

Suggestions and bug reports are welcome.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

All that looks great Michael, I will take a look.}

Many thanks.

El sáb., 4 jul. 2020 a las 16:37, Michael Gogins (<michael.gogins@gmail.com>) escribió:

I have completed an initial release of the vst3-opcodes plugin opcode
for Csound.

The vst3-opcodes plugin enables Csound to host VST3 plugins. VST3 is
the current version of the VST protocol from Steinberg. It offers some
advantages over the earlier VST2 protocol: sample accurate scheduling
of parameter updates, more flexible parameter naming and arrangement,
and real-time control of individual notes.

The VST3 SDK from Steinberg is hosted on GitHub and is GPLv3 for
non-commercial uses, such as Csound and the vst3-opcodes. The
vst3-opcodes project, also hosted on GitHub, is also GPLv3. That means
the vst3-opcodes are compatible with Csound's LGPLv2.1 license, thanks
to that clause permitting re-licensing Csound code to "any later
version" of the GPL. Therefore, the vst3-opcodes are fully and legally
licensed according to both the Steinberg license and the Csound
license.

I have attached a copy of the documentation for these opcodes to this
email. The major differences with the earlier vst4cs opcodes, which
are still the only way for Csound to host VST2 plugins, are that the
vst3-opcodes do not provide a way to open a plugin's user interface
window, and that the vst3init opcode requires an additional parameter
to specify the name of the plugin within its loadable module (AKA
shared library, DLL, or bundle).

I have only tested these opcodes on Linux. However, I scrupulously
followed the guidelines of the VST3 SDK and used its CMake build
system, which is cross-platform. So, with very little work, it should
be possible to build and use the vst3-opcodes also on Windows and
macOS.

Suggestions and bug reports are welcome.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

--

Dr. Oscar Pablo Di Liscia
Profesor Titular
Director Programa de Investigación "Sistemas Temporales y Síntesis Espacial en el Arte Sonoro"
http://stseas.web.unq.edu.ar/
Director Colección Editorial "Música y Ciencia"
Escuela Universitaria de Artes
Universidad Nacional de Quilmes
Argentina

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Thanks, keep us posted!

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Fri, Jul 10, 2020 at 1:59 PM walker davis <walkerdavismusic@gmail.com> wrote:
>
> Michael,
>
> Super exciting.  I posted here a few months ago about this very issue, so really excited to see what is possible here.  Will check it out soon.
>
> Thank you!
>
> --------------------------------
> Walker Davis
>
>
> On Sat, Jul 4, 2020 at 4:00 PM Oscar Pablo Di Liscia <oscarpablodiliscia@gmail.com> wrote:
>>
>> All that looks great Michael, I will take a look.}
>> Many thanks.
>>
>> El sáb., 4 jul. 2020 a las 16:37, Michael Gogins (<michael.gogins@gmail.com>) escribió:
>>>
>>> I have completed an initial release of the vst3-opcodes plugin opcode
>>> for Csound.
>>>
>>> The vst3-opcodes plugin enables Csound to host VST3 plugins. VST3 is
>>> the current version of the VST protocol from Steinberg. It offers some
>>> advantages over the earlier VST2 protocol: sample accurate scheduling
>>> of parameter updates, more flexible parameter naming and arrangement,
>>> and real-time control of individual notes.
>>>
>>> The VST3 SDK from Steinberg is hosted on GitHub and is GPLv3 for
>>> non-commercial uses, such as Csound and the vst3-opcodes. The
>>> vst3-opcodes project, also hosted on GitHub, is also GPLv3. That means
>>> the vst3-opcodes are compatible with Csound's LGPLv2.1 license, thanks
>>> to that clause permitting re-licensing Csound code to "any later
>>> version" of the GPL. Therefore, the vst3-opcodes are fully and legally
>>> licensed according to both the Steinberg license and the Csound
>>> license.
>>>
>>> I have attached a copy of the documentation for these opcodes to this
>>> email. The major differences with the earlier vst4cs opcodes, which
>>> are still the only way for Csound to host VST2 plugins, are that the
>>> vst3-opcodes do not provide a way to open a plugin's user interface
>>> window, and that the vst3init opcode requires an additional parameter
>>> to specify the name of the plugin within its loadable module (AKA
>>> shared library, DLL, or bundle).
>>>
>>> I have only tested these opcodes on Linux. However, I scrupulously
>>> followed the guidelines of the VST3 SDK and used its CMake build
>>> system, which is cross-platform. So, with very little work, it should
>>> be possible to build and use the vst3-opcodes also on Windows and
>>> macOS.
>>>
>>> Suggestions and bug reports are welcome.
>>>
>>> Regards,
>>> Mike
>>>
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>>
>>
>> --
>> Dr. Oscar Pablo Di Liscia
>> Profesor Titular
>> Director Programa de Investigación "Sistemas Temporales y Síntesis Espacial en el Arte Sonoro"
>> http://stseas.web.unq.edu.ar/
>> Director Colección Editorial "Música y Ciencia"
>> Escuela Universitaria de Artes
>> Universidad Nacional de Quilmes
>> Argentina
>> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>
> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Hey Michael n co,

Wow, getting to this so much later than anticipated(last here June 2020 yikes), my apologies.  Anyways, I am struggling to follow the installation instructions for Mac on README.md.

I have followed these steps(substituting the “linux” str’s with “mac” where possible):

1) cloned repo from:  https://github.com/gogins/csound-vst3-opcodes

Run the following:

2) bash update-submodules.bash -> no apparent issues

3) bash clean-build-macos.bash -> error below, but completes

** BUILD FAILED **

The following build commands failed:

        CompileC /YOUR_DIR/Github/csound-vst3-opcodes/csound-vst3/build/vst3-opcodes/vstsdk.build/Debug/vst3_plugins.build/Objects-normal/x86_64/vst3-opcodes.o /YOUR_DIR/Github/csound-vst3-opcodes/csound-vst3/vst3-opcodes/vst3-opcodes.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler

(1 failure)

mv: rename lib/Debug/libvst3_plugins.so to lib/Debug/libvst3_plugins.dylib: No such file or directory

Completed a clean build of csound-vst3.

Install to: Frameworks/CsoundLib64.framework/Versions/6.0/Resources/Opcodes64/libvst3_plugins.dylib.

This location may differ on your system.

(libvst3_plugins.dylib does not seem to exist anywhere on my machine)

4) bash zip-macos.bash -> produces several ‘7za: command not found’ errors

(thought I try this, was not in your instructions)

5) move/rename ‘/YOUR_DIR/Github/csound-vst3-opcodes/csound-vst3/vst3-opcodes/vst3-opcodes.cpp’ to the new ‘/YOUR_DIR/Github/csound-vst3-opcodes/csound/Opcodes’

6) csound csound-vst3/vst3-opcodes/CollidingComb.csd AND/OR csound csound csound-vst3/vst3-opcodes/vst3-opcodes-test-macos.csd 

error: syntax error, unexpected T_IDENT  (token "vst3init") from file csound-vst3/vst3-opcodes/CollidingComb.csd (1)

 line 39:

>>>gi_vst3_handle_CollidingCombSynth vst3init <<<

Unexpected untyped word gi_vst3_handle_CollidingCombSynth when expecting a variable

Parsing failed due to invalid input!

I have seen similar errors before, confirms that the vst3init was not correctly installed

I feel like something is going wrong at step 3, or I am not following the instructions somehow… I am also unclear on what you mean by the Csound plugin directory, is that the CsoundLib64.framework/Versions/6.0/Resources/Opcodes64 directory installed by the .dmg?  I am assuming that libvst3_plugins.dylib needs to end up in that folder, correct?

Any advice/instructions here would be greatly appreciated.  Again, apologies for taking so long to get back on this, I have some time to test things here on the Mac side for you in the upcoming months if need be, please let me know.  

Cheers, thanks again Michael,

Best,

Walker

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Michael,

Thanks for the quick response here.  I went through the steps on your github workflow page and it looks like that was what I was trying yesterday.  Still getting the same errors mentioned above.

Although I imagine there isn't too much I can help with here(I am not super fluent in C/C++), please let me know if there is anything I can do to help when you get to debugging the Github build.  

Thanks again,

Walker

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Sounds good Mike, happy to test.  I personally do not have access to Windows machine at the moment, however.

Still receiving the same errors as the previous build currently.  Seems like something is failing in clean-build-macos.bash

Walker

Hey Mike,

Followed your changes on the Github repo today.  Definitely have made some progress since this morning.

With your latest commit, I was able to build the libvst3_plugins.dylib, however it only ended up in build-tacos/lib/Debug/, not build-tacos/lib/Release/.  

I have been working on running ../csound-vst3-opcodes/csound-vst3/vst3-opcodes/vst3-opcodes-test-macos.csd.

So far:

- replacing “Release” with “Debug” in all of the filepath’s loads the plug-ins (ie”../../build-macos/VST3/Debug/mda-vst3.vst3”) seems to properly load the vst3cs opcodes, woohoo!

- there seems to be an issue with the prints statements, results in “Abort trap: 6”

- once prints statements are removed, the file runs and completes, however there isn’t any audio written to the test.aif (perhaps it is too quiet)

In an attempt to isolate a single vst, I removed all non-Piano/PianoOutput instruments, hoping to see if I could get just a single VST to work.  I am not super familiar with the ‘connect’, ‘outleta’, and ‘inleta’ opcodes, but I believe I was able to properly pass audio to the Master_Output.  Messing with some of the Score_Generator values, I was able to produce a few short square wave sounding noise/notes at the beginning of the written audio file, but I don’t think that was supposed to behave that way.

Other things I noticed/thought:

- line 20: 0dbfs = 20 seems weird to me(although I am not quite sure I fully understand what this constant does)

- perhaps the plug-ins are not cross-platform/behave differently(downloaded the mda plug-ins and they behave nicely in Ableton 10)

As for some of the other .csd files (Odin, Dexed, CollidingComb) I did not spend too much time here, but it looks like there are some local file paths hanging around.

Thanks again for all of your work, has been fun day trying to hook up plug-ins into csound.  Looking forward to further debugging.

Walker

On Fri, Nov 5, 2021 at 11:43 AM walker davis <walkerdavismusic@gmail.com> wrote:

Sounds good Mike, happy to test.  I personally do not have access to Windows machine at the moment, however.

Still receiving the same errors as the previous build currently.  Seems like something is failing in clean-build-macos.bash

Walker

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Thanks for the update! Much appreciated. 

I'm working what I think is the final issue in producing binaries on GitHub. My GitHub runner for MacOS picks up the wrong version of the vstgui repository. No idea why but I have some things to try. 

Regards, 

Mike

On Fri, Nov 5, 2021, 19:39 walker davis <walkerdavismusic@gmail.com> wrote:

Hey Mike,

Followed your changes on the Github repo today.  Definitely have made some progress since this morning.

With your latest commit, I was able to build the libvst3_plugins.dylib, however it only ended up in build-tacos/lib/Debug/, not build-tacos/lib/Release/.  

I have been working on running ../csound-vst3-opcodes/csound-vst3/vst3-opcodes/vst3-opcodes-test-macos.csd.

So far:

- replacing “Release” with “Debug” in all of the filepath’s loads the plug-ins (ie”../../build-macos/VST3/Debug/mda-vst3.vst3”) seems to properly load the vst3cs opcodes, woohoo!

- there seems to be an issue with the prints statements, results in “Abort trap: 6”

- once prints statements are removed, the file runs and completes, however there isn’t any audio written to the test.aif (perhaps it is too quiet)

In an attempt to isolate a single vst, I removed all non-Piano/PianoOutput instruments, hoping to see if I could get just a single VST to work.  I am not super familiar with the ‘connect’, ‘outleta’, and ‘inleta’ opcodes, but I believe I was able to properly pass audio to the Master_Output.  Messing with some of the Score_Generator values, I was able to produce a few short square wave sounding noise/notes at the beginning of the written audio file, but I don’t think that was supposed to behave that way.

Other things I noticed/thought:

- line 20: 0dbfs = 20 seems weird to me(although I am not quite sure I fully understand what this constant does)

- perhaps the plug-ins are not cross-platform/behave differently(downloaded the mda plug-ins and they behave nicely in Ableton 10)

As for some of the other .csd files (Odin, Dexed, CollidingComb) I did not spend too much time here, but it looks like there are some local file paths hanging around.

Thanks again for all of your work, has been fun day trying to hook up plug-ins into csound.  Looking forward to further debugging.

Walker

On Fri, Nov 5, 2021 at 11:43 AM walker davis <walkerdavismusic@gmail.com> wrote:

Sounds good Mike, happy to test.  I personally do not have access to Windows machine at the moment, however.

Still receiving the same errors as the previous build currently.  Seems like something is failing in clean-build-macos.bash

Walker

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here