FFmbc 0.7 rc7 and rc8 detects some 1440x1080i/25 DVCProHD MOV files as 960x720p

[GoogleCodeExporter]

A colleague has supplied me with MOV files exported from Premiere Pro 5.5, 
which contains DVCProHD 1440x1080i/25 media. 

FCP7, QuickTime, and MediaInfo detect the media correctly. FFmbc does not - and 
does not decode the file correctly.

$ ./ffmbc -loglevel debug -i STONES\ CLIP_1.mov
FFmbc version 0.7-rc8
Copyright (c) 2008-2013 Baptiste Coudurier and the FFmpeg developers
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x2aa26a0] Format mov,mp4,m4a,3gp,3g2,mj2 probed 
with size=2048 and score=100
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x2aa26a0] ISO: File Type Major Brand: qt
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x2aa26a0] Probe buffer size limit 5000000 reached
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x2aa26a0] 0: start_time: 0 duration: 750
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x2aa26a0] 1: start_time: 0 duration: 1440000
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x2aa26a0] 2: start_time: 0 duration: 750
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'STONES CLIP_1.mov':
  Metadata:
    major_brand: qt
    minor_version: 537199360
    compatible_brands: qt
    timecode: 00:00:00:00
  Duration: 00:00:30.00, start: 0.000000, bitrate: 116740 kb/s
    Stream #0.0(eng), 9, 1/25: Video: dvvideo, yuv422p, 960x720p [PAR 4:3 DAR 16:9], tbc 1/50, 115200 kb/s, tbr 25/1, tba 25/1, 25.00 fps
    Metadata:
      codec_name: DVCPRO HD 1080i50
      gamma: 2.199997
    Stream #0.1(eng), 0, 1/48000: Audio: pcm_s16le, 48000 Hz, 2 channels, s16, 1536 kb/s
    Stream #0.2(eng), 0, 1/25: Data: unknown (tmcd)
At least one output file must be specified

I will send via IRC the location of a demonstration file.

Original issue reported on code.google.com by mark.him...@gmail.com on 26 Apr 2013 at 2:03

[GoogleCodeExporter]

This file has stype wrong specifying 720p. I hardly believe premiere would 
create such broken files

Original comment by baptiste...@gmail.com on 26 Apr 2013 at 11:50

[GoogleCodeExporter]

It's even more interesting. If you extract the raw dv:
ffmbc -i STONES\ CLIP_1.mov -vcodec copy -f rawvideo test.dv

mediainfo see it as 720p as well now too.
My guess is that Quicktime and mediainfo follow the fourcc.

Should we workaround the same way ? I need to know more about where the file is 
coming from.

Original comment by baptiste...@gmail.com on 27 Apr 2013 at 1:20

[GoogleCodeExporter]

Thank you for looking at that file.

I do not believe that following the fourcc is the right thing to do, but if 
Premier Pro 5.5 is that broken it might be the only way.

I have no access to Premier Pro 5.5 - this report is coming from colleagues in 
another building. I have asked them to:

Make 100% sure that the sequence settings and export settings are correct
Make sure you have tested on the latest version of Premier Pro (Google tells me 
there is a 5.5.2)
Export the same media as MXF from Premier Pro, if that is decoded correctly by 
FFmbc then we have a work-around

When I receive an update I shall parse it on.

Original comment by mark.him...@gmail.com on 27 Apr 2013 at 8:13

[GoogleCodeExporter]

Baptiste, I have some more information about the file I uploaded.

I now believe that the original essence was rendered on an FCP7 seat. The file 
I sent was a non-transcoded sub-clip from an original 30 minute programme - 
i.e. it is the original essence as rendered within FCP7 - and the sub-clip was 
created in Premier Pro. So currently I am ruling out Premier Pro 5.5 as the 
problem software.

I have a copy of original 30 minutes of essence, and I'm going to investigate a 
bit more (next week).

I have a theory that there might have been some progressive footage on a 
DVCPROHD 1440x1080/25i timeline, and that theory continues that either FCP7 a 
third-party export plugin might have rendered the essence for that progressive 
shot into 1440x1080 DVCPROHD but flagged incorrectly.

I have asked for some tests to be carried out by my colleagues, and when I get 
back to my desk (next week) I shall also do some more tests. I'll update you 
when I get more information.

Original comment by mark.him...@gmail.com on 2 May 2013 at 9:53

[GoogleCodeExporter]

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

• Changed state: Invalid