Closed
Description
I've seen a number of people running into the same issue when using whopper (whipper-team/whipper#234), and one user going as far as just removing errors checks in the source code to force cd-paranoia to continue working (whipper-team/whipper#234 (comment)).
My hardware is HL-DT-ST GH22NS50, and in the AccurateRip database, it is expected that its read offset is +667. However, when using that number with cd-paranoia, it stops saying that the time/sector goes beyond end of my specified track:
$ cd-paranoia --stderr-progress --sample-offset=667 --force-cdrom-device /dev/sr0 1[00:00:00.00]-1[00:03:13.44] /tmp/tmpoEuyVd.track01.offset667.whipper.wav
Sending all callback output to stderr for wrapper script
cdparanoia III release 10.2 libcdio 2.0.0 x86_64-pc-linux-gnu
(C) 2001 Monty <[email protected]> and Xiphophorus
(C) 2004, 2005, 2008 Rocky Bernstein <[email protected]>
(C) 2014 Robert Kausch <[email protected]>
Report bugs to [email protected]
Time/sector offset goes beyond end of specified track.
However, Xiph's cdparanoia works ok:
$ cdparanoia --stderr-progress --sample-offset=667 --force-cdrom-device /dev/sr0 1[00:00:00.00]-1[00:03:13.44] /tmp/tmpoEuyVd.track01.offset667.whipper.wav
Sending all callbacks to stderr for wrapper script
cdparanoia III release 10.2 (September 11, 2008)
Ripping from sector 1 (track 1 [0:00.00])
to sector 14520 (track 1 [3:13.44])
outputting to /tmp/tmpoEuyVd.track01.offset667.whipper.wav
##: 0 [read] @ 25872
(== PROGRESS == [> | ...... 00 ] == :^D . ==) ##: 0 [read] @ 57624
(== PROGRESS == [> | ...... 00 ] == :^D o ==) ##: 0 [read] @ 89376
(== PROGRESS == [> | ...... 00 ] == :^D 0 ==) ##: 0 [read] @ 121128
(== PROGRESS == [> | ...... 00 ] == :^D O ==) ##: 0 [read] @ 152880
(== PROGRESS == [> | ...... 00 ] == :^D 0 ==) ##: 0 [read] @ 184632
##: 0 [read] @ 216384
(== PROGRESS == [> | ...... 00 ] == :^D o ==) ##: 0 [read] @ 248136
(== PROGRESS == [> | ...... 00 ] == :^D . ==) ##: 0 [read] @ 279888
(== PROGRESS == [> | ...... 00 ] == :^D ==) ##: 0 [read] @ 311640
(== PROGRESS == [> | ...... 00 ] == :^D . ==) ##: 0 [read] @ 343392
##: 0 [read] @ 375144
##: 0 [read] @ 406896
...
And following the advice to leave out the time argument to cd-paranoia to guess, I end up with a very weird time signature indeed (but the sector number does match and the track is correctly ripped):
$ cd-paranoia --stderr-progress --sample-offset=667 --force-cdrom-device /dev/sr0 1 /tmp/tmpoEuyVd.track01.offset667.whipper.wav
Sending all callback output to stderr for wrapper script
cdparanoia III release 10.2 libcdio 2.0.0 x86_64-pc-linux-gnu
(C) 2001 Monty <[email protected]> and Xiphophorus
(C) 2004, 2005, 2008 Rocky Bernstein <[email protected]>
(C) 2014 Robert Kausch <[email protected]>
Report bugs to [email protected]
Ripping from sector 1 (track 1 [0:00.00])
to sector 14520 (track 2 [0:00.-1])
outputting to /tmp/tmpoEuyVd.track01.offset667.whipper.wav
##: 0 [read] @ 21168
(== PROGRESS == [> | ...... 00 ] == :^D . ==) ##: 0 [read] @ 50568
(== PROGRESS == [> | ...... 00 ] == :^D o ==) ##: 0 [read] @ 79968
(== PROGRESS == [> | ...... 00 ] == :^D 0 ==) ##: 0 [read] @ 109368
##: 0 [read] @ 138768
(== PROGRESS == [> | ...... 00 ] == :^D O ==) ##: 0 [read] @ 168168
(== PROGRESS == [> | ...... 00 ] == :^D 0 ==) ##: 0 [read] @ 197568
(== PROGRESS == [> | ...... 00 ] == :^D o ==) ##: 0 [read] @ 226968
(== PROGRESS == [> | ...... 00 ] == :^D . ==) ##: 0 [read] @ 256368
...
Metadata
Metadata
Assignees
Labels
No labels