On March 22, 2016 04:02:54 PM Tim E. Real wrote:
> Got plugins in various locations?
> 
> Got a plugin that your package installer inexplicably
>  put in some weird location?
> 
> Tired of messing with environment variables?
> 
> * New Plugin Path editor in Global Settings:
> 
> The LADSPA_PATH DSSI_PATH VST_PATH LINUX_VST_PATH and LV2_PATH
>  environment variables are now read only ONCE upon first-time run,
>  to fill the Global Settings boxes.
> Afterwards these variables are SET (internally) by MusE at each startup,
>  from the paths in the Global Settings boxes, so that the various plugin
>  systems can find plugins.
> (Actually, LV2 /required/ setting LV2_PATH since we use the recommended
>  lilv_world_load_all, and there doesn't seem to be any other way to set
>  the paths programmatically in that case.)
> 
> - Updated -h help text to reflect changes.
> 
> Enjoy!
> Tim.

NOTE: Ensure the directory containing core LV2 bundles is always
 included in the LV2 paths entry box. Typically it is /usr/lib/lv2.

Otherwise all plugins may not load properly !

A warning to that effect has now been added to the LV2 paths tab.

For those who may have previously been trying to set the LV2_PATH
 environment variable externally, and did NOT include /usr/lib/lv2,
 you may have had problems missing plugins in MusE !

Tim.


------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer

Reply via email to