Steven Nichols
Forum Replies Created
-
Steven Nichols
October 2, 2012 at 5:27 am in reply to: Pro Import with Avid in CS6: bug RAM previewing comp ?I also tried the Boris plugin and ended up with the same problem. I think it’s related to XDCAM EX… I don’t have FCP on this machine.
-
Steven Nichols
September 25, 2012 at 5:29 pm in reply to: Pro Import with Avid in CS6: bug RAM previewing comp ?I did another test on another machine. For a moment I thought it worked because MP was not enabled.
However when I tried to reopen the project, AE gave me an error message telling me “this “Moov” file was damage or unsupported” 🙁
Looks like Adobe has still some work to do with Avid. Is there a way to report that bug ? -
Same issue here with Sonnet D800RAID. I just updated the drivers before the OS and it was a total disaster 🙁
Anything new with ATTO ? -
I tried importing the very same clip that causes this bug on another Mac with another Kona card and it worked just fine. So this is definitely not a Aja driver issue, probably more a multi processor error as I suspected…
-
I think you are getting confused because there are 2 distinct issues here.
The know issues with Aja and CS5 occur EVERYTIME you use specific codecs (MJPEG…). Lots of people have been reporting it over the www. I got in touch with Aja’s tech support and they released a fix for that last week. I installed it and there is no shift color bug anymore.
However as I said the XDCAM EX problem does not occur with every XDCAM EX clip, only a couple of files. If it was a simple Aja driver issue, don’t you think that would affect ALL the XDCAM EX clips ? I will try that on another machine with another Aja card. Besides, what about the error messages regarding multiprocessing ? Not sure – again – this is just a driver issue.
-
I had the latest drivers, the one that were updated for CS5. I experienced some trouble before (a hue shift with motion JPEG codec when previewing the comp with the Kona card) but nothing quite like that with XDCAM EX. This is definitely a nasty bug 🙁
-
I am running QT 10 on both machines. Or maybe it has something to do with my Kona card… I found a workaround by re-exporting manually the clips from FCP. I think the problem is with clips that have the same name that some older clips from another projects, but it still does not make sense.
-
I have the latest version available.
I know that XDCAM EX is indeed MPEG-2 encapsuled as an MP4 file. When you import it with FCP it is converted to QT with the XDCAM EX codec.
But that does not explain why AE does not see some file as QT but still as MPEG file (that seems to be the problem). I tried that on another machine and it worked fine. This happens on a 12-core Mac Pro. When MP rendering is not enabled, it seems to get a little better… So I suspect a hardware bug.
Anyone had this kind of trouble ?
-
I think I figured it out. For some compatibility issues with my Sonnet Qio, the Mac was running in 32-bit mode-hence the random behavior (it was like sleeping during rendering).
I restarted the Mac in 64-bit and everything is fine now. -
I tried iStat. Very interesting: when “Render Multiple Frames Simultaneously” is not enabled, I can see that all the cores are working! After Effects uses as much as 800%. What does this mean ?
When”Render Multiple Frames Simultaneously” is enabled, the machine is sometimes unresponsive and stuck… Very weird.