The new current ffmpeg version (June 02) is writing IMX50 MXF in the
correct way (thanks to Michael Niedermayer):
SIGNAL STANDARD=1 (SMPTE ST386 2004)
COLOR SITING=0 (SMPTE ST 377) (the value 4 is debrecated)
before this new ffmpeg version it was no set information in this flags:
SIGNAL
On Tue, May 5, 2015 at 8:41 AM, tim nicholson
nichot20-at-yahoo@ffmpeg.org wrote:
On 05/05/15 15:52, Christoph Gerstbauer wrote:
Am 05.05.2015 um 09:06 schrieb tim nicholson:
[...]
The tricky bit is to decide what to do if the values aren't manually
specified. According to the
On 04/06/15 12:06, Kuban Altan wrote:
On Tue, May 5, 2015 at 8:41 AM, tim nicholson
nichot20-at-yahoo@ffmpeg.org wrote:
On 05/05/15 15:52, Christoph Gerstbauer wrote:
Am 05.05.2015 um 09:06 schrieb tim nicholson:
[...]
The tricky bit is to decide what to do if the values aren't
Am 05.05.2015 um 09:06 schrieb tim nicholson:
On 02/05/15 14:38, Christoph Gerstbauer wrote:
Am 01.05.15 um 11:21 schrieb tim nicholson:
[..]
Christoph do you actually require the mxf metadata setting (as it really
ought to be, and what I thought you were after) or are you content with
it
On 05/05/15 15:52, Christoph Gerstbauer wrote:
Am 05.05.2015 um 09:06 schrieb tim nicholson:
[...]
The tricky bit is to decide what to do if the values aren't manually
specified. According to the specs there is no default value, so we
would have to invent one.
Hm, so what is happening
On 02/05/15 14:38, Christoph Gerstbauer wrote:
Am 01.05.15 um 11:21 schrieb tim nicholson:
[..]
Christoph do you actually require the mxf metadata setting (as it really
ought to be, and what I thought you were after) or are you content with
it in the essence, in which case, in the absence
Am 01.05.15 um 11:21 schrieb tim nicholson:
On 30/04/15 22:03, Marton Balint wrote:
On Wed, 29 Apr 2015, Christoph Gerstbauer wrote:
I found out that a IMX50 mxf file encoded with FFmbc and the IMX50 mxf
file encoded with actual ffmpeg builds are different in these mxf
metadata flags (by
On 30/04/15 22:03, Marton Balint wrote:
On Wed, 29 Apr 2015, Christoph Gerstbauer wrote:
I found out that a IMX50 mxf file encoded with FFmbc and the IMX50 mxf
file encoded with actual ffmpeg builds are different in these mxf
metadata flags (by reading out via ffprobe - show_streams)
Are
You can manually specify these settings to force them being set with
these parameters:
-color_primaries 5
-color_trc 1
-colorspace 6
What does not work as far as I know in ffmpeg is to actually get these
settings from the source video, even if ffprobe detects them.
Regards,
Marton
Thank
On 29/04/15 22:22, Christoph Gerstbauer wrote:
I found out that a IMX50 mxf file encoded with FFmbc and the IMX50 mxf
file encoded with actual ffmpeg builds are different in these mxf
metadata flags (by reading out via ffprobe - show_streams)
FFMBC IMX FILE stream 0:0:
color_range=tv
On Wed, 29 Apr 2015, Christoph Gerstbauer wrote:
I found out that a IMX50 mxf file encoded with FFmbc and the IMX50 mxf file
encoded with actual ffmpeg builds are different in these mxf metadata flags
(by reading out via ffprobe - show_streams)
FFMBC IMX FILE stream 0:0:
color_range=tv
I found out that a IMX50 mxf file encoded with FFmbc and the IMX50 mxf file
encoded with actual ffmpeg builds are different in these mxf metadata flags (by
reading out via ffprobe - show_streams)
FFMBC IMX FILE stream 0:0:
color_range=tv
color_space=smpte170m
color_transfer=bt709
12 matches
Mail list logo
