[HELP] Color change after encoding !

[sonikk]

I have a massive problem, so I would be really thankful if someone of you could lend me out a hand:

After rendering(uncompressed)> this is my result:



Looks fine, right?


But when it comes to encoding it to an mp4 file: here are the results I get:


Zarx



Amvsimple:




AMVcomplex:


BakeEncoder



These are my settings:






Also I tried encoding with lagarith: But I am receiving a error with baka-encoder and Amvsimple, when compressing:

[l33tmeatwad]

Edit: Retracted, incorrect assessment.

[mirkosp]

The colormatrix is correct, that's a range issue.
Your footage is TV levels, but is being decoded as PC levels, that's my closest guess as to why it gets that look.
I'd first make sure you have a proper playback setup: uninstall all your players and then install CCCP ( http://cccp-project.net/ ).
If after rebooting and repairing CCCP in the CCCP Settings you still get the wrong range in Media Player Classic Home Cinema, come back here.

PS: The colormatrix is set on auto by default. That means it's autoguessed based on the resolution. A 960x720 gets autoguessed to bt709, as per ffmpeg standard, anything that is larger than 1024 and/or taller than 600 is considered HD.

[l33tmeatwad]

Edit: Retracted, incorrect assessment.

[mirkosp]

Since we're getting in OT territory, I'll spoiler it out:

Spoiler :

He has a YUV input to begin with, so obviously if the colormatrix conversion was wrong, it was within the NLE, before the comparison screenshot.
Encoding side, the issue is if you feed RGB clip to x264. And here's what happens:

http://mewiki.project357.com/wiki/X264_ ... olormatrix
http://mewiki.project357.com/wiki/X264_Settings#resize

So undef, and resize deals with the conversion.
I did a couple tests. Command line as follows:

Code: Select all

x264_x86 input.avi -o output.mkv

255,0,0 RGB SD. Gets converted as bt601, as default LAV decode autoguesses bt601 on the undef and outputs 255,0,0.
255,0,0 RGB HD. Gets converted as bt709, as default LAV decode autoguesses bt709 on the undef and outputs 255,0,0.

This is with default behaviour in an x264 build compiled with libswscale, which means that it automatically used lavf in my build. A build with ffms will also behave in the same way. I also manually forced avs as the demuxer, and as expected the resulting files were decoded correctly. The command line was simply:

Code: Select all

x264_x86 input.avi -o output.mkv --demuxer avs

EDIT: I did a better check, with colorbars instead of just a 255,0,0 clip, and it still holds up wtih what I said.

Now to get back on track with the OP's screenshots, here's what happens to the "wrong" images after the following code:

Code: Select all

converttoyv12(matrix="PC.709")
converttorgb32(matrix="Rec709")

Which means it only goes through a levels conversion, no matrix conversion. Using PC.601 and then Rec601 would result in identical output.

http://abload.de/img/0e8j8z.png

I think we can agree it now matches the input screenshot posted, both in matrix and range.

So, now that you are convinced the issue is in the range, and not in the colormatrix, we have to wait for OP to respond.

[l33tmeatwad]

Good eye, but perhaps you should have posted all that information with your first post? Would have been a bit more helpful ;p