Thanks for your information.

I am the author of CsoundVST. I have Cubase 4.0.2 and the development version of CsoundVST installed on my notebook. It is installed from the development version of the Windows installer (double precision samples). 

I have examined the directions in the Csound 5.08 manual. These directions were indeed out of date. I have just now corrected them in the manual sources in CVS, and I have attached the corrected page to this email. I also summarize the most relevant changes below.

Where the manual used to read:

Use the Devices menu, Plug-In Information dialog, VST Plug-Ins tab, Shared VST Plug-ins Folder text field to add your csound5 directory to Cubase's plugin path. You can have multiple directories separated by semicolons.

It now reads:

Use the Devices menu, Plug-In Information dialog, VST Plug-Ins tab, Shared VST Plug-ins Folder text field to add your csound/bin directory to Cubase's plugin path. You can have multiple directories separated by semicolons.

Wherever the manual used to mention _CsoundAC, it should now be simply CsoundVST.

The manual used to mention a "Classic" check box in the CsoundVST GUI. This check box is no longer used, and has been removed.

The example .csd file is now csound/examples/CsoundVST.csd.

There is a new bug in CsoundVST that causes a loud annoying buzz when an instance of CsoundVST is first created. You can shut off the buzz by editing the instrument and clicking on the run button to deactivate it. You then need to load a valid .csd file and reactivate the instrument. After that things should be fine. I will fix this bug as soon as possible, and upload the new DLL to Steven Yi's site.

I just now confirmed that my installation of CsoundVST works fine (except for the initial buzz). If you follow the corrected procedures and CsoundVST still does not work...

There must still be some difference between your setup and mine. The problem may very well relate to the Microsoft runtime libraries. The way programs link with and use the Microsoft runtime libraries has changed with current versions of the Microsoft compiler. The version of Csound in the Windows installers is built with MinGW/MSYS, but the PortAudio library and some other libraries used by Csound and installed with Csound are built with Microsoft Visual Studio 2008 Express Edition. Therefore, Csound indirectly requires current versions of the Microsoft runtime libraries. Csound's Windows installers put these required Microsoft runtime libraries into:

    Csound\bin\Microsoft.VC90.CRT

Possibilities:

-- Song files saved with data from earlier versions of CsoundVST may no longer work. You may need to create a new song.

-- CsoundVST is no longer included in the SourceForge Windows installers, because we decided to conform to SourceForge policies regarding non-open source software. Where did you get your CsoundVST.dll? If is is left over from an earlier installer which did contain CsoundVST, that seems likely to cause a problem. Or did you download CsoundVT.dll from Steven Yi's web site? If not, try downloading the current version from http://www.kunstmusik.com/gogins/CsoundVST.dll and trying it. 

-- Or did you build CsoundVST from sources? If so, did you build it with MinGW/MSYS or with Microsoft Visual Studio? For things to work properly, perhaps CsoundVST and Csound need to be built with the same compiler (I'm not sure about this).

-- You may be using the double-precision sample version of CsoundVST with the float sample version of Csound. This would definitely cause a problem. If that is the case, uninstall the float version of Csound and install the double version instead.

-- I, of course, have Microsoft Visual Studio 2008 Express Edition installed, and you may not. Installing MSVS also installs the required Microsoft runtime libraries in the WINDOWS/WinSxS directory.

-- I have the Csound/bin directory in my Windows PATH environment variable. Perhaps you do not. This may be required for proper loading of the Microsoft runtime libraries.

-- Perhaps Cubase 4.1 loads VST plugins differently from Cubsase 4.0. I will upgrade to 4.1 as soon as I can to try to reproduce this problem, but I can't do it this weekend, since my Cubase DVD is at home but I am up on my farm.

You could download and run the "Microsoft Visual C++ 2005 Redistributable Package (x86)" for the Microsoft runtime libraries to see if that clears up the problem. You can get it from:

     http://www.microsoft.com/downloads/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b62a191ee&displaylang=en

You could also try temporarily removing the PortAudio DLL and perhaps other DLLs from the Csound/bin directory in order to keep CsoundVST from indirectly loading the Microsoft runtime libraries.

Hope this helps. I will try to upgrade Cubase when I get home next week. Please let me know what happens.

Regards,
Mike

-----Original Message-----
>From: Jim Aikin 
>Sent: May 23, 2008 11:42 PM
>To: csound@lists.bath.ac.uk
>Subject: [Csnd]  Using CsoundVST in Cubase
>
>
>The manual for 5.08 includes some out-of-date instructions for using
>CsoundVST with Cubase SX. I attempted to do the same procedure with Cubase
>4.1.3 for Windows, namely, adding the Csound directory to the Plug-In
>Information box under the VST 2.x Plug-Ins button, which is where the
>plug-in directories are listed. On quitting and relaunching Cubase, I get
>the following alert box:
>
>Microsoft Visual C++ Runtime Library
>Runtime Error!
>Program: F:\Program Files\Steinberg\Cubase4.exe
>R6034
>An application has made an attempt to load the C runtime library
>incorrectly. Please contact the application's support team for more
>information.
>
>I've never had this alert box before -- and indeed, when I remove the Csound
>directory from the list of paths and restart again, Cubase launches without
>trouble. So it's evident that the documented procedure for gaining access to
>CsoundVST within Cubase is failing.
>
>Can anyone suggest how I might fix the problem? Thanks!
>
>--Jim Aikin
>
>P.S.: I'm working on a new magazine article on Csound, and I'd really like
>to be able to say in the article that I got CsoundVST running. (I tried a
>couple of years ago, and failed.)
>-- 
>View this message in context: http://www.nabble.com/Using-CsoundVST-in-Cubase-tp17444141p17444141.html
>Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
>Send bugs reports to this list.
>To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thanks for the quick response, Mike. I'll try a few more things tonight and
let you know the results.

> There must still be some difference between your setup and mine.

There was also a big slug of user error. I had two versions of Csound,
downloaded a year apart and lodged on different drives. When I point Cubase
at the one that has the Microsoft.VC90.CRT folder, the alert box doesn't
appear. That much I had time to test this morning.

> -- CsoundVST is no longer included in the SourceForge Windows installers,
> because we decided to
> conform to SourceForge policies regarding non-open source software. Where
> did you get your
> CsoundVST.dll? If is is left over from an earlier installer which did
> contain CsoundVST, that seems
> likely to cause a problem. Or did you download CsoundVT.dll from Steven
> Yi's web site? If not, try
> downloading the current version from
> http://www.kunstmusik.com/gogins/CsoundVST.dll and trying
> it. 

Just as a suggestion, you might want to add that information to the manual.
As it stands, I believe the manual just launches into an explanation of how
to get CsoundVST running, without mentioning that you'll need to do
 with the .dll after downloading it. Such as, perhaps, tucking it
away in the Steinberg VSTplugins folder? I'm going to try that, anyhow.

> -- Or did you build CsoundVST from sources?

That would be well beyond my comfort zone.

> -- You may be using the double-precision sample version of CsoundVST with
> the float sample
> version of Csound. This would definitely cause a problem. If that is the
> case, uninstall the float
> version of Csound and install the double version instead.

This raises an interesting question, namely, how would I be able to tell
which version I'm using? I launched the Csound5GUI last night and had a look
for precisely this information, and nowhere could I find any indication of
which version I was running. Is that information visible at any point in the
program? If so, where would I find it?

--JA

-- 
View this message in context: http://www.nabble.com/Using-CsoundVST-in-Cubase-tp17444141p17449434.html
Sent from the Csound - General mailing list archive at Nabble.com.

>      VST Plugin
>      The following instructions are for Cubase 4.0. You would follow
>      roughly similar procedures in other hosts. 
>      Use the Devices menu, Plug-In
>        Information dialog, VST Plug-Ins tab,
>      VST 2.x Plug-in Paths dialog, Add button to add your
>      csound/bin directory to Cubase's plugin path. You
>      can have multiple directories separated by semicolons. Then select
> the CsoundVST path and 
>      click on the Set as Shared Folder button. 
>      Quit Cubase, and start it again. 
>      Use the File menu, New
>        Project dialog to create a new song. 
>      Use the Project menu, Add
>        Track submenu, to add a new Instrument track. 
>      In the Add Instrument Track dialog, 
>      click on the No VST Instrument label and select 
>      CsoundVST. 

There is no such label -- not in my installation of 4.1.3. Possibly it
depends on how I have Cubase set up, or possibly Steinberg changed
something. So I'm unable to follow the rest of the instructions.

I've put CsoundVST.dll in the Steinberg VSTplugins folder and restarted
Cubase. CsoundVST does not show up in the pop-up list of instruments in the
VST Instruments window.

--JA

-- 
View this message in context: http://www.nabble.com/Using-CsoundVST-in-Cubase-tp17444141p17449620.html
Sent from the Csound - General mailing list archive at Nabble.com.