Abcde Scsi Read Error
Contents |
by: [ date ] [ thread ] [ subject ] [ author ] I was hoping for a little help in solving a problem. Linux Debian - Unstable cdparanoia III release 9.8 (March 23, 2001) abcde v2.0.3. 1ghz scsi_read error AMD with 512mb RAM HP 9100+ CD Writer At the bottom of this email is
Abcde Input Output Error
3 examples I've taken from rips: a. The first is a standard song rip that goes very well. 70% of all my transport error medium reading data from medium rips look like this one. b. Hidious and messy and takes about 4 hours to rip the single song. 5% of all rips are like this. c. Averagely horrible, taking about an hour to rip a song. 25% look like this. The problem is, my cds are perfect quality - zero scratches and I can rip them perfectly in windows. But in linux I'm having problems as can be seen in my examples below. Given the huge amount of scsi related spam I get I naturally decided that was the cause, so I went to the website and found out that /dev/sg0 should be used. Presently I use /dev/scd0. I cant use sg0, it cant read the cdrom. All finished ogg files sound fine when played (except for the 5% that fail outright) - this is not the problem. What is the problem is the HUGE amount of spam and the extra time it takes to rip and encode due to this spam. 25% of all songs I rip takes an HOUR to complete. 5% of all songs I rip NEVER finish (I give up about the 5 hour mark) Any ideas?
=======EXAMPLES============== ----------------------------------------------------------------------- ------------------- [[ a. Here is an common example of a single song rip ]] Grabbing track 1: Communication Breakdown... cdparanoia III release 9.8 (March 23, 2001) (C) 2001 Monty
Unanswered Index »Help & Support (Crunchbang 11 "Waldorf") »CD ripping - whats the deal then? Pages: 1 #1 2010-12-08 12:18:47 silince #! CrunchBanger Registered: 2010-07-22 Posts: 166 CD ripping - whats the deal then? I've seen a few topics on this without much of a clear conclusion.I've tried a few applications to rip audio CDs (ripperx, sound-juicer and another whose name escapes me), and its either really slow, or I get a message http://lists.xiph.org/pipermail/paranoia/2002-June/000815.html saying that the disc can't be read. Is there a recommended ripper for statler, or do I need to just keep experimenting with things like chmod-ing my cdrom? I can't post some outputs when I get home if that help... Debian Wheezy on VeryPC Low Energy Desktop | Elementary on Lenovo Thinkpad SL510 | #! on http://crunchbang.org/forums/viewtopic.php?id=10438 Lenovo Ideapad S205 | Raspbmc on Pi | Linux Mint 17 XFCE on Lenovo W530. Offline Help fund CrunchBang, donate to the project! #2 2010-12-08 13:17:43 GuruX #! Die Hard Registered: 2009-01-18 Posts: 527 Re: CD ripping - whats the deal then? Have you tried ripit? This thread gives you some info on it. It's in the squeeze repo.http://forums.debian.net/viewtopic.php?t=36826 Offline #3 2010-12-08 13:30:21 rabidjoe #! Member From: Under My Hat Registered: 2010-09-24 Posts: 78 Re: CD ripping - whats the deal then? I use pacpl to rip my CD's to MP3....pacpl --rip all --to mp3 --bitrate 320 --nocddb --device=/dev/sr0 --outdir /home/youdir Offline #4 2010-12-08 14:13:19 luvva_cuppa #! CrunchBanger Registered: 2009-09-06 Posts: 214 Re: CD ripping - whats the deal then? abcde command line ripper does the trick for me. It's simple and effective. A perfect partner for mocp (music on console player). And yes, I am a fan of KMandla.http://kmandla.wordpress.com/software/ "In spite of the cost of living, it's still popular."Kathleen Norris Offline #5 2010-12-08 15:44:35 silince #! CrunchBanger
(March 23, 2001)abcde v2.0.3.1ghz AMD with 512mb RAMHP 9100+ CD WriterAt the bottom of this email is 3 examples I've taken from rips:a. The http://paranoia.xiph.narkive.com/kEubB4R6/scsi-read-error-guidance-required first is a standard song rip that goes very well. 70% of all myrips look like this one.b. Hidious and messy and takes about 4 hours to rip the single song. 5%of all rips are like this.c. Averagely horrible, taking about an hour to rip a song. 25% look likethis.The problem is, my cds are perfect quality read error - zero scratches and I canrip them perfectly in windows. But in linux I'm having problems as canbe seen in my examples below. Given the huge amount of scsi related spamI get I naturally decided that was the cause, so I went to the websiteand found out that /dev/sg0 should be used. Presently I use /dev/scd0. Icant use abcde scsi read sg0, it cant read the cdrom.All finished ogg files sound fine when played (except for the 5% thatfail outright) - this is not the problem. What is the problem is theHUGE amount of spam and the extra time it takes to rip and encode due tothis spam. 25% of all songs I rip takes an HOUR to complete. 5% of allsongs I rip NEVER finish (I give up about the 5 hour mark)Any ideas?=======EXAMPLES==============------------------------------------------------------------------------------------------[[ a. Here is an common example of a single song rip ]]Grabbing track 1: Communication Breakdown...cdparanoia III release 9.8 (March 23, 2001)(C) 2001 Monty <***@xiph.org> and XiphophorusReport bugs to ***@xiph.orghttp://www.xiph.org/paranoia/Ripping from sector 0 (track 1 [0:00.00])to sector 11204 (track 1 [2:29.29])outputting to /home/public/ogg/abcde.d411160f/track1.wav(== PROGRESS == [> | 000231 00 ] == :^D .==) scsi_read error: sector=261 length=13 retry=0Sense key: 3 ASC: 2 ASCQ: 0Transport error: Medium reading data from mediumSystem error: Input/output errorscsi_read error: sector=261 length=6 retry=1Sense key: 3 ASC: 2 ASCQ: 0Transport error: Medium reading data from mediumSystem error: Input/output errorscsi_read error: sector=261 length=3 retry=