avlinux + renoise

[hsnlv]

Hi,
Took a hiatus from avlinux and have come crawling back!  I've had a similiar problem before, but following the steps of my original post last year yield no positive result.

I'm trying to get renoise to see the VSTs in usr/local/lib/linux_vst to no avail (it's in my .bashrc). 

Anybody had any luck or know how to do this?

For the record, I've uninstalled the renoise demo, got my license ( 2.7.2) extracted to a folder in my home file and have run the installer.

Cheers,

Hasan

[GMaq]

Hi,

In the renoise-demo I placed a launch script that shows Renoise the VST PATH. I don't know why Renoise doesn't pick up the PATH from .bashrc, it has never seemed terribly reliable for that so that is why I created the launch script.

So you can export the VST_PATH in terminal and then launch Renoise in the same terminal like this:

Code:

export VST_PATH=/usr/local/lib/linux_vst

then when returned to the terminal prompt launch Renoise ('/PATH/TO/' is whatever your actual path wherever the Renoise installer puts the executable)

Code:

/PATH/TO/renoise

I can help you with a script so you don't have to do this every time if you want... but I'm short on time today.

[hsnlv]

Okay,
I tried re-installing again and followed the steps for a system wide installation as per the linux renoise faq:

su: password
sh install.sh

typing in "renoise" will bring up the program and find all my vsts!  Success.  Now, where would this executable have installed to for me to put it my menu?

Cheers,

Hasan

[hsnlv]

Hi,
I'm happy to call up the terminal and bring up renoise, but I would appreciate an answer for my own developing knowledge on how to get the menu item that I set up run the same way.

Cheers,

Hasan

[GMaq]

Hi,

Just so I understand correctly... You installed Renoise as Root and now it finds the VSTs without using the export PATH method I suggested above? The Renoise installer doesn't create a launcher, or at least one that you can see?

My guess is that it did create a launcher but it doesn't show up in the AV Linux customized audio menu. Read the AV Linux manual on pages 13 and 14, that should give you info you are looking for.

[hsnlv]

Hi,
Sorry for bringing back this post from the dead (hey!  I was making music!).

I followed all the instructions in the manual for adding a launcher and I was successful in doing so.  Looking at the properties of the renoise launcher confirm that it is pointing to the renoise executable. 

The odd thing is that the launcher will load renoise sans vsts...as opposed to opening up a terminal, going to the renoise directory, and running renoise.

Any ideas why those two behaviours are different?  Is it related to the .bashrc file?

Cheers,
Hasan

[GMaq]

OK

The problem is my launcher for the Renoise demo points to a custom script showing the VST path which in turn points to the Renoise executable. The actual installed Renoise launcher points directly to the Renoise executable so it doesn't see the VST path.

You can try this to see if it helps:

Open your .bashrc with gedit and try changing the 'export VST_PATH' line to this:

Code:

export VST_PATH=/usr/local/lib/vst:/usr/lib/vst:/usr/local/lib/linux_vst

Then log out log back in and try launching Renoise again. Let me know if this works...

[hsnlv]

Okay, I'll try that, but just to put this all in context:  I've uninstalled the renoise 2.7 demo via synaptic, installed 2.8, and created my own launcher via avlinux manual.

How does the old launcher come in to play? 

My apologies for dragging this on and my thanks for all your help.

Cheers,

Hasan

[hsnlv]

okay, this worked!  I'd still like to figure this out. I don't have this issue on linux mint - I'm a linux neophyte and I'm trying to get to intermediate status.
 
I'm going to eliminate the multiple VST paths to determine which path is actually being read so I can eliminate duplication in my filesystem.

Cheers,
Hasan

[GMaq]

Hi,

Some of the issue is that AV Linux has to run live with 2 different kinds of VST's (Windows and Linux). When I started distributing Renoise I had a single vst folder in /usr/local/lib/vst and Renoise would pitch a fit and choke on its first run because it didn't like Windows VST's. This wasn't a very appealing demonstration of Renoise on the LiveDVD so I then created a second folder specifically for LinuxVST's in /usr/local/lib/linux_vst. I then created a simple launch script for Renoise to differentiate the path it would search to correctly locate the VSTs.

My guess is that your Linux Mint install has the VST files in either /usr/lib/vst or /usr/local/lib/vst which is the path that Renoise will scan by default so it just works. With AV Linux I have various Sequencers looking for different kinds of VST's and they have to be set up to run correctly on the first launch from the LiveDVD.

I hope that answers your question.

[hsnlv]

Thanks GMaq, it really does.  Where is the launch script?

[GMaq]

Hi,

The renoise-demo package places this launch script in /usr/bin it is called 'renoise_launch.sh'. This is all there is to it:

Code:

#!/bin/sh
VST_PATH=/usr/local/lib/linux_vst /opt/Renoise/renoise f%

Notice that it points to the renoise-demo executable which is in /opt/Renoise. To use this script with an installed registered Renoise the script would have to be edited to point to wherever the Renoise installer places the executable (most likely /usr/local/bin or /usr/bin.

To use this script with a launcher the launcher has to point to the script in the 'Exec=' text line of the launcher like this:

Code:

Exec=/usr/bin/renoise_launch.sh'

[hsnlv]

Sorry to drag this out (learning linux and making music!):  If I delete the script, does this essentially reset my system to zero?  By that I mean, undo whatever is that you did to compromise on making windows vst work?

GMaq, are there are any resources that you recommend that I check into to figure this stuff out? 

Cheers,
Hasan

[linuxdsp]

The script just sets an environment variable "VST_PATH" to point to the location of the native linuxVST plugins (note - these are VSTs built for linux, VST is just a 'standard' it does not mean they are Windows VSTs - which I don't believe renoise supports on linux)

When renoise starts, it looks at the 'path' the environment variable "VST_PATH" points to, and uses that as the location to search for linuxVST plugins.

The launcher, has been told to run this script instead of running renoise directly, so the 'chain' is something like

(mouse-click-on-icon) -> (starts_launcher_script) -> (launcher script starts renoise after setting a new VST_PATH)

the new VST_PATH exists only in (and for the lifetime of) the script therefore it will not affect anything else which is running before, after or during the time renoise (or its launcher script) is running.