Bug 61081 - Playing OGG files produces only unreadable output
Summary: Playing OGG files produces only unreadable output
Status: RESOLVED UNMAINTAINED
Alias: None
Product: mpeglib
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Multimedia Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-11 09:08 UTC by Raffaele Sandrini
Modified: 2008-12-28 21:26 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Raffaele Sandrini 2003-07-11 09:08:48 UTC
Version:           2.2.1 (using KDE 3.1.2)
Installed from:     (testing/unstable)
Compiler:          gcc version 3.3 (Debian)
OS:          Linux (i686) release 2.4.20herkules-1

Hi

When I tried to switch from XMMS to Noatun i recongnized that it was not able to play OGGs correct. If i play an ogg file a terrible mess comes out of my speakers (i can send u a try if u wisch :) ). I'm a little confused because i thoght noatun/arts was able to play OGGs (at least i ment that). I use Debian here and the arts package claims to have ogg compiled in.

I don't know exactly where the problem is now... It could also be a debian bug using the wrong ogg libs (is that possible?). BTW: I'm running unstable/sid here.

cheers,
Raffaele
Comment 1 Roger Larsson 2003-07-12 01:22:53 UTC
Please provide ogginfo output on the problematic files. 
> ogginfo file.ogg 
 
Comment 2 Raffaele Sandrini 2003-07-13 23:06:35 UTC
I did as requested. Here's the output: 
<ogginfo> 
Processing file "Daniel Bedingfield - Gotta Get Through This (D'N'D Full 
Length Version).ogg"... 
 
New logical stream (#1, serial: 00b7b738): type vorbis 
Vorbis headers parsed for stream 1, information follows... 
Version: 0 
Vendor: Xiph.Org libVorbis I 20020717 (1.0) 
Channels: 2 
Rate: 44100 
 
Nominal bitrate: 144.003000 kb/s 
Upper bitrate not set 
Lower bitrate not set 
User comments section follows... 
	TITLE=Daniel Bedingfield / Gotta Get Through This (D'N'D Full Length 
Version) 
	ARTIST=Various 
	ALBUM=Addicted to Bass CD2 
	TRACKNUMBER=1 
	GENRE=Dance 
	DATE=2002 
Vorbis stream 1: 
	Total data length: 3796489 bytes 
	Playback length: 3m:47s 
	Average bitrate: 133.241308 kbps 
Logical stream 1 ended 
</ogginfo> 
 
If i play this file then only a big sound mess comes out of my speackers (and 
no its not the song thats a mess :)) ). I have this problem with every ogg so 
this is just an example. 
Comment 3 Raffaele Sandrini 2003-07-13 23:09:34 UTC
Just to add: Its NOT a ogg error on my system. If i play the same file with 
ogg123 or winamp it plays perffectly. 
Comment 4 Roger Larsson 2003-07-14 10:59:42 UTC
Subject: Re:  Playing OGG files produces only unreadable output

On s
Comment 5 toojays 2004-09-06 13:06:57 UTC
I have just upgraded to KDE 3.3.0 and am seeing this problem for the first time. Playing an Ogg Vorbis file in JuK, or with artsplay, results in only static coming out of the speakers. artsplay can play MP3 files with no problem. I can use ogg123 to play Ogg Vorbis files with no problem. With KDE 3.2.3, I could play Ogg Vorbis in JuK and hear it fine.

By the way, this is on a ppc system.

What can I do? This is a gentoo build with full debug. If you want more info, just tell me how to get it.
Comment 6 Allan Sandfeld 2004-09-06 14:16:55 UTC
Sounds like you are using the xine_artsplugin, it doesn't work on ppc for some reason. Install akodelib, and it should solve the issue.
Comment 7 toojays 2004-09-06 15:44:20 UTC
carewolf,

Thanks for the quick reply. It does appear that I have akodelib on my system:

fuzz root # ls /usr/kde/3.3/lib/libarts_*
/usr/kde/3.3/lib/libarts_akode.la                /usr/kde/3.3/lib/libarts_splay.la
/usr/kde/3.3/lib/libarts_akode.so                /usr/kde/3.3/lib/libarts_splay.so
/usr/kde/3.3/lib/libarts_mpeglib-0.3.0.so.0      /usr/kde/3.3/lib/libarts_splay.so.0
/usr/kde/3.3/lib/libarts_mpeglib-0.3.0.so.0.0.3  /usr/kde/3.3/lib/libarts_splay.so.0.0.0
/usr/kde/3.3/lib/libarts_mpeglib.la              /usr/kde/3.3/lib/libarts_xine.la
/usr/kde/3.3/lib/libarts_mpeglib.so              /usr/kde/3.3/lib/libarts_xine.so

fuzz root # ls /usr/kde/3.3/lib/libakode*
/usr/kde/3.3/lib/libakode.la               /usr/kde/3.3/lib/libakode.so
/usr/kde/3.3/lib/libakode_mpc_decoder.la   /usr/kde/3.3/lib/libakode.so.1
/usr/kde/3.3/lib/libakode_mpc_decoder.so   /usr/kde/3.3/lib/libakode.so.1.0.0
/usr/kde/3.3/lib/libakode_mpeg_decoder.la  /usr/kde/3.3/lib/libakode_xiph_decoder.la
/usr/kde/3.3/lib/libakode_mpeg_decoder.so  /usr/kde/3.3/lib/libakode_xiph_decoder.so

What do I need to do to get arts to use it? (I did google, but I didn't find any clues.) 
Comment 8 Allan Sandfeld 2004-09-06 17:38:56 UTC
It should do that automatically. I was only assuming xine_artsplugin was used because I've seen a similiar problem with it on ppc.

Anyway if you have akodelib installed your bug is unrelated to this one, and you should open a new bug on akodelib. I will take it from there.

You can check which decoder is actually being used by first killing artsd, and then restarting it in a konsole with "artsd -l0". That will provide debug-info like decoders being loaded.
Comment 9 toojays 2004-09-07 13:02:13 UTC
Moving my problem to bug 88992.
Comment 10 esigra 2005-04-03 15:33:23 UTC
I can play ogg files with kde media players, but there are severe problems. It is not total garbage, like the reporter got, but very serious. I found out that higher encoding quality makes the problem much worse. See bug 102527.
Comment 11 Charles Samuels 2005-04-03 15:43:08 UTC
make sure the akode arts plugin is installed
Comment 12 esigra 2005-04-03 16:03:43 UTC
> make sure the akode arts plugin is installed

Yes:
/usr/kde/3.3/lib # ls -l libakode*
-rwxr-xr-x  1 root root  1025 Mar 22 17:29 libakode.la
lrwxrwxrwx  1 root root    17 Mar 22 17:29 libakode.so -> libakode.so.1.0.0
lrwxrwxrwx  1 root root    17 Mar 22 17:29 libakode.so.1 -> libakode.so.1.0.0
-rwxr-xr-x  1 root root 52624 Mar 22 17:29 libakode.so.1.0.0
-rwxr-xr-x  1 root root  1172 Mar 22 17:29 libakode_mpc_decoder.la
-rwxr-xr-x  1 root root 53024 Mar 22 17:29 libakode_mpc_decoder.so
-rwxr-xr-x  1 root root  1196 Mar 22 17:29 libakode_mpeg_decoder.la
-rwxr-xr-x  1 root root 13076 Mar 22 17:29 libakode_mpeg_decoder.so
-rwxr-xr-x  1 root root  1210 Mar 22 17:29 libakode_src_resampler.la
-rwxr-xr-x  1 root root  8168 Mar 22 17:29 libakode_src_resampler.so
-rwxr-xr-x  1 root root  1309 Mar 22 17:29 libakode_xiph_decoder.la
-rwxr-xr-x  1 root root 31752 Mar 22 17:29 libakode_xiph_decoder.so

But the problem exists. Is it a linking problem? Should ../bin/artsd be linked to libakode? It is not:
/usr/kde/3.3/bin # ldd artsd|grep libakode

(nothing)

It is a Gentoo system on Intel Pentium M.
Comment 13 Allan Sandfeld 2005-04-03 16:38:39 UTC
The standard procedure for debugging this sort of thing is to open a konsole. Kill the existing artsd (killall artsd) and start a new with debugging (artsd -l0). When playing a file the output will tell which plugin is used. If aKode is used, please file a new bug for akodelib.
Comment 14 esigra 2005-04-03 17:21:01 UTC
1. execute "killall artsd"
2. execute "artsd -l0"
3. start Noatun and play a file: it works (and uses akode)
4. execute "killall artsd"
5. play the file again in Noatun: it does not work (the sound is bad)

So it seems like arts works when it is started without arguments, or with "-l0", but when the file is played the second time, arts is started automatically with some arguments. "ps x" shows this:
22384 ?        S      0:00 //usr/kde/3.3/bin/artsd -F 128 -S 8192 -a alsa -d -b 16 -s 60 -m artsmessage -c drkonqi -l 3 -f
22481 ?        S      0:00 //usr/kde/3.3/bin/artsd -F 128 -S 8192 -a alsa -d -b 16 -s 60 -m artsmessage -c drkonqi -l 3 -f
22486 ?        S      0:00 //usr/kde/3.3/bin/artsd -F 128 -S 8192 -a alsa -d -b 16 -s 60 -m artsmessage -c drkonqi -l 3 -f

Has the problem something to do with that it is 3 processes? or any of the arguments?
Comment 15 Allan Sandfeld 2005-04-03 18:05:11 UTC
No. It seems you have bad settings for arts in kcontrol. 

Some broken ALSA drivers react poorly to certain buffer settings. Also try disabling full duplex.
Comment 16 esigra 2005-04-04 20:43:49 UTC
Now I changed the buffer setting from max to 487 ms, 21 fragments with 4096 bytes. With this setting the problem does not appear (the sound is good). I saw that the 8192 in the command line from "ps x" is now changed to 4096. I use the driver snd_intel8x0. So maybe I should report this to the driver developers?
Comment 17 Allan Sandfeld 2005-04-04 21:05:17 UTC
You can try. The snd_intel8x0 driver already have a very poor reputation.
Comment 18 Stefan Gehn 2005-04-04 22:33:40 UTC
sometimes the oss i8x0 drivers work better than also. The funny thing is that this seems to change in every kernel-version :/
Comment 19 FiNeX 2008-12-28 21:26:54 UTC
This bug is related to artsd which is no more supported. This bug is closed as "unmantained" for this reason.

Regards