Broken click track on 64-bit (*ubuntu 9.10 workaround?)

[personman]

I'm reading up on how to manually extract .deb packages and copy the files to the appropriate location. I'm hopeful I should have some work-around fairly soon.

Once I do, I'll post detailed instructions.

-Andy

[steve]

If you are building the libraries from source, can you do "./configure --program-suffix=32" or something?
Good luck.

[personman]

I'm trying to avoid a manual compilation for a couple reasons:

1.) I'm lazy.

2.) If we can use the precompiled binary packages, it might be easier to duplicate for others.

I have two ideas I'm going to investigate as potential work-arounds:

First Idea:

Install the 32-bit compatibility layer. Download the 32-bit package of Audacity, as well as the dependencies. Create a temporary directory to extract the .deb files to, and extract them. Copy the libraries to /lib32 and/or /usr/lib32

This SHOULD enable people to use the 32-bit audacity w/ nyquist, while keeping the system use-able. The downside would be, there probably won't be an easy way to manually remove only the copied libraries.

Second Idea:

Like the first idea: Install the 32-bit compatibility layer. Download the 32-bit package of Audacity, as well as the dependencies.

Temporarily point the symlinks /lib and /usr/lib to the 32-bit library directories, install the packages via dpkg, and then change the symlinks back... The bright side to this would be that if you want to remove the 32-bit libraries later on, you can point the symlinks to /lib32 and /usr/lib32 again, and hopefully just remove the packages, then change the symlinks back again...

The downside to this is I'm not real sure how the package manager will handle having both a 32-bit and 64-bit version of the same package name installed... It might consider it an upgrade, and think it no longer has the native 64-bit package installed...

Man, my head hurts already and I haven't even started yet...

The instructions will be specific to Karmic, but applicable to anything Debian based, with perhaps some minor differences.

I'm thinking I might try the second idea first, as it's simpler and probably easier to undo.

...Then there's the fact that I'll no longer have any excuses for not putting some compositions together. :/ jk

Good luck.

Thanks!

-Andy

[personman]

Hmm the second idea may have to be done differently, I was mistaken in that it is /usr/lib64 and /lib64 that are the symlinks, and not /usr/lib and /lib...

Might still be doable with some ugly moving around and such... If I don't post back soon, assume I've borked my system and don't follow my instructions.

[personman]

The system does NOT like having /lib moved... at all.

I'll probably fix it with a live CD and try the "First Idea."

[personman]

Ok, I seem to have success going with the First Idea... I haven't yet done really in-depth testing of each and every audacity feature, but as far as running and making a click track, so far so good.

It is messy as hell: I had to manually download, extract, and copy the individual dependencies, so I'm going to make a highly experimental *ubuntu 9.10 package that will place the 32-bit dependencies in /usr/lib32. Hopefully, this will enable clean uninstalling as well...

When I get some time I'll type out instructions for doing it manually for people running other Debian-based distros, or older versions of *ubuntu.

...Now I have to bone-up on making .deb packages...I did it once before, just need to refresh my memory. It looks like it'll be around 8 megs or so, so if it's larger than the attachment limit, I'll host it on my own webspace and post a link... Stay tuned...

As I said, highly experimental. Once a few experienced users give it the thumbs up, I'll quit trying to scare people away from it.

I'd like to do more testing too just in case there are optional dependencies that are needed as well...not real sure...

-Andy

[personman]

Ok, here we go... First the disclaimer:

* These are currently recommended only for experienced users. *

I'm a complete newb at making packages... so I'm not responsible if these obliterate your computer, burn down your house, and smack your mother.

There is no reason they should...but I'm just sayin'.

This is for machines running the amd64 build of *ubuntu 9.10. I've no idea if it will work with anything else. The files will be placed in /usr/lib32.

Here are the steps for installation:

1.) Install the 32-bit compatibility layer: sudo aptitude install ia32-libs

2.) Install the audacity-data package: sudo aptitude install audacity-data
(If it asks to install audacity, go ahead and let it. We'll be overwriting it with the 32-bit version anyway...)

3.) Download and install the 32-bit audacity package:
http://us.archive.ubuntu.com/ubuntu/poo ... 6_i386.deb

You will need to force the installation: sudo dpkg -i --force-all audacity_1.3.9-6_i386.deb

4.) Install the 32-bit dependencies:

http://anarchismtoday.org/Downloads/details/id=20.html

sudo dpkg -i lib32audacity-deps_0.1_amd64.deb

You should be able to run Audacity like normal, and you should have working nyquist functionality. (click track, etc.)

If you're an experienced user and you're feeling brave enough to give these a shot, please post back and let us know how it goes, or any problems you run in to.

Enjoy!



-Andy Rink

[steve]

Congratulations.
I'm book-marking this. Let us know if it keeps working without any side effects.

[personman]

Congratulations.

Thanks very much.

There ARE some minor issues. For example if you want to export with lame, you will need to install the 32-bit version under /usr/lib32

Also, it doesn't seem to recognize the 64-bit ladspa plugins, so I think with those as well they will need the 32-bit version to be put under /usr/lib32

I might throw together another package with the common 32-bit LADSPA plugins to make things easier on people.

Other than that though, it seems pretty good... Outputs to .ogg and .flac fine. Records great. Got my click track (which makes it all the more apparent I'm not John Bonham on the drums...ugh I'm a happy camper.

I might be able to improve the dependency info in the package so that it will automate a few of the steps, but I'll wait and see what all issues crop up.

-Andy

[personman]

If you don't need to use the LADSPA plugins with any 64-bit applications, you can download and force install the 32-bit versions.

Edit: This could probably be done with lame as well: if you don't need to use lame with any native 64-bit apps, you could probably just force install the 32-bit version.