only half the DVD ripped, starting in the middle
Forum rules
An Activity Log is required for support requests. Please read How-to get an activity log? for details on how and why this should be provided.
An Activity Log is required for support requests. Please read How-to get an activity log? for details on how and why this should be provided.
only half the DVD ripped, starting in the middle
I have tried to rip a 2.5 hour long instructional DVD using the latest version of Handbrake on my G4 1Gigaherz iMac, OS X 10.4.1., using the iPod presets Each time it took almost 13 hours to rip, and the mp4 file began exactly in the same spot, almost 1.25 hours into the file (both in QuickTime and once transferred to the iPod.).I can't find help with this problem researching the forum. Any help now would be greatly appreciated.
Well, did you verify stuff such as the title being the correct length before encoding? It's just possible that the video is split over two titles.
It could be copy protection, but you don't mention if you ripped properly first or if HB was encoding from the DVD.
There are probably lots of possibilities that I haven't covered. Some more information may help. By the way, if 10.4.1 isn't a typo you should really upgrade your operating system.
It could be copy protection, but you don't mention if you ripped properly first or if HB was encoding from the DVD.
There are probably lots of possibilities that I haven't covered. Some more information may help. By the way, if 10.4.1 isn't a typo you should really upgrade your operating system.
Well, it'd be highly unusual for it to be split, but you're encoding an unusual DVD so I just wonderedtg wrote:I didn't check the title: I confess ignorance on that. What other information would be helpful?
Ripping with a separate app is usually good practice, HB's not great at getting over some recent copy protection so it needs a little help. Not saying that's definitely what happened here though.
The biggest thing that would hep is the log from the activity window - if the title is definitely the right length, and it seems to be HB that's choking on it, then we need to see what's been going through HB's mind!
I encoded again using 9.0: same result.
Here is the Activity:
[00:01:24] hb_init: checking for updates
[00:01:25] thread 1838c00 started ("update")
[00:01:25] latest stable: 0.7.1, build 2006022400
[00:01:25] latest unstable: 0.7.1, build 2006022400
[00:01:25] thread 1838c00 exited ("update")
[00:01:25] thread 1838c00 joined ("update")
[00:01:25] hb_init: checking cpu count
[00:01:27] hb_init: starting libhb thread
[00:01:27] thread 1838c00 started ("libhb")
Thanks.
Here is the Activity:
[00:01:24] hb_init: checking for updates
[00:01:25] thread 1838c00 started ("update")
[00:01:25] latest stable: 0.7.1, build 2006022400
[00:01:25] latest unstable: 0.7.1, build 2006022400
[00:01:25] thread 1838c00 exited ("update")
[00:01:25] thread 1838c00 joined ("update")
[00:01:25] hb_init: checking cpu count
[00:01:27] hb_init: starting libhb thread
[00:01:27] thread 1838c00 started ("libhb")
Thanks.
Here's what came up when I went back in after reading your note:
22:07:49] hb_init: checking for updates
[22:07:49] thread 1896a00 started ("update")
[22:07:49] latest stable: 0.7.1, build 2006022400
[22:07:49] latest unstable: 0.7.1, build 2006022400
[22:07:49] thread 1896a00 exited ("update")
[22:07:50] thread 1896a00 joined ("update")
[22:07:50] hb_init: checking cpu count
[22:07:50] hb_init: starting libhb thread
[22:07:50] thread 1896a00 started ("libhb")
The Activity Window is otherwise blank.
22:07:49] hb_init: checking for updates
[22:07:49] thread 1896a00 started ("update")
[22:07:49] latest stable: 0.7.1, build 2006022400
[22:07:49] latest unstable: 0.7.1, build 2006022400
[22:07:49] thread 1896a00 exited ("update")
[22:07:50] thread 1896a00 joined ("update")
[22:07:50] hb_init: checking cpu count
[22:07:50] hb_init: starting libhb thread
[22:07:50] thread 1896a00 started ("libhb")
The Activity Window is otherwise blank.