If most tools you have been using to convert your precious movies to h264 have been giving you trouble it is usually due to encoding settings set wrong or the main one you havent stripped out the menu.
Here is my guide that I use every time to convert my movies to H264.
Steps:
1. Decrypt in dvd decrypter (decrypt all of it in file mode, ifo mode is rarely needed in this case)
2. Open up clone dvd 2 click the 2nd button down. Titled "clone dvd"
3. Untick preserve menus (not doing this will fail your encoding in most encoders). Untick everything uneeded. You should have only the video, audio, wanted captions and forced captions left)
4. Write to an iso.
5. Open up in fairuse wizard, click on a preset (the ps3 one works well).
6. next a few times.
7. 7 hours later on a core 2 duo e5000 series machine with a geforce 8600gt your encoding will be finished.
You will be left with an mp4 movie encoded with h264 brilliance
Actually they are usually larger in size.
H264 is just like your divx, xvid etc. Its jsut a codec. You can have whatever dimensions you like.
Blueray DVDs use H264 (and they are not small in size by any standards).
Benefits include:
More defined colour blocks (more lifelike, notice how in some divx you can see big blocks of colour? This is nearly eliminated in H264)
I believe it is also a multi threaded
It seems to be the standard codec for anything high definition (720p and above)
Can confirm that my home compiled fairuse wizard does indeed do a great job. If you find the source code and build it for the number of processors/cores you have it will utilise the full system.
Look in the source code for the line "threads=1" and change to threads=(however many processors you want to throw at it, in my case 48!) Fairuse after undoing the code on an auto windows install does look to see how many processors are present and sets the number accordingly up to 4.. above that building your own is probably a better option.. and it can speed up the operation significantly for people with quad cores and above.
Takes me on average about 35 mins to encode a full film to x264 (I don't use the H.. it's not an open standard) using my cluster.
Originally posted by varnull: Can confirm that my home compiled fairuse wizard does indeed do a great job. If you find the source code and build it for the number of processors/cores you have it will utilise the full system.
Look in the source code for the line "threads=1" and change to threads=(however many processors you want to throw at it, in my case 48!) Fairuse after undoing the code on an auto windows install does look to see how many processors are present and sets the number accordingly up to 4.. above that building your own is probably a better option.. and it can speed up the operation significantly for people with quad cores and above.
Takes me on average about 35 mins to encode a full film to x264 (I don't use the H.. it's not an open standard) using my cluster.
Nice simple guide.. thanks.
shizz 48 thats alot of CPU power, thats not a PC its a TRANSFORMER robot - hehe
