MeGUI: General Questions and Troubleshooting Thread

[videoh]

DGDecNV or DGDecIM will properly handle those AVC streams.

[ryszardzonk]

yeah except is DGDecNV is for nvidia cards only which kinda sucks if you have shiny new radeon which is what I purchased just prior to buying licence for it and second DGDecIM has no gui like other DG* tools have which mean I am not able to use it to make indexes with parts already cut out to feed it into MeGUI. That leaves me only with l-smash which by all means is perfect for the job. Only those delays kinda strange.

From further testing I did it seems that it is not index that gets recreated as time on those files does not change. It might be related to this https://github.com/l-smash/l-smash/issues/7 Probably whole index has to be read and movie checked to go through the megui heuristics of AVS script checking for proper values.
Question is there any way around it? Possibly option in preferences to disable that script checking until it is started in the queue could appear?

[Zathor]

2529 [MainForm] improved Drag & Drop handling. Bug #786
2528 [AVI Muxer] disabled FPS change option as it is not supported. Bug #785
2527 [Audio Encoder] fixed RaWavSource() for 64bit files >2GB. Bug #792
2526 [HD Streams Extractor] fixed 3D Blu-Ray processing (regression of eac3to 3.28+). Bug #795

[salam2009]

Hi everyone,
I get this frustrating mkvmerge error occasionally after encoding videos (without adding their audio tracks) using x264 Encoder (which I need) then muxing the result with the audio from the file source.

"video.720p.mkv: Error in the Matroska file structure at position 4010858. Resyncing to the next level 1 element.
The last timecode processed before the error was encountered was 00:00:19.978000000.
Resyncing successful at position 4782373.
The first cluster timecode after the resync is 00:00:25.025000000."

Now when the video reaches the defective minutes, the picture freezes with continuous audio until the point of the first cluster timecode arrives!
If the error doesn't show up in mkvmerge, the muxed file will probably get the same issue!
I tried the old versions of mkvmerge to be sure but got the same error, so it must has something to do with MeGUI encoding process.
I'm using v2525 of MeGUI with updated components and even tried reinstalling it along with K-Lite Mega Codec Pack but sadly that didn't help either!
Any tip would be greatly appreciated.
Thanks a bunch!

Cheers,
Salaam

@Zathor
Here you go:
http://pastebin.com/7X64tJeS
It used to encode properly before! I even tried without any AviSynth script and the same thing.
Thanks for any tip :)

@Zathor
Just in case you missed it.

[videoh]

DGDecIM has no gui like other DG* tools have which mean I am not able to use it to make indexes with parts already cut out to feed it into MeGUI. That leaves me only with l-smash which by all means is perfect for the job. Does Lsmash have a GUI that makes those cuts? Just trying to understand what Lsmash is giving you that DGDecIM does not.

[ryszardzonk]

Lsmash is easier to use as it is present in the MeGUI while DGDecIM is not and is command line only. From picking the two index creators preparing the index I therefore much rather use Lsmash.

Lsmash is also actively developed while the other is not which means that in the future there will be codec which first will support and latter would not. There is a chance that someone would take a look at my posts and figure out the way to speed up the avs creation through megui based on its index ;)

[Zathor]

@Zathor
Here you go:
http://pastebin.com/7X64tJeS
It used to encode properly before! I even tried without any AviSynth script and the same thing.
Thanks for any tip :)

Is the problem reproducible? In the log I cannot find the error at all. If yes encode from the command line or with a different tool If the problem still exist you should ask for support on e.g. on the mkvmerge side.

[salam2009]

Is the problem reproducible? In the log I cannot find the error at all. If yes encode from the command line or with a different tool If the problem still exist you should ask for support on e.g. on the mkvmerge side.

What about log's "Standard error stream" repeated errors?
And how do I run the command line exactly?
I don't think it has to do with mkvmerge as it only occurs with MeGUI encodings!
Thanks man :)

[tebasuna51]

What about log's "Standard error stream" repeated errors?

Blocks like:
--[Information] [01/04/2015 06:13:11 ?] Standard error stream
---[Information] [01/04/2015 06:13:14 ?] raw [info]: 1280x536p 1:1 @ 60000/1001 fps (cfr)
...
---[Information] [01/04/2015 08:28:31 ?] encoded 342413 frames, 42.18 fps, 4716.90 kb/s

are only info with encoding statistics.

In your pastebin there are 10 jobs without errors.

[LigH]

Many CLI encoders prefer writing normal information for reading on the console to the "standard error stream" (STDERR) to avoid corrupting the output of the encoded video bitstream in case it is redirected to a pipe, using the "standard output stream" (STDOUT) for the video output in this case.

To avoid being alarmed about it, the log categorizes this output as "[Information]". Always remember, there are three stages of messages from an application to a user:

[Information]: Notice it or ignore it, but everything is fine.
[Warning]: Please notice it and think about it, decide for yourself if everything is still fine.
[Error]: Something is not fine. Now you may be concerned.

Using the STDERR, though, is nothing to be concerned about a priori; it is just an alternative text output stream, used to display text when the STDOUT is already redirected and may not be read by the user.

[salam2009]

Blocks like:


are only info with encoding statistics.

In your pastebin there are 10 jobs without errors.

Many CLI encoders prefer writing normal information for reading on the console to the "standard error stream" (STDERR) to avoid corrupting the output of the encoded video bitstream in case it is redirected to a pipe, using the "standard output stream" (STDOUT) for the video output in this case.

To avoid being alarmed about it, the log categorizes this output as "[Information]". Always remember, there are three stages of messages from an application to a user:

[Information]: Notice it or ignore it, but everything is fine.
[Warning]: Please notice it and think about it, decide for yourself if everything is still fine.
[Error]: Something is not fine. Now you may be concerned.

Using the STDERR, though, is nothing to be concerned about a priori; it is just an alternative text output stream, used to display text when the STDOUT is already redirected and may not be read by the user.

Got it! Thanks for clearing this up.
Still have to try the command line encoding (which I still don't know how) if it ever gonna solve my issue!

[Zathor]

In the log you can see lines starting with:
Job commandline: "C:\Program Files (x86)\MeGUI\tools\x264\avs4x264mod.exe"

Copy the whole line to a cmd window and execute it. The encoding will be done without MeGUI - you can do that also with mkvmerge.exe
EDIT: Copy everything after "Job commandline: "

[salam2009]

@Zathor
cmd gives me this error:
'Job' is not recognized as an internal or external command, operable program or batch file.

[LigH]

Then you copied too much. Only the content of the job command line, after the colon!

[salam2009]

Oh! Didn't know that :o
OK, tried encoding 2 videos via command line and didn't get any errors in mkvmerge!
What's that suppose to mean? Does the GUI faulty somehow? I've reinstalled it earlier.
Thanks for the awesome support guys!

[LouieChuckyMerry]

Please, is it possible to have MeGUI's File Indexer default to "L-SMASH Works" instead of "FFMSIndex"? I ask not because it's difficult to tick the "L-SMASH Works" option but because I too often forget to tic the "L-SMASH Works" option ;) . Thanks.

[GodRealm]

Hello! I wonder, what is the forecast for the adding of 2-pass parameter on x265, because other software already accept this, least MeGUI.

[Zathor]

Likely soon, but soon still may be weeks or more.

[GodRealm]

Likely soon, but soon still may be weeks or more.

Thank you! I will be waiting.

[honey01]

@Zathor

Thank you.. I'm also looking forward to 2 pass x265 in Megui preferably in One Click Mode

And any update on feature request #457 Pause encoding ?
Encoding x265 takes a lot of time, so pause button will be great. (maybe we can put the machine to hibernate and resume at a later stage?)

Finally when encoding x265 in Megui, the Mediainfo is kinda blank.
I mean it doesn't mention the x265 version used or any other x265 parameters.
Is it a known bug?

[LouieChuckyMerry]

Happy Friday! Please, is there a method to have MeGUI default to "L-SMASH Works" instead of "FFMSIndex" when loading an .mkv? Perhaps a trick with the setting.xml? Anything? Thanks.

[hello_hello]

And any update on feature request #457 Pause encoding ?

Yes please! For x264 encoding also!

[Kurtnoise]

Happy Friday! Please, is there a method to have MeGUI default to "L-SMASH Works" instead of "FFMSIndex" when loading an .mkv? Perhaps a trick with the setting.xml? Anything?
why a such request ?

[hello_hello]

why a such request ?

I'd like the ability to set the default indexer, and I'd like to go further and be able to set it for specific file types, and in a perfect world where everything is made of chocolate, I'd also like to be able to specify which indexer to use according to video type.
MeGUI already makes some of those choices anyway (for example it'll index TS files containing mpeg2 video with DGIndex but won't if TS files contain h264 etc).

There's an established problem with ffms2 and AVIs when a frame rate is specified in the script (an issue with frames being dropped/repeated), so I'd like to be able to tell MeGUI to use AVISource or L-Smash for those.
And indexing some AVI's with ffms2 results in this:
[Error] [18/04/15 4:14:21 AM] Process exits with error: 1
I'm fairly sure that's ffms2 being all upset when there's junk data at the beginning of an MP3 audio stream, because if you elect not to index the audio the job completes, but I do forget to change the indexer to L-Smash quite a bit.

The current ffms2 errors out every time I try to index an MKV containing lossless video, so I'd like to tell MeGUI to use L-Smash for those in case I forget.

ffms2 tends not to play well with VC1, so maybe L-Smash there too, but I'm happy to use it for most other files.

Thinking about it......
Given L-Smash now has the same fpsnum & fpsden parameters as ffmsindex, it'd be nice if MeGUI could add them to the script when indexing with L-Smash too, because playing favourites seems unfair...... ;)

And I'd really, really like an ability in the Script Creator GUI to change the frame rate MeGUI adds to the script when indexing with ffms2/L-Smash, just as you can when using DirectShow for the same reasons, and because when MeGUI can't determine the frame rate it defaults to 23.976 which isn't the best frame rate to default to 99.999% of the time and changing it manually is an exercise in frustration because every time you change anything in the Script Creator (ie cropping) MeGUI re-writes the script which changes the frame rate back to 23.976 and eventually it wears me down and I feel like crying.....

Personally, I'd pick a higher frame rate as the default if MeGUI can't determine the frame rate. I think 29.970 would be a better choice. If the video is actually 23.976 it's easy enough to enable de-interlacing and apply a little decimation, but if it's 29.970 and MeGUI specifies 23.976, applying un-decimation is a little trickier.....

On the subject of decimation (referring to the "M" value in the Script Creator), there should be no ability to add a decimation of zero to a script because it makes no sense and just results in an error (unless when zero is specified the decimation is removed from the script completely), and it shouldn't be possible to specify a decimation amount greater than four when by default it has to be less than the decimation cycle and by default that's five.

Speaking of an extra setting...... I'd like to be able to tell MeGUI to default to ITU resizing for 4:3 DVDs and non-ITU for 16:9, given I'm pretty sure every 4:3 DVD I've met has been ITU but for newer 16:9 DVDs they tend not to be, and while I don't use OneClick myself that might also be handy for those who do.
Maybe that ITU option could also be hidden in the AVS Profile configuration next to the upsizing option where nobody can find it. ;)

why a such request ?

Sorry, I guess you weren't asking me....... :)

[damascus]

I'd like the ability to set the default indexer

All the things you are wishing to have done for you would be incredibly trivial tasks if you were writing your own scripts using AvsPMod instead of using the script creator gui which really should not be on a x264 front end like meGui. It is simply a nod to those people who don't actually want to learn how to encode video. Encoding should be fun. You are trying to avoid the fun part.

[hello_hello]

All the things you are wishing to have done for you would be incredibly trivial tasks if you were writing your own scripts using AvsPMod instead of using the script creator gui which really should not be on a x264 front end like meGui. It is simply a nod to those people who don't actually want to learn how to encode video. Encoding should be fun. You are trying to avoid the fun part.

The Script Creator GUI shouldn't be on an x264 front end like MeGUI? That's the oddest thing I've heard in a while. What's stopping me from manually creating scripts using the Script Creator's Script tab as I would with AvsPMod? What's stopping me from creating script templates for MeGUI's Script Creator to use?

For the record, I use AvsPMod now and then. For simpler scripts I tend to use MeGUI's script creator. AvsPMod has nothing to with changes I'd like to see in MeGUI. The two are completely unrelated. Please refrain from telling me what I am or am not trying to do when you simply couldn't know.

[LouieChuckyMerry]

why a such request ?

I'm not requesting a feature, just wondering if it's presently possible because, sadly, I'm prone to forgetting to choose "L-SMASH Works" :rolleyes: .

[LouieChuckyMerry]

thinking about it......
Given l-smash now has the same fpsnum & fpsden parameters as ffmsindex, it'd be nice if megui could add them to the script when indexing with l-smash too, because playing favourites seems unfair...... ;)

I wholeheartedly agree, as after some testing with L-SMASH Works and QTGMC I noticed that the frame rate goes screwy without this information.

[hello_hello]

I wholeheartedly agree, as after some testing with L-SMASH Works and QTGMC I noticed that the frame rate goes screwy without this information.

It shouldn't have anything to do with QTGMC as such.

Without QTGMC in a script if you index with ffms2 and open the preview, MeGUI will display the total number of frames at the top (and the total duration if the option to "add time position" is enabled in it's settings).
The frame rate conversion parameters convert the frame rate to a constant frame rate. If you check the total number of frames/duration, delete the frame rate conversion stuff from the script and refresh the preview, and the total frame count/duration remains the same, then the video was constant frame rate to begin with. If the frame count/duration changes then either MeGUI got the frame rate wrong, or the source video is variable frame rate (that can include video with "repeated" frames, or frames with twice the normal duration, because ffms2/L-Smash treat that type of video as variable frame rate also). If the video is variable frame rate, without the frame rate conversion stuff in the script ffms2/L-Smash output a constant average frame rate, which will no doubt be a little different to what it's supposed to be.

There's a very slim chance that a variable frame rate video will have exactly the same number of frames and total duration as a constant frame rate video, but it's pretty unlikely, so if the frame count/duration changes with/without the frame rate conversion stuff in the script the source is very likely to be variable frame rate.

QTGMC just does it's thing from there. Aside from the lack of de-interlacing, I think you'll find the result will be the same with or without QTGMC added to the script.

[hello_hello]

When L-Smash was first added to MeGUI as an indexer it was made the default indexer over ffms2. This was later changed partly due to the ability of ffms2 to apply it's own frame rate conversion, and I think there was some sort of L-Smash issue with a certain video type at the time, but that's all better now, L-Smash can convert the frame rate, it doesn't have the same issue with AVIs when frame rate conversion is applied, and it's possibly a bit more reliable than ffms2 in general now (ffms2 doesn't seem to be updated much these days), so if there can't be an option for the user to pick the default indexer, maybe it's time to change the default back to L-Smash.

[kuchikirukia]

Here is was detecting it as 120FPS with L-Smash and QTGMC.


--[Information] [4/16/2015 12:41:18 AM] Started handling job
--[Information] [4/16/2015 12:41:18 AM] Preprocessing
--[Information] [4/16/2015 12:41:18 AM] Avisynth input script
---[NoImage] #LoadPlugin("C:\Program Files\MeGUI_2507_x86\tools\avisynth_plugin\qtgmc\SSE2tools.dll")
---[NoImage] #LoadPlugin("C:\Program Files\MeGUI_2507_x86\tools\avisynth_plugin\rgtools.dll")
---[NoImage] #LoadPlugin("C:\Program Files\MeGUI_2507_x86\tools\avisynth_plugin\qtgmc\mt_masktools-26.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI_2507_x86\tools\avisynth_plugin\nnedi3.dll")
---[NoImage] #LoadPlugin("C:\Program Files\MeGUI_2507_x86\tools\avisynth_plugin\qtgmc\EEDI2.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI_2507_x86\tools\avisynth_plugin\mvtools2 -2.6.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI_2507_x86\tools\avisynth_plugin\avstp.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI_2507_x86\tools\avisynth_plugin\qtgmc\masktools2.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI_2507_x86\tools\avisynth_plugin\RemoveGrainSSE2.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI_2507_x86\tools\avisynth_plugin\qtgmc\fft3dfilter.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI_2507_x86\tools\avisynth_plugin\repairsse2.dll")
---[NoImage] import("C:\Program Files\MeGUI_2507_x86\tools\avisynth_plugin\QTGMC-3.32.avsi")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI_2507_x86\tools\dgavcindex\DGAVCDecode.dll")
---[NoImage] setmemorymax(900)
---[NoImage] LoadPlugin("C:\Program Files\MeGUI_2507_x86\tools\lsmash\LSMASHSource.dll")
---[NoImage] LWLibavVideoSource("E:\title00 (1)-001.avi")
---[NoImage] assumetff()
---[NoImage] QTGMC(preset="very slow", edithreads=3)
---[NoImage] spline36resize(1280, 720)
---[NoImage] removegrain(mode=1)
---[NoImage] #trim(3000,0)
--[Information] [4/16/2015 12:41:22 AM] resolution: 1280x720
--[Information] [4/16/2015 12:41:22 AM] frame rate: 2000000000/16683333
--[Information] [4/16/2015 12:41:22 AM] aspect ratio: 16:9 (1.778)
--[Information] [4/16/2015 12:41:22 AM] Job commandline: "C:\Program Files\MeGUI_2507_x86\tools\x264_10b\x264-10b.exe" --preset veryslow --crf 18.0 --threads 2 --deblock -1:-1 --keyint 1199 --open-gop --bframes 6 --ref 8 --qcomp 0.7 --psy-rd 0.80:0 --sar 1:1 --output "E:\title00 (1)-001.avi.264" "E:\title00 (1)-001.avi.avs"
--[Information] [4/16/2015 12:41:22 AM] Process started
--[Information] [4/16/2015 12:41:22 AM] Standard output stream
--[Information] [4/16/2015 12:41:22 AM] Standard error stream
--[Information] [4/16/2015 12:42:01 AM] Process exits with error: 0xFFFFFFFF (-1)
--[Information] Deleting aborted output

[hello_hello]

Here is was detecting it as 120FPS with L-Smash and QTGMC.

I still don't think it's QTGMC's fault. QTGMC either outputs the same frame rate as the input:

QTGMC()
SelectEven()

or double the frame rate of the input:

QTGMC()

and the input frame rate is the input frame rate it's given. I've never seen it do anything else.

Looking at your example I'd guess it's 29.97 interlaced, L-Smash is outputting it as 59.940 progressive and QTGMC is de-interlacing at double frame rate and you end up with 118.99fps.
Is the video in question definitely interlaced?

Chances are you'd fix it the same way you'd fix it when ffms2 makes the same mistake:

LoadPlugin("C:\Program Files\MeGUI_2507_x86\tools\lsmash\LSMASHSource.dll")
LWLibavVideoSource("E:\title00 (1)-001.avi", fpsnum=30000, fpsden=1001)
assumetff()
QTGMC(preset="very slow", edithreads=3)
spline36resize(1280, 720)
removegrain(mode=1)

L-Smash will hopefully output 29.97 interlaced and QTGMC will output 59.94fps progressive, but if you take QTGMC out of the equation I think you'll find it's the L-Smash output that's wrong.

By the way, you do know QTGMC has built in noise removal? I thought I'd ask as it kind of surprised me to see you'd followed QTGMC with RemoveGrain. Have you tried EzDenoise? Generally low EzDenoise values (2 or lower) are sufficient and I suspect it won't blur detail as much as RemoveGrain might. QTGMC uses RemoveGrain itself as it's a required plugin.

QTGMC(preset="very slow", edithreads=3, EzDenoise=1)

And I mention using QTGMC for noise removal for progressive video every chance I get because it tends to do a pretty good job and this seems like one of those chances. I often use it in combination with LSFMod() these days with something like this as a starting point (I find a slightly faster preset produces a more natural result a lot of the time).

QTGMC(InputType=1, Preset="medium", EzDenoise=1)
LSFMod(strength=75)

Here's a before and after (http://forum.doom9.org/showthread.php?p=1715276#post1715276) screenshot if you're interested.

[damascus]

The Script Creator GUI shouldn't be on an x264 front end like MeGUI? That's the oddest thing I've heard in a while. What's stopping me from manually creating scripts using the Script Creator's Script tab as I would with AvsPMod? What's stopping me from creating script templates for MeGUI's Script Creator to use?

For the record, I use AvsPMod now and then. For simpler scripts I tend to use MeGUI's script creator. AvsPMod has nothing to with changes I'd like to see in MeGUI. The two are completely unrelated. Please refrain from telling me what I am or am not trying to do when you simply couldn't know.

Allowing any encoding software to make any decisions for you whatsoever can only result at the very best in an encoding that is "good enough", that is, if you don't actually care if it is encoded correctly. Without a thorough examination of the source material and the ability to instantly see the results of any filter you may wish to use you are just clicking "encode" and hope for the best. No software can possibly anticipate everything that might be done when a DVD is authored. Anyone who is using a Script Creator or one click encoder is looking for shortcuts when they should be looking for answers instead. I've encoded several thousand DVDs and written a very popular and detailed AviSynth based meGui programming guide. I've seldom seen the kind of silly questions and insane log files as I have in this thread. Yes, you can manually create your own scripts in the script creator pad. You could also do the same in Notepad. Either way you are working in the blind. Why would someone not want to make the small amount of effort required to become somewhat competent in AviSynth instead of looking for short cuts?

[hello_hello]

Allowing any encoding software to make any decisions for you whatsoever can only result at the very best in an encoding that is "good enough", that is, if you don't actually care if it is encoded correctly.

Well I guess when I'm requesting features such as the ability to choose a particular indexer as the default, that'd be an example of my wanting to allow the software to make the decisions. Is that what you're saying?

Without a thorough examination of the source material and the ability to instantly see the results of any filter you may wish to use you are just clicking "encode" and hope for the best.

Well I guess it's just a well MeGUI's Script Creator comes with a preview then, and the fact I can use the Script Creator to save a script and open it in MPC-HC to preview it that way obviously doesn't count as an ability to see the result of filters. And here's me thinking, when I create scripts with different filtering and open them in different instances of MPC-HC and run them fullscreen on my TV, that it not only constituted previewing the results of filtering, but comparing them too. I guess the AvsPMod preview must preview filters in ways they can't be previewed using other preview methods.

No software can possibly anticipate everything that might be done when a DVD is authored. Anyone who is using a Script Creator or one click encoder is looking for shortcuts when they should be looking for answers instead.

"Twaddle" on the Script Creator comment and "irrelevant" on the OneClick encoder comment because it hasn't anything to do with this discussion. I don't use it. There's no reason why you can't totally control what filtering is used in an encode.

I've encoded several thousand DVDs and written a very popular and detailed AviSynth based meGui programming guide. I've seldom seen the kind of silly questions and insane log files as I have in this thread.

You're writing guides and then telling people not to use it?
Any chance of a link? I've yet to see a guide to using MeGUI that's not fairly out of date and/or contains odd encoding advice.

To what kind of silly questions do you refer? Have you an example of a type of Avisynth question that was asked because someone used MeGUI's Script Creator that wouldn't been asked if they'd used AvsPmod?

Yes, you can manually create your own scripts in the script creator pad. You could also do the same in Notepad. Either way you are working in the blind.

Really? So now creating scripts with Notepad somehow requires less knowledge than creating scripts with AvsPMod? And if you create them that way they can't be previewed? Is that what you're saying?

Why would someone not want to make the small amount of effort required to become somewhat competent in AviSynth instead of looking for short cuts?

What was it about my post that gave you the impression I'm not at least a little competent when it comes to using Avisynth? Mentioning specific combinations of container/video/audio where ffms2 fails and why it does? The fact that I'm aware the script creator can sometimes add decimation values to a script that don't make sense and I know why they don't make sense? My suggestion to use a higher default frame rate when MeGUI can't determine what the frame rate should be? Wanting to be able to default to ITU resizing for one type of DVD but default to non-ITU resizing for another type?
What was it I said that gave the impression I haven't encoded several thousand DVDs myself?

MGUI is just software designed to help achieve particular tasks. Some software makes all the decisions for you. Some software gives you a hand. Some software won't let you modify any of it's process, but some software gives you a lot of control.
I happen to think MGUI is a good balance between software that gives you a hand while still allowing the user almost total control. I don't know why you'd have an issue with that, but you can always not use it. Given you've written MeGUI guides though, I'm guessing you have, which is another reason your arguments aren't making enough sense for me to be sure I know exactly what the point is you're trying to make.

[LouieChuckyMerry]

LoadPlugin("C:\Program Files\MeGUI_2507_x86\tools\lsmash\LSMASHSource.dll", fpsnum=30000, fpsden=1001)
LWLibavVideoSource("E:\title00 (1)-001.avi")
assumetff()
QTGMC(preset="very slow", edithreads=3)
spline36resize(1280, 720)
removegrain(mode=1)

I've noticed that FFMS places the ", fpsnum=X, fpsden=X, theads=1" at the end of the "Source" line, not the "LoadPlugin" line; is the above also acceptable? And, is there any reason to add "threads=1" to the end of the L-SMASH Works "LoadPlugin" or "Source" line?


...open it in MPC-HC...

How do you do this, please?

Edit: ahhh, needed the 32 bit version. What do you do to expedite the--what is it technically?--buffering?

[sneaker_ger]

I've noticed that FFMS places the ", fpsnum=X, fpsden=X, theads=1" at the end of the "Source" line, not the "LoadPlugin" line; is the above also acceptable?
No. It belongs into the LWLibavVideoSource() function.

And, is there any reason to add "threads=1" to the end of the L-SMASH Works "LoadPlugin" or "Source" line?
It should not be necessary. It's something to test when there are weird decoding errors but L-SMASH isn't all that prone to such errors.

[LouieChuckyMerry]

Thanks for the clarification, sneaker_ger :) .

[hello_hello]

Sorry, putting fpsnum=X and fpsden=X on the end of the LoadPlugin line was just me being careless when I posted. I've edited my previous post to correct it.

[hello_hello]

Edit: ahhh, needed the 32 bit version. What do you do to expedite the--what is it technically?--buffering?

I bang my head against the desk sometimes. It doesn't make it faster, but it seems to help. ;)

If you're not using any complex filtering you should be able to open and preview the script while it runs at normal speed. It's just the slow QTGMC type filtering that probably makes it seem like it's buffering, but I don't think that's the problem. It can take a while for Avisynth to output a frame after opening a script or navigating to a different location in the video if there's slow filtering involved. MPC-HC keeps playing and probably starts skipping frames as it'd be designed to try to play the video at normal speed, unlike MeGUI's preview which can wait for each frame no matter how slow, and you end up completely losing control.

One way around the MPC-HC playback problem is to temporarily slow the frame rate down while you're previewing so the Avisynth output can "keep up". Try AssumeFPS at the end of a script to slow it down to one or two frames per second if you have to. Whatever it takes:

AssumeFPS(2,1)

That way you can open a script that includes QTGMC and let MPC-HC run and it should slowly step through the frames in an orderly manner. It'll probably be fairly slow to navigate though and I find it pays to navigate to a new location, pause the player, wait for AVISynth to output the required frame, then resume playback.

The main reason I use MPC-HC for previewing is most of the video I encode is a lower than 1080p in resolution and I prefer to see it fullscreen on my TV before I encode it. MeGUI's preview doesn't have a fullscreen mode. Although even then I still sometimes run short sample encodes because sometimes I really need to preview fullscreen and at the correct speed. :)

I don't think AVSPMod's preview has a fullscreen mode either, but don't quote me on that. It's preview has an option not to drop frames so it'll wait for them like MeGUI's preview however maybe I'm missing the obvious, but I find AvsPMod's preview to be quite frustrating when using slow filtering in a script as it makes the whole program unresponsive and eventually I want to punch the screen. Maybe I'm missing something there though as I don't use AvsPMod a lot myself.

PS. A MPC-HC previewing tip:
If you go into MPC-HC's options and under Internal Filters you uncheck the Avisynth Source Filter, that'll stop MPC-HC from locking scripts when you open them. That way you can save a script, open it with MPC-HC, and if you want to change something you can open the script with Notepad, edit it and save the change without having to close MPC-HC or the video first. Then to refresh the preview, use Ctrl+E while MPC-HC's window is in the foreground.
And if you do that, you can compare different filtering using a single script if you want to. For example, create a script without denoising and open it in MPC-HC. Edit the script to add some denoising, save the change and open the same script in a second instance of MPC-HC. You'll still have one script but two previews. The first without noise filtering and the second preview with it.

[Poutnik]

I want to post this for a long time, and I have also did not see it being solved recently.

MeGUI often creates hidden modal windows, causing for me in past strange MeGUI behavior until I have realized that. It is typical for Dialog asking for a new name of a Video/Audio/Oneclick config profile, or for some other questions , I guess overwriting of files.

The only option I realized to work is ALT-SPACE to switch to window kbd driven moving, and to move the hidden window by arrows to place I can see it.

Until I have realized this procedure, I stayed helpless with strange behaving not responding MeGUI, usually lost patience and killing MeGUI.

Not sure if it is OS specific, I use last stable MeGUI on Vista64 Home Premium SP2, with all the .NET updates.

[Zathor]

Which one is "hidden" (behind other MeGUI Windows) for you?

[kuchikirukia]

I'm not sure what you're trying to say there. The only window shenanigans I've seen MeGUI play is it won't let you do jack with certain configuration pages open. If you're playing around with x264 config or one-click avisynth config, go back to doing something else on the computer, then click the taskbar icons to bring up one of MeGUI's other windows, they'll come up, but you can't do anything with them. You can't do anything until you find the configuration window and close it.

[LigH]

The priorized configuration window is "modal", therefore it will certainly and obviously block access to its parent window. If you get another window in front of MeGUI and then click the MeGUI window bar in the taskbar to bring it to front, the configuration window will also come to front, blinking to remind you that it is modal if you try to access the blocked parent window. At least this works well in Windows 7.

I can't imagine any circumstances where a modal window gets into the background.

[LouieChuckyMerry]

One way around the MPC-HC playback problem is to temporarily slow the frame rate down while you're previewing so the Avisynth output can "keep up". Try AssumeFPS at the end of a script to slow it down to one or two frames per second if you have to. Whatever it takes:

AssumeFPS(2,1)

That way you can open a script that includes QTGMC and let MPC-HC run and it should slowly step through the frames in an orderly manner. It'll probably be fairly slow to navigate though and I find it pays to navigate to a new location, pause the player, wait for AVISynth to output the required frame, then resume playback.

This is a great help, thanks.


I don't think AVSPMod's preview has a fullscreen mode either, but don't quote me on that. It's preview has an option not to drop frames so it'll wait for them like MeGUI's preview however maybe I'm missing the obvious, but I find AvsPMod's preview to be quite frustrating when using slow filtering in a script as it makes the whole program unresponsive and eventually I want to punch the screen. Maybe I'm missing something there though as I don't use AvsPMod a lot myself.

The concept of AvsPMod is awesome but the function is a different story. Even with 16 GB of RAM it freezes-crashes regularly on my system, and I've not found a way to make the preview fullscreen...


PS. A MPC-HC previewing tip:
If you go into MPC-HC's options and under Internal Filters you uncheck the Avisynth Source Filter, that'll stop MPC-HC from locking scripts when you open them. That way you can save a script, open it with MPC-HC, and if you want to change something you can open the script with Notepad, edit it and save the change without having to close MPC-HC or the video first. Then to refresh the preview, use Ctrl+E while MPC-HC's window is in the foreground.
And if you do that, you can compare different filtering using a single script if you want to. For example, create a script without denoising and open it in MPC-HC. Edit the script to add some denoising, save the change and open the same script in a second instance of MPC-HC. You'll still have one script but two previews. The first without noise filtering and the second preview with it.

Also very helpful, thanks again.

[kuchikirukia]

The priorized configuration window is "modal", therefore it will certainly and obviously block access to its parent window. If you get another window in front of MeGUI and then click the MeGUI window bar in the taskbar to bring it to front, the configuration window will also come to front, blinking to remind you that it is modal if you try to access the blocked parent window..

MeGUI has more than one window.

http://s16.postimg.org/ko0vmtcw5/untitled.png (http://postimage.org/)
image post (http://postimage.org/)

That Avisynth configuration open will block you from doing anything else when nothing about the other windows shows you anything that says they shouldn't be working.

[LigH]

Ah, okay, this is an interesting chain of dependencies...

When you open the AVS Script Creator, it is a normal window, logically a child, but otherwise equal to the MeGUI main window.

When you open the AviSynth configuration, this window is modal to the AVS Script Creator window. If you click on the AVS S.C. window, the config window blinks. But the MeGUI main window is blocked as well and does not make the config window blink when clicked.

[hello_hello]

Is that why the script creator and it's preview often steal focus in a more selfish manner than other windows?

Normally when a window opens, I tend to move it to the background by clicking on the program/window I was using before being interrupted (assuming the new window didn't open maximised), and that brings it to the foreground. Unless it's MeGUI's script creator or preview windows, because then it doesn't. Their title bar colours change to the background title bar colour (I'm fairly sure) but the windows themselves remain in the foreground.

Of course that doesn't stop me from trying to bring the window I'm using to the foreground by clicking on it each and every time, because if there's some of the window still on the screen I've done it that way since I bought my first PC somewhere around the mid 90s, so clicking on the background window is a habit I'll probably never break. I gave up smoking a year ago and that's my brains ability to cope with breaking lifetime habits all used up. I'm pretty sure the habit breaking neural pathways are already running at full capacity 24/7.

I should go to bed. I do waffle when I'm really tired.....

[hello_hello]

A heads up for those of us still using XP.

It seems MKVMerge is no longer XP friendly so if you let MeGUI upgrade it to version 7.9.0 (assuming that version makes it to the update server) it'll break MeGUI's ability to mux MKVs. Apparently XP hasn't been supported for the last couple of MKVMerge versions but 7.8.0 and 7.7.0 and 7.6.0 all play with XP for me. It's only 7.9.0 that doesn't.

http://forum.doom9.org/showthread.php?p=1721137#post1721137

[Zathor]

So question is - what should I do? The last months there were several issues regarding XP (x265 builds, recent AviSynth+, ...) so I am not sure if MeGUI should also stop to support XP. I would not prevent MeGUI to run on XP but when newer versions of tools stop to work there is nothing I can do (except to proivide a dedicated version only for XP users which I cannot efford).

[Octo-puss]

There really is no reason whatsoever to use Windows XP these days. Don't bother with any additional work on that, it's not worth it. If people are stubbornly adamant about using crappy outdated insecure system which is no longer supported in even the most basic way (security updates), that's their problem and they should deal with problems themselves.