Bug 133255 - Ripping CD to OGG produces white noise on powerpc (probably endianness issue)
Summary: Ripping CD to OGG produces white noise on powerpc (probably endianness issue)
Status: RESOLVED INTENTIONAL
Alias: None
Product: kaffeine
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Mauro Carvalho Chehab
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-30 10:18 UTC by Fathi Boudra
Modified: 2016-06-06 00:21 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fathi Boudra 2006-08-30 10:18:35 UTC
Version:           0.8.1 (using KDE KDE 3.5.4)
Installed from:    Debian testing/unstable Packages
OS:                Linux

This is a forwarded bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=376025

When ripping a CD:

- chose "Rip CD"
- selected all tracks
- chose "Encode"
- selected "paranoia" CD ripping
- selected OGG quality level 6

On an i386 system, this works perfectly.  On powerpc, the OGG file is
just white noise.

I've checked ripping with cdparanoia and encoding with oggenc separately
on both systems, and both systems do it perfectly.  As a result, I
suspect an endianness issue in kaffeine, probably something like the
byte order of the ripped CD bitstream being encoded.

If you want any testing or more information, I'll be happy to do
whatever you need.
Comment 1 Mauro Carvalho Chehab 2016-06-06 00:21:11 UTC
This bug is too old, for a version < 1.3. Closing it, as the latest version is 2.0.1, and lots of things changed since version 1.2.x, including the usage of VLC as video display backend, support for DVB-T2 and ISDB-T via libVLC, etc.

You may check on the upstream version and see if the bug was solved. The README file contains instructions about how to compile it. You can find it at our git repository: 

https://quickgit.kde.org/?p=kaffeine.git 

If you find similar issues with version 2.0.1, please re-open.