MeGUI: General Questions and Troubleshooting Thread

[hello_hello]

For anyone running XP, MeGUI updates it's Avisynth+ to a non-XP compatible version when it updates Avisynth+ to version 3.5.1.
To get MeGUI working again, you need to follow my instructions in a couple of posts prior to this one, using the XP compatible versions of Avisynth+ and it's plugins from here.

The file you need to download is "AviSynthPlus_3.5.1_20200402_filesonly.7z"

[Lord Dredd]

Hi
I would be grateful if someone can guide and explain how deblocking works in the newer megui versions.

I read and re read a lot of older threads and my mind is totally confused about what are the sane values of alpha and beta,
Some claimed using-3.-3 to give a sharper look 1.e. not letting the x264 encoder to smoothen up the source
some claimed the safest option to just keep ( if one is inclined to give a sharper look to the video ) is -2,-1

I am totally confused now so mucj so that I have totally forgotten about how it works

every few months I get an urge to re encode a few of my videos just for the heck of it , these are again those times

HD and FHD both i am trying my hands on

[Zetti]

Hello.

When i cut videos, i can't get the last frame.

This cut should give me 33537 frames but it will only give me 33536 frames.

__film = last
__t0 = __film.trim(33536, 67072)
__t0

MeGUI will only let me cut these frames of a the video (33536, 67071), i have tried to edit the last frame to 67072 so i can get all frames but the last frame is still 67071

Can it be a bug in MeGUI or Avisynth??

[videoh]

If you mean the last frame of the file (rather than last frame of your trim) then specify 0 as the last frame. That will include the final frame of the file.

[Zetti]

When i specify 0 as the last frame, i still only getting 33536 frames and not 33537 frames.

[tebasuna51]

Originally Posted by Zetti

When i cut videos, i can't get the last frame.

This cut should give me 33537 frames but it will only give me 33536 frames.

__film = last
__t0 = __film.trim(33536, 67072)
__t0

MeGUI will only let me cut these frames of a the video (33536, 67071), i have tried to edit the last frame to 67072 so i can get all frames but the last frame is still 67071

Can it be a bug in MeGUI or Avisynth??

If your video have 67072 frames the last frame is the 67071 because the first frame is the 0

[tebasuna51]

Originally Posted by Lord Dredd

I read and re read a lot of older threads and my mind is totally confused about what are the sane values of alpha and beta,
Some claimed using-3.-3 to give a sharper look 1.e. not letting the x264 encoder to smoothen up the source
some claimed the safest option to just keep ( if one is inclined to give a sharper look to the video ) is -2,-1

There aren't changes in MeGUI about that point.

If you limit the deblock filter (-3,-3) you can obtain macroblocks in the video, is recommended only with high bitrates (crf 16 for instance) and now you can obtain sharper look, if you want less bitrate (crf 19 for instance) is better let the default deblock (-1,-1).

BTW is your choice, limit the deblock filter -> risk of macroblocks at low bitrate.

[hello_hello]

Originally Posted by Zetti

When i specify 0 as the last frame, i still only getting 33536 frames and not 33537 frames.

If you navigate to the end of the video using the AVS Cutter you'll see something like this in the title bar above the preview.

44871/44872

Which shows there's a total of 44872 frames in human counting, while using Avisynth's counting (where the first frame is number zero) the last frame is number 44871.

Likewise the first frame would display as

0/44872

[Zetti]

I think i understand it now but it will make more sense that frame 1 is frame 1 and not frame 0

[stax76]

I guess most apps show the current frame zero based because most programming languages use zero based collections and programmers are used to that. Lua which is used by mpv is using 1 based collections.

[videoh]

Originally Posted by Zetti

I think i understand it now but it will make more sense that frame 1 is frame 1 and not frame 0

If you are a Pascal programmer, OK. C/C++ not so much. If you are not a programmer, who cares? RTFM.

[beto]

I am using version 2913 from the development update server. I am having an odd issue trying to index a VOB file obtained from a DVD.

Whenever I try to index this VOB file (using DGINDEX since L-SMASH and FFMSINDEX both appear grayed out to me with this MeGUI version) the file indexes partially and not entirely. It indexes around 45 minutes of the VOB file and the rest is not indexed and appears to be truncated. There are no apparent error messages.

If I use DGIndex directly (and not through MeGUI) the file indexes entirely with no issues.

The logs related to the indexing job are available below if anyone is interested:

https://pastebin.com/kyPXW7K5

I am on Windows 10 v1909.

Any help is appreciated.

Regards.

[Lirk]

MeGUI version 2913 crashes when using yadifmod2 plugin.

[jlw_4049]

When I setup a series of batch encodes, the workers will only do 1 encode at a time, regardless of how I set the worker settings.

[kalehrl]

Press start button and new video encode worker will start and then you won't need to manually start them once again.
When one finishes, the other will pop up.

[Lord Dredd]

Originally Posted by tebasuna51

There aren't changes in MeGUI about that point.

If you limit the deblock filter (-3,-3) you can obtain macroblocks in the video, is recommended only with high bitrates (crf 16 for instance) and now you can obtain sharper look, if you want less bitrate (crf 19 for instance) is better let the default deblock (-1,-1).

BTW is your choice, limit the deblock filter -> risk of macroblocks at low bitrate.

Thanks a lot for the tip
But -1,-1 aint default anymore, No matter the profile settings the default de-blocking values are 0,0 now , are you suggesting its best to use -1,-1 for crf values from 19 to lets say 21 ??
what about x264 and x265 , Should one stick to same -1,-1 for lower bitrates for x264 and x265 encoding ???

once again many thanks Big T

Also just to get some sharpness going at those crf values , do you recommend any avisynth sharpening filters as well , nothing complicated may be something internal just to give some sharp margins and stuff.
Thanks

[tebasuna51]

Originally Posted by Lord Dredd

But -1,-1 aint default anymore,

You are right, -1,-1 is added by -tune film, recommended for film movies.

Also just to get some sharpness going at those crf values , do you recommend any avisynth sharpening filters as well

There are a internal filter Sharpen but I never use it.

[Lord Dredd]

Originally Posted by tebasuna51

You are right, -1,-1 is added by -tune film, recommended for film movies.



There are a internal filter Sharpen but I never use it.

Thanks a bunch Dear mate
Being an expert : what would you suggest to an eternal newbie and hobby encoder like myself , about getting good details and least blocking in a low bitrate x264 or may be x265 encode.

In x264 i tend to use slower preset always with no filters via AVISYNTH , try to use crf around 19 to 22 , sometimes I try and use 2pass with bitrates of around 1200 to 1600 to see how much details one can retain , but the fuzzyness in the background and margins can be caught when you watch the video from pretty near the TV ( Have a HD TV in my study 32inches )


Recently i started experimenting with x265 as well , but I was surprised to see that there is no option to look through advanced settings like x264 has , also I found the colors of a x265 encoded video are colder than x264 ( May be its just me ).

--- What would be your recommendations regarding encoding with x265 , MEDIUM , crf21 I guess ?? I always try and see how low one can go in bitrate but still maintain decent details and sharpness ..


Would be highly THANKFUL for the suggestions...
God Bless


EDIT :
I have heard a lot of people say that using VBR mode of encoding can prove magic for low bitrate encoding process, especially by settings qcomp to 0.9ish ( I know how our developers feel about qcomp here at MEGUI) hence asking again ...
How can one encode in VBR via MEGUI in crf and 2 pass encoding and whats the sweet value of qcomp

Thanks again

[tebasuna51]

I'm not a expert in video encode at all (my specialty is audio).

- Slower presets are always better if you don't care encoder time.
- Use filters only if the source need them.
- The bitrate 1200-1600 only for low resolution (DVD sources)
- x265 better improvements for high resolution (1080 or more)
- VFR can save some bitrate, but can be a problem for players or further recode.

Test yourself.

[Lord Dredd]

Originally Posted by tebasuna51

I'm not a expert in video encode at all (my specialty is audio).

- Slower presets are always better if you don't care encoder time.
- Use filters only if the source need them.
- The bitrate 1200-1600 only for low resolution (DVD sources)
- x265 better improvements for high resolution (1080 or more)
- VFR can save some bitrate, but can be a problem for players or further recode.

Test yourself.

sure
Any idea how to turn on VFR in megui ???
I dont see that option anywhere.

Originally Posted by Lord Dredd

Thanks a bunch Dear mate
Being an expert : what would you suggest to an eternal newbie and hobby encoder like myself , about getting good details and least blocking in a low bitrate x264 or may be x265 encode.

In x264 i tend to use slower preset always with no filters via AVISYNTH , try to use crf around 19 to 22 , sometimes I try and use 2pass with bitrates of around 1200 to 1600 to see how much details one can retain , but the fuzzyness in the background and margins can be caught when you watch the video from pretty near the TV ( Have a HD TV in my study 32inches )


Recently i started experimenting with x265 as well , but I was surprised to see that there is no option to look through advanced settings like x264 has , also I found the colors of a x265 encoded video are colder than x264 ( May be its just me ).

--- What would be your recommendations regarding encoding with x265 , MEDIUM , crf21 I guess ?? I always try and see how low one can go in bitrate but still maintain decent details and sharpness ..


Would be highly THANKFUL for the suggestions...
God Bless


EDIT :
I have heard a lot of people say that using VBR mode of encoding can prove magic for low bitrate encoding process, especially by settings qcomp to 0.9ish ( I know how our developers feel about qcomp here at MEGUI) hence asking again ...
How can one encode in VBR via MEGUI in crf and 2 pass encoding and whats the sweet value of qcomp

Thanks again

Originally Posted by tebasuna51

I'm not a expert in video encode at all (my specialty is audio).

- Slower presets are always better if you don't care encoder time.
- Use filters only if the source need them.
- The bitrate 1200-1600 only for low resolution (DVD sources)
- x265 better improvements for high resolution (1080 or more)
- VFR can save some bitrate, but can be a problem for players or further recode.

Test yourself.

@ All tebasuna51 has been very helpful
I would be grateful if you guys can chip in with your specialist opinions regarding my queries I mentioned in previous post