MeGUI/Profiles
From MeWiki
Profiles are MeGUI's way of remembering groups of settings. They are very useful in saving the user work when doing the same thing multiple times. Use them!
Contents |
General
How they work
A profile has a name and the settings that you configure. In various places where there are settings (the main window, the One Click Encoder, the AviSynth script creator) you can name your settings by saving a profile. You can access those settings later by clicking on the name in the combobox, and those settings will be selected.
Importing/Exporting profiles
Profiles are kept within MeGUI, and it is best to let it manage them itself. However, profiles are often useful to distribute, so you can share settings. The safest way to do this is using MeGUI's import/export profile functions, which you can access from the file menu of the main window. This will take care of any external files required, as well as other profiles required, and it will package them for you in a nice zip archive.
AviSynth Profiles
AviSynth profiles, just like other profiles, contain the settings grouped under a name. However, they also provide a more advanced kind of setting: AviSynth templates.
AviSynth templates are a flexible way of inserting custom filters while retaining some of the automation that MeGUI provides. Of course, you should only play with these if you are familiar with AviSynth, or else you could run into a lot of trouble with broken scripts.
The idea behind the AviSynth profiles is that, for most AviSynth processing, large amounts of your filter-chain will remain the same, while some parts will have to be source-specific (like loading the input, cropping, etc). The way MeGUI manages both parts of this, then, is to allow you to outline the basic structure of the script, then it configures the source-specific values.
How it actually works:
- You write a template script.
- When MeGUI needs to generate the actual AviSynth script, it loads the template script and it replaces <resize> with the correct resize filter, <denoise> with the correct denoise filter, <crop> with the correct cropping values, and so on for <input> and <deinterlace>. Everything else, it leaves the way it is (don't worry about remembering those keywords; MeGUI has buttons to insert them for you).
That's all that MeGUI does. Now let me give an example. Suppose you have this SUPER FABULOUS TEN-TIMES-BETTER-THAN-ANYTHING-ELSE deinterlacer, but MeGUI doesn't support it. Not to worry, here's what you do: copy and modify the default profile, which looks like
<input> <deinterlace> <crop> <resize> <denoise>
and make a new profile like this:
<input> MySuperDeinterlacer() <crop> <resize> <denoise>
Now, when generating the script, MeGUI won't insert its own deinterlacer, but it will leave yours there. Here's an example of what might be the result:
mpeg2source("Yoursource.d2v")
MySuperDeinterlacer()
crop(10,24,-88,-20)
lanczosresize(320,240)
#denoise
Notice that the denoise is commented out. This is what happens if the user chooses there not to be any denoising. The same goes for all the optional filters.
If you want to add a postprocessor, just add a filter at the end. You get the point.
