Hi, I see that uncompressed RGB is not supported within MXF. I know that Resolve can create 10-bit RGB but only at HD resolution. I didn't see anything relating to uncompressed RGB in the UL list in mxfenc.c and I don't have an SMPTE account to get beyond the Paywall that would let me know what RGB pixel formats are possible within MXF in a general sense. I'm assuming that there isn't some option that I'm missing out on here, it just isn't supported? $ ./ffmpeg -f lavfi -i testsrc -pix_fmt gbrp10le -c:v copy out.mxf ffmpeg version N-92260-g3cc3cb663b Copyright (c) 2000-2018 the FFmpeg developers built with gcc 7 (Ubuntu 7.3.0-27ubuntu1~18.04) configuration: libavutil 56. 20.100 / 56. 20.100 libavcodec 58. 33.102 / 58. 33.102 libavformat 58. 19.102 / 58. 19.102 libavdevice 58. 4.106 / 58. 4.106 libavfilter 7. 37.100 / 7. 37.100 libswscale 5. 2.100 / 5. 2.100 libswresample 3. 2.100 / 3. 2.100 Input #0, lavfi, from 'testsrc': Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: rawvideo (RGB[24] / 0x18424752), rgb24, 320x240 [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc [mxf @ 0x56227a627880] track 0: could not find essence container ul, codec not currently supported in container Could not write header for output file #0 (incorrect codec parameters ?): Operation not permitted Stream mapping: Stream #0:0 -> #0:0 (copy) Last message repeated 1 times Best, Kieran.
On 10/24/18, Kieran O Leary <kieran.o.leary@gmail.com> wrote:
Hi,
I see that uncompressed RGB is not supported within MXF. I know that Resolve can create 10-bit RGB but only at HD resolution. I didn't see anything relating to uncompressed RGB in the UL list in mxfenc.c and I don't have an SMPTE account to get beyond the Paywall that would let me know what RGB pixel formats are possible within MXF in a general sense.
I'm assuming that there isn't some option that I'm missing out on here, it just isn't supported?
We need people like you to get it supported. Feel free to share such samples.
$ ./ffmpeg -f lavfi -i testsrc -pix_fmt gbrp10le -c:v copy out.mxf ffmpeg version N-92260-g3cc3cb663b Copyright (c) 2000-2018 the FFmpeg developers built with gcc 7 (Ubuntu 7.3.0-27ubuntu1~18.04) configuration: libavutil 56. 20.100 / 56. 20.100 libavcodec 58. 33.102 / 58. 33.102 libavformat 58. 19.102 / 58. 19.102 libavdevice 58. 4.106 / 58. 4.106 libavfilter 7. 37.100 / 7. 37.100 libswscale 5. 2.100 / 5. 2.100 libswresample 3. 2.100 / 3. 2.100 Input #0, lavfi, from 'testsrc': Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: rawvideo (RGB[24] / 0x18424752), rgb24, 320x240 [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc [mxf @ 0x56227a627880] track 0: could not find essence container ul, codec not currently supported in container Could not write header for output file #0 (incorrect codec parameters ?): Operation not permitted Stream mapping: Stream #0:0 -> #0:0 (copy) Last message repeated 1 times
Best,
Kieran. _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email ffmpeg-user-request@ffmpeg.org with subject "unsubscribe".
Hi Paul, On Thu, 25 Oct 2018, 08:32 Paul B Mahol, <onemda@gmail.com> wrote:
On 10/24/18, Kieran O Leary <kieran.o.leary@gmail.com> wrote:
Hi,
I see that uncompressed RGB is not supported within MXF. I know that Resolve can create 10-bit RGB but only at HD resolution. I didn't see anything relating to uncompressed RGB in the UL list in mxfenc.c and I don't have an SMPTE account to get beyond the Paywall that would let me know what RGB pixel formats are possible within MXF in a general sense.
I'm assuming that there isn't some option that I'm missing out on here, it just isn't supported?
We need people like you to get it supported. Feel free to share such samples.
So the RGB export from resolve could help? I will upload when I have access to this software in about ten days. Best, Kieran
Here is a sample - https://wetransfer.com/downloads/99e7bddc04e6faee2e001ad2ebed4a3c20181119152... This was exported from Resolve 14 using the AVID 1:1 10-bit RGB 1080p setting. Apologies for the delay, Kieran O'Leary ------ This email has been scanned for spam and malware by The Email Laundry.
2018-11-19 16:25 GMT+01:00, Kieran O'Leary <kieran.oleary@irishfilm.ie>:
Here is a sample - https://wetransfer.com/downloads/99e7bddc04e6faee2e001ad2ebed4a3c20181119152...
To decode this file: $ ffmpeg -vcodec avrp -i file $ ffplay -vcodec avrp file I was unable to find a useful uid != 0 in this file, suggestions welcome. Carl Eugen
2018-11-19 16:25 GMT+01:00, Kieran O'Leary <kieran.oleary@irishfilm.ie>:
Here is a sample - https://wetransfer.com/downloads/99e7bddc04e6faee2e001ad2ebed4a3c20181119152...
Can you use a binary editor and damage the metadata of the file around hex position 0x1050 that currently says "R.G.B." to check if the file still plays with whatever is supposed to play it? I wonder if metadata is really sufficient to decode an mxf file... Carl Eugen
Carl Eugen Hoyos wrote:
I wonder if metadata is really sufficient to decode an mxf file...
In my personal opinion, no. Best regards, Reto
2018-11-19 18:34 GMT+01:00, Reto Kromer <lists@reto.ch>:
Carl Eugen Hoyos wrote:
I wonder if metadata is really sufficient to decode an mxf file...
In my personal opinion, no.
My question was: Does the player that already supports this abomination depend on the metadata? I would prefer to rule this out before spending more time with this 4G file. Carl Eugen
Dont know wut iz mxf but already had some well taged mp3 on aimp that ffprobe doesnt read (on a normal mp3) Maybe be private data id3 or no id WTF … Hugo De : Carl Eugen Hoyos Envoyé le :lundi 19 novembre 2018 18:36 À : FFmpeg user questions Objet :Re: [FFmpeg-user] uncompressed RGB within MXF 2018-11-19 18:34 GMT+01:00, Reto Kromer <lists@reto.ch>:
Carl Eugen Hoyos wrote:
I wonder if metadata is really sufficient to decode an mxf file...
In my personal opinion, no.
My question was: Does the player that already supports this abomination depend on the metadata? I would prefer to rule this out before spending more time with this 4G file. Carl Eugen _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-request@ffmpeg.org with subject "unsubscribe".
On 11/19/18, yUGz afterLife <yugz.afterlife.888@gmail.com> wrote:
Dont know wut iz mxf but already had some well taged mp3 on aimp that ffprobe doesnt read (on a normal mp3) Maybe be private data id3 or no id WTF …
Please, share file.
On Mon, 19 Nov 2018, 17:36 Carl Eugen Hoyos <ceffmpeg@gmail.com wrote:
2018-11-19 18:34 GMT+01:00, Reto Kromer <lists@reto.ch>:
Carl Eugen Hoyos wrote:
I wonder if metadata is really sufficient to decode an mxf file...
In my personal opinion, no.
My question was: Does the player that already supports this abomination depend on the metadata? I would prefer to rule this out before spending more time with this 4G file.
I understand. I will try to hack around with it tomorrow and see if resolve and avid can read it. Thanks, Kieran
2018-11-19 18:41 GMT+01:00, Kieran O Leary <kieran.o.leary@gmail.com>:
On Mon, 19 Nov 2018, 17:36 Carl Eugen Hoyos <ceffmpeg@gmail.com wrote:
2018-11-19 18:34 GMT+01:00, Reto Kromer <lists@reto.ch>:
Carl Eugen Hoyos wrote:
I wonder if metadata is really sufficient to decode an mxf file...
In my personal opinion, no.
My question was: Does the player that already supports this abomination depend on the metadata? I would prefer to rule this out before spending more time with this 4G file.
I understand. I will try to hack around with it tomorrow and see if resolve and avid can read it.
Did you have time to test this? Carl Eugen
Carl Eugen Hoyos wrote:
My question was: Does the player that already supports this abomination depend on the metadata? I would prefer to rule this out before spending more time with this 4G file.
It's actually what I'm trying to figure out! I suspect no, but I cannot say it for sure so far. Best regards, Reto
2018-11-19 18:42 GMT+01:00, Reto Kromer <lists@reto.ch>:
Carl Eugen Hoyos wrote:
My question was: Does the player that already supports this abomination depend on the metadata? I would prefer to rule this out before spending more time with this 4G file.
It's actually what I'm trying to figure out! I suspect no, but I cannot say it for sure so far.
Just change "R.G.B." into "S.H.C." and check if the file still plays. Carl Eugen
On 11/19/18, Carl Eugen Hoyos <ceffmpeg@gmail.com> wrote:
2018-11-19 18:42 GMT+01:00, Reto Kromer <lists@reto.ch>:
Carl Eugen Hoyos wrote:
My question was: Does the player that already supports this abomination depend on the metadata? I would prefer to rule this out before spending more time with this 4G file.
It's actually what I'm trying to figure out! I suspect no, but I cannot say it for sure so far.
Just change "R.G.B." into "S.H.C." and check if the file still plays.
Why S.H.C.? and not C.E.H.
Becoz nike Hugo De : Paul B Mahol Envoyé le :lundi 19 novembre 2018 18:55 À : FFmpeg user questions Objet :Re: [FFmpeg-user] uncompressed RGB within MXF On 11/19/18, Carl Eugen Hoyos <ceffmpeg@gmail.com> wrote:
2018-11-19 18:42 GMT+01:00, Reto Kromer <lists@reto.ch>:
Carl Eugen Hoyos wrote:
My question was: Does the player that already supports this abomination depend on the metadata? I would prefer to rule this out before spending more time with this 4G file.
It's actually what I'm trying to figure out! I suspect no, but I cannot say it for sure so far.
Just change "R.G.B." into "S.H.C." and check if the file still plays.
Why S.H.C.? and not C.E.H. _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-request@ffmpeg.org with subject "unsubscribe".
participants (6)
-
Carl Eugen Hoyos -
Kieran O Leary -
Kieran O'Leary -
Paul B Mahol -
Reto Kromer -
yUGz afterLife