How to get the fastest encoding speed

Faster encoding speed is attained with faster computers and more processors per system.
We are constantly improving our speed. Our latest released version encodes 1920x1080 source frames faster than real-time in a dual 3.6GHz Pentium. There are many reasons why your encoding speed may be slower than this such as slow, virus scan during or faulty disk access and delays in your codec that extracts frames from AVI or QuickTime files. For benchmarking our software (using our SDK or one of our HD encoders) we recommend that you duplicate our test conditions. Configure the encoder using our MP2Speed.ini and input HD YUV frames. Contact us if you have performance questions as we have included built in timers that allow benchmarking of the SDK or Stand Alone encoders right in your development environment.
(A note of interest: our first MPEG-2 encoder took 1000 seconds to encode a second of Standard Def video on the fastest PC available in 1995).

To attain the fastest encoding speed, load the encoder with M2Speed.ini and adapt the bit-rate and frame size your situations. Encoding with YUV source frames from a disk buffer should enable you to achieve the published encoding speeds. Encoding from RGB source files or via MOV or AVI files will slow down the encoding. Also, increasing the motion estimation for better quality in some videos will decrease the decoding speed. Yes there is a tradeoff between speed and quality. And our encoders provide the flexibility to optimize that decision.

How does HDProQT compare with the stand alone PC encoders ExpertHD and MPEGRepairHD?
HDProQT uses the identical MPEG encode engine as used in our PC encoders. HDProQT is easier to use as it only exposes the most significant MPEG encode options. This also makes it less flexible. For normal High Definition video content, the HDProQT MPEG output should be almost identical to that of our PC encoders. For special content such as animation, text, or high motion and complex content, our PC encoders provide additional controls that can often allow you to output better quality MPEG.

The fields are swapped on playback. Can this be fixed?
In the encode configure | Field Style selection box, select the “top field first” or the “bottom field first” option. This option instructs the decoder which field to display first.

How do I make my 24 fps content play at 30 fps?
In the encode configure | Field Style selection box, choose the “telecine” option. This causes the encoder to encode 24 fps content but instructs the decoder as to which fields to repeat in order to play back at 30 fps.

The export process exits Final Cut Pro part way through my source video
Final Cut Pro has lots of file editing options (including the addition of Slugs within your source video). Sometimes these edit points look to HDProQT like the end of the file. It is usually most reliable to use HDProQT on the QuickTime Player Pro tool as this tool can not do sophisticated editing.

How to set the encoding frame size?
The HDProQT export encodes at the identical frame size as your source video. If your video is a QuickTime Mov file, you can check the frame size in the windows properties. The “current” size is the frame size used for encoding. The Apple QuickTime Player Pro allows you to change the “current” size. This will change the encoded frame size.

How to set the encoding frame rate?
The HDProQT export encodes at the identical frame rate as your source video. Your source video must have a valid MPEG frame rate. Valid MPEG frame rates include:
23.96, 24.0, 25.0, 29.97, 30.0, 50.0, 59.94, and 60.0 frames per second

I get an “Export Failed” error at the start of my encode. What went wrong?
Apple disabled the Export Componets ability to send detailed alert messages to the user in QuickTime7 and so we write all error messages to the PtHdMpegExport.log file in the root of your boot directory. If you look at the bottom of theis file, you may see an explanation for the failure. Common demo failure messages are that the demo has expired or that your file exceeds the maximum demo length. Common release messages are that the detected frame rate is not a valid frame rate.