title
Products            Buy            Support Forum            Professional            About            Codec Central
 
Results 1 to 6 of 6

Thread: Slient .wav files

  1. #1

    Join Date
    Nov 2015
    Posts
    3

    Slient .wav files

    Help!

    Hi I've tried ripping with various settings and the resultant .wav files are all silent. I've ripped the same CD in secure mode on EAC and the files are fine.
    Secure ripping is taking forever too - a day to rip a CD! Is that normal?
    I'm using Interpolate - the whole reason I bought dbPoweramp as I have a lot of fairly scratched CDs.

    Technical :-
    Windows 10 x64 latest build all updated
    Intel Core i5-3570K
    4GB DDR3-1600 / PC3-12800 DDR3 SDRAM UDIMM

    Drive :-
    Manufacturer: ATAPI
    CD Drive: iHAS124 F
    Firmware: CL02
    Serial: 2014/10/15 14:22
    Maximum Speed: 8467 KB/sec (x47)
    Current Speed: 8467 KB/sec (x47)
    Spin-down After: 2 minutes
    Buffer Size: 512 KB
    Accurate Stream: Yes
    C2 Error Pointers: Yes
    Reads ISRC: Yes
    Reads UPC: Yes

  2. #2
    dBpoweramp Guru
    Join Date
    Feb 2014
    Posts
    1,740

    Re: Slient .wav files

    Try to disable C2 Error Pointers.


    Dat Ei

  3. #3

    Join Date
    Nov 2015
    Posts
    3

    Re: Slient .wav files

    Quote Originally Posted by Dat Ei View Post
    Try to disable C2 Error Pointers.


    Dat Ei
    Still taking a day but now every track says Error in red :-(

    At least I can hear the .wav files but this is unusable with the time to rip and indeterminate errors.

  4. #4
    Administrator
    Join Date
    Apr 2002
    Posts
    43,859

    Re: Slient .wav files

    Set the ripping method to 'Burst' as a test.

  5. #5

    Join Date
    Nov 2015
    Posts
    3

    Re: Slient .wav files

    Burst works fine and quickly but I want to have secure rips or as close as possible with interpolation to remove any possible clicks.

  6. #6
    Administrator
    Join Date
    Apr 2002
    Posts
    43,859

    Re: Slient .wav files

    It suggests there is an option set on the secure ripping options page which is causing it not to work, such as C2 pointers, or overread into lead in / out.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •