Well, despite the terrible noise, this solution is certainly better than letting audacious suddenly die. However, I can't avoid comparing this to mplayer's behaviour, where it just keeps playing without any audible problem. This is what I see when I open such an ape file with the mplayer version currently at the Debian unstable repositories:
$ mplayer file.ape MPlayer SVN-r28799-4.3.3 (C) 2000-2009 MPlayer Team mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Playing file.ape. libavformat file format detected. [lavf] Audio stream found, -aid 0 ========================================================================== Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders AUDIO: 44100 Hz, 2 ch, s16le, 0.0 kbit/0.00% (ratio: 0->176400) Selected audio codec: [ffape] afm: ffmpeg (FFmpeg Monkey's Audio) ========================================================================== AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Video: no video Starting playback... [ape @ 0x99a9290]Error decoding frame A: 45.0 (44.9) of 45.3 (45.2) 5.4% Exiting... (End of file) $ Perhaps checking how ffape decodes these files could help? > I'm attaching a patched binary of the .ape plugin > (/usr/lib/audacious/Input/demac.so) for Lenny i386, so you can try it > for yourself if you trust me. Heh... Should I? :-) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
