[Ardour-Users] ARDOUR_DLL_PATH not set in environment - exiting
jonetsu
jonetsu at teksavvy.com
Sat May 5 09:05:06 PDT 2018
On Sat, 5 May 2018 12:59:18 +0200
Robin Gareus <robin at gareus.org> wrote:
> https://github.com/Ardour/ardour/blob/master/gtk2_ardour/bundle_env_linux.cc#L87
Thanks. Here are a bit more details as well as an overview of the
problem at the end.
1) When all goes good:
[...]
(mixbus32c-4.3.19:5474): Gtk-WARNING **: Unable to locate theme engine
in module_path: "adwaita",
Color shuttle bg not found
ardour: [INFO]: Loading color file
/opt/Mixbus32C-4.3.19/share/themes/dark-mixbus32c.colors
ardour: [INFO]: Loading color file
/home/mevla/.config/mixbus4/my-dark-mixbus32c-4.3.colors
(mixbus32c-4.3.19:5474): Gtk-WARNING **: Unable to locate theme engine
in module_path: "adwaita",
ardour: [INFO]: Loading ui configuration file
/opt/Mixbus32C-4.3.19/etc/clearlooks.rc
ardour: [INFO]: Loading ui configuration file
/opt/Mixbus32C-4.3.19/etc/clearlooks.rc
Found 5 along
/home/mevla/.config/mixbus4/templates:/opt/Mixbus32C-4.3.19/share/templates
run dialog
2) When it will not launch, the last two lines ('Found' and 'run
dialog') are replaced by:
ARDOUR_DLL_PATH not set in environment - exiting
I haven't browsed the code, although it looks like
export_search_path() is not a function that would return something
important, if anything at all. It's assumed it works.
So it's later on when that variable is actually needed and checked
upon that the problem is reported.
This said, restarting jackd solves this problem.
The idea behind asking these things is to perhaps just get a slight
overview of how these things works regarding a problem that breaks the
workflow: linVST crashinbg sometimes, and in crashing puts jacks in a
bad state such that jackd will report:
JackPosixSemaphore::TimedWait err = Connection timed out
JackFreewheelDriver::ProcessSync: SuspendRefNum error
JackAudioDriver::ProcessGraphSync: ProcessWriteSlaves error, engine
may now behave abnormally!!
More information about the Ardour-Users
mailing list