Re-write ReadFFMPEG to be up to date with ffmpeg.c

[devernay]

From @manuelsongokuh on March 17, 2016 21:56

hi

i testing natron, i find strange 3 messages errors:
1 yellow warning:
rendered rectangle (0,0)-(960,540) contains NaN values.They have been converted to 1.

2 red error:
-... detected deconding stall, possibile file corruption
-... failed to seek frame: Operation not permitted

see my record screen
http://sendvid.com/7di9ka2c

the file footage MXF:
https://mega.nz/#!D0ojBJQA!W476CDKWyBbDgQWucTaQt0WDBr8OmvJX9tT20Wdt8oM

natron version is 4926612.

Copied from original issue: MrKepzie/Natron#1244

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[devernay]

From @olear on March 19, 2016 12:53

FFmpeg has problems reading MXF files from Canon, this results in several issues. At the moment we are not sure how to resolve this (seems to be an issue with the codec), so I recommend you re-encode the footage in a more supported format, or just use an image sequence.

[devernay]

From @manuelsongokuh on March 19, 2016 16:25

hi olear
yes that is sure for image sequences, this is know, but i port to natron report bug issue, so natron will be best stable for future like as quality software ok?

i write here issue like as memo for issue for remember for future ok?

[devernay]

ReadFFmpeg will be rewritten from the ground up

[devernay]

From @manuelsongokuh on March 27, 2016 10:51

ok thank you devernay

[devernay]

From @manuelsongokuh on June 8, 2016 10:52

thank you for change title of issue..

[devernay]

see also MrKepzie/openfx-io#15

[devernay]

stripped-down ffplay: https://github.com/devernay/ffplay