CsoundVST, which enables Csound to be used as a VST instrument or
effect in VST-enabled digital audio workstations (almost all of them),
and the vst4cs opcodes, which enable regular Csound to host VST
instrument and effect plugins, are now by default a part of the Visual
Studio build of Csound on AppVeyor, and are included by default in the
Windows installer artifact produced on AppVeyor.

To download this installer, go to
https://ci.appveyor.com/project/csound/csound/branch/develop, click on
"ARTIFACTS," and click on the file link for "Csound installer." This
is for Windows 8 or later with 64 bit CPU architecture.  The installer
includes almost all features of the earlier installer built with
mingw64, but does not contain the Csound Reference Manual, the Csound
API Documentation, LuaJIT and the LuaJIT opcodes, or a local copy of
NW.js.

I have made this change after carefully reviewing our agreements such
as the Csound LGPL v2.1 license, the GPL FAQ, the Steinberg VST SDK
licenses, and the terms of use of GitHub and AppVeyor, and the code
bases and licenses used by a number of open source projects that use
the VST SDK. A summary of my research can be found in the Csound
GitHub repository at
https://github.com/csound/csound/blob/develop/Opcodes/vst4cs/licensing_considerations_for_csoundvst_and_vst4cs.md

In addition the AppVeyor build, which happens automatically for every
commit to the Csound Git repository, documentation at
https://github.com/csound/csound/blob/develop/msvc/README.md shows how
to perform the AppVeyor build locally to produce the same Visual
Studio build of Csound with all the same features. The only
requirement is that you build on Windows 8 or later with Visual Studio
2015 or later.

Such a local build is advised for Csound developers working on
Windows, for it produces a Csound.sln solution that can be loaded into
Visual Studio for fast incremental builds and excellent debugging
facilities.

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

I think the latest build is currently in the process of being built,
hence no artifacts yet.  You can look at the build history:

https://ci.appveyor.com/project/csound/csound/history

And look for one that is green. For example:

https://ci.appveyor.com/project/csound/csound/build/1.0.617/artifacts



On Mon, Sep 25, 2017 at 10:13 AM, Anders Genell  wrote:
> This is great!!
> Just a few comments/questions:
>
> 1. When following the appveyor link you posted, there is nothin under
> artifacts.
> Message says "The build job does not contain any artifacts."
>
> 2. As appveyor builds every git commit, could a link to a "latest build" exe
> installer be included on the csound.github.io site? It would be a nice way
> to benefit from fixes and feature additions between releases without having
> to build locally.
>
> Regards,
> Anders
>
>
> On Mon, Sep 25, 2017 at 4:04 PM, Michael Gogins 
> wrote:
>>
>> CsoundVST, which enables Csound to be used as a VST instrument or
>> effect in VST-enabled digital audio workstations (almost all of them),
>> and the vst4cs opcodes, which enable regular Csound to host VST
>> instrument and effect plugins, are now by default a part of the Visual
>> Studio build of Csound on AppVeyor, and are included by default in the
>> Windows installer artifact produced on AppVeyor.
>>
>> To download this installer, go to
>> https://ci.appveyor.com/project/csound/csound/branch/develop, click on
>> "ARTIFACTS," and click on the file link for "Csound installer." This
>> is for Windows 8 or later with 64 bit CPU architecture.  The installer
>> includes almost all features of the earlier installer built with
>> mingw64, but does not contain the Csound Reference Manual, the Csound
>> API Documentation, LuaJIT and the LuaJIT opcodes, or a local copy of
>> NW.js.
>>
>> I have made this change after carefully reviewing our agreements such
>> as the Csound LGPL v2.1 license, the GPL FAQ, the Steinberg VST SDK
>> licenses, and the terms of use of GitHub and AppVeyor, and the code
>> bases and licenses used by a number of open source projects that use
>> the VST SDK. A summary of my research can be found in the Csound
>> GitHub repository at
>>
>> https://github.com/csound/csound/blob/develop/Opcodes/vst4cs/licensing_considerations_for_csoundvst_and_vst4cs.md
>>
>> In addition the AppVeyor build, which happens automatically for every
>> commit to the Csound Git repository, documentation at
>> https://github.com/csound/csound/blob/develop/msvc/README.md shows how
>> to perform the AppVeyor build locally to produce the same Visual
>> Studio build of Csound with all the same features. The only
>> requirement is that you build on Windows 8 or later with Visual Studio
>> 2015 or later.
>>
>> Such a local build is advised for Csound developers working on
>> Windows, for it produces a Csound.sln solution that can be loaded into
>> Visual Studio for fast incremental builds and excellent debugging
>> facilities.
>>
>> Regards,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>

No idea, maybe Appveyor docs have info. (About to fly, can't look up)

I did want to say this build does need some thorough testing. At
least, for my local build, since there is no portmidi driver, running
with -+rtmidi=mme for MIDI causes a crash.

On Mon, Sep 25, 2017 at 10:18 AM, Anders Genell  wrote:
> Thanks!
> Is there a way to have a generic link to the latest finished build?
>
> Regards,
> Anders
>
> On Mon, Sep 25, 2017 at 4:16 PM, Steven Yi  wrote:
>>
>> I think the latest build is currently in the process of being built,
>> hence no artifacts yet.  You can look at the build history:
>>
>> https://ci.appveyor.com/project/csound/csound/history
>>
>> And look for one that is green. For example:
>>
>> https://ci.appveyor.com/project/csound/csound/build/1.0.617/artifacts
>>
>>
>>
>> On Mon, Sep 25, 2017 at 10:13 AM, Anders Genell 
>> wrote:
>> > This is great!!
>> > Just a few comments/questions:
>> >
>> > 1. When following the appveyor link you posted, there is nothin under
>> > artifacts.
>> > Message says "The build job does not contain any artifacts."
>> >
>> > 2. As appveyor builds every git commit, could a link to a "latest build"
>> > exe
>> > installer be included on the csound.github.io site? It would be a nice
>> > way
>> > to benefit from fixes and feature additions between releases without
>> > having
>> > to build locally.
>> >
>> > Regards,
>> > Anders
>> >
>> >
>> > On Mon, Sep 25, 2017 at 4:04 PM, Michael Gogins
>> > 
>> > wrote:
>> >>
>> >> CsoundVST, which enables Csound to be used as a VST instrument or
>> >> effect in VST-enabled digital audio workstations (almost all of them),
>> >> and the vst4cs opcodes, which enable regular Csound to host VST
>> >> instrument and effect plugins, are now by default a part of the Visual
>> >> Studio build of Csound on AppVeyor, and are included by default in the
>> >> Windows installer artifact produced on AppVeyor.
>> >>
>> >> To download this installer, go to
>> >> https://ci.appveyor.com/project/csound/csound/branch/develop, click on
>> >> "ARTIFACTS," and click on the file link for "Csound installer." This
>> >> is for Windows 8 or later with 64 bit CPU architecture.  The installer
>> >> includes almost all features of the earlier installer built with
>> >> mingw64, but does not contain the Csound Reference Manual, the Csound
>> >> API Documentation, LuaJIT and the LuaJIT opcodes, or a local copy of
>> >> NW.js.
>> >>
>> >> I have made this change after carefully reviewing our agreements such
>> >> as the Csound LGPL v2.1 license, the GPL FAQ, the Steinberg VST SDK
>> >> licenses, and the terms of use of GitHub and AppVeyor, and the code
>> >> bases and licenses used by a number of open source projects that use
>> >> the VST SDK. A summary of my research can be found in the Csound
>> >> GitHub repository at
>> >>
>> >>
>> >> https://github.com/csound/csound/blob/develop/Opcodes/vst4cs/licensing_considerations_for_csoundvst_and_vst4cs.md
>> >>
>> >> In addition the AppVeyor build, which happens automatically for every
>> >> commit to the Csound Git repository, documentation at
>> >> https://github.com/csound/csound/blob/develop/msvc/README.md shows how
>> >> to perform the AppVeyor build locally to produce the same Visual
>> >> Studio build of Csound with all the same features. The only
>> >> requirement is that you build on Windows 8 or later with Visual Studio
>> >> 2015 or later.
>> >>
>> >> Such a local build is advised for Csound developers working on
>> >> Windows, for it produces a Csound.sln solution that can be loaded into
>> >> Visual Studio for fast incremental builds and excellent debugging
>> >> facilities.
>> >>
>> >> Regards,
>> >> Mike
>> >>
>> >> -----------------------------------------------------
>> >> Michael Gogins
>> >> Irreducible Productions
>> >> http://michaelgogins.tumblr.com
>> >> Michael dot Gogins at gmail dot com
>> >
>> >
>

Hi Michael,

How refreshing... thank for all this work that help us (the Windowzers)...

Regards,

Marc

-----Message d'origine-----
De : A discussion list for users of Csound [mailto:CSOUND@LISTSERV.HEANET.IE] De la part de Michael Gogins
Envoyé : lundi 25 septembre 2017 10:04
À : CSOUND@LISTSERV.HEANET.IE
Objet : [Csnd] VST Features are now the default in the AppVeyor build and Windows installer

CsoundVST, which enables Csound to be used as a VST instrument or effect in VST-enabled digital audio workstations (almost all of them), and the vst4cs opcodes, which enable regular Csound to host VST instrument and effect plugins, are now by default a part of the Visual Studio build of Csound on AppVeyor, and are included by default in the Windows installer artifact produced on AppVeyor.

To download this installer, go to
https://ci.appveyor.com/project/csound/csound/branch/develop, click on "ARTIFACTS," and click on the file link for "Csound installer." This is for Windows 8 or later with 64 bit CPU architecture.  The installer includes almost all features of the earlier installer built with mingw64, but does not contain the Csound Reference Manual, the Csound API Documentation, LuaJIT and the LuaJIT opcodes, or a local copy of NW.js.

I have made this change after carefully reviewing our agreements such as the Csound LGPL v2.1 license, the GPL FAQ, the Steinberg VST SDK licenses, and the terms of use of GitHub and AppVeyor, and the code bases and licenses used by a number of open source projects that use the VST SDK. A summary of my research can be found in the Csound GitHub repository at https://github.com/csound/csound/blob/develop/Opcodes/vst4cs/licensing_considerations_for_csoundvst_and_vst4cs.md

In addition the AppVeyor build, which happens automatically for every commit to the Csound Git repository, documentation at https://github.com/csound/csound/blob/develop/msvc/README.md shows how to perform the AppVeyor build locally to produce the same Visual Studio build of Csound with all the same features. The only requirement is that you build on Windows 8 or later with Visual Studio
2015 or later.

Such a local build is advised for Csound developers working on Windows, for it produces a Csound.sln solution that can be loaded into Visual Studio for fast incremental builds and excellent debugging facilities.

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

I downloaded this and installed.  I get:

	Csound version 6.09.1 (double samples) Sep 25 2017

I look in Program Files\Csound6_x64\bin and see CsoundVst.dll.
So I add that directory to the VST path in Reaper and re-scan
for plugins, but nothing related to csound shows up.  Am I doing
it right?

Thanks,

Tobiah


> And look for one that is green. For example:
> 

The MinGW build installs to Csound6_x64 and the Visual Studio/Appveyor
build installs to Csound_x64. Make sure that your Reaper configuration
is picking up the right directory. It has to be Csound_x64\bin for the
AppVeyor build. You might have a conflict.

It works fine for me with Reaper 5.40 and a recent AppVeyor build.

Regards,
Mike

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


On Sat, Sep 30, 2017 at 3:04 PM, Michael Gogins
 wrote:
> I will check it out in Reaper, thanks.
>
> Regards,
> Mike
>
> On Sep 30, 2017 12:36 PM, "Tobiah"  wrote:
>>
>> I downloaded this and installed.  I get:
>>
>>         Csound version 6.09.1 (double samples) Sep 25 2017
>>
>> I look in Program Files\Csound6_x64\bin and see CsoundVst.dll.
>> So I add that directory to the VST path in Reaper and re-scan
>> for plugins, but nothing related to csound shows up.  Am I doing
>> it right?
>>
>> Thanks,
>>
>> Tobiah
>>
>>
>>> And look for one that is green. For example:
>>>

I uninstalled all previous Csound, and installed
Setup_Csound_x64_6.09.2beta4-vst.exe.  I see CsoundVst.dll
in C:\Program Files\Csound_x64.  Add that to the Reaper
VST path.  Clear cache and rescan.  Nothing Csound available.

Now, I'm using 64 bit Reaper, is that ok?

Thanks,


Tobiah



On 10/3/2017 8:44 AM, Michael Gogins wrote:
> The MinGW build installs to Csound6_x64 and the Visual Studio/Appveyor
> build installs to Csound_x64. Make sure that your Reaper configuration
> is picking up the right directory. It has to be Csound_x64\bin for the
> AppVeyor build. You might have a conflict.
> 
> It works fine for me with Reaper 5.40 and a recent AppVeyor build.
> 
> Regards,
> Mike
> 
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
> 
> 
> On Sat, Sep 30, 2017 at 3:04 PM, Michael Gogins
>  wrote:
>> I will check it out in Reaper, thanks.
>>
>> Regards,
>> Mike
>>
>> On Sep 30, 2017 12:36 PM, "Tobiah"  wrote:
>>>
>>> I downloaded this and installed.  I get:
>>>
>>>          Csound version 6.09.1 (double samples) Sep 25 2017
>>>
>>> I look in Program Files\Csound6_x64\bin and see CsoundVst.dll.
>>> So I add that directory to the VST path in Reaper and re-scan
>>> for plugins, but nothing related to csound shows up.  Am I doing
>>> it right?
>>>
>>> Thanks,
>>>
>>> Tobiah
>>>
>>>
>>>> And look for one that is green. For example:
>>>>