Closed GoogleCodeExporter closed 8 years ago
I've got two questions...
(1) Can you test against current svn if it solves your problem? There have been
quite some
changes meanwhile.
(2) Does your problem occur with the default settings as well or have you
changed any
cdparanoia parameters?
Original comment by rubyripp...@gmail.com
on 20 Jun 2008 at 10:03
Hi -
1. I can try and test against the SVN ... however, I am not really a
programmer, does
anyone have some simple CLI instructions to get me going ? I can usually
figure it
out once pointed in the right direction -- have built from source before but
can't
remember the svn syntax. (am on ubuntu 8.04)
2. I didn't change any of the settings, just selected flac and ogg with a click
... I
did try the debug/verbose options after it started happening but I actually
didn't
really notice a change ... it wasn't until I ran it via terminal that I saw
what was up.
Thanks!
PS: gone this weekend, so will have to try it next week. If there aren't
rubyripper
install instructions from the svn, I will search around and figure it out.
Original comment by damont...@gmail.com
on 20 Jun 2008 at 11:31
To use svn is quite simple. You have to install subversion first ofcourse ;)
Just go to the tab 'Source' on this page and copy-paste the shown command in a
terminal.
Then go into the directory rubyripper and run ./rubyripper_gtk.rb. No need to
install or
compile.
Original comment by rubyripp...@gmail.com
on 20 Jun 2008 at 11:50
You are right! Very easy - I already tested it out using the svn version (only
took
a second) ... anyhow, I still have the same problem with this CD: "WARNING: Flac
exited with an error..."
And from the terminal am getting the same output saying: "track7_1.wav is not a
WAVE
file" (get that for each file, obviously the track# changes)
And, again, it seems like this "wave problem" only happens when there is a
chunk that
doesn't match 2 times, starting trial #3 ... when it gets back to a track where
"Every chunk matched 2 times" the encoding works.
Damon
Original comment by damont...@gmail.com
on 20 Jun 2008 at 12:22
Could you run an svn update and then try again please? I think r237 should fix
your
problems.
Original comment by rubyripp...@gmail.com
on 20 Jun 2008 at 12:47
I can try that ...
Sorry I am clueless, but do you mean to run:
svn update http://rubyripper.googlecode.com/svn/trunk/ rubyripper-read-only
?? I have never really used svn before.
Original comment by damont...@gmail.com
on 20 Jun 2008 at 3:03
Just enter `svn update` in the same directory you previously used the svn
command. This
will update your version to the latest revision.
Original comment by rubyripp...@gmail.com
on 20 Jun 2008 at 3:07
So r241 fixed it. Was able to burn without an issue.
Thanks!
Original comment by damont...@gmail.com
on 22 Jun 2008 at 5:46
You're welcome :) Thanks for the feedback and the detailled description of your
bug report!
Original comment by rubyripp...@gmail.com
on 22 Jun 2008 at 9:02
Original issue reported on code.google.com by
damont...@gmail.com
on 20 Jun 2008 at 1:14