If that doesn't work try shutting own MeGUI, opening the settings.xml file in MeGUI's installation folder with notepad, and do a search for YV12.
There's a button in MeGUI's option for resetting dialogues. It's just a bit more info for you.ĭid you check the "don't bother me with this s#*t again" option last time it asked if you wantred the colorspace conversion added to the script? You don't really need to understand it completely.
MEGUI 64 BIT WINDOWS 7 HOW TO
It's just some information on the colorspaces Avisynth will play with and how to convert between them. If you want to read a bit more about colorspaces, there's some info here. That's all my guesses used up for the moment. If it's mpeg2 video in the TS file MeGUI will default to DGIndex for indexing and that'd be the best option. With ffmsindex or L-Smash doing the indexing and then the decoding (depending which you choose) there should be no conversion. Add the indexing job to the queue and run it. Use MeGUI's File/Open menu to open the video. It's not necessarily the most reliable method anyway. If you're not using a DirectShow decoder you can configure yourself, maybe don't use Directshow. Or before adding ConvertToYV12() to the end of the script, add Info() and you should learn which colorspace you're working with that way. I don't know what decoder you're using (something that came from Microsoft with Windows?) but for me it's easy enough to see the format when decoding via DirectShow because ffdshow and it tells you. Maybe whatever codec is decoding is also converting to another format in the process (edit: it looks like jagabo beat me to that one). Someone else may know something about the recorder, but maybe it's the decoding and not the original video. What's different about the latest source? Did it come from somewhere unusual? A type of video you don't normally work with etc? There's no colour issues to worry about when it's YV12 in and YV12 out (unless you're downscaling HD to SD but that's another story). YV12 is the standard colorspace used for most video (mpeg, DVD, Bluray etc). Depending on the conversion taking place if they're converted with the wrong formula the colors can look slightly different (high def or standard def formula) and you can't even trust MeGUI's preview for that one. It might pay to check the colors of the encoded video are the same as the original. The x264 encoder can cope with a few different input formats but MeGUI assumes you're ultimately going to want a YV12 encode so I think it plays it safe and offers to convert it for you regardless. And now after all these years, you're encoding a video that isn't YV12.
Probably because up until now, all the video you've encoded has been YV12, and MeGUI and the tools it uses can all process YV12 video, so it's always been YV12 in/out. Could someone please post a very brief idiots' guide as to what this 'problem' is exactly and whether i should add the extra instruction to the avs script? And why has this suddenly surfaced after all these years?Thanks.
0 kommentar(er)
