When I queue up more than 1 Rip job (regardless of DVDFab version, going to Apple TV 3), if there is a lot of disc activity (such as a backup running, copying M4V files to a hard drive) when the next task starts, DVDFab immediately aborts the job.
Why does DVDFab Ripper require the hard drive to be relatively idle when a rip job begins?
Why does DVDFab Ripper require the hard drive to be relatively idle when a rip job begins?
Comment