On Fri, Jul 02, 2021 at 10:04:04PM +0100, Richmond wrote:
> Greg Wooledge writes:
> > Audio CDs do not have a file system. There's nothing to mount. There
> > are no ".wav files".
> Using Caja file manager I have put in the localtion bar (or rather it put in)
>
> cdda://sr0/
>
> This shows
Greg Wooledge writes:
> On Fri, Jul 02, 2021 at 08:51:54PM +0100, Richmond wrote:
>> Michael Lange writes:
>>
>> > So, does anyone know about a way to verify the integrity of burned
>> > audio-CDs?
>> >
>>
>> This is a bit speculative because I cannot test it, but:
>>
>> k3b and brasero have
On Fri, Jul 02, 2021 at 08:51:54PM +0100, Richmond wrote:
> Michael Lange writes:
>
> > So, does anyone know about a way to verify the integrity of burned
> > audio-CDs?
> >
>
> This is a bit speculative because I cannot test it, but:
>
> k3b and brasero have options to verify written cd.
>
>
Michael Lange writes:
> So, does anyone know about a way to verify the integrity of burned
> audio-CDs?
>
This is a bit speculative because I cannot test it, but:
k3b and brasero have options to verify written cd.
I think you could verify using diff, i.e. diff /dev/cdrom file.iso
Or you
Hi,
On Tue, 29 Jun 2021 10:32:04 +0200
Linux-Fan wrote:
(...)
> I usually go for this kind of command:
>
> cmp whatever.iso /dev/sr0
>
> If it reports "EOF on whatever.iso" its fine :)
I think this is similar to that recipe from the debianforum, only that
the latter seems to be a
Michael Lange writes:
[...]
I discovered then that, unless I missed something, that verifying the
success of the burning procedure appears to be surprisingly (to me at
least) non-trivial. For data-discs I finally found a recipe that seems to
work in the archives of debianforum.de :
$ cat
Hi,
On Thu, 24 Jun 2021 09:19:43 +0200
"Thomas Schmitt" wrote:
(...)
> In any case, test it with all your intended use cases, as soon as it
> arrives.
Thanks, that definitely sounds like good advice (I had no idea that these
drives are so cheap these days, no wonder that they leave testing to
> On June 25, 2021 at 5:49 AM Thomas Schmitt wrote:
>
>
> Hi,
>
> Michael Lange wrote:
> > If someone here can report about experience (good or bad) with specific
> > make and models (still not sure whether the next drive will be a DVD- or
> > BD-writer), it would be welcome...
>
> In
Hi,
Michael Lange wrote:
> If someone here can report about experience (good or bad) with specific
> make and models (still not sure whether the next drive will be a DVD- or
> BD-writer), it would be welcome...
In general i'd buy any brand of full height drives.
I currently run 3 LGs, 2 ASUS, 1
Hi,
On Fri, 25 Jun 2021 08:44:58 +0200
"Thomas Schmitt" wrote:
(...)
> > But maybe this is to be expected when cdrskin runs with the
> > modesty_on_drive=... option?
>
> Yes. That option causes frequent inquiry of the drive's buffer status.
> At the time of above READ BUFFER CAPACITY command
Hi,
i wrote:
> >modesty_on_drive=1:min_percent=75:max_percent=80
Michael Lange wrote:
> burning failed with this option, too (two out of three runs).
Looks like you really need a new drive.
> cdrskin: FATAL : SCSI error on write(299,13): See MMC \
> specs: Sense Key 5 "Illegal
Hi,
On Thu, 24 Jun 2021 14:18:08 +0200
"Thomas Schmitt" wrote:
> Hi,
>
> i got an SCSI log of a failed burn run from Michael Lange.
>
> No artsy dance between drive and libburn is to see, which could explain
> a misunderstanding between both.
> The drive buffer becomes full, after 17 seconds
Hi,
i got an SCSI log of a failed burn run from Michael Lange.
No artsy dance between drive and libburn is to see, which could explain
a misunderstanding between both.
The drive buffer becomes full, after 17 seconds some few sectors seem to
have been actually written, and then the second next
Hi,
i am making theories how the drive firmware could perceive any illegal
request while WRITE(10) commands come in. (Senile dementia is not among
the usual signs of drive ageing. Rather they go blind or suffer stroke.)
I would be interesting to see the SCSI log of a failed dummy burn. I.e. with
Hi,
On Thu, 24 Jun 2021 09:19:43 +0200
"Thomas Schmitt" wrote:
(...)
> > $ cdrskin dev=/dev/sr0 -minfo 2>&1 | tee -i /tmp/cdrskin_minfo
> > ...
> > Vendor_info: 'PLEXTOR'
> > Identifikation : 'DVDR PX-810SA'
> > Revision : '1.01'
>
> According to Google this drive iseems to have
Hi,
i wrote:
> > What were your exact cdrskin arguments ?
Michael Lange wrote:
> cdrskin -v -dummy -eject dev=/dev/sr0 -sao speed=10 '04 Pujeva.wav' \
>sao_pregap=75 '05 New Pulse.wav' sao_pregap=225 '07 Rocket \
>Keronian.wav' '10 Dodo.wav'
Looks quite unsuspicious. The
Hi,
thanks for the quick responese!
On Wed, 23 Jun 2021 20:58:17 +0200
"Thomas Schmitt" wrote:
> Hi,
>
> Michael Lange wrote:
> > cdrskin: FATAL : SCSI error on write(442,13): See MMC specs: Sense Key
> > 5 "Illegal request", ASC A8 ASCQ 04
>
> The hex number triple (5, A8, 04) is the reply
Hi,
Michael Lange wrote:
> cdrskin: FATAL : SCSI error on write(442,13): See MMC specs: Sense Key
> 5 "Illegal request", ASC A8 ASCQ 04
The hex number triple (5, A8, 04) is the reply of the drive to command
WRITE(10) after 34 such commands succeeded. (34 = 442 / 13. 13 is the
smallest multiple
Hi,
I have recently been encountering errors while trying to burn CDDA discs;
I had previously used cdrdao for ages for this task, which (at least it
looks like that to me) hasn't really been maintained for well over 10
years, so I thought it *might* be a software bug with cdrdao.
Too bad, now I
19 matches
Mail list logo
