I've noticed this issue since upgrading to 6.1. When running Max in 32-bit mode on OSX, I can instantiate a new 'jit.qt.movie @colormode uyvy' object without a problem. However, if I relaunch Max in 64-bit mode, the same object generates a "colormode is not a valid attribute argument" error.

I am curious if anyone else can confirm this error, as I haven't found any references to it in the forums, docs, online, etc. Other Jitter objects that have the @colormode attribute do not generate that error in 64-bit mode as far as I can tell.

I've noticed this issue since upgrading to 6.1. When running Max in 32-bit mode on OSX, I can instantiate a new 'jit.qt.movie @colormode uyvy' object without a problem. However, if I relaunch Max in 64-bit mode, the same object generates a "colormode is not a valid attribute argument" error. 

colormode-for-jit-qt-movie-breaking-in-64-bit-mode

colormode is not currently supported in 64 bit jit.qt.movie.

Ok, I wondered about that, though didn't see any reference to it in the documentation - is it specified somewhere? Thanks!

This has been broken for quite some time. Any plans to fix this?

colormode for jit.qt.movie breaking in 64-bit mode?