cc1plus: error: unrecognized command line option “-msse”
make[4]: *** [AAFilter.lo] Error 1
make[4]: Leaving directory `/home/jason/Desktop/audacity-src-1.3.3-beta/lib-src/soundtouch/source/SoundTouch’
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/jason/Desktop/audacity-src-1.3.3-beta/lib-src/soundtouch/source’
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/jason/Desktop/audacity-src-1.3.3-beta/lib-src/soundtouch’
make[1]: *** [soundtouch-recursive] Error 2
make[1]: Leaving directory `/home/jason/Desktop/audacity-src-1.3.3-beta/lib-src’
make: *** [audacity] Error 2

does anyone know what could be wrong here?
thanks in advance for any help!

I’m an absolute newbie at Ubuntu. I switched specifically BECAUSE Windows XP had given up on cooperating, and I needed to use it specifically for audacity. I followed your directions and successfully got the beta version running. However, I did it so that I could use my samson mic to record multiple tracks of audio. In the audacity wiki it gives directions to use portaudio to achieve ALSA support in Audacity 1.3.2 Beta. I followed their directions after yours; but to no avail. It does not give me the option in Preferences of using an ASLA device. I experimented with many commands and directories. I think most of the problem is that I do not really understand the problem, the instructions, or the solution. Can you help me get through?

Audacity homepage http://audacity.sourceforge.net/download/beta_source states that if you should install optional libraries using a package management system like Apt or RPM, make sure to install the “dev” (development) packages for each library.

So, I installed dev packages as well as the newer versions of some packages, such as libwxgtk2.8-dev, suggested in the previous instructions. (Some of the packages might be redundant.)

This installation process worked for me:

1) download audacity-src-1.3.3-beta at http://audacity.sourceforge.net/beta/audacity-src/audacity-src-1.3.3.tar.gz on your desktop
2) extract the tarball on your Desktop
3) cd Desktop/audacity-src-1.3.3-beta
4) sudo apt-get install build-essential libwxgtk2.8-0 libwxgtk2.8-dev libmad0 libmad0-dev libsndfile1 libsndfile1-dev gettext libwxbase2.6-dev libwxgtk2.6-dev wx2.6-headers libmad0-dev libvorbis-dev libogg-dev libflac-dev libflac++-dev libid3tag0-dev zlib1g-dev libtwolame0 libtwolame-dev libgtk-dev libwxgtk-dev twolame libasound2-dev libjack0.100.0-dev portaudio19-dev libgtk2.0-dev
5)./configure –program-suffix=beta && make
6) sudo make install
7) audacitybeta

configure: Expat libraries are available as system libraries
checking for ./lib-src/expat/xmlparse/xmlparse.h… yes
configure: Expat libraries are available in the local tree
checking for ./lib-src/twolame/libtwolame/twolame.h… no
configure: libtwolame library is NOT available in the local tree
configure: Figuring out what libraries to enable
configure: error: I didn’t understand the argument yes for LIBVORBIS

What do I need to do to resolve these as I have all the libraries on my box by now.
Do I need to make a symboliclink perhaps … if so from where to where … do others get these configure failuers too?

thanks again

philj

ubustu:Instead of pointing directly to files in sourceforge.net ,point them to the download
page and let sf.net choose the mirror since some mirrors do not accept direct links to download.

I configured it with the following :
{ ./configure –program-suffix=beta –with-vorbis –with-libmad –with-flac –with-id3tag }

the compiling went smooth as silk and I now have v1.3.3-beta up and running here. Great! .This was just FYI.

sudo apt-get install libmad0-dev libvorbis-dev libogg-dev libflac-dev libflac++-dev libid3tag0-dev zlib1g-dev

which will also install any necessary dependencies. Also, you really don’t need to mess with command line options with ./configure, as support for these features will be enabled by default if the necessary libraries are present.

Also, I followed the directions to install LAME support, and it didn’t work.

We know it doesn’t exactly help you much, but we also want to emphasize that a stone-cold freeze is a very unsual thing to happen in Ubuntu. We’ve been using it since Dapper Drake, and tho we’ve definitely had individual programs freeze up, we’ve never had to resort to a forced reboot. Those fancy features in W2K and XP that allowed the OS to continue working even tho a certain program had failed have long been staples in the Linux world.

We suggest you get a 5gb partition ready for Ubuntu Studio and do a truely clean i386 install (you can always browse your old partitions for bookmarks etc)… if not for full-time consistent use at least for tinkerings sake!

This time, with Ctrl + Alt + F2, things looked good for a while. The verbiage did pause, but the cursor continued to blink. I left my computer alone for more than 35 minutes. When I returned, the text on the screen looked exactly the same, although the cursor was still blinking. Ctrl + Alt + Del didn’t do anythng; nor did Ctrl + Alt + F7. Again, all I could do was push the reset button.

In my previous attempts to find a solution to this problem, I did run across a Debian package for Audacity 1.3.2, but it wouldn’t install in Ubuntu AMD64. Now that I’m running the i386 version, I’m going to try to find and install the Audacity Debian package again. I’ll leave further attempts at compiling for another time.

I must say again that you folks have been extremely helpful and friendly. When I encounter this sort of attitude, it helps renew my faith in the open source community and give me the patience to keep trying and not to give up on Linux altogether. Sorry if my previous message seemed a little testy, or if I overreacted a bit to the “WinBlows” comment.

We also meant no harm with our slanderous Windows comments. We’ve been PC users since ‘nibbles.bas’ was the most entertaining thing you could do. 2K was amazingly stable. XP is impressively stable! We must admit our dedication to Ubuntu and Open Source is less for “cool free software” and more for the philosophical underpinning of an Open Society.

That being said, we do sympathize with your struggles, and asbolutely cringed after we read it didn’t work after a complete OS reinstall. We do wish we could drop by for a beer and sit down at your box and see for ourselves.

We do have a final suggestion however

You may not be aware, but there are several different workspaces under Ubuntu.

Ctrl + Alt + F7 is the graphical interface workspace (where you are reading this now if you havent thrown your Ubuntu install off a cliff)

However, by pressing Ctrl + Alt + F2 (or F1, F3, etc… lets just stick with F2) you can switch to what looks like an old DOS prompt.

Try it now : press Ctrl + Alt + F2, look around at the DOS-like envrioment, then press Ctrl + Alt + F7 to come back to the Gnome GUI… pretty slick eh?

We suggest you try compiling the program from one of these textual workspaces. Write down the last few commands you need (make sure you re-try to download the dependecies as we’ve had to update them several times) and give it a go. Just switch to F2, login, and you’re basically at the terminal screen.

After you type in the ./compile… commands, go do something thats gonna take 30 minutes. Promise us not to watch the screen! Even if you computer is potentially frozen for the entire time, just promise! after you press enter walk away for 20-30 minutes

Many times when things do not work in the GUI workspace, they will work in the textual workspace. Maybe its still worth a try for you? It is very very unusual for linux to just freeze without simply writing an error.log of some sort and shutting down the offending process. Good luck either way our friend

It happens while the program is being compiled - while all the verbiage is appearing in the terminal window. It seems to occur at random points, rather than at a specific step in the compiling process. There’s no way to escape except to press the reset button on my computer.

Anyway…I was excited that you confirmed my suspicion that Ubuntu AMD64 is not exactly a finished product. I backed up the important files in my Home directory, formatted my Root partition, and proceeded to install Ubuntu i386. I then started running through your steps again, hopeful that it was going to work this time…and again my computer froze while the program was compiling. ARRRGHHH!!

While I’m a bit frustrated that a) I just reinstalled my OS apparently for nothing, and b) I might never be able to use Audacity 1.3.2 in Ubuntu, I want to make it clear that I really do appreciate your sympathy and prompt attention to my situation, as well as your use of clear, standard English in your responses (not all that common in the Linux world, in my experience!).

One note, though: While I can fully understand why people prefer the “community” approach of Ubuntu and other Linux distros to the “corporate” approach of software corporations like Microsoft, I really don’t like it when people gratuitously call Windows “Winblows.” Windows 2000 worked nearly flawlessly for me.

Yes, that’s right: I said “Windows 2000 worked nearly flawlessly for me.”

Unfortunately, so far I can’t say the same for Ubuntu. It has a lot of potential, and I’m sure it’ll be great when it’s finished, but for now I just want to get some work done, and I think I need to choose the path of least resistance in order to do so.

We have an AMD64 as well, but prefer to run i386 until 64-bit Ubuntu (or 64 bit any-OS) has more widespread support

We’ve got a feeling the Audacity team is worried about getting the i386 version nice and polished before they get to work on the i686 bit version

Ubuntu Studio will only be released as i386 at first, tho during the quesiton/answer session yesterday they did say a i686 version is planned… Don’t give up and go back to WinBlows just because of this! NOBODY has very good 64-bit support at this time

So yes, when Ubuntu Studio releases, I would suggest switching to the i386 version of Ubuntu. Anyone running anything 64-bit at the moment is sorta testing the waters for the future of computing!

tb: its hard to say without actually sitting down at your computer, but from the sounds of it, you may need to go to preferences and make sure your video card is selected and the proper settings are setup…

The audio devices prefences window has been majorly updated and overhauled in 1.3.2

So either go to Edit > Prefences, or press Ctrl-P, and see if you can figure out whats going on (or simply just trial and error until you get it right)

Of course, it is a beta… you may just happen to have a device (not necessarily your sound card, it could be any component of your computer) that doesn’t play well with 1.3.2

But we’re confident the Prefences window will help you on your way.

What kind of sound card do you have? You can set the sample rate at the bottom left hand corner of the screen. Most generic cards default to 41000, but even cheap cards like certain old SoundBlaster cards defaulted to 48000, and high end cards can go as high as 96000 (probably even higher these days)

Read up on your card via google and see whats what

Let us know what you find out of course!

Also, what exactly do you do to cause this error? Simply going to Tracks > Add New > Audio Track? Or are you importing a soundfile into the session or what?

Error while opening sound device. Please check the input device settings and the project sample rate.

Although I am willing to make compromises in order to work with Linux (and have done so in numerous instances), I’m afraid that if I can’t get Audacity 1.3.2 compiled and running on my machine, it might be time for me to abandon the Linux experiment and return to [a certain widely-reviled commercial OS, the very mention of the name of which frequently raises the ire of Linux advocates]!

By the way, I’m using the AMD64 version of Ubuntu, on a computer with a AMD Athlon 64 X2 4400+ processor, and 2GB RAM. I would think that my hardware should be more than sufficient. Is there some other command I need to run in order to accommodate the 64-bit OS and processor? Should I perhaps switch to 32-bit Ubuntu?

Again, thanks!

Cheers.

You need to install libwxgtk2.6-dev as well. This includes all the config file and header files required to compile.

Cheers.