Hello, everyone

I wanted to reach out to see if my recent troubles sound familiar to anyone.
I'm running Windows XP and I can't get my exported Cabbage VSTs to show in
Cubase. Other third party VSTs work fine in the same directory I export my
Cabbage VSTs to (csd and dll files). I've tried exporting with older
versions of Cabbage as well as the latest release and the end result is the
same. I even tried Iain McCurdy's examples (in case my code was causing the
issue) to no avail. Until recently I've just been using Cabbage as a
stand-alone host. Rory was kind enough to offer some suggestions, but
nothing has worked so far. Seeing as the Cabbage site's down at the moment I
thought I might post my issue here. I know on such an old OS it's a long
shot, but any recommendations would be greatly appreciated.



--
View this message in context: http://csound.1045644.n5.nabble.com/Cabbage-Question-tp5743835.html
Sent from the Csound - General mailing list archive at Nabble.com.

------------------------------------------------------------------------------
_______________________________________________
Csound-users mailing list
Csound-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-users
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Unfortunately I had a lot going on this past month, but I did finally get
around to installing Reaper to see if my Cabbage plugins would work. No
luck. The plugins do not show up when Reaper is up and running, which is
strange because when I first open Reaper and it initially scans for plugins
mine pop up, but once Reaper's running they are nowhere to be found. Other
third-party plugins open fine. The dll file and the associated csd file are
in the same directory as my other plugins. I'm clueless as to what to try
next. I would appreciate any help. Being able to run multiple Cabbage
plugins in a DAW would greatly simplify things for me.



--
View this message in context: http://csound.1045644.n5.nabble.com/Cabbage-Question-tp5743835p5744768.html
Sent from the Csound - General mailing list archive at Nabble.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

> The plugins do not show up when Reaper is up and running, which is
> strange because when I first open Reaper and it initially scans for plugins
> mine pop up, but once Reaper's running they are nowhere to be found.

Could it be a problem with your choice of 64/32 bit version of Reaper?

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

Just a note, Cabbage plugs work well both with 32 and 64 bit Reaper.  The Reaper 32 bit bridge works fine to use 32 bit plugs under 64 bit.

Rory,

First off, thanks again for your help. I downloaded and installed the latest
Cabbage release from the link you provided and restarted my computer. I ran
the new Cabbage and exported my plugin to the same directory as my other
third-party plugins. I also made sure Cubase and Reaper were scanning the
right directory. I'm still not able to locate my plugins in either Reaper or
Cubase. The stand-alone host works fine. When I open Reaper or Cubase and
they first scan for plugins before running, my Cabbage plugins are listed
off along with my other plugins, but once the DAW is running I can't find
them listed. Cabbage32 is added to my Path. I do not have an OPCODE6DIR
variable, but I do have an OPCODE6DIR64 variable that is set to Cabbage32. I
also have an OPCODEDIR64 variable that is set to csound\plugins64. I also
have Csound 5.19 installed (I recently rolled back from a newer version
because the CsoundQt version that installed with it wouldn't run). I hope
this information helps.



--
View this message in context: http://csound.1045644.n5.nabble.com/Cabbage-Question-tp5743835p5744789.html
Sent from the Csound - General mailing list archive at Nabble.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

Hi Marshall,

Not sure if this helps. but youi can try.
- Rename the Csound 5.19 directory to make sure it does not interfere
with the Cabbage plugins (when renamed it will not be in the system
PATH)
- change the score of the csd for a plugins to : f0 600, with no other
events in it (assuming you don't have ftables in the score). When the
VST host scans for plugins, it will test run them (initialize and run
one audio signal block, as far as I understand). If you have no events
in the score there is less chance of anything going wrong in the
scan-and-test stage. If you get it to wrok this way, then edit the
score back to what you need it to be. The plugin will not be scanned
again until you explicitly asks the host to do so. Obviously, this is
not a good solution, but it is an ok step for locating the problem.

Oeyvind

2015-10-29 6:58 GMT+01:00 Marshall West :
> Rory,
>
> First off, thanks again for your help. I downloaded and installed the latest
> Cabbage release from the link you provided and restarted my computer. I ran
> the new Cabbage and exported my plugin to the same directory as my other
> third-party plugins. I also made sure Cubase and Reaper were scanning the
> right directory. I'm still not able to locate my plugins in either Reaper or
> Cubase. The stand-alone host works fine. When I open Reaper or Cubase and
> they first scan for plugins before running, my Cabbage plugins are listed
> off along with my other plugins, but once the DAW is running I can't find
> them listed. Cabbage32 is added to my Path. I do not have an OPCODE6DIR
> variable, but I do have an OPCODE6DIR64 variable that is set to Cabbage32. I
> also have an OPCODEDIR64 variable that is set to csound\plugins64. I also
> have Csound 5.19 installed (I recently rolled back from a newer version
> because the CsoundQt version that installed with it wouldn't run). I hope
> this information helps.
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Cabbage-Question-tp5743835p5744789.html
> Sent from the Csound - General mailing list archive at Nabble.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

Can you change opcde6dir64 to simply OPCODE6DIR?

Okay, I feel like we're getting somewhere. Rory, I renamed OPCODE6DIR64 to
OPCODE6DIR. After rebooting I opened Reaper, and as Reaper was scanning VSTs
it started displaying error messages every time it got to one of my Cabbage
plugins. The message was "Unable to open file libFLAC-8.dll." I remember
this message being displayed at least once before upon starting Cubase, but
I wasn't able to discern then the connection to my plugins. But I do know
I've gotten this message before changing any environment variables. Hope
this helps. I also tried Oeyvind's suggestions to no avail.



--
View this message in context: http://csound.1045644.n5.nabble.com/Cabbage-Question-tp5743835p5744801.html
Sent from the Csound - General mailing list archive at Nabble.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 am not sure what it means but I have discovered something odd about Csound and libsndfile. I am running the develop head on Windows 8.

I used to run Csound from the build directory in order to test new features and debug. Then this quit working because I would get an error to the effect that libFLAC-8.dll couldn't be loaded. I tried many ways to debug this but nothing worked until now.

I ran the dependency walker on Csound in my build directory and saw that libsndfile reported a missing dependency on libFLAC-8.dll (which I do not have; indeed, I suspect it is statically linked to libsndfile). When I have run the dependency walker on Csound in the installation directory, this missing dependency is not reported and indeed libsndfile doesn't even report a dependency on libFLAC-8.dll.

So I copied libsndfile into my build directory and the problem went away.

Some of you may recall that I reported some months ago problems running CsoundVST in Reaper. I copied libsndfile into the Reaper bin directory and CsoundVST started working.