Nuke5 Quicktime Support?

[iconoklast]

Is there something I need to do to get QuickTime read support? My source files are often QuickTime, coming from Final Cut Pro. I can actually write to QT, but I can't read. The codec doesn't seem to matter. The error message says "Couldn't open movie for reading".

Of course I can convert to image sequences, but it would be easier to avoid that step.

Any ideas?

[ior]

QUOTE(foggybog @ 03/21/08, 10:43 AM) [snapback]282999[/snapback]
Is there something I need to do to get QuickTime read support? My source files are often QuickTime, coming from Final Cut Pro. I can actually write to QT, but I can't read. The codec doesn't seem to matter. The error message says "Couldn't open movie for reading".

Of course I can convert to image sequences, but it would be easier to avoid that step.

Any ideas?

Quicktime read and write is working for me. NUKE 5, QT 7.4.1, various codecs tried.

Post details of your configuration... that will help troubleshooting.

In the meantime, use Quicktime Player to re-export a .mov out of Final Cut into a different format and read that into NUKE. Does it work?

[bjerregaard]

Also make sure you have .mov on your file. Nuke wouldn't play with my FCP generated QT's unless I renamed them

[mark1977]

I am having the same problem on some of my boxes, it seems that currently Quicktime is unsupported on powerpc macs. I have two intel macs and they work perfectly but the two powerpc macs do not work at all with any codec for quicktime whatsoever. I contacted The Foundry and they said they were working on a fix to the code, and they would release a new beta when it was fixed. They said there are also reports of this on some windows xp machines.

Not much for a solution, but at least you know there are others with your same problem.

-Brennan

[giantpixel]

I am running a MAC pro intel and no 4:4:4 RGB codec in Nuke, only 4:4:2

[iconoklast]

Just to give this thread some closure, new releases of Nuke have fixed this problem for me.

[user_deleted]

QUOTE(foggybog @ 07/17/08, 05:46 PM) [snapback]288485[/snapback]
Just to give this thread some closure, new releases of Nuke have fixed this problem for me.

yes..this was a PPC issue, the same build on Intels worked fine.

5.0v2 should fix it on PPC