HandBrake

update: After updating to 0.9.6 i still had issues with playback on WDTV SMP. After finding some posts about this issue i ran the file through mkxtoolnix and that sorted the problem.

Hi mate,
Sorry not a Mac user but have you tried the Mac section of the forum?

Good luck

I upgraded and ran War Horse through again. I changed Constant Quality to 17 and it reduced file size from 32GB to 16.5GB. Pic quality looks good on computer. Will test it out on WDTV a little later.
Thanks for the help people

Cheers

Thanks Guys

Will upgrade and check it out.

The file was processed by the earlier version and it has sound it just stops and starts etc. If 0.9.5 cant do DTS HD in MKV then why would it have still worked to some degree? Wouldnt it just fail or does it still go through the motions anyway?

Hi John, here is info from the log [12:51:22] hb_init: checking cpu count [12:51:22] hb_init: starting libhb thread HandBrake 0.9.5 (2011010300) - MinGW i386 - http://handbrake.fr 4 CPUs detected Opening F:\Movies\Bluray\War Horse\War Horse.mkv... [12:51:22] hb_scan: path=F:\Movies\Bluray\War Horse\...

Hi guys, I havent posted here in a while as I havent been using HB. I have been ripping my Bluray movies with MakeMKV and putting them straight onto my HDD's (Full size without extra's and unnecessary soundtracks) for playback on WD Media Player. I decided to give one of my recent Bluray's a try on ...

thanks for the info guys, i hadnt used constant quality with my previous 5 or 6 encodes. Instead i chose target size of 15GB or thereabouts. I was just surprised that it came out so small. I havent looked at it on the big TV but looked ok on the computer monitor. Is 20 the best setting for Blu Ray a...

Hi Guys,

I used the constant quality video setting of 20 for a 20GB mkv file created off a blu ray disc. It created a file that was 2.7GB in size. I didnt change any other default settings.
why would i get a file size this small?

Thanks

i dont think your laptop would be much good for anything else whilst running handbrake as its pretty cpu intensive. it maxes out my 4 cores. even on a quad core with hyperthreading it gets up to 80 odd percent on each core.

thompson wrote:I doubt he'd be using Target File Size, as that option is both the Worst Way To Encode and, for that reason, has been removed from Handbrake after 0.9.5.

well ive used it and i dont see much of a difference. why is it the worst? what does it do for you?

you can download CPUID HW monitor here http://www.cpuid.com/softwares/hwmonitor.html which will give you a live look at what temps on your CPU and Hard drive are and what your fan speeds are. You can then run handbrake or any other CPU intensive program and monitor what temps your system is getting ...

well i mean if you put a 20GB mkv file into it, then leave everything on default under normal preset with say DTS passthru and Target size say 15000MB.

i tried this on friends i7 2600 and it was running around 60-70fps on 8 threads

wow ok. what sort of fps do you get at standard settings when working on a large mkv file taken from a bluray disc for example?

ok cool thanks John.

what sort of cpu do you use out of interest?

Hi John,

yes that had me confused.
this is what someone wrote about it in the forum i was reading.
"It's (quick sync) a dedicated device on Sandy Bridge silicon that does h264 encoding *instead* of any other encoder you'd use, like x264."

Hey guys, Quick question. If i upgrade my computer to the new sandy bridge CPU i7 2600, does that mean that quick sync will take over the encoding that handbrake does. I was just reading on a forum in Australia that someone is looking to use this new CPU because it flies though encoding at much fast...

put the movie, mentioned above, onto the media player and it looks fine. definitely sticking with this method rather than taking twice as long for little to no visible diff

ok, i just finished on a 104min blu ray mkv file. Source was 22.6GB after using Make MKV. I set Target size to 15000MB (came out at 14.2GB), DTS Passthru for audio and used the code for Very Fast. Everything else was the same under Normal Preset. It took exactly 1 hour and 20 mins to complete so tha...

So you should pick options that match your target encoding speed first, and only then pick an RF that gives you the desired quality. Also, ultrafast is crap. x264's fastest usable preset is superfast. hi rodeo if i choose say "very fast" can i just leave the RF setting at 20 for a blu ray...

i just tried on very fast and ultra fast. i used source file as a 20min simpsons episode in avi format at 176MB in size. very fast took 58 seconds, ultrafast took 40 sec and standard setting took 1m48s. very fast reduced file to 110mb but ultra fast increased to 297MB. why would it get smaller with ...

Here is the other side of encodeing, that storage and back up maintenance tasks I just got done backing up 3Tb of data, took about 20+ hours a really long file copy LOL LOL, thats pretty quick for 3TB. i had to copy 1TB of video files using 2 x usb2 external HDD and it took about 15 hours !!! MY GO...

If someone told me I could have these speeds, I would have thought they borrowed some technology from aliens :D as it used to take two days to do one movie lol, yeah maybe im being impatient. Its just that i have a large collection of movies on disc and trying to move all the across to the media pl...

hi and thanks phibertron. how much faster will say "faster" and "very fast" be in comparison to the default settings for high profile for example? Also how much quality is lost with these settings rather than default? how do i copy that code over - i cant copy and paste so i assu...

thanks again s55 i was just looking at this "Tutorial: x264 presets/tunes and HandBrake" i was a more than a little lost with this but am i to assume that if i copied any of those codes into the text box at the bottom of the Advanced Tab section that this will speed up the encoding process...

thanks s55. i should have used the search function before i tried here. i have seen video encoding programs that used the nvidia GPU's with CUDA. Ive seen comparisons done against other software and the time differences are incredible. i wonder if its possible for HB to get that soft of capability s...