Nick, I get the same as you with your chart, so it seems to be a transform that's not correct, if it's changing with differing levels of RGB.

I hadn't realised there was a Sony MP4 encoder, which is correct, if a little sloooww ;-)

ffmpeg rendering with frameserving from Vegas doesn't solve the issue (seen from Vegas preview with x264 encoding).

• Red becomes 250,1,1
• Blue becomes 0,0,248
• Green becomes 5,252,6

It seems that converting RGB to YV12 causing this error.

ffmpeg always(defaults) does a RGB to YUV conversion with a 601 colorspace. It is a quirk/annoyance of ffmpeg that goes back to it's early days before HD/709 existed. That is why I did the RGB to YUV conversion in Avisynth before passing to ffmpeg. My full scripts are somewhere on this forum.

ConvertToYV12(matrix="rec709")

Also, I always pass full range to the frameserve.

Also from other posts in this thread the matrix and transform metadata that MediaInfo will show is really optional VUI info. I don't think any decoder looks at this info. I know I have put bogus info in there and I've seen no change on playback/import.

Norm, not really VUI, that's an actual flag (yuvj420p) that talks to the decoder, if it is one that is actually aware of such things. We have Apple to thank for that.

I agree that the metadata TAGS signify nothing to the decoder; however, it is unsettling to see all these little color space errors without the encoders in Vegas telling us what they are actually doing....

ffmpeg rendering with frameserving from Vegas doesn't solve the issue (seen from Vegas preview with x264 encoding).

• Red becomes 250,1,1
• Blue becomes 0,0,248
• Green becomes 5,252,6

It seems that converting RGB to YV12 causing this error.

ffmpeg always(defaults) does a RGB to YUV conversion with a 601 colorspace. It is a quirk/annoyance of ffmpeg that goes back to it's early days before HD/709 existed. That is why I did the RGB to YUV conversion in Avisynth before passing to ffmpeg. My full scripts are somewhere on this forum.

ConvertToYV12(matrix="rec709")

I also use an avisynth script but with the following line as the op wants to keep full range.

ConvertToYV12(matrix="PC.709")

That is often used to convert fullrange to 709 levels; I have no idea of its usefulness in converting 601 to 709 (as if it mattered).

Here's another RGB test chart:

And here's one with cyan, magenta, yellow and orange:

So, the MAGIX AVC/AAC encoder in MainConcept encode mode greatly reduces pure red and blue, cyan receives lots of unwanted red, and yellow receives lots of unwanted blue. Here are the figures. The worst ones are in bold:

Red, RGB 255,0,0 becomes 226,8,0
Green, RGB 0,255,0 becomes 10,252,1
Blue, RGB 0,0,255 becomes 0,3,221
Cyan, RGB 0,255,255 becomes 29,247,255
Yellow, RGB 255,255,0 becomes 255,252,34
Magenta, RGB 255,0,255 becomes 245,3, 254

However when all 3 channels are in a mix, the issue doesn't occur. For example:

White, RGB 255,255,255 becomes 254,254,254
"Pink", RGB 255,128,128 remains 255,128,128

Below is what happens when the rendered file is uploaded to YouTube. You can sample the colors with Just Color Picker or similar. (Apologies for the irrelevant intro. The first time I did this, I got a YouTube community guidelines strike for uploading duplicate content!)

MAGIX AVC MainConcept mode:

Sony AVC/MVC CPU-only:

I submitted a support request, [Ticket#2017103117003394]

I got a quick response from Support that included this:

​"This is a known issue which will be resolved in a future application update."

The same one I had, not what you might call good customer service, e.g It was broken when you bought it, but we will charge you for an upgrade to fix it ;-(

It was broken when you bought it, but we will charge you for an upgrade to fix it ;-(

Hopefully, in a free update and not in an upgrade you need to pay for.

Absolutely, no-one can stop us hoping ;-)

And fixed in VP14.  Also paid for!

I have pointed this out to Magix, will let you know what they reply.

They don't seem very good on customer service. I reported this problem to them, but they denied any knowledge of an issue.

They would have saved Me, Nick, MusicVid and others, a great deal of time, if they had just admitted they knew about this.

Hope they monitor these forums.

They would have saved Me, Nick, MusicVid and others, a great deal of time, if they had just admitted they knew about this.

Keeps us off the streets and out of detox, Andrew.

Has this been fixed in 261?  Checked list but may have missed it.  Still hoping.