I am pleased to report that both CsoundVST and the vst4cs opcodes
build and run without problems on Linux (Ubuntu 16.04 with Csound
develop head and gcc 5.4.0). I have tested the vst4cs opcodes with the
Pianoteq 6 VST plugin, which is available on Linux for license
holders.

I had to fix a couple of minor bugs in the Csound build system to get
this to work, so be sure to do a fresh pull if you want to try this.

Now that the Windows installer is building on AppVeyor and Csound
seems to be running fine from the AppVeyor-built installer, I am
planning to quit using Windows, and from now on to use exclusively
Linux.

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

We now have an AppVeyor build that produces the Windows installer.
People who break this build will be responsible for fixing it.

I think the AppVeyor build is much better than what I used to do. I
helped create the AppVeyor build. I will help out with maintaining it
if necessary. Other developers also have helped to create, and are
helping maintain, the AppVeyor build.

Just to be clear, the AppVeyor build is hosted in the cloud, so I can
make changes and see if they work without having my own Windows
computer. Also, I do have access to Windows computers that I can use
for seeing if the AppVeyor-built installer works.

However, one of my motives here is to cut down on the time I have
spent maintaining software, and to increase the time I spend
composing. Another, less important motive is that my Windows system
has become virtually obsolete.

Best,
Mike

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


On Tue, Dec 5, 2017 at 2:10 PM, Arthur Hunkins
<000001e1d761dea2-dmarc-request@listserv.heanet.ie> wrote:
> Michael said:
>  I am planning to quit using Windows, and from now on to use exclusively
> Linux.
>
> What does this mean for the maintenance and development of Csound in
> Windows?
>
> Art Hunkins
> http://www.arthunkins.com
>
> On Tue, Dec 5, 2017 at 1:34 PM, Dave Seidel  wrote:
>>
>> Woo-hoo! This is great.
>>
>> On Tue, Dec 5, 2017 at 1:23 PM, Michael Gogins 
>> wrote:
>>>
>>> I am pleased to report that both CsoundVST and the vst4cs opcodes
>>> build and run without problems on Linux (Ubuntu 16.04 with Csound
>>> develop head and gcc 5.4.0). I have tested the vst4cs opcodes with the
>>> Pianoteq 6 VST plugin, which is available on Linux for license
>>> holders.
>>>
>>> I had to fix a couple of minor bugs in the Csound build system to get
>>> this to work, so be sure to do a fresh pull if you want to try this.
>>>
>>> Now that the Windows installer is building on AppVeyor and Csound
>>> seems to be running fine from the AppVeyor-built installer, I am
>>> planning to quit using Windows, and from now on to use exclusively
>>> Linux.
>>>
>>> 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
>>
>>
>>
>>
>> --
>> http://mysterybear.net
>> https://soundcloud.com/mysterybear
>> https://mysterybear.bandcamp.com
>>
>> http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz
>> 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

You're welcome,
Mike

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


On Tue, Dec 5, 2017 at 2:32 PM, Arthur Hunkins
<000001e1d761dea2-dmarc-request@listserv.heanet.ie> wrote:
> Thanks for clarifying, Mike.
>
> I expected/hoped for some such. You bring a lot to the table, for which I am
> extremely grateful.
>
> Art Hunkins
> http://www.arthunkins.com
>
> On Tue, Dec 5, 2017 at 2:19 PM, Michael Gogins 
> wrote:
>>
>> We now have an AppVeyor build that produces the Windows installer.
>> People who break this build will be responsible for fixing it.
>>
>> I think the AppVeyor build is much better than what I used to do. I
>> helped create the AppVeyor build. I will help out with maintaining it
>> if necessary. Other developers also have helped to create, and are
>> helping maintain, the AppVeyor build.
>>
>> Just to be clear, the AppVeyor build is hosted in the cloud, so I can
>> make changes and see if they work without having my own Windows
>> computer. Also, I do have access to Windows computers that I can use
>> for seeing if the AppVeyor-built installer works.
>>
>> However, one of my motives here is to cut down on the time I have
>> spent maintaining software, and to increase the time I spend
>> composing. Another, less important motive is that my Windows system
>> has become virtually obsolete.
>>
>> Best,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Tue, Dec 5, 2017 at 2:10 PM, Arthur Hunkins
>> <000001e1d761dea2-dmarc-request@listserv.heanet.ie> wrote:
>> > Michael said:
>> >  I am planning to quit using Windows, and from now on to use exclusively
>> > Linux.
>> >
>> > What does this mean for the maintenance and development of Csound in
>> > Windows?
>> >
>> > Art Hunkins
>> > http://www.arthunkins.com
>> >
>> > On Tue, Dec 5, 2017 at 1:34 PM, Dave Seidel 
>> > wrote:
>> >>
>> >> Woo-hoo! This is great.
>> >>
>> >> On Tue, Dec 5, 2017 at 1:23 PM, Michael Gogins
>> >> 
>> >> wrote:
>> >>>
>> >>> I am pleased to report that both CsoundVST and the vst4cs opcodes
>> >>> build and run without problems on Linux (Ubuntu 16.04 with Csound
>> >>> develop head and gcc 5.4.0). I have tested the vst4cs opcodes with the
>> >>> Pianoteq 6 VST plugin, which is available on Linux for license
>> >>> holders.
>> >>>
>> >>> I had to fix a couple of minor bugs in the Csound build system to get
>> >>> this to work, so be sure to do a fresh pull if you want to try this.
>> >>>
>> >>> Now that the Windows installer is building on AppVeyor and Csound
>> >>> seems to be running fine from the AppVeyor-built installer, I am
>> >>> planning to quit using Windows, and from now on to use exclusively
>> >>> Linux.
>> >>>
>> >>> 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
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> http://mysterybear.net
>> >> https://soundcloud.com/mysterybear
>> >> https://mysterybear.bandcamp.com
>> >>
>> >> http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz
>> >> 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
>
>
> 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

Hi,

this is great news!

I was trying to test it, but had no success setting the correct VST dir. What 
should I tell to cmake or where should I place my VST SDK?

Currently the location is:
$HOME/SDKs/VST3_SDK/

and the necessary header files are in:
/home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/

I tried cmake
cmake VSTSDK2X_INCLUDE_DIR="/home/tarmo/SDKs/VST3_SDK/" ../
and
cmake VST_SDK2_HOME="/home/tarmo/SDKs/VST3_SDK/" ../

but no success.


Maybe I am missing something very basic in the cmake options...

Thank you!
tarmo


On Tuesday, December 5, 2017 8:23:53 PM EET you wrote:
> I am pleased to report that both CsoundVST and the vst4cs opcodes
> build and run without problems on Linux (Ubuntu 16.04 with Csound
> develop head and gcc 5.4.0). I have tested the vst4cs opcodes with the
> Pianoteq 6 VST plugin, which is available on Linux for license
> holders.
> 
> I had to fix a couple of minor bugs in the Csound build system to get
> this to work, so be sure to do a fresh pull if you want to try this.
> 
> Now that the Windows installer is building on AppVeyor and Csound
> seems to be running fine from the AppVeyor-built installer, I am
> planning to quit using Windows, and from now on to use exclusively
> Linux.
> 
> 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

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 right,

I got a step further -

created Custom.cmake file in the source dir of Csound, added a line

set(VST_SDK2_HOME "/home/tarmo/SDKs/VST3_SDK/")

cmake found and building vst4cs opcodes was enabled.

Unfortunately I get error while building:

---

[ 59%] Building CXX object Opcodes/CMakeFiles/vst4cs.dir/vst4cs/src/vst4cs.cpp.o
In file included from /home/tarmo/SDKs/VST3_SDK/public.sdk/source/vst2.x/audioeffect.h:38:0,
                from /home/tarmo/SDKs/VST3_SDK/public.sdk/source/vst2.x/audioeffectx.h:38,
                from /home/tarmo/src/csound6-git/Opcodes/vst4cs/src/vsthost.h:55,
                from /home/tarmo/src/csound6-git/Opcodes/vst4cs/src/vst4cs.cpp:58:
/home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:158:32: error: expected ‘)’ before ‘*’ token
typedef VstIntPtr (VSTCALLBACK *audioMasterCallback) (AEffect* effect, VstInt32 opcode, VstInt32 index, VstIntPtr value, void* ptr, float opt);
                               ^
/home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:159:32: error: expected ‘)’ before ‘*’ token
typedef VstIntPtr (VSTCALLBACK *AEffectDispatcherProc) (AEffect* effect, VstInt32 opcode, VstInt32 index, VstIntPtr value, void* ptr, float opt);
                               ^
/home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:160:27: error: expected ‘)’ before ‘*’ token
typedef void (VSTCALLBACK *AEffectProcessProc) (AEffect* effect, float** inputs, float** outputs, VstInt32 sampleFrames);
                          ^
/home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:161:27: error: expected ‘)’ before ‘*’ token
typedef void (VSTCALLBACK *AEffectProcessDoubleProc) (AEffect* effect, double** inputs, double** outputs, VstInt32 sampleFrames);
                          ^
/home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:162:27: error: expected ‘)’ before ‘*’ token
typedef void (VSTCALLBACK *AEffectSetParameterProc) (AEffect* effect, VstInt32 index, float parameter);
                          ^
/home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:163:28: error: expected ‘)’ before ‘*’ token
typedef float (VSTCALLBACK *AEffectGetParameterProc) (AEffect* effect, VstInt32 index);
                           ^
/home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:182:2: error: ‘AEffectDispatcherProc’ does not name a type
 AEffectDispatcherProc dispatcher;

etc

---

Is there probably a mismatch with the SDKs used? The version of mine is 3.6.0, Cabbage builds fine with it. Unfortunatley I could not find VST-SDK2 any more from anywhere, Steinberg is mysterious sometimes.

What do you suggest?

Thanks!

tarmo

On Wednesday, December 6, 2017 10:54:37 AM EET Tarmo Johannes wrote:

> Hi,

>

> this is great news!

>

> I was trying to test it, but had no success setting the correct VST dir.

> What should I tell to cmake or where should I place my VST SDK?

>

> Currently the location is:

> $HOME/SDKs/VST3_SDK/

>

> and the necessary header files are in:

> /home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/

>

> I tried cmake

> cmake VSTSDK2X_INCLUDE_DIR="/home/tarmo/SDKs/VST3_SDK/" ../

> and

> cmake VST_SDK2_HOME="/home/tarmo/SDKs/VST3_SDK/" ../

>

> but no success.

>

>

> Maybe I am missing something very basic in the cmake options...

>

> Thank you!

> tarmo

>

> On Tuesday, December 5, 2017 8:23:53 PM EET you wrote:

> > I am pleased to report that both CsoundVST and the vst4cs opcodes

> > build and run without problems on Linux (Ubuntu 16.04 with Csound

> > develop head and gcc 5.4.0). I have tested the vst4cs opcodes with the

> > Pianoteq 6 VST plugin, which is available on Linux for license

> > holders.

> >

> > I had to fix a couple of minor bugs in the Csound build system to get

> > this to work, so be sure to do a fresh pull if you want to try this.

> >

> > Now that the Windows installer is building on AppVeyor and Csound

> > seems to be running fine from the AppVeyor-built installer, I am

> > planning to quit using Windows, and from now on to use exclusively

> > Linux.

> >

> > 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

You need to patch the VST SDK. But it's easy.

In the VST2_SDK, in aeffect.h, at about line 67, just replace __GNUC__
with __MINGW32__. This is an error by the VST SDK programmers. They
MEANT "GCC on Windows only" but they SAID "GCC on all operating
systems."
I will document all the steps in a README.md in the CsoundVST directory.

Best,
Mike

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


On Wed, Dec 6, 2017 at 4:17 AM, Tarmo Johannes  wrote:
> All right,
>
>
>
> I got a step further -
>
>
>
> created Custom.cmake file in the source dir of Csound, added a line
>
> set(VST_SDK2_HOME "/home/tarmo/SDKs/VST3_SDK/")
>
>
>
> cmake found and building vst4cs opcodes was enabled.
>
>
>
> Unfortunately I get error while building:
>
> ---
>
> [ 59%] Building CXX object
> Opcodes/CMakeFiles/vst4cs.dir/vst4cs/src/vst4cs.cpp.o
> In file included from
> /home/tarmo/SDKs/VST3_SDK/public.sdk/source/vst2.x/audioeffect.h:38:0,
>                 from
> /home/tarmo/SDKs/VST3_SDK/public.sdk/source/vst2.x/audioeffectx.h:38,
>                 from
> /home/tarmo/src/csound6-git/Opcodes/vst4cs/src/vsthost.h:55,
>                 from
> /home/tarmo/src/csound6-git/Opcodes/vst4cs/src/vst4cs.cpp:58:
> /home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:158:32: error:
> expected ‘)’ before ‘*’ token
> typedef VstIntPtr (VSTCALLBACK *audioMasterCallback) (AEffect* effect,
> VstInt32 opcode, VstInt32 index, VstIntPtr value, void* ptr, float opt);
>                                ^
> /home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:159:32: error:
> expected ‘)’ before ‘*’ token
> typedef VstIntPtr (VSTCALLBACK *AEffectDispatcherProc) (AEffect* effect,
> VstInt32 opcode, VstInt32 index, VstIntPtr value, void* ptr, float opt);
>                                ^
> /home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:160:27: error:
> expected ‘)’ before ‘*’ token
> typedef void (VSTCALLBACK *AEffectProcessProc) (AEffect* effect, float**
> inputs, float** outputs, VstInt32 sampleFrames);
>                           ^
> /home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:161:27: error:
> expected ‘)’ before ‘*’ token
> typedef void (VSTCALLBACK *AEffectProcessDoubleProc) (AEffect* effect,
> double** inputs, double** outputs, VstInt32 sampleFrames);
>                           ^
> /home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:162:27: error:
> expected ‘)’ before ‘*’ token
> typedef void (VSTCALLBACK *AEffectSetParameterProc) (AEffect* effect,
> VstInt32 index, float parameter);
>                           ^
> /home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:163:28: error:
> expected ‘)’ before ‘*’ token
> typedef float (VSTCALLBACK *AEffectGetParameterProc) (AEffect* effect,
> VstInt32 index);
>                            ^
> /home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:182:2: error:
> ‘AEffectDispatcherProc’ does not name a type
>  AEffectDispatcherProc dispatcher;
>
> etc
>
> ---
>
>
>
> Is there probably a mismatch with the SDKs used? The version of mine is
> 3.6.0, Cabbage builds fine with it. Unfortunatley I could not find VST-SDK2
> any more from anywhere, Steinberg is mysterious sometimes.
>
>
>
> What do you suggest?
>
>
>
> Thanks!
>
> tarmo
>
>
>
>
>
>
>
>
>
>
>
> On Wednesday, December 6, 2017 10:54:37 AM EET Tarmo Johannes wrote:
>
>> Hi,
>
>>
>
>> this is great news!
>
>>
>
>> I was trying to test it, but had no success setting the correct VST dir.
>
>> What should I tell to cmake or where should I place my VST SDK?
>
>>
>
>> Currently the location is:
>
>> $HOME/SDKs/VST3_SDK/
>
>>
>
>> and the necessary header files are in:
>
>> /home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/
>
>>
>
>> I tried cmake
>
>> cmake VSTSDK2X_INCLUDE_DIR="/home/tarmo/SDKs/VST3_SDK/" ../
>
>> and
>
>> cmake VST_SDK2_HOME="/home/tarmo/SDKs/VST3_SDK/" ../
>
>>
>
>> but no success.
>
>>
>
>>
>
>> Maybe I am missing something very basic in the cmake options...
>
>>
>
>> Thank you!
>
>> tarmo
>
>>
>
>> On Tuesday, December 5, 2017 8:23:53 PM EET you wrote:
>
>> > I am pleased to report that both CsoundVST and the vst4cs opcodes
>
>> > build and run without problems on Linux (Ubuntu 16.04 with Csound
>
>> > develop head and gcc 5.4.0). I have tested the vst4cs opcodes with the
>
>> > Pianoteq 6 VST plugin, which is available on Linux for license
>
>> > holders.
>
>> >
>
>> > I had to fix a couple of minor bugs in the Csound build system to get
>
>> > this to work, so be sure to do a fresh pull if you want to try this.
>
>> >
>
>> > Now that the Windows installer is building on AppVeyor and Csound
>
>> > seems to be running fine from the AppVeyor-built installer, I am
>
>> > planning to quit using Windows, and from now on to use exclusively
>
>> > Linux.
>
>> >
>
>> > 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
>
>
>
>
>
> 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

Thanks!

That did the trick! I was now able to build the opcode and tried vstinit 
example from manual.

I don't have any Linux VST plugins in this laptopn right now, I tried with a 
VST plugin generated with Cabbage but that caused segmentation fault. I will 
try out later with something else and learn closer about using VST plugins in 
Csound.

Also it is great that John got using LADSPA plugins working within Csound, and 
if in future we can hope for LV2 support, Linux people should be happy - 
sometimes it is so comfortable to add some functionality from already existing 
plugins.

greetings,
tarmo 

On Wednesday, December 6, 2017 3:33:16 PM EET you wrote:
> You need to patch the VST SDK. But it's easy.
> 
> In the VST2_SDK, in aeffect.h, at about line 67, just replace __GNUC__
> with __MINGW32__. This is an error by the VST SDK programmers. They
> MEANT "GCC on Windows only" but they SAID "GCC on all operating
> systems."
> I will document all the steps in a README.md in the CsoundVST directory.
> 
> Best,
> Mike
> 
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
> 
> On Wed, Dec 6, 2017 at 4:17 AM, Tarmo Johannes  wrote:
> > All right,
> > 
> > 
> > 
> > I got a step further -
> > 
> > 
> > 
> > created Custom.cmake file in the source dir of Csound, added a line
> > 
> > set(VST_SDK2_HOME "/home/tarmo/SDKs/VST3_SDK/")
> > 
> > 
> > 
> > cmake found and building vst4cs opcodes was enabled.
> > 
> > 
> > 
> > Unfortunately I get error while building:
> > 
> > ---
> > 
> > [ 59%] Building CXX object
> > Opcodes/CMakeFiles/vst4cs.dir/vst4cs/src/vst4cs.cpp.o
> > In file included from
> > /home/tarmo/SDKs/VST3_SDK/public.sdk/source/vst2.x/audioeffect.h:38:0,
> > 
> >                 from
> > 
> > /home/tarmo/SDKs/VST3_SDK/public.sdk/source/vst2.x/audioeffectx.h:38,
> > 
> >                 from
> > 
> > /home/tarmo/src/csound6-git/Opcodes/vst4cs/src/vsthost.h:55,
> > 
> >                 from
> > 
> > /home/tarmo/src/csound6-git/Opcodes/vst4cs/src/vst4cs.cpp:58:
> > /home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:158:32: error:
> > expected ‘)’ before ‘*’ token
> > typedef VstIntPtr (VSTCALLBACK *audioMasterCallback) (AEffect* effect,
> > VstInt32 opcode, VstInt32 index, VstIntPtr value, void* ptr, float opt);
> > 
> >                                ^
> > 
> > /home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:159:32: error:
> > expected ‘)’ before ‘*’ token
> > typedef VstIntPtr (VSTCALLBACK *AEffectDispatcherProc) (AEffect* effect,
> > VstInt32 opcode, VstInt32 index, VstIntPtr value, void* ptr, float opt);
> > 
> >                                ^
> > 
> > /home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:160:27: error:
> > expected ‘)’ before ‘*’ token
> > typedef void (VSTCALLBACK *AEffectProcessProc) (AEffect* effect, float**
> > inputs, float** outputs, VstInt32 sampleFrames);
> > 
> >                           ^
> > 
> > /home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:161:27: error:
> > expected ‘)’ before ‘*’ token
> > typedef void (VSTCALLBACK *AEffectProcessDoubleProc) (AEffect* effect,
> > double** inputs, double** outputs, VstInt32 sampleFrames);
> > 
> >                           ^
> > 
> > /home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:162:27: error:
> > expected ‘)’ before ‘*’ token
> > typedef void (VSTCALLBACK *AEffectSetParameterProc) (AEffect* effect,
> > VstInt32 index, float parameter);
> > 
> >                           ^
> > 
> > /home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:163:28: error:
> > expected ‘)’ before ‘*’ token
> > typedef float (VSTCALLBACK *AEffectGetParameterProc) (AEffect* effect,
> > VstInt32 index);
> > 
> >                            ^
> > 
> > /home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/aeffect.h:182:2: error:
> > ‘AEffectDispatcherProc’ does not name a type
> > 
> >  AEffectDispatcherProc dispatcher;
> > 
> > etc
> > 
> > ---
> > 
> > 
> > 
> > Is there probably a mismatch with the SDKs used? The version of mine is
> > 3.6.0, Cabbage builds fine with it. Unfortunatley I could not find
> > VST-SDK2
> > any more from anywhere, Steinberg is mysterious sometimes.
> > 
> > 
> > 
> > What do you suggest?
> > 
> > 
> > 
> > Thanks!
> > 
> > tarmo
> > 
> > On Wednesday, December 6, 2017 10:54:37 AM EET Tarmo Johannes wrote:
> >> Hi,
> >> 
> >> 
> >> 
> >> this is great news!
> >> 
> >> 
> >> 
> >> I was trying to test it, but had no success setting the correct VST dir.
> >> 
> >> What should I tell to cmake or where should I place my VST SDK?
> >> 
> >> 
> >> 
> >> Currently the location is:
> >> 
> >> $HOME/SDKs/VST3_SDK/
> >> 
> >> 
> >> 
> >> and the necessary header files are in:
> >> 
> >> /home/tarmo/SDKs/VST3_SDK/pluginterfaces/vst2.x/
> >> 
> >> 
> >> 
> >> I tried cmake
> >> 
> >> cmake VSTSDK2X_INCLUDE_DIR="/home/tarmo/SDKs/VST3_SDK/" ../
> >> 
> >> and
> >> 
> >> cmake VST_SDK2_HOME="/home/tarmo/SDKs/VST3_SDK/" ../
> >> 
> >> 
> >> 
> >> but no success.
> >> 
> >> 
> >> 
> >> 
> >> 
> >> Maybe I am missing something very basic in the cmake options...
> >> 
> >> 
> >> 
> >> Thank you!
> >> 
> >> tarmo
> >> 
> >> On Tuesday, December 5, 2017 8:23:53 PM EET you wrote:
> >> > I am pleased to report that both CsoundVST and the vst4cs opcodes
> >> > 
> >> > build and run without problems on Linux (Ubuntu 16.04 with Csound
> >> > 
> >> > develop head and gcc 5.4.0). I have tested the vst4cs opcodes with the
> >> > 
> >> > Pianoteq 6 VST plugin, which is available on Linux for license
> >> > 
> >> > holders.
> >> > 
> >> > 
> >> > 
> >> > I had to fix a couple of minor bugs in the Csound build system to get
> >> > 
> >> > this to work, so be sure to do a fresh pull if you want to try this.
> >> > 
> >> > 
> >> > 
> >> > Now that the Windows installer is building on AppVeyor and Csound
> >> > 
> >> > seems to be running fine from the AppVeyor-built installer, I am
> >> > 
> >> > planning to quit using Windows, and from now on to use exclusively
> >> > 
> >> > Linux.
> >> > 
> >> > 
> >> > 
> >> > 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
> > 
> > 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 Tarmo,


On 12/06/2017 09:36 AM, Tarmo Johannes wrote:
> I don't have any Linux VST plugins in this laptopn right now...
>

Just in case you don't already know about this page:

http://linux-sound.org/linux-vst-plugins.html

Best,

dp

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