Jump to content

luci0m

  • Posts

    4
  • Joined

  • Last visited

  • Country

    country-ZZ

Retained

  • Member Title
    Newbie
  1. Mr Wicked, I've ripped many SACD to ISOs with a quite old rev of SacdRipper, maybe the r259. Are those ISOs OK or it worths to rip the SACD again with a newer revision of SACD-Ripper because of consistent software improvements? The ISOs extracted with sacd-ripper r259 are identical to those extracted with the r378? Are there important differences?
  2. I always download updated sources and compile the package by myself. Is there a place where I can find precompiled binaries? Anyway, it seems that sacd_daemon needs libsacd to compile, but libsacd compile returns the above error...
  3. I'm trying to compile the last revision of SACD-Ripper to update my PS3, but I'm having the following error: #error the PS3 SACD Ripper code is currently broken in the 0.30 branch. For now I advice you to use the SACD Daemon in combination with sacd_extract. I got the sources using: svn checkout http://sacd-ripper.googlecode.com/svn/trunk/ sacd-ripper-read-only What's wrong? Someone can explain me where to get the last working sources and which is the current stable version? Lucio
  4. Hi, I dowloaded the sa-cd ripper source code using: svn checkout http://sacd-ripper.googlecode.com/svn/trunk/ sacd-ripper-read-only The downloaded code is rev 275. After package compilation on my Ubuntu Linux box (having the automake-1.7 warning that I ignore) I got sacd-ripper-read-only.pkg that I succesfully installed on my CFW PS3. Running the sacd-ripper application, it shows that the version is 0.21, but I know that the last version is 0.30. Also, the PC tool to extract tracks from ISO that I compile with MSVC is named scarletbook instead of sacd-extract that I know to be the new name. Someone can help me to clarify this issues? Thank you.
×
×
  • Create New...