Version: 2.2.1 (using KDE KDE 3.1) Installed from: Compiled From Sources Compiler: gcc-3.2 (GCC) 3.2 (Mandrake Linux 9.0 3.2-1mdk) KDE 3.1 compiled for Athlon optimization OS: Linux I had this bug in KDE vrsion 3.0 (mandrake 9.0 standard RPMs) and now that I compiled KDE 3.1 from sources, this bug still exists. Noatun displays incorrect bitrate for all my OGG files (while ogg123 and xmms show a correct variable bitrate while playing them). Here are example lines from playlist: [Catharsis] - Sunrise Beast (1965219kbps) 04:57 [Catharsis] - Crusader (1994022kbps) 04:52 While ogginfo reports the following information for these files: Nominal bitrate: 192,003000 kb/s Average bitrate: 190,080065 kbps for the first one, and Nominal bitrate: 192,003000 kb/s Average bitrate: 191,304142 kbps for the second one. These are just examples, there is no OGG file that I have for which noatun would show a correct bitrate. All my OGGs were grabbed by grip and encoded with oggenc with the following list of options: "-o %m -a "%a" -l "%d" --genre "%G" -b "%b" -d "%y" -N "%t" -t "%n" %w -q 6". In version 3.0 noatun even displayed negative bitrate for some files. In version 3.1 it doesn't display bitrate for some files at all. Versions of libogg and libvorbis are the following: libogg0-devel-1.0-3mdk libogg0-1.0-3mdk libvorbis0-1.0-6mdk libvorbisenc2-1.0-6mdk libvorbisfile3-1.0-6mdk libvorbis0-devel-1.0-6mdk
I have this bug too. I'm using SuSE 8.1 with the RPMs found in ftp://ftp.kde.org/pub/kde/stable/3.1/SuSE/ix86/8.1 The Ogg and vorbis packages are: libvorbis-1.0-32 libvorbis-devel-1.0-32 vorbis-tools-1.0-48 libogg-1.0-31 libogg-devel-1.0-31 The ogg's I've tested recently were created with oggenc of the vorbis-tools-1.0-48-package.
Created attachment 1150 [details] Showing an incorrect bitrate The file being played has a nominal bitrate of 128 kbps
I too see this on SuSE 8.1.
I don't think this has anything to do with filedialogs.
research indicates that this is a gcc 3 bug. It definitely exists on gcc 3.2.0. Renchi Raju (irc) tried compiling libvorbis with -O3 -march=athlon-mp -mcpu=athlon-mp on gcc 3.2.2 and reported correct (i.e., reasonable) bitrates. I recompiled libvorbis with -O0 and the values were correct.
also -O3 -ffast-math works with gcc 3.2.2. I'm closing this Bug Report in the hopes that this bug will vanish as we move away from gcc 3.2.0 to 3.2.2 (and 3.3).
Created attachment 1253 [details] Still incorrect bitrate with noatun compiled in mandrake 9.1 Just installed Mandrake 9.1. It has KDE 3.1 with Noatun 2.2.1. Compiler that is used is gcc 3.2.2: gcc (GCC) 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk) Copyright (C) 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Noatun in Mandrake 9.1 still shows incorrect bitrate for all my OGG files (all other applications show correct bitrate).
1) are you certain that ogg was recompiled in 8.2? (ask MDK) 2) Add new files to the playlist. It doesn't reread the tags when you startup again.
when I said 8.2, I meant 9.1 ;)
Yes it seems that mandrake didn't recompile libvorbis package after some fix in gcc. Package build date is Jan 08 2003, quite old considering that gcc build date is Mar 03 2003. I recompiled libvorbis src.rpm package and now everything seems to work fine. Go figure. Thank you.