Rendering from PRman to MPlay now shows frames past 1. Since v6.2.64, mplay would not increase the frame range as more frames were rendered, making it appear that the frames were not rendering. This could be worked around by manually updating the frame range.

Rendering from PRman to MPlay now shows frames past 1. Since v6.2.64, mplay would not increase the frame range as more frames were rendered, making it appear that the frames were not rendering. This could be worked around by manually updating the frame range.

Rendering from PRman to MPlay now shows frames past 1. Since v6.2.64, mplay would not increase the frame range as more frames were rendered, making it appear that the frames were not rendering. This could be worked around by manually updating the frame range.

Rendering from PRman to MPlay now shows frames past 1. Since v6.2.64, mplay would not increase the frame range as more frames were rendered, making it appear that the frames were not rendering. This could be worked around by manually updating the frame range.

MPlay now defaults to using all the phyical memory on a system minus 64Mb. If the physical memory reported is less than 128Mb, Mplay will use half instead. This is only the default, and can be user-configured.

MPlay now defaults to using all the phyical memory on a system minus 64Mb. If the physical memory reported is less than 128Mb, Mplay will use half instead. This is only the default, and can be user-configured.

MPlay now defaults to using all the phyical memory on a system minus 64Mb. If the physical memory reported is less than 128Mb, Mplay will use half instead. This is only the default, and can be user-configured.

MPlay now defaults to using all the phyical memory on a system minus 64Mb. If the physical memory reported is less than 128Mb, Mplay will use half instead. This is only the default, and can be user-configured.

MPlay now defaults to using all the phyical memory on a system minus 64Mb. If the physical memory reported is less than 128Mb, Mplay will use half instead. This is only the default, and can be user-configured.

A bug with Operator dependencies on IA64 Linux machines has been fixed.

A bug with Operator dependencies on IA64 Linux machines has been fixed.

A bug with Operator dependencies on IA64 Linux machines has been fixed.

A bug with Operator dependencies on IA64 Linux machines has been fixed.

A bug with Operator dependencies on IA64 Linux machines has been fixed.

For VOPs which claimed to allow any number of inputs, the limit was actually 32 inputs. Now that limit has been increased to 64, and the help for these VOPs now reports that 64 is the maximum number of inputs.

For VOPs which claimed to allow any number of inputs, the limit was actually 32 inputs. Now that limit has been increased to 64, and the help for these VOPs now reports that 64 is the maximum number of inputs.

For VOPs which claimed to allow any number of inputs, the limit was actually 32 inputs. Now that limit has been increased to 64, and the help for these VOPs now reports that 64 is the maximum number of inputs.

For VOPs which claimed to allow any number of inputs, the limit was actually 32 inputs. Now that limit has been increased to 64, and the help for these VOPs now reports that 64 is the maximum number of inputs.

For VOPs which claimed to allow any number of inputs, the limit was actually 32 inputs. Now that limit has been increased to 64, and the help for these VOPs now reports that 64 is the maximum number of inputs.

On Windows, mcp now has command line options to save and load codec settings file. Useful for scripting movie compression without requiring user intervention.

Special Windows Usage:

mcp [-r framerate] -w width -h height -C settings_file

This usage will prompt you for the compression settings for an AVI file and save them to the specified options file. After that, you can use the -c option with the settings file in the regular usage to compress without further prompting.

NOTES: - The options file is a platform dependent binary file.

• The -r, -w, -h options must match when reusing the file.

eg. Create an options file: mcp -r 24 -w 640 -h 480 -C cmp.opt eg. Use options file: mcp tmp*.pic -o -c cmp.opt -r 24 -w 640 -h 480 tmp.avi

On Windows, mcp now has command line options to save and load codec settings file. Useful for scripting movie compression without requiring user intervention.

Special Windows Usage:

mcp [-r framerate] -w width -h height -C settings_file

This usage will prompt you for the compression settings for an AVI file and save them to the specified options file. After that, you can use the -c option with the settings file in the regular usage to compress without further prompting.

NOTES: - The options file is a platform dependent binary file.

• The -r, -w, -h options must match when reusing the file.

eg. Create an options file: mcp -r 24 -w 640 -h 480 -C cmp.opt eg. Use options file: mcp tmp*.pic -o -c cmp.opt -r 24 -w 640 -h 480 tmp.avi

On Windows, mcp now has command line options to save and load codec settings file. Useful for scripting movie compression without requiring user intervention.

Special Windows Usage:

mcp [-r framerate] -w width -h height -C settings_file

This usage will prompt you for the compression settings for an AVI file and save them to the specified options file. After that, you can use the -c option with the settings file in the regular usage to compress without further prompting.

NOTES: - The options file is a platform dependent binary file.

• The -r, -w, -h options must match when reusing the file.

eg. Create an options file: mcp -r 24 -w 640 -h 480 -C cmp.opt eg. Use options file: mcp tmp*.pic -o -c cmp.opt -r 24 -w 640 -h 480 tmp.avi

On Windows, mcp now has command line options to save and load codec settings file. Useful for scripting movie compression without requiring user intervention.

Special Windows Usage:

mcp [-r framerate] -w width -h height -C settings_file

This usage will prompt you for the compression settings for an AVI file and save them to the specified options file. After that, you can use the -c option with the settings file in the regular usage to compress without further prompting.

NOTES: - The options file is a platform dependent binary file.

• The -r, -w, -h options must match when reusing the file.

eg. Create an options file: mcp -r 24 -w 640 -h 480 -C cmp.opt eg. Use options file: mcp tmp*.pic -o -c cmp.opt -r 24 -w 640 -h 480 tmp.avi

On Windows, mcp now has command line options to save and load codec settings file. Useful for scripting movie compression without requiring user intervention.

Special Windows Usage:

mcp [-r framerate] -w width -h height -C settings_file

This usage will prompt you for the compression settings for an AVI file and save them to the specified options file. After that, you can use the -c option with the settings file in the regular usage to compress without further prompting.

NOTES: - The options file is a platform dependent binary file.

• The -r, -w, -h options must match when reusing the file.

eg. Create an options file: mcp -r 24 -w 640 -h 480 -C cmp.opt eg. Use options file: mcp tmp*.pic -o -c cmp.opt -r 24 -w 640 -h 480 tmp.avi