On Sat, 27 Jan 2018 17:27:33 -0600
"Martin McCormick" wrote:
> deloptes writes:
> > IMO read error means CD is bad, dirty scratched whatever
> >
> > regards
>
> Thank you but I think it is confused as the disk is brand new,
> part of a set and
Hi,
David Wright wrote:
> $ od cd-track00-432975-2/track00.cdda.wav > /tmp/od
> 000 044522 043106 027524 01 040527 042526 066546 020164
Octal. Argh. gdb and man ascii to the rescue.
R I F F T / \001 \000 W A V E f m t
Looks like a .wav header:
On Wed 31 Jan 2018 at 12:42:20 (+0100), Thomas Schmitt wrote:
> Hi,
>
> i wrote:
> > > The "problem CD" is pure audio.
>
> Jonathan Dowland wrote:
> > I thought you'd identified that track 17 (at least) was marked as a data
> > track, but I might not have been following the discussion closely
>
Hi,
i wrote:
> > The "problem CD" is pure audio.
Jonathan Dowland wrote:
> I thought you'd identified that track 17 (at least) was marked as a data
> track, but I might not have been following the discussion closely
> enough.
To my memory this was shown as example of a "no problem" CD.
On Mon, Jan 29, 2018 at 12:03:27PM +0100, Thomas Schmitt wrote:
Hi,
i wrote:
> They saw a CD and tried UDF. Cluelessly and in vain.
Jonathan Dowland wrote:
They did that because of the fstab line which specified udf, and the
presence of a data track on the CD.
The "problem CD" is pure
Hi,
allthough it quite works now, there remain some riddles to me in your report.
Martin McCormick wrote:
> There were 6 CD's in the book and the first 4
> all had that spoiler file in track 0 and audio files the rest of
> the way to LOUT.
Normally track counting begins by 1. Sometimes at a
"Thomas Schmitt" writes:
> This is a READ(10) attempt, which a system with a clue should not try
> on tracks with CONTROL value 0.
> I get a more standards compliant Sense Code from my ASUS BW-16D1HT burner
> than Martin McCormick got from his SONY CRX140E, which seems to be
Hi,
deloptes wrote:
> it is really a pity - as those things are just bits
Actually its pits and lands.
The bits emerge only after detecting pit-land changes, converting 14
nearly-bits to 8 quite-really-bits and then decoding them from Reed-
Solomon representation to even fewer payload bits.
Charlie Gibbs writes:
> On 28/01/18 01:04 AM, Thomas Schmitt wrote:
>
>
> Martin McCormick wrote:
>
>
> cdparanoia [...] plays but you lose the individual track
> boundaries as
> you see in the listing above.
>
>
> I guess you'd need to read the
Jonathan Dowland wrote:
> Good luck reading audio track data from CD-ROMs with dd. Or subcode
> information. Tip: you can't.
:D you are correct - it is really a pity - as those things are just bits
On Monday, January 29, 2018 04:51:33 AM Jonathan Dowland wrote:
> On Sun, Jan 28, 2018 at 01:27:08AM +0100, deloptes wrote:
> >in any case no one can take the power of dd away :D
>
> Good luck reading audio track data from CD-ROMs with dd. Or subcode
> information. Tip: you can't.
I guess I'll
Hi,
i wrote:
> > They saw a CD and tried UDF. Cluelessly and in vain.
Jonathan Dowland wrote:
> They did that because of the fstab line which specified udf, and the
> presence of a data track on the CD.
The "problem CD" is pure audio. No indication on Table-Of-Content level
that there would be
On Sun, Jan 28, 2018 at 10:04:22AM +0100, Thomas Schmitt wrote:
Martin McCormick wrote:
I thought it was udf because one of the two systems I
tried it on spewed out a reference to udffs
They saw a CD and tried UDF. Cluelessly and in vain.
They did that because of the fstab line which
On Sun, Jan 28, 2018 at 01:27:08AM +0100, deloptes wrote:
in any case no one can take the power of dd away :D
Good luck reading audio track data from CD-ROMs with dd. Or subcode
information. Tip: you can't.
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC
Hi,
Charlie Gibbs wrote:
> My CD player, however, likes CD-DA much better. Insists on it, actually.
This illustrates the general decay of moral and good manners.
CD drives should be seen but not heard.
Have a nice day :)
Thomas
On 28/01/18 01:04 AM, Thomas Schmitt wrote:
Martin McCormick wrote:
cdparanoia [...] plays but you lose the individual track boundaries as
you see in the listing above.
I guess you'd need to read the tracks one by one, like
cdparanoia -d $drivespec "1-1" track_1.wav
cdparanoia -d
Hi,
so the problem CD is just a pure audio CD with no filesystem to mount.
Entertainment CD pliayers should have no problem with it. Operating systems
and system demons should be able to recognize its state, and thus avoid
the futile mount attempts.
Martin McCormick wrote:
> cdparanoia [...]
May I suggest cdparanoia? I'm calling it with Python, and it's a
lovely piece of software. Makes wavs of everything I've thrown at it,
with good info on the screen and all the tracks are on my HDD, with
no silliness.
--
Glenn English
"Thomas Schmitt" writes:
> I see that wodim does not display session end marks, as cdrskin does.
cdrskin to the rescue.
> With cdrskin there is an option with better readable output
>
> cdrskin -v dev=/dev/sr1 -minfo
>
> (Not to be confused with option -msinfo.)
> It
"Thomas Schmitt" writes:
> Hi,
>
> Martin McCormick wrote:
> > Here is the output from a normal music CD.
> > track: 1 lba: 0 (0) 00:02:00 adr: 1 control: 0 mode: 0
> > track: 2 lba: 19142 (76568) 04:17:17 adr: 1 control: 0 mode: 0
>
> These are
Martin McCormick wrote:
> I think there is a deliberate protocol violation in the
> control data that is there to discourage copying as there are
> just too many brand new disks (6 all together) for them all to be
> duds. I do agree that damaged disks do normally throw these
> errors but it also
Hi,
Martin McCormick wrote:
> Here is the output from a normal music CD.
> track: 1 lba: 0 (0) 00:02:00 adr: 1 control: 0 mode: 0
> track: 2 lba: 19142 (76568) 04:17:17 adr: 1 control: 0 mode: 0
These are audio tracks. No filesystem. Neither ISO 9660 nor UDF.
>
deloptes writes:
> IMO read error means CD is bad, dirty scratched whatever
>
> regards
Thank you but I think it is confused as the disk is brand new,
part of a set and all of them spew errors when placed in a drive.
They also play flawlessly in a DVD player which is one of
Martin McCormick wrote:
> sr 1:0:1:0: [sr1] <> ASC=0xc6 ASCQ=0x2ASC=0xc6 ASCQ=0x2
> sr 1:0:1:0: [sr1] CDB: Read(10): 28 00 00 05 06 a2 00 00 02 00
> end_request: I/O error, dev sr1, sector 1317512
> Buffer I/O error on device sr1, logical block 164689
>
> It looks like it probably can read
"Thomas Schmitt" writes:
> First issue will be to clarify the true nature of this CD medium.
> Audio CDs (CD-DA) are recorded without any filesystem. There are "tracks"
> which usually each contain one piece of music. Tracks may be grouped
> by sessions. But that's rare with
Hi,
Bernd Gruber wrote:
> I'm not sure, but isn't there a certain package / library that's needed for
> udf-support?
Jessie's kernel 3.16 should have full UDF support by the code in:
https://github.com/torvalds/linux/tree/64aa90f26c06e1cb2aacfb98a7d0eccfbd6c1a91/fs/udf
fs/udf/Kconfig points
Hi,
Martin McCormick wrote:
> I started to play an audio CD which is part of a book and ran in
> to an interesting problem. The CD is recorded using the UDF file
> system and it does play perfectly on a DVD player.
First issue will be to clarify the true nature of this CD medium.
Audio CDs
27 matches
Mail list logo