[Jean Bertin]

Just to say how to check ProRes/MOV.

OSX.6*, in Terminal :

grep -bao moov file

Output :
Offset:moov
...

If you get more one moov, the last or the first, the nearest of beginning or end of file is the right.

And, this file is potentially affected by artifacts.

* : Strangely, grep command doesn’t work on big files on a OSX.10.

[Jean Bertin]

We wonder since how long we have this problem. We process too many programs for broadcast (TV etc.), without issue.

FCP7, like QT, hides most of artifacts. No editor in our company has seen fault. It’s detected before or after process or editing.

Most recent example : trailer in ProRes (HQ) : one artifact, one bad moov. Transcoding (PRHQ always) with PP CC : just one, good, moov, no artifact.

We don’t know when a bad moov will induce artifact, rarely. It depends on this location on the mdat flow, if it overwrites a essential part of frame (icpf atom).

Thanks.

[Jean Bertin]

Thanks for the answer.
But :
– OSX.6 is affected, obsolete too, yes I know, but FCP7 is supported until OSX.7
– a professional video software modify a file just by opening
– this modification is a corruption
– this corruption leads sometimes to visible artifacts
– this artifacts are hidden, most of time, by QuickTime during playback. Another prolem.
– FCPX have many inconvenients (i.e. MXF playback, no VTR ingest or output)

After that, we have found alternative (FCPX, PP CC and BM MediaExpress). But given several files from outside are affected, FCP7 is still widespread.

This message is both a question (have you meet this issue ?) that a feedback.

Sorry for my english writing.

Sorry for my english writing.