[Benjamin Byleen]

Thanks again for responding. Actually that was my first thought and I made sure that everything was 48khz.

I’m currently investigating the below error message and whether it is related or not. My rather unscientific thinking is that if I have a flaky RAM chip, the necessary overhead for the trim tool is not met. System profiler reports that the RAM is “OK” but I’ve heard (heresay of course) that’s not always 100% reliable. I’ve searched online for this error, but no posts that really relate to mine. Anyone seen these errors before and know specifically what they mean?

Nov 22 10:57:16 Final Cut Pro[45715]: Final Cut Pro(45715,0xde7500) malloc: *** mmap(size=268439552) failed (error code=12)\n*** error: can’t allocate region\n*** set a breakpoint in malloc_error_break to debug
Nov 22 10:57:16 [0x0-0x139139].com.apple.FinalCutPro[45715]: Final Cut Pro(45715,0xde7500) malloc: *** mmap(size=268439552) failed (error code=12)
Nov 22 10:57:16 [0x0-0x139139].com.apple.FinalCutPro[45715]: *** error: can’t allocate region
Nov 22 10:57:16 [0x0-0x139139].com.apple.FinalCutPro[45715]: *** set a breakpoint in malloc_error_break to debug

It seems somewhat implausible but I cannot ignore the error, so maybe going to try a few new sticks of RAM, and see whether it gets rid of the error and the audio problem.

Thanks again all!

Ben

[Benjamin Byleen]

Thanks for the response.

Yeah I was kind of leaning against a glitchy tool / FCP version but had to ask. Currently I am looking into hardware causes.

Any other responses still welcome of course!

Thanks!

[Benjamin Byleen]

My guess is then yes – definitely the XSan – and definitely should go up to XSan 2.2.1 to avoid the problem in the future.

Glad to hear it is mostly disappeared.

Ben

[Benjamin Byleen]

Hi Mark:

Well I’m glad to know that it’s probably not After Effects. I could never show that it was, only that the mentioned AE preference does modify the file’s code structure.

So you have QTs (RED) on the SAN that later on randomly go “corrupt” so that when the files are launched in quicktime an error reports “bad public movie atom” and will not open?

I’m pretty sure that a recent XSan update spoke of this error and that it was fixed. This would lend credence to your local harddrive test.

“Resolves an issue that could cause QuickTime media to report “invalid public movie atom found” on playback”

https://support.apple.com/kb/ht3927

I haven’t seen the problem again, and I hope this fixes it for you, though I’m guessing you are on a recent version. And btw if you need some of the corrupt movies back I might have found a way to resurrect them.

Sorry I didn’t post the link earlier.

Ben

[Benjamin Byleen]

For those out there having this problem, would you be willing to try a test?

I am leaning towards the “write XMP data” preference in After Effects CS4 (in Media & Disk Cache settings) as the problem. Now I’m not saying that it’s Adobe’s problem(!), but just that somehow when the XMP data is written back to the file there could a faulty writing of that data (perhaps related obscurely with the XSan filesystem).

A few things have led me to this conclusion. First, this preference does alter the quicktime file. Modified dates on the file are changed and of course, as the preference implies, metadata is written to the QT file. Second, the modified date on the file only changes after the first interaction with the file (as far as I can tell), which would lend credence to all of us that had a working file for awhile which then went randomly bad. Third, using HexEdit and studying the code that makes up each QT, I have noticed that this preference adds additional code to the QT file other than the XMP metadata.

Also, as far as I can tell, when the preference is disabled, the file is never modified during interactions in AE.

SUMMARY:
If you want to try a test and/or are not using the XMP metadata feature anyway, please disable the preference and report back if any corruptions occur or not. I have not encountered any corruptions since disabling it, but a larger test group would bolster these test results.

[Benjamin Byleen]

The problem described above seems very similar to something that I have encountered as well, but I have not been able to determine the exact cause of the problem or a solution.

Quicktime files (various codecs) that have been successfully imported into AE CS4 from the SAN, later on randomly go “corrupt” saying that the moov file is unsupported. When these files are launched in quicktime an error reports “bad public movie atom” and will not open.

Is there any chance that the AE Preference “write XMP data”, when enabled, causes this problem? I have not seen any posts that would suggest that, just grasping at straws here.

Any updates Mike? or OP?

—————-
2.94 MacPro Nehalem
12 GB Ram
XSan 2.1.1
Adobe CS4 Master Collection
FCP 6.06
Decklink HD Extreme