Progress bar doesn't work correctly about rubyripper

[GoogleCodeExporter]

ugh, forgot summary again.  How about progress at 0.167%?

Original comment by [email protected] on 8 Nov 2006 at 10:36

[GoogleCodeExporter]

I don't know about the particular 0.167%, but I do know it isn't working 
correctly 
right now. I'll fix it.

Original comment by [email protected] on 8 Nov 2006 at 5:57

• Changed title: Progress bar doesn't work correctly
• Changed state: Accepted

[GoogleCodeExporter]

Fixed at revision 14.

Original comment by [email protected] on 9 Nov 2006 at 9:34

• Changed state: Fixed

[GoogleCodeExporter]

hi, i'm on debian sid, and installed rr from git (git log says "Clone of svn 
r308"),
and the progress bar stays always at 0%

Original comment by [email protected] on 27 Sep 2008 at 11:45

[GoogleCodeExporter]

i enclose a screenshot too

Original comment by [email protected] on 28 Sep 2008 at 12:15

Attachments:

• Screenshot-2.png

[GoogleCodeExporter]

This is normal in your case since the disc only has one track.  Currently 
rubyripper
only updates after the second rip of a track is completed.  

This does bring up a consideration... on discs with one long 60 minute track (I 
have
a few) a clueless user would have no idea rubyripper is working.  I always hear 
the
drive spinning and can see progress in the terminal window, but in a noisy
environment with debug off it's certainly possible that rr may appear to do 
nothing.

Original comment by [email protected] on 28 Sep 2008 at 12:38

[GoogleCodeExporter]

Well, the image ripping was sort of hacked into it, fitting the current model 
of how
to rip. To improve the progress bar, we need to improve the way of ripping. So 
wee
need sector based ripping, like mentioned in issue 240.

Original comment by [email protected] on 28 Sep 2008 at 8:45