rerendering ProRes HQ in FCP 7 as reference files

[GoogleCodeExporter]

What steps will reproduce the problem?
1. create proResHQ in ffmbc with -vcodec prores -profile hq
2. import into FCP 7
3. export from FCP 7 as proresHQ.mov (not writing independant file but only a 
reference.mov)

What is the expected output? 
output should be small size mov including audiostreams, rendered passages with 
fades or not-ProRes-oringl codec, references to existing proresHQ files 
(instead of including its content)
What do you see instead?
a complete independant proresHQ file with no references but newly rendered / 
maybe transcoded proresHQ with the size of the source file.

What version of the product are you using? On what operating system?
ffmbc 0.7 RC7 on win7-Pro-64bit
Final Cut Pro 7 on MAC os 10.6.8 and 10.7.5

Please provide any additional information below:
The files from ffmbc could be imported without problems into final cut so we 
could do editing etc. FCP did NOT show in the timeline, it needs to render the 
material. But when we want to render the edited material into a reference 
quicktime file (which will only contain references to the original files, 
rendered fades and the complete audio) Final Cut is writing all content into 
the reference file. So it has the same size afterwards and we think, FCP will 
apply a new transcode from proresHQ into proresHQ.

We just tried to change two entries in the file header (found that info 
somewhere in the web):
...
Fscreator code = "KeyG"
...
FS type code = "MooV"
...

But this did not fix the problem.

- Full commandline run (with -v 3) and everything the program printed
without
the repeating parts.
ffmbc.exe -i source.mxf  -vcodec prores -profile hq output.mov

Do you have an idea, why this happens and what could be done to avoid it?

Many thanks and best regards,
Harald 

Original issue reported on code.google.com by harger.h...@googlemail.com on 4 Oct 2013 at 11:40

[GoogleCodeExporter]

I tried here on FCP7 with the sequence properly configured and it worked.
It only created a reference file, I explicitely unchecked "make movie 
self-contained, and recompress all frames"
Can you try with FFmbc compiled on MAC OSX instead of windows ?

Original comment by baptiste...@gmail.com on 11 Oct 2013 at 8:40

[GoogleCodeExporter]

Hi

We use ffmbc only on the pc workstations so far. Maybe we could check it on
Mac OS as well.

Thanks and best, Harald
Am 11.10.2013 22:40 schrieb <ffmbc@googlecode.com>:

Original comment by harger.h...@googlemail.com on 12 Oct 2013 at 9:03

[GoogleCodeExporter]

Dear Baptiste,

happy and succesful New Year!

sorry for the long dely in resonding to our last conversation - it was too much 
work to investigate further. But we made a new test have used ffmbc on MAC for 
testing and still have the same problem. Even if we want to create a reference 
file, the filesize will be the same as the original ProRes file. So FCP creates 
a new complete file, not a reference file.

Version used on MAC:
FFmbc version 0.7-rc7
Copyright (c) 2008-2012 Baptiste Coudurier and the FFmpeg developers
built on Oct 21 2013 16:56:27 with gcc 4.2.1 (Apple Inc. build 5666) (dot 3)
configuration: --enable-gpl --enable-nonfree --disable-yasm
libavutil    51. 11. 0 / 51. 11. 0
libavcodec   53.  9. 0 / 53.  9. 0
libavformat  53.  6. 0 / 53.  6. 0
libavdevice  53.  2. 0 / 53.  2. 0
libavfilter   2. 27. 3 /  2. 27. 3
libswscale    2.  0. 0 /  2.  0. 0
libpostproc  51.  2. 0 / 51.  2. 0

Is there any add. paramter we need to add to the command line to get a ProRes 
File which will be "recognized" by FCP as a prores.mov which does not need a 
new transcode?
Or could you send us a clean FCP project file with the correct settings - maybe 
something needs to be changed in the fcp project?

Many thanks and best regards,
Harald

Original comment by harger.h...@googlemail.com on 2 Jan 2014 at 3:53

[GoogleCodeExporter]

Dear Babtiste,

my Colleague just checked RC 8 on the MAC - and this created correct reference 
files.
I remeber, that we checked something newer than RC 7 on windows, but did not 
used it due to problems I d not remember. I guess we should check this again.

Best regards,
Harald

Original comment by harger.h...@googlemail.com on 7 Jan 2014 at 12:30

[GoogleCodeExporter]

Original comment by baptiste...@gmail.com on 1 Apr 2014 at 4:31

• Changed state: Invalid