Audacious-1.4.5 issues

Message

selig · Post by **selig** » Wed Feb 06, 2008 11:47 am

Hello,
I have recently updated my system and one of the programs that got updated was Audacious. There are some annoyances with Audacious-1.4 (Audacious-1.3 worked fine).

1. it refuses to open .wav files - no error whatsoever (and no output to console), it just does not add them to playlist even though the sndfile wav plugin is loaded and enabled
2. no analogue CD audio playback!! I never imagined that I would want to use "cdplay" again...
3. CDDB does not work either! Again, I may as well as use "cdplay" which does not have CDDB support either.
4. It is unable to change OGG info - it just says "Failed to modify tag (close)"

What is even worse - Gentoo folks decided that Audacious-1.4 is OK, marked it stable and removed all older ebuilds. I had to get all files required for building Audacious-1.3.2 and its corresponding plugins from CVS and put them into my Portage overlay.
Are you experiencing these problems too? If yes, a bug report should be filed...

Another interesting thing is that playing .wav files in audacious-1.3 (I do not remember the behaviour in older versions) eats up 50% of the CPU! When you play them in a different player, for example mplayer, it eats up 0% - the data can really be just passed on to the sound card. What does Audacious do with wav files???

My architecture is amd64.

psycho3d · Post by **psycho3d** » Wed Feb 06, 2008 12:13 pm

4. same here

i didn't check your other problems, but i've got my own

audacious always starts with maximum volume

x86, software volume, alsa output, version 1.4.5

blueflame · Post by **blueflame** » Wed Feb 06, 2008 1:42 pm

I think adding the "musepack" USE flag solves the wav playback problem...

selig · Post by **selig** » Wed Feb 06, 2008 10:09 pm

I have got musepack use flag enabled, but it is for .mpc files so that does not solve the issue.

dark_glaive · Post by **dark_glaive** » Fri Feb 08, 2008 11:27 pm

Can someone post the 1.3.2 ebuild and 1.3.3 audacious-plugins ebuild? I refuse to use the 1.4 series of audacious which clips the end off a lot of ogg songs and I currently can't use the emerge -upD command because of it and there are no snapshots with those ebuilds now.

Dammital · Post by **Dammital** » Sat Feb 09, 2008 5:02 pm

A "me too" post. (Sorry!)

Can't play .wav or .ogg here with audacious-1.4.5. No indication why. mp3 works fine though. Here's what's installed:

$ emerge -pv audacious audacious-plugins

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild R ] media-sound/audacious-1.4.5 USE="dbus nls -chardet -libsamplerate" 0 kB
[ebuild R ] media-plugins/audacious-plugins-1.4.4 USE="aac alsa dbus flac gnome mp3 nls sdl vorbis wma -adplug -arts -chardet -esd -jack -lirc -modplug -mtp -musepack -oss -pulseaudio -sid -sndfile -sse2 -timidity -tta -wavpack" 0 kB

01mf02 · Post by **01mf02** » Sat Feb 09, 2008 5:35 pm

Try to use the latest "unstable" audacious/audacious-plugins versions, the WAV problem was fixed recently.

gundelgauk · Post by **gundelgauk** » Sat Feb 09, 2008 6:01 pm

I'm also quite unhappy with Audacious. Have been for a long time now. The player is not bad, I rather like it. It's the bugs that really kill it for me.

Very often when I launch a playlist with URLs to a live stream, Audacious crashes. Sometimes it doesn't even crash, but sits there, frozen, consuming 100% CPU. I have to go to a terminal, ps, kill -9 and restart it. And bang, all my settings are lost - visualization, window positions, plugin settings and so on. So this means a complete reconfiguration on an hourly basis. I've had this problem since I started using Audacious (back when XMMS disappeared) and it's still there with 1.4.5. I've tried it on my laptop (pentium-m, x86) and my desktop computer (nocona, amd64) and I'm having the same problem everywhere.

Back when I still used -O3 and various optimization flags in make.conf, Audacious wasn't able to play live streams correctly at all. Well I have since changed to the supposedly safe standard flags and now I can listen to streams. If the program doesn't crash, that is.

I don't want to live with that any more. It can't seem to get fixed and I'm compiling XMMS from source right now - something which I dispise since I love portage so much. Oh well...

Dammital · Post by **Dammital** » Sat Feb 09, 2008 6:19 pm

01mf02 wrote:Try to use the latest "unstable"

Good idea 01mf02, but didn't help in my case.

I notice that newly created oggfiles will play, but old ones won't. Another clue...

01mf02 · Post by **01mf02** » Sat Feb 09, 2008 7:08 pm

Okay, I think that those bugs are probably fixed in SVN. If you are brave enough, use the following script to try it. It only creates a directory "audacious" in your home directory and does not need root rights or anything, but you need to have "mercurial" installed before.

Code: Select all

#!/bin/sh
SERVER=http://hg.atheme-project.org
SUBDIR=~
PREFIX=$SUBDIR/audacious/usr

function compile {
	hg pull -u
	./autogen.sh
	PKG_CONFIG_PATH=$PREFIX/lib/pkgconfig CPPFLAGS="-I." ./configure --prefix=$PREFIX
	make
	make install
}

cd $SUBDIR

hg clone $SERVER/audacious audacious
cd audacious

hg clone $SERVER/libmowgli libmowgli
cd libmowgli
compile
cd ..

hg clone $SERVER/libmcs libmcs
cd libmcs
compile
cd ..

compile

hg clone $SERVER/audacious-plugins plugins
cd plugins
compile

Afterwards, start Audacious - the program is located in ~/audacious/usr/bin/audacious. Good luck!

[EDIT]
If you still experience problems and want those fixed, you may try to report them. In that case sorry for the inconvenience.

psycho3d · Post by **psycho3d** » Thu Feb 14, 2008 9:58 pm

wohoo, thanks (?) to another problem i found the pet sematary where old ebuild files can be revived
http://sources.gentoo.org/viewcvs.py/ge ... ideattic=0

click the version you want and then (download)

selig · Post by **selig** » Sun Feb 17, 2008 10:11 am

Thanks 01mf02, the SVN build is much better! Analogue CD playback is not supported but that is not such a big issue since digital CD playback and WAV playback does not eat up CPU any more. The only problem that remains is non-functional CDDB.

96140 · Post by **96140** » Mon Feb 18, 2008 9:17 am

selig · Post by **selig** » Mon Feb 18, 2008 11:22 am

I was having issues after upgrading from 1.3 to 1.4, so I deleted the ~/.config/audacious directory and after configuring it anew, it did not forget its settings. However, I really dislike Audacious 1.4 so I reverted back to using 1.3 (pulled the ebuilds from portage CVS and put them into my overlay).
There is already a bug filed for CDDB in 1.4 in Audacious' bugzilla - it was "unconfirmed" so I confirmed it... hopefully somebody starts working on it. As far as I can see, Audacious 1.4 is much worse than 1.3. What I would really like to see is for example gapless CD playback and certainly not tons of new bugs.

mantono · Post by **mantono** » Wed Feb 20, 2008 9:09 pm

I do also have major problems with audacious-1.4.5 (upgrading to masked 1.4.6 did not help). As some of you mentioned the preferences seems to be saved only sporadic. What really irritates me tough is that the CLI-commands are really fucked up. If I for example do "audacious --fwd", a new audacious-session is opened and my command doesn't effect the current audacious window at all. Also the synchronization between ALSA's PCM-level and the one on audacious doesn't work very well either. None of these bugs struck me when I used earlier versions of audacious.

mantono · Post by **mantono** » Wed Feb 20, 2008 9:48 pm

I made some new ebuilds (for 1.3.2) and downgraded, everything works like a charm now!

selig · Post by **selig** » Thu Feb 21, 2008 11:01 am

I think we will have to wait for Audacious-1.5 and pray for a better release than 1.4... and use 1.3 in the meantime

mantono · Post by **mantono** » Thu Feb 21, 2008 8:19 pm

Maybe, still we shouldn't have to wait for a new "major" release to get bug fixes. I wonder why they had to remove the 1.3.x-ebuilds from portage. They seemed to be stable, not even worth masking.

96140 · Post by **96140** » Thu Feb 21, 2008 9:49 pm

mantono · Post by **mantono** » Fri Feb 22, 2008 12:04 pm

nightmorph wrote:
mantono wrote:I wonder why they had to remove the 1.3.x-ebuilds from portage.
In part because upstream doesn't support anything but the latest release. They don't take bugs for older versions; the response is always "you should upgrade to the newest version."

Ah, okey. Quite understandable, I wouldn't want to get any bugs for older versions either. Tough with this odd situation, the annoying bugs seems to be in the newer versions, and 1.3.x looks way more stable, at least for me. However, that's just have it affected me. Maybe the Gentoo users (and audacious users) in general befitted from an upgrade to 1.4.x.

doubledr · Post by **doubledr** » Sat Feb 23, 2008 7:07 pm

Actually, is it possible to get audacious-1.3 ebuild back to Portage? 1.4 really sucks...

psycho3d · Post by **psycho3d** » Sat Feb 23, 2008 7:32 pm

psycho3d wrote:... where old ebuild files can be revived
http://sources.gentoo.org/viewcvs.py/ge ... ideattic=0

click the version you want and then (download)

selig · Post by **selig** » Sun Feb 24, 2008 12:11 pm

A developer asked me to try new Mercurial again, so I did. Now it says "Audacious 1.5.0" but CDDB is still not working, adding a CD to the playlist is even more obscure (you have to right-click on the playlist, then choose module services or something like that and there you will find "add cd") and what is even worse, some of my skins stopped working. They show up in the list, but they do nothing when selected. I should not have talked about possible improvements in Audacious 1.5

doubledr · Post by **doubledr** » Sun Feb 24, 2008 6:58 pm

psycho3d wrote:
psycho3d wrote:... where old ebuild files can be revived
http://sources.gentoo.org/viewcvs.py/ge ... ideattic=0

click the version you want and then (download)

aha, I didn't notice that

Fenice · Post by **Fenice** » Tue Feb 26, 2008 2:24 pm

I've seen other problems with this branch : alsa pcm mixer bar does not work well and if you use the default 1.4 theme with a certain gtk theme, you will have problem with menus and configuration windows.

I had those problems on a pentium-M and on a core2 desktop (using the amd64 arch).

Did anyone had those problems?