cabbage native linux renoise

16 views
Skip to first unread message

Nil Geisweiller

unread,
Oct 6, 2012, 8:18:58 AM10/6/12
to cabbag...@googlegroups.com
Hi,

first of all, many thanks for this AWESOME project.

I compiled revision r230 under Linux, the standalone synth runs, but I
can't get it to run under Renoise (I don't have another native linux
VST host to test).

I can load the plugin but then when I ask to display its interface I
get a black window (with Cabbage written in the lower right corner),
see the snapshot attached.

Is that normal?

Anything I can do to help debug?

Also, would you be willing to move development under github, it's just
so much easier to involve others (no need to grant write access to the
repo), github offers "Pull Requests", that is the outsiders commit
their changes and it's up to the official maintainer(s) to accept
them.

Nil
cabbage_renoise_snapshot.png

Rory Walsh

unread,
Oct 6, 2012, 8:33:44 AM10/6/12
to cabbag...@googlegroups.com
Hi Nil. The latest source I have up there should be Ok, there was
problems with earlier version. As of early last week I think the
current source is up there. It has the build file that builds all the
binaries? If you start Renoise from the command line and then
instantiate your plugin it should tell you what's happening. You
didn't by any change move the plugin .so to a new directory and forget
to move the corresponding csd file as well? It looks like the Cabbage
plugin can't find the csd file?

I do have intentions of moving to github but I'm swamped with other
stuff right now. Also, would you mind registering on the forum at
www.thecabbagefoundation.org, I'm hoping to keep all Cabbage related
correspondence there so others can search the archives for answers to
similar questions that might have!

Btw, what version of Linux are you using?

Nil Geisweiller

unread,
Oct 6, 2012, 11:27:24 AM10/6/12
to cabbag...@googlegroups.com
Hi Rory,

On Sat, Oct 6, 2012 at 2:33 PM, Rory Walsh <rory...@ear.ie> wrote:
> Hi Nil. The latest source I have up there should be Ok, there was
> problems with earlier version. As of early last week I think the
> current source is up there. It has the build file that builds all the
> binaries? If you start Renoise from the command line and then
> instantiate your plugin it should tell you what's happening. You
> didn't by any change move the plugin .so to a new directory and forget
> to move the corresponding csd file as well? It looks like the Cabbage
> plugin can't find the csd file?

I started Renoise on the cmd line and set my VST_PATH directly where
the pluggins were built, but it does work, it indeed doesn't find
CabbagePluginSynth.csd

UnifiedCSD: /home/nilg/Sources/cabbage-read-only/Builds/Linux/build/CabbagePluginSynth.csd
Failed to open csd file: No such file or directory
Reading CSD failed ... stopping

The strange thing is I can't find it anywhere

nilg@laptop:~/Sources/cabbage-read-only$ find . -name "CabbagePluginSynth.csd"

outputs nothing.

>
> I do have intentions of moving to github but I'm swamped with other
> stuff right now.


> Also, would you mind registering on the forum at
> www.thecabbagefoundation.org, I'm hoping to keep all Cabbage related
> correspondence there so others can search the archives for answers to
> similar questions that might have!

Got it, I'll move any further discussion there.

>
> Btw, what version of Linux are you using?

Ubuntu 12.04

Nil

Rory Walsh

unread,
Oct 6, 2012, 12:29:30 PM10/6/12
to cabbag...@googlegroups.com
I see. I think the problem is that you need to export the plugin
before you can use it. So launch Cabbage and open a csd file from the
examples. Then go to 'export as' and browse to your VST folder. After
you export, Cabbage will create a copy of the generic plugin lib with
the same name as the .csd file. Both files need to be in the same
directory. Now launch Renoise and do a re-scan of teh plugins. You
should be able to run the exported plugin then. Note tha tif you wish
to make changes to the plugin thereafter, you only need to edit the
associated csd file, i.e, the one in the same directory as the newly
copied plugin lib.

Nil Geisweiller

unread,
Oct 6, 2012, 6:34:37 PM10/6/12
to cabbag...@googlegroups.com
Sorry, I had not read the documentation and I had some preconceived
idea of how it's supposed to work, it much clearer now (and I'm
reading the doc).

Nil

Rory Walsh

unread,
Oct 7, 2012, 9:19:33 AM10/7/12
to cabbag...@googlegroups.com
Is it working now?

Nil Geisweiller

unread,
Oct 7, 2012, 4:47:34 PM10/7/12
to cabbag...@googlegroups.com
On Sun, Oct 7, 2012 at 3:19 PM, Rory Walsh <rory...@ear.ie> wrote:
> Is it working now?

Sort of, first when I exported the synth it didn't create a
CabbagePluginSynth.csd file as explained in the doc, so I manually
copied the one I wanted to load in Renoise and renamed it
CabbagePluginSynth.csd.

Then I can indeed call the plugin from Renoise, but when I display the
GUI I get a black screen and on the terminal an infinite display of
the message

timerCallback():1

The plugin in question is AdditiveAuto.csd (if that's any relevant).

Rory Walsh

unread,
Oct 7, 2012, 5:01:43 PM10/7/12
to cabbag...@googlegroups.com
Hmm. Ok. It's not going to create a file called
CabbagePluginSynth.csd, it should create a .csd file with the same
name as the one you open directly in Cabbage. If you choose to export
to the same directory you are working from then all Cabbage will
create is a .so with the same file name as the .csd file you are
working from. If you export to a different folder Cabbage will create
a copy of the .csd file and a .so of the same name. If you have to
rename things something is up?
Reply all
Reply to author
Forward
0 new messages