Oh, my mistake. I suppose I was asking for YUV (YCrCb) but since the filter was called 'xyz2rgb' I said RGB instead. The issue of YCrCb vs RGB encoding is important but ffmpeg usually gets it right, so I was focussed on converting from the XYZ (really X'Y'Z') primaries and gamma to the Rec709 equivalents.
"Snapshots" vs "Releases" isn't an obvious distinction to me. "Releases" is clear but "Snapshots" is not. "Daily Build" vs "Production Build" is more common terminology in the VFX software world I am familiar with, and seems more readily obvious. The page you linked (https://evermeet.cx/ffmpeg/) has some font size hierarchy issues that cause your instructions ("FFmpeg developers strongly encourage all users to use a current snapshot build instead of a release build.") to get overlooked. That instructions should be in a larger font size and could also be simplified: "We strongly encourage all users to use a current snapshot build instead of a release build." or "All uses are recommended to use the current snapshot build instead of the release build." With the current small font size and my dyslexia, I had misread the line to say "FFmpeg developers are strongly encouraged to use a current snapshot build instead of a release build." I wasn't a developer so I opted for the release build. Lastly, there should be column headings over the Snapshot/Daily Build column and Release Build column. It is not immediately obvious that the large green link above the words "More ffmpeg snapshots" is the snapshot link and that the large green link above the words "More ffmpeg releases" is the release link. Sure I can use reasoning to figure it out, but you asked for more optimized wording. There should be a heading in font size larger than the links, ABOVE the links. The links should probably be reduced in font size so there isn't a general font size escalation. On Jul 7, 2015, at 1:00 AM, Carl Eugen Hoyos <[email protected]> wrote: > John Pilgrim <lists <at> johnpilgrim.net> writes: > >> My goal is to convert an XYZ-encoded MXF from a DCP to >> an RGB Rec709-encoded ProRes MOV. > > I may just misunderstand but ProRes does not support RGB > (only YUV). > >> I am using a MacOS ffmpeg binary from >> https://evermeet.cx/ffmpeg/ > >> ffmpeg version 2.7.1-tessus > > I tried so hard to find a wording that prevents people > from downloading this binary: Could you suggest a better > wording for https://evermeet.cx/ffmpeg/ ? > Note that it makes an actual difference for your > use-case, the j2k decoder was finally fixed for many > input files. > > Carl Eugen > > _______________________________________________ > ffmpeg-user mailing list > [email protected] > http://ffmpeg.org/mailman/listinfo/ffmpeg-user _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user
