That says it all. Ardour takes two minutes to start. I recompiled it again and it still happens. No errors appear when I start it from a terminal. It just takes two minutes to start.
I have no clue about this one. I’d appreciate any help. I don’t even know what information to provide. I can’t think of anything relevant. I updated my Wine and system in general recently, but everything else that I do with audio works, including JACK.
I see in my JACK messages “ERROR: cannot find client 2”
That’s it for messages.
Ardour also has stopped working. It hasn’t played the last several times I tried to simply play an existing project. I click on the play button and… nothing. It’s not silent, it just doesn’t move.
Along with all this, Ardour freezes when I try to quit. I have to open a terminal and kill Ardour and several wine processes.
I do have some output, after all:
This is the entire output from the terminal from starting Ardour, opening a project, playing it (which worked fine at that point), and opening Rosegarden, at which point Ardour goes psycho and sticks its head in the sand as I described earlier.
I didn’t have this problem a few days ago.
audiodef@Tchaikovsky ~ $ ardour2 &
audiodef@Tchaikovsky ~ $ fixme:advapi:SetEntriesInAclA 1 0x33f72c (nil) 0x33f764
fixme:advapi:SetEntriesInAclA 1 0x33f71c (nil) 0x33f764
fixme:advapi:SetEntriesInAclA 1 0x33f73c (nil) 0x33f784
fixme:iphlpapi:NotifyAddrChange (Handle 0x73e914, overlapped 0x73e918): stub
audiodef@Tchaikovsky ~ $ err:process:__wine_kernel_init boot event wait timed out
(built using 8136 and GCC version 4.4.5)
Copyright (C) 1999-2008 Paul Davis
Some portions Copyright (C) Steve Harris, Ari Johnson, Brett Viren, Joel Baker
Ardour comes with ABSOLUTELY NO WARRANTY
not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This is free software, and you are welcome to redistribute it
under certain conditions; see the source for copying conditions.
Cannot install SIGPIPE error handler
/usr/share/themes/NOX/gtk-2.0/gtkrc:233: Murrine configuration option “gradients” is no longer supported and will be ignored.
/usr/share/themes/NOX/gtk-2.0/gtkrc:233: Murrine configuration option “gradients” is no longer supported and will be ignored.
loading default ui configuration file /etc/ardour2/ardour2_ui_default.conf
loading user ui configuration file /home/audiodef/.ardour2/ardour2_ui.conf
Loading ui configuration file /etc/ardour2/ardour2_ui_dark.rc
theme_init() called from internal clearlooks engine
ardour: [INFO]: Ardour will be limited to 1024 open files
loading system configuration file /etc/ardour2/ardour_system.rc
loading user configuration file /home/audiodef/.ardour2/ardour.rc
Startup win32 GUI thread
ardour: [INFO]: Using SSE optimized routines
ardour: [ERROR]: LADSPA: cannot load module “/usr/lib/ladspa/dahdsr_hexp.so” (/usr/lib/ladspa/dahdsr_hexp.so: undefined symbol: log)
ardour: [ERROR]: LADSPA: cannot load module “/usr/lib/ladspa/dahdsr_fexp.so” (/usr/lib/ladspa/dahdsr_fexp.so: undefined symbol: log)
ardour: [ERROR]: LADSPA: cannot load module “/usr/lib/ladspa/foo_limiter_v2.so” (/usr/lib/ladspa/foo_limiter_v2.so: undefined symbol: powf)
ardour: [ERROR]: LADSPA: cannot load module “/usr/lib/ladspa/wasp-noisifier.so” (/usr/lib/ladspa/wasp-noisifier.so: undefined symbol: pow)
ardour: [ERROR]: LADSPA: cannot load module “/usr/lib/ladspa/t00b_limiter.so” (/usr/lib/ladspa/t00b_limiter.so: undefined symbol: powf)
ardour: [ERROR]: LADSPA: cannot load module “/usr/lib/ladspa/foo_driver.so” (/usr/lib/ladspa/foo_driver.so: undefined symbol: powf)
ardour: [ERROR]: LADSPA: cannot load module “/usr/lib/ladspa/foo_saturator.so” (/usr/lib/ladspa/foo_saturator.so: undefined symbol: powf)
ardour: [ERROR]: LADSPA: cannot load module “/usr/lib/ladspa/foo_limiter.so” (/usr/lib/ladspa/foo_limiter.so: undefined symbol: powf)
ardour: [ERROR]: LADSPA: cannot load module “/usr/lib/ladspa/power_4400.so” (/usr/lib/ladspa/power_4400.so: undefined symbol: powf)
ardour: [ERROR]: LADSPA: cannot load module “/usr/lib/ladspa/vocoder.so” (/usr/lib/ladspa/vocoder.so: undefined symbol: pow)
ardour: [ERROR]: LADSPA: cannot load module “/usr/lib/ladspa/wasp-booster.so” (/usr/lib/ladspa/wasp-booster.so: undefined symbol: powf)
ardour: [ERROR]: LADSPA: cannot load module “/usr/lib/ladspa/wasp-noise_variable.so” (/usr/lib/ladspa/wasp-noise_variable.so: undefined symbol: pow)
VST_PATH not set, defaulting to /home/audiodef/vst:/usr/local/lib/vst:/usr/lib/vst
RemoteVSTClient: all cache files are up-to-date, not running scanner
ardour: [ERROR]: LADSPA: cannot load module “/usr/lib/ladspa/adenv_lvl.so” (/usr/lib/ladspa/adenv_lvl.so: undefined symbol: log)
ardour: [ERROR]: LADSPA: cannot load module “/usr/lib/ladspa/hz_voct_4200.so” (/usr/lib/ladspa/hz_voct_4200.so: undefined symbol: logf)
ardour: [ERROR]: LADSPA: cannot load module “/usr/lib/ladspa/foo_transients_mono.so” (/usr/lib/ladspa/foo_transients_mono.so: undefined symbol: powf)
ardour: [ERROR]: LADSPA: cannot load module “/usr/lib/ladspa/foo_transients.so” (/usr/lib/ladspa/foo_transients.so: undefined symbol: powf)
ardour: [ERROR]: LADSPA: cannot load module “/usr/lib/ladspa/wasp-x-shaper.so” (/usr/lib/ladspa/wasp-x-shaper.so: undefined symbol: sin)
ardour: [INFO]: detecting VST plugins along /usr/local/lib/vst:/usr/lib/vst
ardour: [WARNING]: Cannot get VST information from /usr/local/lib/vst/mixer1.dll
discovering /usr/local/lib/vst/Classic Flanger.dll
discovering /usr/local/lib/vst/Classic Reverb.dll
ardour: [WARNING]: Cannot get VST information from /usr/local/lib/vst/mixer3.dll
discovering /usr/local/lib/vst/Classic Auto-Filter.dll
discovering /usr/local/lib/vst/Classic Phaser.dll
ardour: [WARNING]: Cannot get VST information from /usr/local/lib/vst/mixer2.dll
discovering /usr/local/lib/vst/Triangle II.dll
ardour: [WARNING]: Cannot get VST information from /usr/local/lib/vst/MidiFilter.dll
ardour: [WARNING]: Cannot get VST information from /usr/local/lib/vst/gemma.dll
discovering /usr/local/lib/vst/Classic Master Limiter.dll
ardour: [WARNING]: Cannot get VST information from /usr/local/lib/vst/HarmoniEQ.dll
discovering /usr/local/lib/vst/Classic Chorus.dll
ardour: [WARNING]: Cannot get VST information from /usr/local/lib/vst/intermod.dll
ardour: [WARNING]: Cannot get VST information from /usr/local/lib/vst/erida.dll
discovering /usr/local/lib/vst/Classic Delay.dll
discovering /usr/local/lib/vst/Classic EQ.dll
discovering /usr/local/lib/vst/Classic Compressor.dll
discovering /usr/local/lib/vst/Deft Compressor.dll
ardour: [INFO]: looking for control protocols in /home/audiodef/.ardour2/surfaces/:/usr/lib/ardour2/surfaces/
powermate: Opening of powermate failed - No such file or directory
ardour: [INFO]: Control protocol powermate not usable
ardour: [INFO]: Control surface protocol discovered: “Generic MIDI”
ardour: [INFO]: Control protocol Tranzport not usable
ardour: [INFO]: Control surface protocol discovered: “Mackie”
loading bindings from /home/audiodef/.ardour2/ardour.bindings
(F:\usr\lib\ardour2\ardour_vst.exe.so:2939): Gtk-WARNING **: EnableTranslation: missing action EnableTranslation
Session writable based on /home/audiodef/ArdourMasters/LovelyMadhouse/I Want To Believe/
Layering call for Audio 2-4.1
Layering call for Audio 2-3.2
Layering call for Audio 2-2.6
Layering call for Audio 2-2.3
Layering call for Audio 2-1.12
Layering call for Audio 2-1.11
Layering call for Audio 2-1.10
Layering call for Audio 2-1.9
Layering call for Audio 2-1.7
Layering call for Audio 3-1.17
Layering call for Audio 3-1.16
Layering call for Audio 3-1.14
Layering call for Audio 3-1.13
Layering call for Audio 3-1.12
Layering call for Audio 3-1.10
Layering call for Audio 3-1.9
Layering call for Audio 3-1.8
Layering call for Audio 3-1.6
Layering call for Audio 4-6.5
Layering call for Audio 4-6.4
Layering call for Audio 4-4.6
Layering call for Audio 4-4.5
Layering call for Audio 4-1.7
Layering call for Audio 4-1.17
Layering call for Audio 4-1.16
Layering call for Audio 4-1.14
Layering call for Audio 4-1.13
Layering call for Audio 4-1.12
Layering call for Audio 4-1.8
Layering call for Audio 5-1.17
Layering call for Audio 5-1.16
Layering call for Audio 5-1.14
Layering call for Audio 5-1.13
Layering call for Audio 5-1.12
Layering call for Audio 5-1.10
Layering call for Audio 5-1.9
Layering call for Audio 5-1.8
Layering call for Audio 5-1.6
Layering call for Audio 6-3.5
Layering call for Audio 6-3.4
Layering call for Audio 6-2.7
Layering call for Audio 6-2.13
Layering call for Audio 6-2.12
Layering call for Audio 6-2.10
Layering call for Audio 6-2.8
Layering call for Audio 6-1.16
Layering call for Audio 6-1.15
Layering call for Audio 6-1.13
Layering call for Audio 6-1.11
Layering call for Audio 6-1.20
Layering call for Audio 6-1.19
Layering call for Audio 6-1.17
Layering call for Audio 7-4.3
Layering call for Audio 7-3.6
Layering call for Audio 7-3.5
Layering call for Audio 7-2.21
Layering call for Audio 7-2.20
Layering call for Audio 7-2.16
Layering call for Audio 7-2.14
Layering call for Audio 7-2.10
Layering call for Audio 7-2.8
Layering call for Audio 7-1.4
Layering call for Audio 7-1.3
Layering call for KB_ Inchworm-3.1
Layering call for KB_ Inchworm-1.1
Layering call for KB, Inchworm 2-1.7
Layering call for KB, Inchworm 2-1.6
Layering call for KB, Inchworm 2-1.5
Layering call for KB, Inchworm 2-1.4
Layering call for KB_ Inchworm 3-2.1
Layering call for KB_ WormARP-1.2
Layering call for KB, PolyNox-1.4
Layering call for AX, A8-1.1
Layering call for BD1-1.1
Layering call for Audio 1-2.1
Layering call for BD2-1.1
Layering call for EX, Snare-1.11
Layering call for EX, Snare-1.10
Layering call for EX, Snare-1.8
Layering call for EX, Snare-1.6
Layering call for EX, Snare-1.4
Layering call for EX, Snare-1.2
Layering call for Snare 2-1.1
Layering call for EX_ Hat-9.1
Layering call for IO:IWantToTick-1.1
Layering call for EX_ Reason Bbass-2.1
Layering call for Reason Modulator-1.1
Layering call for Reasonbass-1.1
Layering call for Wantadef-1.2
Maybe it’s JACK and not Ardour. This is from JACK messages:
Never mind. I couldn’t copy the messages and now it’s no longer in the scroll. But there was bunch of JACK errors that weren’t a problem as of a few days ago.
in qjackctl there is an option to log all output to a file text.
@audiodef: the output on stderr or stdout is almost never useful for debugging. Its not possible to debug your issue without you running a debug build of Ardour, which its unlikely you have unless you built it yourself.
What can I do about this, then? My work is at a complete standstill.
I’m compiling Ardour with debug. Once that’s done, then what?
The major problem in your case is that you are using the Wine-VST build, which is downright difficult to debug. I would suggest getting on IRC and seeing if there is anyone to help you there, but I wouldn’t hold my breath as I can probably count on one hand the amount of people with experience debugging the VST builds of Ardour, and I am not one of them sad to say;)
I don’t know if this has anything to do with why Paul is fed up with Gentoo, at least as far as Ardour goes, but I now have to agree with him. Gentoo is still my main OS, but I’m seeing if setting up Ubuntu for my audio work makes things more stable. I seriously do not need shit blowing up when I need to work. Or rather, I don’t mind if it does as long as it’s a problem that has a chance of being fixed while I learn something.
I would suggest to use AVLINUX 4.1 which has the most of the latest version and the distro is based on Debian and ardour is build with VST support. Here is the link to the ISO:
Dream Studio (dream.dickmacinnis.com) is Ubuntu based (hence compatible, in fact is mostly identical), and comes with both up-to-date versions of ardour and ardourvst.
You can give ubuntu a shot or Fedora too. My advice is to stay away from ubuntu studio, in my experience I have had quite some issues in the past with it, using plain ubuntu and self compiling evrything is and will always be better than ubuntu studio.
If compiling and configuring is just too much then go for DreamStudio like macinnisrr says or try gmaq’s A/V linux. These are two 100% Ardour users just like us, who rolled their own linuxes for this purposes, there can be no more guarantee that things will perform and work better than other distros.
After spending an entire day effing around with Gentoo, I’m about ready to go to bed in tears. Ardour still craps out when I open the programs I need to go along with it, namely Rosegarden and Patchage. This happens with ardour2, not ardourvst. I don’t even want to bother checking ardourvst on this setup again.
Ubuntu Studio and regular Ubuntu crapped out on nvidia drivers, of all things.
I’m going to try the above-mentioned distros. If those don’t work, please send the men in the white coats, for I shall have gone stark raving mad.
OK, more so than usual.
Compiling and configuring, well I love doing it, but when things consistently don’t work, it drives one a bit buggy - pun intended.
One peculiar thing about ArdourVST is that it will choke and puke on processing too many new VST .dll’s at the same time. It needs to write a small ‘.fsi’ file to use the VST.dlls properly. I see in the log you posted that it failed to get the VST information from some of your plugins. It could conceivably take several starts of ArdourVST to work through processing the large number of plugins during which it will try for several minutes and then just horribly die on you.
The secret is to add one Windows VST .dll at a time, launch Ardour from the terminal and see if it successfully integrated the VST. It is important to mention that some VST’s will not be compatible at all by fst (the vst enabling library) within Ardour and will never work, this is repetitive and time consuming but the only way to ensure a smooth start with ArdourVST.
For the record since it was mentioned earlier in this thread, AV Linux ships with several free Windows VST’s included with their accompanying fsi files so you can even launch and use ArdourVST from the LiveDVD with no hiccups. In my personal experience ArdourVST 2.8.11 with a carefully selected set of VST’s is rock solid. YMMV based on which dlls are used and which version WINE you are using as well.
I should mention that because Dream Studio is Ubuntu based, you’ll probably have the same Nvidia issues, although I suspect it’s because you’re using Ubuntu 10.10 (or UbuntuStudio 10.10, or Dream Studio 10.10 for that matter) and the nvidia-96 drivers, which is a known bug. If you want to give Dream Studio a shot (or Ubuntu, or UbuntuStudio) and those drivers are the problem, I recommend using 10.04 LTS instead. Or just use AVLinux
Again, I dont rely in Nvidia from repos, I download the official installer and latest from Nvidia website, and build additional kernel modules for it if necessary, which with repos its just too much of a hassle. That way I also make sure I am running latest Nvidia drivers.
What I’m trying to get to is that I install ubuntu just as a base and then compile as I go along, more stable, no dependency crap and if something is broken I know it’s my fault.
GMaq, the problem is, Ardourvst has been working with that number of VSTs for a while, so while I will follow your advice from now on, I don’t think that was the problem.
I’ve successfully installed AV Linux. Now I’m waiting to see if the nvidia drivers FUBAR on me like they did in Ubuntu. If not, we have a winner.
Joe, thanks for the insight on nvidia and Ubuntu 10.10. I was going to try 10.04 next, but hopefully AV Linux uses a stable version of nvidia drivers.