None of the systems I build use wbar. It is unlikely that I am alone in this based upon it regularly being raised in the forum. My understanding is that wbar is now a separate and optional package. Is this incorrect?

Menu barA single alteration made to app setupEdit-->Preferences-->Import/Export-->Show Metadata Editor prior to export=disableResult:This prevented display of some entries in the app menu barMinimize then maximize window returned all entries

It seems audacity tries to use ffmpeg to function with wav files. I have a build script to create a static ffmpeg, I will build it and plug it in the extension soon. But for now, installing ffmpeg-ffserver will work.

I added a shared build of ffmpeg version 0.7.11, as audacity looks for libavcodec.so.52 for ffmpeg functionality. If one imports wavs that show up when searching for ffmpeg compatible files, they should work.

I added a shared build of ffmpeg version 0.7.11, as audacity looks for libavcodec.so.52 for ffmpeg functionality. If one imports wavs that show up when searching for ffmpeg compatible files, they should work.

I'm not certain what is meant by this.

Successfully tested the import and export of various formats mp3, flac, wma... All work OK.

To see if they might be related to the version of Audacity on which the scm is based, I tried v2.0.0 from the Debian 6 testing repo in another distro. Note, this is not identified as beta. All worked OK including the import/export of wav files. Might it be worth looking at the newer release?

But I will look into a rebuild and an update to 2.0 to see if that will fix it. Actually building against ffmpeg instead of just plugging it in, though the libavcodec library is still recognized, may make things better.