[gstreamer-bugs] [Bug 377280] [cdiocddasrc] issue if drive endianness != machine endianness

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=377280

  GStreamer | gst-plugins-good | Ver: 0.10.4




------- Comment #40 from rocky at panix.com  2007-04-24 05:24 UTC -------
> 
> Rocky: are there some straight forward commands (like, e.g., 'cd-read
> --mode=audio --number=1000 | gzip > log1.gz') that Chris or someone else could
> run on different machines and where the output logs would be useful for you if
> they were attached to this bug report? (apologies for the awful grammer, you
> know what I mean)

The process I used is this. I'll also attach an abbreviated log of the output.

1. Make sure you have an audio cd installed. The command cd-info will verify
you this (just so there's no confusion here). It will also give you track start
information. That is:

   cd-info -A --no-device-info

You should get output like this:

Disc mode is listed as: CD-DA
CD-ROM Track List (1 - 22)
  #: MSF       LSN    Type   Green? Copy? Channels Premphasis?
  1: 00:02:00  000000 audio  false  no    2        no
  2: 02:28:45  010995 audio  false  no    2        no
               ^^^^^^^^^^^^

2. Run cd-read to dump a small bit of audio info. I usually choose track 2.

  cd-read --mode=audio --start=10995 --number=1

You'll see output something like this:
0x0000: eeff 78ff eeff 74ff f4ff 74ff f0ff 76ff   ..x...t...t...v.
0x0010: efff 72ff f0ff 74ff e9ff 78ff e8ff 73ff   ..r...t...x...s.
0x0020: e8ff 75ff eaff 74ff ebff 74ff f0ff 74ff   ..u...t...t...t.
0x0030: efff 72ff e9ff 72ff ebff 72ff e3ff 72ff   ..r...r...r...r.

Eject the audio CD. Let's say the above was on a Solaris box where things
aren't working. So now run it on a computer where things are working. In my
situation this is what I get from GNU/Linux.

Here's the corresponding output:

0x0000: 2100 b4ff 1f00 b3ff 1e00 b1ff 1f00 b2ff   !...............
...
0x0120: eeff 78ff eeff 74ff f4ff 74ff f0ff 76ff   ..x...t...t...v.
0x0130: efff 72ff f0ff 74ff e9ff 78ff e8ff 73ff   ..r...t...x...s.
0x0140: e8ff 75ff eaff 74ff ebff 74ff f0ff 74ff   ..u...t...t...t.
0x0150: efff 72ff e9ff 72ff ebff 72ff e3ff 72ff   ..r...r...r...r.
0x0160: e7ff 6fff e2ff 6cff dbff 69ff deff 65ff   ..o...l...i...e.
0x0170: e2ff 69ff dcff 68ff dcff 6eff dbff 6bff   ..i...h...n...k.
0x0180: d7ff 6bff daff 69ff d5ff 6bff d9ff 6eff   ..k...i...k...n.
0x0190: d6ff 71ff d3ff 6eff d6ff 72ff d5ff 72ff   ..q...n...r...r.

Note that on GNU/Linux things have been shifted by 0x120. But the important
part is that the data is the same: 72ff f0ff remands that rather than ff72 fff0


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=377280.