Does megui used the processed video from ffdshow?

[ikwiata]

My ffdshow is config'd to do postprocessing, picture properties, sharpen.

I notice the tray icons are present when I'm encoding with megui.

Is it using that processing video as the video input?

For example, if I alters Levels in the ffdshow config, is that going to affect the new video?

[buzzqw]

simple answer YES

what ever postprocessing you are using that filters are applied on image

BHH

[Sharktooth]

if the AVS script uses DirectShowSource() AND you enabled FFDShow output for uncompressed video than the answer is YES.

[ikwiata]

Thanks for the responses.

I probably should've put this in the OP as well.

Is there any way to disable this behavior? Or does it require disabling all filters before encoding?

[foxyshadis]

You can set quite a few behaviors in the preset selection. For instance, create a blank preset and set it to autoload for application MeGUI, x264, an xvid_encraw.

[ikwiata]

Awesome! Exactly what I wanted. Thanks.

[orangedude]

Just a quick question about this. Is it a better idea to encode videos in MeGUI with postprocessing enabled in FFDSHOW or with it disabled (blank profile)? Thanks.

[Adub]

What? Can you reword that sentence?

[orangedude]

Is it better to enable postprocessing in FFDSHOW when encoding to X264 or not?

[berrinam]

It might be of interest that sometime in the future, MeGUI will probably support ffmpegsource, which means that a lot of the uses of DirectShow (and ffdshow) will be reduced (eg mkv, mp4)

[Sharktooth]

i think we should focus on ONE framework.
mixing things usually ends up in a mess.
i mean, directshow is a very good choice since there is ffdshow that can do a LOT of things as preprocessor as well as avisynth that's fast and versatile. mixing DS decoding and ffmpeg is usually a pain in the a$$.

[buzzqw]

just 0.02 €

in automkv when DSS fails , i switch to ffmpegsource

BHH

[Sharktooth]

uhm... if its a second choice... then why it's ok. but i have my doubts using it to replace DSsource completely.

[buzzqw]

dss could fail opening mov or mp4 files, even more for aac audio

it's a second change, not a replace (imho)

BHH

[berrinam]

i think we should focus on ONE framework.
mixing things usually ends up in a mess.
i mean, directshow is a very good choice since there is ffdshow that can do a LOT of things as preprocessor as well as avisynth that's fast and versatile. mixing DS decoding and ffmpeg is usually a pain in the a$$.

DirectShowSource has problems with frame-accurate seeking, and postprocessing as well as funny colorspace conversions can also cause a mess on badly setup computers. As far as I'm aware, ffmpegsource solves these problems. You don't lose the functionality of avisynth, since it is an avisynth plugin; it also means you don't have to deal directly with ffmpeg, since it is just a plugin based on ffmpeg libraries.

Also, I think that ffmpegsource allows you to select audio track number, whereas I don't believe directshowsource does.

I am generally somewhat afraid of directshowsource since it pulls in a large unreliable(-seeming) API for what is often a much simpler task.

@buzzqw: Why is it your second choice, not your first choice? For the reasons I mentioned above, isn't ffmpegsource better than DSSource if it works?

[buzzqw]

ffmpegsource is a beta software... and i must admit i haven't tested it as much as the old DSS

maybe after a good set of test i will switch.. but not now

BHH

[orangedude]

Uh... no one's answered my question yet. Is it better to enable postprocessing in FFDSHOW when encoding with MeGUI or not?

[Sharktooth]

depends on your source. if it's blocky or has ringing then yes...
but postprocessing kills details in good sources.
however you have to ensure you use DirectShowSource() and FFDShow enabled for RAW output (or being used for decoding) otherwise the FFDShow processing wont happen.