wine & ardour_vst.exe.so BAD EXE FORMAT

Good day!

Ardour version 2.4.1
Wine version 1.0-rc3

Error:
wine: could not load L"Z:\usr\local\lib\ardour2\ardour_vst.exe.so": Bad EXE format for

Question:
What version wine I must use?

Thanks.

It is a library in the standard linux ELF format. It is loaded as part of the wine environment and wine uses it when a program tries to run a vst program.whenever the plugin makes a call to some windows function, this gets handled by Wine, which maps the windows function’s behavior into something equivalent on Linux.The article is good n very informative also.Thanks for sharing with us.Cohiba cigars

Hello,

I don’t know what distro you are using but on my system WINE 0.9.49 plays nice with Ardour. You will probably be able to find it on the archived packages at www.winehq.org

I solve my problem.
I use Slackware 12.0 and compile new packages (missing in distributive) manually.
When I compile fftw3, my SlackBuild script had error. With double precision must ./configure --enable-shared.
Now ardourvst run normally with wine 1.0.

Sorry my English.

yesterday was the same error, today I have the following …

wine: /home/user/.wine is not owned by you

anyway, I don’t have the file ardour_vst.exe.so in :\usr\local\lib\ardour2\

Thanks in advance for your help

Dell Inspiron 6000
Ubuntu Gutsy Gibbon 7.10
Wine 1.0 (i have the same problem with Wine 0.9.49 i386)
scons 0.97
jack 0.109.2

I try to build ardourvst
Is there anything that can be done about this?

Cheers

wine is intended to run windows EXE files. In technical terms they are in the PE format. ardour_vst.exe.so is NOT a PE executable. It is a library in the standard linux ELF format. It is loaded as part of the wine environment and wine uses it when a program tries to run a vst program.

You do not load this program directly with wine. You load the program you want to run and then when it needs to run a VST plugin, wine calls this library to handling the VST processing.

However, this is located in an Ardour directory, so wine probably doesn’t even know it exists. (And I’m not sure that wine is able to use it independently without being called first by ardour anyway.)

Reuben’s description is close, but still not quite accurate.

ardour_vst.exe.so is actually all of ardour - turned into a shared library. when you run ardour w/vst support you are actually starting wine and telling it load a tiny little windows program. this little program does nothing more than call a function in the ardour shared library, which never returns until you quit ardour.

when you load a VST plugin, most of its code just runs normally (e.g. the DSP code that makes it a useful thing in the first place). however, whenever the plugin makes a call to some windows function, this gets handled by Wine, which maps the windows function’s behaviour into something equivalent on Linux. this includes file i/o, GUI stuff etc. etc.

Hello,
Sorry to wake an old thread, but I started getting the same error today. Ardourvst was working fine for couple of days, and I really can’t figure out what went wrong. I was installing more software like ecasound, but never touched neither wine nor ardour, nor anything important. I uninstalled and rebuilt, still the same error. Now I installed with VST=0, and I am running the plugins through vsthost and routing via jack. Still, it would be easier to have them available directly in ardour.
Best regards and thanks to the devs for the excellent program

wine is an emulating software and is an executive file. Use wisely.
wine is also a liquor you must know…
i am a software engineer and usually works with wine software. i go to Cigar shop to buy it for getting some refreshment while working…
Hope you try and give me a reply…
Enjoy…
Simpy

Wine reports “bad exe format” whenever it can’t load the executable. This can also mean that the executable needs libraries that cannot be loaded, e.g., because they are not found. In the case of Ardour, check for the output of

ldd lib/ardour2/ardour_vst.exe.so

This will give you some entries with “Not found”. Use your package manager to install the missing libraries. There you go.

This did the job on my system and I’m putting this knowledge snippet here for those people who are frustrated from getting answers like “Your system is 64bit, eh?” or “Man, .so is no Windows executable!”… :slight_smile:

Best

DrNI