Redcine exports yield "invalid public movie atom" error

[Zach Hilton]

As the title suggests, renders from Redcine at times yield the "An invalid public movie atom was found in the movie." It is rather strange, because the day that we export the footage, it works just fine. We come back the next day, and there are random clips with this error. We haven't had this issue until just recently (still on Redcine build 90). I don't know why a file that was once working and now is not, and nothing has been done to it or the system during the interim. The only difference between our system from now to when we never had this problem was we upgraded our San's, installed new promise raids, and updated all computers to Leapord. I wouldn't think it would, but computers have a weird way about them at times.

So here's the question. Does anyone know how to fix invalid public movie atoms? Or know why I am having this issue?

 

[Mark L. Pederson]

Does anyone know how to fix invalid public movie atoms?

whatever you do ... DO NOT split them!

 

[Steve Freebairn]

whatever you do ... DO NOT split them!

That's funny! Maybe it's a raid problem?

 

[Zach Hilton]

whatever you do ... DO NOT split them!

Ha ha! I've seen Chain Reaction. No splitting of the atoms here. :biggrin:

 

[Zach Hilton]

So I take it no one knows how to correct this issue? or have any pointers?

 

[Steven Parker]

This is happening to me as well, but only when doing in-camera timelapse...

apparently this is addressed in Build 16, but I for one am waiting to upgrade until 16 is stabilized throughout the camera, redcine, quicktime, etc.

Sorry, no help, but know you're not alone...