Handbreaks speeds vary from 450FPS to 80FPS for no reason.

[tuprox]

I'm trying to convert a bunch of DVD's I've ripped using DVD Decrypter into ISO format. I have tried Handbrake and VidEndocer and I keep getting a strange occurance of one movie converting at something like 450FPS average (Lord of the Rings, Two Towers) and then when I try something like 21 Grams, I get 80-100FPS. I'm using the same settings, either normal or High Profile and it seems dependent upon the movie. All of the files are located on the same source, a USB 3 drive and I'm saving to an internal SATA III drive, so speed shouldn't be an issue. It seems to be extra slow on "High Profile" conversion vs "normal"

Can anyone tell me what is going on here?

Also, I was having problems with HB and VidEncoder shutting off randomly on my I7 3770k CPU so I installed the ASUS control panel that allows me to monitor and control fan speed. It was hitting 70 degrees C within a minute and with it set to high speed, I keep it around 55 degrees. I decided to install a Corsair H100, with a dual length radiator and now I'm getting temps of about 38 degrees while running encoding at full speed. How can I take advantage of this extra cooling that I have and bump up the clock cycles or something (I'm no over-clocker so I don't know the lingo). Any suggestions on this as well?

Thanks for anyone who can help!

[Selur]

If your system get's to hot it will scale down the cpu to avoid overheating.
If you system stays at 38 degree during encoding that is fine.
I wouldn't overclock the system atm., instead I would wait and see how the temprrature behaves, during summer times. (when you room temperature goes up so will your cpu temperature,... due to worse cooling)

[hello_hello]

I'm trying to convert a bunch of DVD's I've ripped using DVD Decrypter into ISO format. I have tried Handbrake and VidEndocer and I keep getting a strange occurance of one movie converting at something like 450FPS average (Lord of the Rings, Two Towers) and then when I try something like 21 Grams, I get 80-100FPS. I'm using the same settings, either normal or High Profile and it seems dependent upon the movie. All of the files are located on the same source, a USB 3 drive and I'm saving to an internal SATA III drive, so speed shouldn't be an issue. It seems to be extra slow on "High Profile" conversion vs "normal"

Can anyone tell me what is going on here?

As a reference of sorts, I just opened a 720x576 pal DVD I have on my hard drive, and without any filtering aside from Yadif deinterlacing my aging Q9450 CPU is encoding at around 35fps using x264's default settings.

The x264 settings used can have a huge effect on encoding speed. I'd stick with the High Profile preset when using HandBrake. It uses a slightly modified version of x264's default settings. Only a couple of settings differ from the defaults but they shouldn't have a huge effect. If anything they might slow encoding a little and/or increase quality a bit. The Normal Handbrake preset should be faster but the x264 settings probably don't provide the same quality. I can't give you much in the way of info aside from advising not to use it. HandBrake's "reset all" button under "Advanced" should give you x264 defaults.

If the video being encoded needs de-interlacing etc it could slow encoding a little, but I doubt HandBrake's filters should slow the process too noticeably. Why one particular movie is converting so quickly I don't know. What's the quality of the encode like?

Given you're opening ISO files maybe try using a compression program (TugZip comes to mind) to extract the contents of an ISO file. You'll end up with the usual collection of DVD files on your drive. Try encoding them instead to see if the encoding speed changes.

Anyway, my suggestion would be to use x264's default settings or HandBrake's High Profile with a CRF value you're happy with. VidCoder is an alternative HandBrake GUI you might also want to try. It lets you use x264's built in speed presets and tunings (HandBrake doesn't). The default speed preset is "medium". Changing the speed preset basically changes some of x264's advanced settings accordingly (although VidCoder doesn't seem to show you the changes as other encoder GUIs do). The slower the preset, the slower the encoding, but the quality should improve for a given file size. The rule of thumb is to basically pick the slowest present you can live with (generally I use medium for HD and slow for SD as my PC isn't all that fast) and then choose the CRF value which gives you the quality you're after.

It's fairly hard to advise how to overclock without at least know the CPU and MB involved. Many newer MB's come with their own software which can automate overclocking, although not generally the budget models. If your MB can overclock, Google for it along with "overclocking". Chances are you'll find several reviews which describe the overclocking process in reasonable detail.

[jagabo]

one movie converting at something like 450FPS average (Lord of the Rings, Two Towers) and then when I try something like 21 Grams, I get 80-100FPS.

21 Grams may have gone through a poor PAL to NTSC conversion. Handbrake may be doing more filtering trying to fix it. I suspect there's nothing wrong with your system or the software.

[tuprox]

My system is running on an Asus P8Z77-Deluxe with a I7 3770K, 32GB RAM, with a Corsair H100 (dual 120mm fan) liquid cooling system, that seems to keep the temp REALLY low. At first with normal h.264 settings, I would get to 70 degrees C and 100% capacity in 1-2 minutes. Now I stay around 35 degrees C and 55-60% CPU usage during encoding. I'd like to have it use 100% if it would go faster, IDK how to do that.

I'll check on the over-clocking with this system and I think I should be OK with it with this cooling system.

As for the question about the encoding at 450FPS, it was excellent! It didn't have a ton of compression, I was using CR-20 and it looked almost like the original, basically I couldn't tell the difference. File size was 1,800GB to 2,100GB.

I'm using Vid Encoder with set file size as it seems to fit my needs ATM. I just need to figure out how to add sub titles if that is possible, are those SRT files or something that are ripped from the DVD?

[theewizard]

i think your mis-construing the data

you Were at 100% capacity, because the HOT CPU could not run at full speed

IMO you now read 55% capacity because, even though the video is still being processed at 100fps, the cpu has more capacity for Other things

you are NOT going to get a higher FPS, because of the condition of the video file and the needed filtering to retain max quality

the extra processing steps consume cpu cycles, limiting the thruput fps

[hello_hello]

My system is running on an Asus P8Z77-Deluxe with a I7 3770K, 32GB RAM, with a Corsair H100 (dual 120mm fan) liquid cooling system, that seems to keep the temp REALLY low. At first with normal h.264 settings, I would get to 70 degrees C and 100% capacity in 1-2 minutes. Now I stay around 35 degrees C and 55-60% CPU usage during encoding. I'd like to have it use 100% if it would go faster, IDK how to do that.

What's changed? Aside from the cooling? It won't effect CPU usage. There must be a bottleneck somewhere. Unless you're using some really slow filtering and the encoder needs to sit around and wait, which most of us generally don't, the x264 encoder should be able to keep your CPU working pretty hard.
70 degrees is probably on the warm side but not necessarily too hot. I've got an older Intel dual core using the stock cooler which is slightly overclocked and while I don't use it for encoding much these days if I do it'll sit on 75 degrees running at 100% for hours on end on a hot day. Even my quadcore, which doesn't have the greatest cooling (better than the Intel cooler though) sits on 60-65 degrees when it working hard and it's sometimes done so for days at a time. I don't know a lot about the I7 series but the older Core2 Intel CPUs have a maximum core temperature of around 100 to 110 degrees before they start to slow themselves down. You can use RealTemp to monitor Intel CPUs. It'll show you what Intel call "Distance to TJMax" which is basically how much headroom you've got till you hit maximum temperature. My CPU cores are currently running at about 50 degrees and I've still got 50 degrees to go. http://www.techpowerup.com/realtemp/

Anyway, unless you've changed something else maybe use MediaInfo to check the encoder settings saved to the video stream after you've run an encode to make sure the number of threads hasn't somehow been set to something silly like "1". By default x264 should use 1.5 times the number of logical processors you have, so for a 4 core CPU with hyperthreading it should be threads=12. If that's okay then something else in the encoding chain must be slowing things down.

I'm using Vid Encoder with set file size as it seems to fit my needs ATM. I just need to figure out how to add sub titles if that is possible, are those SRT files or something that are ripped from the DVD?

If you're running 2 pass encoding are you sure 450fps wasn't just for the first pass? It could possibly be much faster than the second pass.
I don't think HandBrake will encode srt subtitles so VidCoder probably won't either, but I'm not suire what subtitle formats it supports. SRT subtitles are pretty much just text files with an srt extension (many subtitle formats are). DVD subtitles are actually images which need to be converted to text using character recognition software.... hence the majority of srt subtitles on the internet being riddled with OCR and spelling errors. You can convert subtitles from one format to another using a program such as Subtitle Edit or Subtitle Workshop. Both will open subtitles using multiple formats and save them as a different type so it shouldn't be too hard to get them into a Handbrake friendly format. I don't know if HandBrake can encode DVD subtitles in their native format but one of those program can convert DVD subtitles using OCR (I can't remember which one) but it can be a painstaking process if you want to get it right as you need to correct the many mistakes the OCR software will make as it converts.