View Profile
View Forum Posts
Private Message
I had to use DirectShowSource for the first time and I'm not too familiar with that plugin.
When using it, I get an error saying I need to be in YV12 for my antialiasing filter MAA2 to work. So I found 2 ways to convert it to YV12 and am not sure which is the better one.
Which is the better or proper way of doing this?
1.
DirectShowSource("C:\Users\???\Desktop\Encoding\Mo vie\00001.m2ts", fps=23.976, audio=false, convertfps=true).AssumeFPS(24000,1001)
ConvertToYV12(matrix="rec709")
2.
DirectShowSource("C:\Users\???\Desktop\Encoding\Mo vie\00001.m2ts", fps=23.976, audio=false, pixel_type="YV12", convertfps=true).AssumeFPS(24000,1001)
I never used DirectShowSource except once before on an MKV file and I've only ever converted to YV12 with ConvertToYV12 filter once before so was unsure which is the better usage.
The first one has the option rec709 but the second one doesn't. I don't know if that's important or not. The first one is also an extra plugin/filter and line in the script, while the second one is using DirecShowSources ability to convert to YV12 in the same plugin/filter. I don't know if that's better or not using the one built into DirectShowSource.
I notice the first one, I can look through it and change frames in the preview window of my encoding program but the second one, it just stays frozen on a single frame and the preview wont move at all from that image even if I change the frame. The second one still seems to work though even if the preview doesn't.
+ Reply to Thread
Results 1 to 13 of 13
-
-
Why do you have a "Fps" in there along with an "AssumeFPS"? That's redundant, particularly when they seem to specify the same amount (barring rounding).
The difference I see in your colorspace is what you mentioned: rec709 vs. ?/auto. What is your source? - HD or SD or something else? That should determine which rec should be applied.
However, you've got a source which is from .../*.MTS. If that came direct from a camera (and not a professional $$$ one), it has to be YV12 already. Though it does make sense to specify this at the beginning, as the DSS parser might get it wrong in auto mode.
Also, DSS is sometimes NOT the best choice because it has trouble seeking certain files - particularly similar to what you seem to be experiencing (and I think with MTS files it would also fall under that category). I would think DGDecode would do a better job.
Scott -
#2 may be better. It will request that the decompression codec output YV12 directly if possible. Having the decoder output YV12 from a YV12 source will avoid the double conversions in #1. Whether that YV12 is rec.601 or rec.709 depends on the source. Ie, if the source is rec.601 you'll get rec.601, if the source is rec.709 you'll get rec.709.
-
The fps stuff was all put into the script automatically by MeGui after choosing to use DirectShowSource. I didnt do that.Originally Posted by Cornucopia
Its an M2TS file so its HD because thats from a Blu-Ray.
DGDecode is screwing it up, I cant use it for this source. Go read here https://forum.videohelp.com/threads/368455-Blu-Ray-video-becoming-corrupt-or-something-...y-to-encode-it.Last edited by killerteengohan; 21st Nov 2014 at 14:59.
-
Would the double conversion hurt it badly? I didn't notice any output difference in the preview. Are you sure that second method is auto and it will pick the proper rec on its own? If its auto, then I see no reason to even consider using #1.Originally Posted by jagabo
Last edited by killerteengohan; 21st Nov 2014 at 15:00.
-
You could try DGAVCDecDI, but it costs something ($15USD, IIRC). Or try MVCSource, it's built to understand MVC as well as AVC (and in TS streams), but even though you don't need the MVC portion, might be good for you. Just a guess, haven't tried it yet myself.
Scott -
Usually, no.Originally Posted by killerteengohan
It won't "pick" anything. YUV out of the decoder will be rec.601 if rec601 went in, rec.709 of rec.709 went in.Originally Posted by killerteengohan
-
What jagabo is saying, that you might not be picking up, is that "rec601" and "rec709" really only come into play when converting YUV<->RGB. If it stays in YUV land, those don't apply. Think of those as "color conversion formulas".
Scott -
Well colorspace and those different versions of them aren't really my strong point so I wasn't aware of that. I usually never have to mess with or change them at all so I still have stuff to learn about the converting color types or about them in general.
I'm afraid to go with the #2 because the preview wouldn't work and I'm worried my output wont be able to seek at all when played back in a mediaplayer, but I guess Ill give it a go. Am I going to have to worry about not being able to seek in my media player after the encoding is done?
Thanks for the info!! -
What does that mean? Did you get an error message? Did you get a blank screen? Something else?Originally Posted by killerteengohan
After you've encoded the video you have a completely new video. Whether or not you can seek the new depends on the new encoding, not how the original video was handled. It's like recycling aluminum cans. The size and shape of the new cans depends on how you manufacture them, not the size and shape of the original cans.Originally Posted by killerteengohan
-
Originally Posted by jagabo
What does that mean? Did you get an error message? Did you get a blank screen? Something else?Originally Posted by killerteengohan
Exactly what I said in the first post is what I mean.
Originally Posted by killerteengohan
-
Anyways, it turned out great and I watched it and there was no problems at all using method #2
-
I don't know why the preview would be stuck on the first frame. But you need to keep in mind that DirectShowSource() isn't always frame accurate and doesn't behave the same on all systems. It relies on whatever DirectShow components are installed. Different readers, splitter, and codecs will give different results. It looks like it's working for your conversion though.
Quote
