It depends on the speed of your machine, I get around 50 to 70 FPS when ripping straight from DVD to xvid on my Power Mac Dual G5 1.8 GHz.derajfast said:so if i use handbrake, it will make it in to 1 700mb video, and not a bunch of .vob files? how long should this take do you think?
50 to 70 FPS? Right now I'm ripping a DVD folder to an H.264 file and i'm only getting 10-15 FPS on a dual 2.0ghz G5. And thats from a Video_TS folder on the hard drive, not a DVD.risc said:It depends on the speed of your machine, I get around 50 to 70 FPS when ripping straight from DVD to xvid on my Power Mac Dual G5 1.8 GHz.
h.264 is more processor consuming than divx and xvid. I usually get between 10-15 FPS doing h.264 on my dual 2GHz G5 as well.cwright said:50 to 70 FPS? Right now I'm ripping a DVD folder to an H.264 file and i'm only getting 10-15 FPS on a dual 2.0ghz G5. And thats from a Video_TS folder on the hard drive, not a DVD.
I'm not sure why it's not doing the complete encode. I had it do that once, but I just relaunched handbrake and it worked fine. Is there any crash log in the console?cwright said:haha, i guess i should have figured that out. Any ideas on why the encoder randomly quits?
I havent done much testing yet, but is it worth the extra time to encode in h.264? I would assume so... the short 7 minute clip that i actually was able to encode was amazing quality.
so how does h.264 compare to divx/xvid when it comes to video quality/file size ratio?
I usually do 2-pass, but I haven't tested the difference with that in h.264, I just did it with divx cause I knew it was better, and continue to do that now. Since I back up almost all of my movies on cd, I set it to 705mb, which results in a movie a little under 700mb (I dunno why, but that's what I got from my tests). I sometimes will do a movie at 1410mb and split it in two if it's more than a 2 hour movie.cwright said:What settings have you been using? Do you use the default 1000kbps or do you set it to a target size of 700mb? And what about 2-pass encoding? The FAQ on the handbrake website highly recommends it, but is it also really worth the extra time?
Usually I'll get between 700 and 800, but it depends on the length of the movie. If you're not concerned with fitting it on a CD, then I'd just keep it at 1000. 650 might not be bad, but it depends on how much action (fast camera panning and character movement in a shot) and the color tone of the movie... if you're in doubt you can always test by just encoding one chapter at the bit rate it tells you it would do for the whole movie.cwright said:Just out of curiosity, when you set it to 705mb target size, what bitrates does it usually end up using? When I tried a 1.5 hr movie at 700mb, it dropped the bitrate down to about 650kbps. That seems like a pretty big drop in quality from 1000kbps.
If 1000kbps is much better I would just assume use it instead and make backups on DVDs since they're so cheap nowadays.
Yep, I have done it multiple times and it works perfectly fine... though I do wish that just running one handbrake would use both processors for when I don't have multiple movies to encode at once.cwright said:Have you ever tried making duplicate copies of the handbrake app and having each one encode a different movie at the same time? Is that a smart thing to do? I thought that may be a good way to get them done faster by just letting them run simultaneously overnight.
Nope, sometimes I'll get a spike of like 108%, but normally it'll hover around 98% (this is in activity monitor where the total for using both processors would be 200%)cwright said:So when only encoding one video it doesnt support dual processors?
Theoretically it should do the two movies in the same time as it does for one, but practically it'll take a little longer, although it will be shorter than doing the two at separate times. Now I'm off for a couple of days, so if you have more questions hopefully someone else will be here to answer them for you.If thats the case, can you run two application copies at the same time with no performance hit on either one since each app would use its own processor?