Mencoder: Color Problems on Mencoder outputs?
Now you can quickly see how mencoders internal filters mess up the colours of your source :P
EDIT by Inc. This "color" subject was separated from this thread: http://www.kvcd.net/forum/viewtopic....11515&start=48 |
Quote:
|
Quote:
I haven't noticed any color-changing effect when using mencoder internal filters. Have you? C ya |
Quote:
It can be clearly seen on the Back to the Future original VOB captured screenshot I posted (crappy source, I know), that the colors are identical on both the VOB and the one I encoded with mencoder. So I don't see why people are seeing a color mismatch :roll: However, I'm not sure is this is because people are doing AVI conversions, and then, it could possibly be a color space issue. -kwag |
Quote:
I suggest you to use sws 10. See there : http://www.wieser-web.de/MPlayer/sws1 |
Sorry folks but I cant duplicate these color probs as seen in the link!
a) Maybe these tests are old and therefore an old build was used where a colorpsace conversion was forced before when scaling!! Remember? b) When I did that mega mencalc-checking workout using standard "tv-geometric & color patterns" there I also didnt had any color probs. Do you think I would waste my whole time in doing GUIs for a "thing" which would result in such worse qualities?? :lol: |
Quote:
BTW, the first one that duplicate my semi-permanent problem with vobs source encoded with the double of the real number of frames wins a teddy bear. I'm not ready to stop telling that this encoder is not stable... Quote:
Quote:
Quote:
BTW, what does this sentence means ? I am the king of the color screwage and if I tell you there is not, THEN there is not ? Tsssss..... |
We all have to give you credit for being very persistant Phil :lol:
I know that if you say you had color problems is because you really did ;-) Did you try to replicate that lately? Did it happen with all the sources you feeded mencoder with? There's gotta be a pattern there :roll: Can you try and help us find it? Cheers m8 :D |
Sorry guys, but I gotta agree with him in some respects.
I also found colour wandering in mencoder, but I fount it mainly noticable on the 6 luma bicubic / chroma bilinear filter. I have to admit I didn't see it on the lanzcos filter. (Hey, can I still have the teddy? My wife collects them... :lol: :lol: ) v-- I'm with kwag, use sws 2 mostly --v |
Quote:
-kwag |
Quote:
Ok, mainly I used them cause of their Geometric graphics content. BUT they also do got color bars (some of them a lot color bars) and that was the case i.E. where I would see clearly what colors do come out. Here's for example the "Philips PM5544 Electronic TestCard". (Its an orig state out of a very nice test pattern maker program.) http://www.digitalfaq.com/archives/i.../2004/06/3.jpg Everybody could take that (well its 768x576 but the resol. conversions I posted below) and do an avisynth imagereader line where that avs will via Makeavis be inputted in mencoder. And do some tests For PAL: ImageReader("Philips PM5544 Electronic TestCard.tif", 0, 100, 25, true) ConverttoYV12() Bicubicresize(704x576) For NTSC: ImageReader("Philips PM5544 Electronic TestCard.tif", 0, 100, 23.976, true) ConverttoYV12() BicubicResize(704,480,0,0.6,0,1,768,574) These scripts do give a PAL or NTSC size/PAR compilant 100frames long stream of 704x576(480)px to the encoder. And THATs a way to find out WHAT will be done to colors. It makes no sense that many people do use diff movie inputs but do all try to see mencoders behavior related to colors. so: - which build is used of mencoder? - what colorspace goes in? - Does mencoder log report a colorspace converson (mine i.E. not if I go in with a VOB!) - Which decoder type is used "within!!" mencoder - Whats the source? Xvid, VOB, .... so: what input codec? - Use the testpattern above as reference to see what results. .... because that would be interesting why I dont have a problem but some other users DO have. Maybe its just a little "thing" which is done wrong by some users which we could find out and for suhre solving that. :) PS: I just made a fast test: A Mencoder output at 704x576 out of that testpattern above: (scaling via Avisynth) http://www.digitalfaq.com/archives/i.../2004/06/4.jpg (scaling via ":scale:" in mencoder -sws 9) http://www.digitalfaq.com/archives/i.../2004/06/5.jpg And ..... TmpgEnc (scaling via Avisynth) http://www.digitalfaq.com/archives/i.../2004/06/6.jpg And that happens in case of direct VOBs inputs in ALL my cases also! So the conclusion for me is clear ;-) |
http://www.digitalfaq.com/archives/i.../2004/06/1.jpg
And tmpegenc with v4 script at cq 70 http://www.digitalfaq.com/archives/i.../2004/06/2.jpg http://www.digitalfaq.com/archives/i.../2004/06/7.jpg And mencoder with v4 script bitrate 1160 Is an example of what the internal filters do to my avi sources (its also avs filters and mencoder as you can see in bottom pic). It's very clear in avi in dvd you have to look better bent when you use avisynth the colours are correct. |
Hi Koekies!
I didnt understand your workflow ? You did enter in tmpgenc using an avs where a XVID is inputted??? and on the other hand you did enter in mencoder by importing that XVID source directly and used the mencoder internal filters instead of avisynth?? So .... in here also a "codec issue" could be the problem, means how the "decoder" which is used to render the colors of the source codec input. So tell me your EXACT input codec (I see you use XVID) AND what is used as decoding dll in Mencoder AND in the Winsystem. |
From top to bottom
-The source an xvid (5 min sample) - tmpgenc3xp without filters mpeg2 cq70 - Mencoder with internal filters bitrate 1160 2 pass (different colours) - Tmpgenc 2,5 with v4 script and cq 70 - Mencoder with v4 script and bitrate 1160 2 pass (different colours) |
Your mencoder output is more "orange" then "red" in the face of the actor.
So I think theres something going on strange in "your" mencoder build and its used internal xvid decoder?? Theres something strange happen, cause as you see I dont got these probs like you can see above. |
I encoded them with the build included in MencodeMe
|
@rds
When you asked "Did you try to replicate that lately?" I thinl you want to say "Did it happens with lastest mencoder releaser" ? In fact I used only one release, the only one (I know) Inc does specially for P4. I can't tell you if there is a better one since then. Which kind of sources ? All ! Now I can't remember if the things where better or worst with a vob or with something read with a makeAVis file. I think there was with makeAvis. @Inc Color screwing is due to rounding in time with color compenent fluctuation between frames. For sure, with a static picture, you can't have that :-) But your snap are interesting to see how mencoder picture is worse than tmpgenc ones :-P (i'm just ki!dding here, but it's true, look at the borders of the external circle) @koekies Thanks for you snaps. |
http://www.digitalfaq.com/archives/i.../2004/06/8.jpg
This was made with inc's latest build as you can see the same problem occurs |
Quote:
Quote:
But you clearly see at the last two that there the mencoder picture does also have a clear non-ringed circle. ... cause I used the Mencoder internal filter sws9 and :scale.....9:. Tmpgenc was used at CQ 75 (if I do remember) Well In here we where talking about a color problem. But We already did found out that in case of 2pass even when using less filters in mencoder the pic is less blockier then when using CCE. But we already had so many discussions about that, so the pics here are for COLOR comparison :? :) @ Koekies WHAT does include your codecs.conf ??? Maybe the pointer to XVID forCC based inputs do point on a system dll in your system32 folder which gots a bad decoding behaviour (just assuming) ... hummmmm SO do look in the console log whats used to decode your XVID input!! Is a winSystem32 dll used or the mencoder internal XVIDlibcore ??? Well that latest build provided by me is an OLD build! Since that time many new CVS snapshots where offered at the mplayerHQ server. I didnt keep providing newest builds as my free account limit is reached very fast ... and nobody wanted (Maurus was the only one!) to share that providing of those builds as asked there in the thread. But users where downloading and downloading and downloading. So sorry for that. Best would be to get the latest MINGW compiled snapshot from the mplayer win32beta page: http://www.mplayerhq.hu/MPlayer/releases/win32-beta/ These are newer than my latest builds and maybe they do have a fix related to colorprobs??? Cause that "could" be now proofed in our workout in here :!: :) |
Inc,
I already downloaded the CVS version from the url you point at, trying to see if a different mencoder version helped in the hugh problems I'm having lately... Well, I'm just posting to say that it crashes on second pass. I'm using a avs source through makeavis, did first pass without a problem, but when begining second it crashes. Anybody else with the same problem, or is my PC asking formatting?. I'll retry with a vob source :roll: |
I do not have such probs!
Is the "divx2pass.log" ok?? |
Quote:
|
Phil as I do know, you got a P4 cpu?
Could you try (on a little - maybe 10mins- sample) a test using the "generic" build I did? Because IF that works, then the problem is due that I tried to compile a P4 build on an ATHLON, even I did set the correct P4 related params at ./configure. I cant test that as I do not have a P4 to test. BTW: I used my "old" build I offered and: No crashes AND no color probs! Tested on that "old" XP and Generic build. EDIT: PEEEEEEEEEEEEEEEEEEEEEEEEEEP! I did understand you wrong! So a new latest build configured by me "could" solve the problem??? That would mean I will compile a new CVS Snapshot right away as "I did understand" that you & DigiDoc got probs when using the MinGW builds from MplayerTeam??? PS: What do you mean by "don't have all the last improvements included" ? Do you refer to the newest developings based on Mplayer team and therefore new CVS Snapshots or do you refer to a incomplete ./configure Line? EDIT: Shure you mean that as I did understand your lines above now finally :lol: |
The mplayerHq builds don't support makeavis files and give the same results using internal filters. I'll check what mencoder uses to decode xvid.
|
Quote:
Quote:
Quote:
Quote:
Quote:
|
Phil, do read my Post completely as I did edit some passages where I added that I understood you. ;-)
SO: It could be that theres a codec issue! Means a) Ill check my codecs.conf as mybe it gots a pointer to the xvid.dll of my system, means not the mencoder internal xvidlibcore is used??? Ill check that as I experimented a lot with that the last week. EDIT!!: I checked it very easy when watching the log: WHAT DECODER FOR XVID is used in your's cases (Phil and Koekies) ??? Mine got that log output: Code:
AVI file format detected. SAME Colors compared with TmpgEnc!! Sorry but I dont know how to say it in an other way. Try the new "mencoder.exe" builds (Btw: I still did the tests above using the old one): - 06/13/2004 Generic CPU: http://home.arcor.de/ffvfw/Generic-20040613.zip AthlonXP CPU: http://home.arcor.de/ffvfw/AthlonXP-20040613.zip IntelP4 CPU: http://home.arcor.de/ffvfw/P4-20040613.zip (Cygwin1.dll is here: http://home.arcor.de/ffvfw/cygwin1.dll.exe ) |
Quote:
Quote:
Quote:
Quote:
Quote:
Testing it is somewhere in the zillion things I have to do that are prior so I hope someone else will test for you. |
Quote:
But as said, I checked several ways: - Xvid via Makeavis AVI + resizing in mencoder (means "scale:" is used) - Xvid directly into mencoder + resizing in mencoder (means "scale:" is used) - Xvid via Makeavis AVI + resizing via avs (means NO "scale:" is used) - Xvid directly into mencoder + resizing via avs (means NO "scale:" is used) All do come out including same colors as given when encoded using TmpgEnc .... So: Do get the latest Packshot beta (packshot thread) after unstuffing you get a Packshot folder where also the right codecs.conf is contained (in a separate "mplayer" folder) THEN do download the latest mencoder.exe build above related to your CPU and copy that mencoder.exe into the packshot folder. So mencoder.exe gots the right codecs.conf for working. Then do read the "For Avisynth support read this.txt" document where a link to the "standalone" version of FFVFW makeavis is given. Do install it and generate a textdocument using these lines: Code:
REGEDIT4 |
Quote:
Quote:
But I just did a fast chunk ( via slicer() ) XVID encoding out of a DVD where I used that XVID afterwards as input and for shure the colors are ok as the pattern also comes out correctly. If a pic stands "still" or not, the whole range of IBP is used when encoding and "technical" seen the encoder does a YV12 based encoding refering to the reference of predictied and bidirectional frames. And I do think in the sample of "Koekies" the actor "lays" on the floor, so there also will be no movement. But as I do take your knowledge seriously I did the test using the sliced encoding as said above and ... output also there is ok ........ hummmmm I hope "others" dont see that this workout in here is based on a feeling "I want to be right" as I WANT to find out WHY there are some color probs in case of some users. And as I cant duplicate them (and Kwag neither) we should find a solution ;-) |
Quote:
Take a white piece of paper, shoot it with a camera, capture the video and use it into avisynth : the signal is fluctuant. Take a photoshop picture of a white square, use it into avisynth with imagereader : the signal is constant. I think you can easily undersand that the first source will lead to problems that the second one will never have. Quote:
Quote:
For me the discussion ends here . There are other problems I had and not you (crash with last build, twice the number of frames encoded than the real ones* in the video, grainy picture even with no noise added...). And in this big bag you can addd the one of underflows : Kwag says he has none, I use to have DOZENS for each encode I did (with ans without noise added). Mencoder ? Out... bye bye. Do loose you time with this, I will live without. * I insist of this one because nobody even try to investigate on that. For me that is related to a mislead in the progressive/interlaced detection and if it is really related to that, you can imagine how bad is the output :!: |
Quote:
Well phil, ... till now we both did "discussions" like this to find out finally conclusions but I do accept your way if you drop things like now. (Btw: why then you get into it again like in here?) If everybody would end up in such a mess THAN it makes NO sense and we would loose time in such a case i would agree. You take your decision I do respect that, I DONT want to insist on mencoder BUT if I do see that a colorproblem "could" result of a simple mistake, then I think its nice to figure THAT out. And THATS the purpose of my whole latest posting count. |
Code:
AVI file format detected. And Tmpgenc's quality isn't worse and the colours are correct. Mencoder is still in an early stage so it's not really fair to compare them. Maybe the issues will go away in a later build. |
So Avis via makeavis does work?? As I do see in your log!
Btw ... thats not XVID direct input as the xvid decoding by this will be done via avisynth and therefore by the Codec dll in your system32 folder. |
Hi all,
sorry if I wrong you with my last post some posts earlier. The problem I was getting wasn't related to bad colors (I wish I could focus on looking if colours are OK), but that latest MinGW mencoder versions (CVS and pre) were crashing on second pass when loading a video via makeavis (with correct codecs.conf in mplayer). Well, I solved this problem when instead of using lmin=0.01 I used lmin=0.1 But I prefer to use latest Inc version (downloaded :wink: ), willing that it will solve my other problems (and because it loads the fake avi without needing a codecs.conf, did you add the support to ffvfw Inc?). My other problems are: - when encoding mpeg2 with maxrate=2500, I get bitrate peaks around 4000 :( (and when maxrate=7000, peaks 8300 :roll: ). - the worst problem (because it also affects KDVD) is that my player doesn't play well the video stream, and in sudden action it plays in a step-by-step way, even desynchronizing audio. And it doesn't need to be a too high bitrate peak: in my last test (Harry Potter Chamber of Secrets 352x288), at the begining when the camera flies between clouds, the player slows a little, but in bitrate viewer I just see a raise fron 300 to 1300 KB... still don't know why is happening this. BTW, how long have we gone OT? |
Makeavis works with your version and the one included with MencodeMe but not with the one on MplayerHq
|
Code:
AVI file format detected. |
Quote:
MakeAVIS that comes with FFvfw works with any mencoder build, period. I've tested that with many home made CVS builds and with the ones posted at mplayerhq, and I have their latests. That's only a matter of having the right codecs.conf file in a folder named mplayer inside the folder where you have mencoder. What I haven't been able to use is makeAVIS that comes with latest FFdshow and that was working with early mencoder builds. So let's not twist the discussian here ;-) We've been talking about color issue :idea: Who has seen this issue and in which cases? VOB source/AVI source/fake AVI by makeAVIS/PAL/NTSC/KDVD target/KVCD target/long 24-25GOP/short 15-18GOP, etc. Please post as much info as you can because I'm :banghead: here trying to replicate that and I simply can't :crashed: TIA :D Cheers |
Quote:
As I said, the discussion is already stopped for me. I really don't have more time to play with mencoder. Quote:
Quote:
Because this is not because I don't want to lose my time to do more tests that I consider my former experiences as inexistant. Because as I told (in other thread may be ?), if nobody explains to Kwag why and how mencoder is NOT a such good encoder, anyone (I mean the majority here, not people like you or some othr heavy testers) will just drink what he has to serve like if it was god words. I'm deeply sorry but the extract he provided about Back To The Future is awfull. I don't care about the source quality ! And I don't care if the result took 1.6GB or 3 complete DVD ! If anyone would have produced that with other thing than mencoder there will be noone to qualify that as good. We all know that there is lot of ways to have far better results whatever the quality of the source. Just to return back to this color problem : I'm not the one who mentioned it. I just been happy to see someone mentioning it. Quote:
Quote:
I do not have any codec.conf file (nor any conf file at all). I have the same xvid codec realease than anybody (and surely you) I use winXP and a correct installation that works anytime, whatever the job I do. I use a mencoder release that you used to try also (I guess you try the builds you provide ;-)) The only real diff is that you are using an Athlon and I have a P4. IF that is the source of the problem THEN that really confirm that mencoder is not a stable encoder ! We all agree that there are big diff between the processors, but a well coded software should give the same results on both architecture. FYI I tried to use the generic build (the one that crashed on my PC) because I started to have suspicion about a problem with the P4 specific one. That's also why I will try the build you did today but as I said, I have a lot of things to do so I wish koekies tries it also. Quote:
What a really stable and predictable encoder we have here... :hihi: |
Oke Inc I downloaded your new build should I change some things in the codecs.conf you get with the mplayer source (in the etc directory)
to the things you say in the Latest CVS Snapshot Mencoder Builds topic? EDIT: there are 2 codecs.conf in your the pack shot I downloaded both in the mplayer sub dir should I just copy mencoder there? |
I found both these xvid settings in your codecs.conf wil mencoder choose ffmpeg.dll? Could I delete the bottom one?
Code:
"FFmpeg MPEG-4" Code:
"XviD (MPEG-4)" |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.