Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Audacious2 few issues

0 views
Skip to first unread message

Piotrek

unread,
Feb 23, 2010, 1:54:10 PM2/23/10
to freebs...@freebsd.org
Hi

I have few problem related to Audacious2.2 first of all, when i try to play mp3s i get dirty/distorted/interfered sound (FLACs plays perfectly, i use oss plugin), and for eg. mpg123 plays mp3s perfectly, other thing is that when i run audacious with GTKui it crashes xorg randomly, and after i start x again everything works good until i start audacious again and then it crashes xorg straight away, reboot helps until next random crash. Audacious with normal gui causes problems with closeing, when i try close audacious i get message that "process is not responding, close it anyway ?" strange thing is if i click "no" i can change tacks and do anything else with it (so it is responding)

I keep my music on NTFS disk (mounted read only)

Audacious 2.2_1
Audacious-plugins 2.2_2
Xorg http://wiki.freebsd.org/ModularXorg/7.5#preview


FreeBSD sng 8.0-STABLE FreeBSD 8.0-STABLE #0: Tue Feb 16 18:26:01 CET 2010 sng@sng:/usr/obj/usr/src/sys/DESKTOP-DEBUG amd64

Just let me know if You need any additional info

--
Piotrek <piok...@gmail.com>

Steve Polyack

unread,
Feb 23, 2010, 3:44:55 PM2/23/10
to Piotrek, freebs...@freebsd.org
I don't have any of the issues you list, but beginning with Audacious
2.2 I have seen a few others:
* The volume resets to 50% every time the song changes
* Song metadata / ID3 tags are not read for random sections of the
playlist upon restarting Audacious. When adding files to an empty
playlist, this does not seem to be a problem.
* Random songs are missing from the playlist if audacious is closed and
restarted - probably similar to the above
* Audacious locks up when rewinding to the beginning of any song - the
player continues playing music, but the GUI hard locks until the process
is kill -9'd.

None of these were issues with Audacious 2.1. I'm on FreeBSD 8-RELEASE
(amd64). I believe it was also a problem when I was running 7-STABLE.

Piotrek

unread,
Feb 24, 2010, 11:49:56 AM2/24/10
to Steve Polyack, freebs...@freebsd.org
I sorted out @ least one problem...on linux box i could set output bit
deph to 32, and set bypass all of singal processing if possible on, but
it doesn't work for FreeBSD, to get clear sound (mp3) i have to leave
16 bit output deph, and leave bypass all of singal processing if
possible off, is it only my problem, (maybe it is driver
problem) has anyone ESI Juli@ soundcard to confirm or denay this
issue ??

--
Piotrek <piok...@gmail.com>

varga....@gmail.com

unread,
Feb 24, 2010, 3:42:26 PM2/24/10
to Steve Polyack, freebs...@freebsd.org
On Tue, Feb 23, 2010 at 9:44 PM, Steve Polyack <kor...@comcast.net> wrote:

> I don't have any of the issues you list, but beginning with Audacious 2.2 I
> have seen a few others:
> * The volume resets to 50% every time the song changes
>

Doesn't "Preferences > Use software volume control" help with that? It
used to work even better with audio/audacious-crossfade as output,
well at least until they added the mentioned option directly to the
main app, since then software mixing with crossfade clashes horribly
with it (among other things, though this is still pretty minor in
comparison with the rest of the issues).

Anyway - Audacious 2.2 is quite a disappointment, seems that every new
release breaks more things than it fixes, and it's starting to become
a routine.

m.

Steve Polyack

unread,
Feb 24, 2010, 3:50:32 PM2/24/10
to varga....@gmail.com, freebs...@freebsd.org
On 02/24/10 15:42, varga....@gmail.com wrote:
> On Tue, Feb 23, 2010 at 9:44 PM, Steve Polyack<kor...@comcast.net> wrote:
>
>
>> I don't have any of the issues you list, but beginning with Audacious 2.2 I
>> have seen a few others:
>> * The volume resets to 50% every time the song changes
>>
>>
> Doesn't "Preferences> Use software volume control" help with that? It
> used to work even better with audio/audacious-crossfade as output,
> well at least until they added the mentioned option directly to the
> main app, since then software mixing with crossfade clashes horribly
> with it (among other things, though this is still pretty minor in
> comparison with the rest of the issues).
>
>
It does indeed help, but when using software volume control there is a
1-2 second lag between moving the slider and the volume actually
changing. I guess at leas the volume does not reset upon changing songs.

varga....@gmail.com

unread,
Feb 24, 2010, 4:42:22 PM2/24/10
to Steve Polyack, freebs...@freebsd.org
On Wed, Feb 24, 2010 at 9:50 PM, Steve Polyack <kor...@comcast.net> wrote:
> It does indeed help, but when using software volume control there is a 1-2
> second lag between moving the slider and the volume actually changing.  I
> guess at leas the volume does not reset upon changing songs.
>
Yes, this is too one of the issues that -crossfade output never had
while running with software mixer (I personally hate my apps messing
with my global volume levels as they have no "right" to do that -
software volume is a must in my world).

Anyway - you can try setting the buffer sizes to any min. allowed
values (100-200ms?) in both main app and your output plugin, it should
minimize the lag to only 'slightly' annoying. As you say - it's better
than the other way around.

m.

0 new messages