MeGUI: bug reports and feature requests

[Solon8]

Any clue why some AV softwares consider ffmindex as bad?

[hello_hello]

Any clue why some AV softwares consider ffmindex as bad?

https://en.wikipedia.org/wiki/Heuristic_analysis

Maybe the software has a setting for it's "taking a guess" level you could dial back a bit.

[Atlantis]

Set an exclusion for ffmsindex.exe - this should fix then also the deletion of MeGUI.

Are we sure that they are safe? Why should I do that?

[LigH]

You are never sure (and not secure either). With or without AV software. If you don't trust first-hand sources of your software, then don't trust AV heuristics either.

You can check more heuristics at virustotal and malwr, and if the number of suspicions is low, the probability of a false alarm is high. In this case, send a sample to your AV author to have this false alarm removed.

[Gieferg]

I wanted to recompress video with Blindehalo3 filter using MeGui.

LoadPlugin("C:\Program Files\Avisynth 2.5\plugins\masktools2.dll")
LoadPlugin("C:\Program Files\Avisynth 2.5\plugins\RgTools.dll")
Import("C:\Program Files\Avisynth 2.5\plugins\BlindDeHalo3_mt2.avs")
BlindDeHalo3( 3,3,125 )

I've checked the path like ten times, so everything is in right place. And every time MeGui give me some error:

Unable to Load "C:\Program Files\Avisynth 2.5\plugins\RgTools.dll", module not found

But it's there.
If I remove that line from the script, I get following error:

Invalid arguments to function Blinddehalo3

If I remove that line I get this:

The script's returns was not a video file.

Any suggestions?

Just for clarification:
I've never used MeGui before.

[LigH]

Where is your source filter? You never loaded any video to be filtered.

Not being able to load a plugin ... are all necessary compiler runtimes installed? And check if you don't try to load an AviSynth 2.6+ plugin in AviSynth 2.5.x; try if it works if you enforce MeGUI using its internal AviSynth copy, instead of the version installed in your system.

Usually it is helpful to publish a log file of such a failed attempt.

[hello_hello]

I wanted to recompress video with Blindehalo3 filter using MeGui.

LoadPlugin("C:\Program Files\Avisynth 2.5\plugins\masktools2.dll")
LoadPlugin("C:\Program Files\Avisynth 2.5\plugins\RgTools.dll")
Import("C:\Program Files\Avisynth 2.5\plugins\BlindDeHalo3_mt2.avs")
BlindDeHalo3( 3,3,125 )

I've checked the path like ten times, so everything is in right place. And every time MeGui give me some error:

Unable to Load "C:\Program Files\Avisynth 2.5\plugins\RgTools.dll", module not found

Aside from what LigH said, "C:\Program Files\Avisynth 2.5\plugins" is usually the auto-loading plugins folder (for a fresh install of Avisynth 2.6.0.6 it's just "C:\Program Files\Avisynth\plugins") so if Avisynth is installed you shouldn't need to manually load those plugins. Likewise if you give BlindDeHalo3_mt2.avs an avsi extension you shouldn't need to import it. That applies to MeGUI using it's own portable version of Avisynth (you can switch between the portable version of Avisynth and the installed version in Options). As long as Avisynth is also installed, plugins in that folder should still auto-load.

According to the info here (http://avisynth.nl/index.php/RgTools), Avisynth 2.6 or higher is required for RGTools. MeGUI currently uses Avisynth 2.6.0.6 for it's portable version.
Did you download the 64 bit version of RGTools instead of the 32 bit version?

Maybe try Avisynth Info Tool (http://forum.doom9.org/showthread.php?t=170647).

BlindDeHalo3( 3,3,125 )
If I remove that line from the script, I get following error:
Invalid arguments to function Blinddehalo3

That's probably unrelated to the RGTools error. I've not used BlindDeHalo3 but the first two values are expressed as float so I think it'd need to be
BlindDeHalo3(3.0, 3.0, 125)
or
BlindDeHalo3(rx=3.0, ry=3.0, strength=125)
Mind you those values appear to be the defaults (http://avisynth.nl/index.php/BlindDeHalo3), so you'd get exactly the same result with this:
BlindDeHalo3()

[StainlessS]

Informational only.

Just got 'Unclassified Malware' alert from Comodo Internet Security for ffmsindex.exe (updated MeGUI development, earlier today) .
I've submitted as false +ve to Comodo.
Here, results from Virustotal today:- https://www.virustotal.com/en/file/af42e338285477302b93243331873fd21185126883fdbd2b2472c663c1f6e486/analysis/1449762152/

EDIT: Anyone who would like to give opinion to VirusTotal can vote on their Votes TAB.

[LigH]

Very interesting that it gets detected as "Downloader", but I doubt a pure file indexer uses any networking functions. Maybe except UNC file access? Or unused functions in a bigger linked library?

P.S.: malwr (https://malwr.com/analysis/ZTA3NjJlZDY5ZDg2NGNkY2JhNDQxOTZjNGFmZDI4ZGU/) / Cynomix (http://cynomix3.appspot.com/sample/2a93573490dbae630d8a03399f6b86dac831dbec)

[StainlessS]

unused functions in a bigger linked library?

Yes, much/most of the strings mentioned @ Cynomix are also present in the previous version ffmsindex.exe. (about 70% of the way through the file).
Probably just part of some library as LigH suggests.

[LigH]

I have a strange issue with MPC-HC (64-bit) 1.7.10 (d911f14). It seems to apply a kind of automatic de-shaker filter to every video played. They are all surrounded by a black border which seems to get adapted to moving content (shrinks sometimes when letterboxes are included). It is especially obvious when you have slightly shaking footage with a logo in a corner, then you can see how the image is stabilized but the logo is shaking, half covered by the border.

What may that be? How can I disable that? I don't think I have such a filter installed, it seems to appear in MPC-HC with internal LAV Filters only (but I am not aware that they implement such a feature), not in e.g. GraphStudioNext rendering a media file (this uses MS DTV-DVD filters for decoding because there are no other DirectShow filters installed yet).

Technical info:

MPC-HC (64-bit)
---------------

Build information:
Version: 1.7.10 (d911f14)
Compiler: MSVC 2013 Update 5
Build date: Nov 14 2015 18:25:24

LAV Filters:
LAV Splitter: 0.66.0.0
LAV Video: 0.66.0.0
LAV Audio: 0.66.0.0
FFmpeg compiler: MinGW-w64 GCC 4.9.2

Operating system:
Name: Windows NT 6.1 (build 7601, Service Pack 1)
Version: 6.1 (64-bit)

Hardware:
CPU: AMD A4-4000 APU with Radeon(tm) HD Graphics
GPU: AMD Radeon HD 7480D (driver version: 8.17.10.1116)
Filters currently loaded:
- Default DirectSound Device
- Enhanced Video Renderer (custom presenter)
- Audio Switcher
- LAV Video Decoder (internal)
- LAV Audio Decoder (internal)
- LAV Splitter Source (internal)
__

Oh, heck, it helps writing about it...

It's not a feature of MPC-HC.

It's not a feature of LAV Filters either.

It's a feature of AMD, called "Steady Video".

I hate AMD Catalyst drivers. They are full of ghosts you never intended to call.

[Zathor]

MediaInfo v0.7.80 have been released
Version 0.7.80, 2015-11-30
Thanks, it is now online.

[ravewulf]

I don't see any option in MeGUI to manage VFR video: http://forum.doom9.org/showthread.php?t=172917

Feature request:

1) Add a tool to extract video timecodes from mkv.

2) Add a option to load video timecodes in mkv muxer.

Additional request for VFR support in mp4 files:

The easiest way to support this is probably through x264 as it can load timecode files directly via --tcfile-in as long as the output format also supports vfr (use internal mp4/mkv muxer, optionally use external muxer after if for some reason the external muxers are preferred). Another method I know of is here http://forum.doom9.org/showthread.php?t=112199

EDIT: To address 1) FFVideoSource can output the timecodes from the file being read https://github.com/FFMS/ffms2/blob/master/doc/ffms2-avisynth.md

[kotuwa]

MeGUI FLAC issue.

MeGUI 2624. Flac 1.3.1

Just encoded into FLAC using different speed presets...
8 and 0.
Both gave same file size. Looks like 0 was used in both.

Any reason or Fix?

[Atlantis]

Sorry I have not read this long thread. My MeGUI is updated to 2624 and today I noticed I can no longer encode to ac3. Any reason why Aften was removed? What you should use to encode to AC3 in MeGUI 2624?

[Barough]

Sorry I have not read this long thread. My MeGUI is updated to 2624 and today I noticed I can no longer encode to ac3. Any reason why Aften was removed? What you should use to encode to AC3 in MeGUI 2624?

Use FFmpeg AC-3 ;)

[Atlantis]

Why they removed Aften?

[LigH]

I believe the AC3 encoder in ffmpeg developed a bit further, especially in its psychoacoustic routines, while Aften didn't. But I am not completely sure.

[tebasuna51]

Yep, Aften is discontinued, the same developper make the ffmpeg AC3 encoder (libav) improving stereo encode and other parts.

http://forum.doom9.org/showthread.php?p=1522077#post1522077

[hello_hello]

I just re-started MeGUI and auto-update downgraded MediaInfo from 0.7.80 to 0.7.79. Was that intentional?

[Barough]

I just re-started MeGUI and auto-update downgraded MediaInfo from 0.7.80 to 0.7.79. Was that intentional?

Wonder the same here also

[Zathor]

Just encoded into FLAC using different speed presets...
8 and 0.
Both gave same file size. Looks like 0 was used in both.
Thanks, will be fixed in the next build.

I just re-started MeGUI and auto-update downgraded MediaInfo from 0.7.80 to 0.7.79. Was that intentional?
Thanks, one of the update server was out of sync.

[Zathor]

The newer FFM2 plugin versions seem to require a recent AviSynth version. At least it does not work with 2.5.8 but it does work with 2.6

I am unsure which way to go. I could block all AviSynth versions which are not using the recent interface version and use the portable AviSynth instead.
Or I can print out only a error message and continue with the old way.

Both ways have pros and cons. Which would you prefer?

[tebasuna51]

The newer FFM2 plugin versions seem to require a recent AviSynth version. At least it does not work with 2.5.8 but it does work with 2.6

Yes, I see that. I use sometimes 2.5.8 and need switch to 2.6 to work with FFM2.

I prefer "use the portable AviSynth instead" for me.

[Barough]

"always use the included AviSynth" is what i use.


FFmpeg v2.8.4 is out
http://ffmpeg.zeranoe.com/builds/win32/static/

[Zathor]

Ok, I will emplement it in the way that I update the AviSynthWrapper to the recent interface version (currently 2, will be 6). With this new DLL no old AviSynth versions can be accessed. During startup of MeGUIthis will be checked and if necessary a fallback to the portable AviSynth will be done.

After this change it is not possible to use MeGUI with older AviSynth versions (replacing the DLL is the only way).

[hello_hello]

I found myself explaining to someone again today, why an anamorphic option called "Encode non-mod16" lets you encode mod16.
I still think a rename might be in order. "Encode any-mod" would work. Anamorphic "strict" as Handbrake calls it seems pretty succinct. Not to mention accurate..... :)

[hello_hello]

I'm using an anamorphic DVD encode to illustrate the problem. It's an MKV. I open and index it. The script creator looks like this:

http://s21.postimg.org/vz9lxudvr/megui1.gif

Problem #1. The display aspect ratio of the source video isn't in the drop down list. So if I change it, I can't change it back, unless....

http://s18.postimg.org/qbim2sdp5/megui2.gif

Problem #2: I create a custom aspect ratio in which case the source aspect ratio will be automatically be listed, so as long as I remember to create a custom aspect ratio first, I'm fine. Until......

http://s13.postimg.org/8cwy4zjfb/megui3.gif

Problem #3. I don't want to use the custom aspect ratio any longer and wish to delete it, but I can't unless I delete all the custom aspect ratios.

Happy New Year everyone. Especially Zathor. :)

PS. I still think it's time for MeGUI to switch from using the old ITU pixel aspect ratios for DVDs to the MPEG4 pixel aspect ratios. Because.....
- They're easier to remember.
- The display aspect ratios for NTSC and PAL are exactly the same, so there's only two display aspect ratios in total.
- They're included in the list of pixel aspect ratios in the x264 encoder configuration. The ITU PARs aren't.
- If you use --bluray-compat in the command line MeGUI (or the x264 encoder) automatically changes the ITU PARs to MPEG4 PARs.
- It keeps everything more consistent.
- Depending on the setting in preferences, MeGUI will choose either an ITU or generic display aspect ratios for NTSC or PAL Bluray video. I'm pretty sure both would technically be wrong.
- It's 2016 (give or take a day or so).

[hello_hello]

One more pixel aspect ratio related question. The mpeg4 and generic pixel aspect ratios are:

MPEG4:
PAL NTSC
4:3 12:11 10:11
16:9 16:11 40:33

Generic:
PAL NTSC
4:3 16:15 8:9
16:9 64:45 32:27

All the above are listed in the drop down list of pixel aspect ratios (SARs) in MeGUI's x264 encoder configuration, except the one highlighted in blue (generic PAL 4:3).
Not that it really matters, aside from the fact that once I noticed I realised I'll probably never sleep well again until I know why. :)

[Zathor]

2627 [Main] detects during startup if AviSynth can be used
automatic fallback to the portable AviSynth
2626 [AvisynthWrapper] updated to recent avisynth.h (requires AviSynth 2.6)
improved error handling
added x64 support
2625 [Flac Encoder] fixed always using compression level 0 (regression of 2536)

Please report as usual issues with this new build. I expect some problems due to the switch to avisynth interface version 6 (before it was 2).
EDIT: A positive effect is that due to the improved error handler AviSynth should not be able to crash MeGUI anymore (like with FFM2 and fast cropping).
EDIT2: With hello_hello in mind I have compiled the wrapper also for XP. I hope it works :-)

[LigH]

IIRC, ITU AR are based on microsecond timings of TV signals designed for CRT TV sets, where a line has a length equivalent to the height of 702 lines. The simpler MPEG-4 AR are based on modulo-16 widths of 704 pixels.

I doubt any human would recognize the difference.

[Barough]

Thnx for the new release Zathor :)

[hello_hello]

IIRC, ITU AR are based on microsecond timings of TV signals designed for CRT TV sets, where a line has a length equivalent to the height of 702 lines. The simpler MPEG-4 AR are based on modulo-16 widths of 704 pixels.

I doubt any human would recognize the difference.

Is that a reason not to make the aspect ratios consistent throughout the GUI?

Plus the way I understand it, if the list of PARs here (https://www.doom9.org/showthread.php?p=1058927#post1058927) is correct, the PARs used by MeGUI ("almost exact and commonly used ITU-PARs") aren't correctly based on "microsecond timings of TV signals designed for CRT TV sets, where a line has a length equivalent to the height of 702 lines", and are in fact the least accurate.

[hello_hello]

EDIT2: With hello_hello in mind I have compiled the wrapper also for XP. I hope it works :-)

Thanks. I'm updating to test as I type.
I still do intend to build a new PC. And it'll probably run Win7. And I'll try to do it this week while I'm on holiday, even though I've been saying that for a year.
But this old PC will keep running XP. As will the other one. So I hope XP support won't go away any time soon. I suspect there's a lot of old XP PCs out there that'd still like to be able to encode video.....

[hello_hello]

EDIT2: With hello_hello in mind I have compiled the wrapper also for XP. I hope it works :-)

I've found one peculiarness.

When indexing with ffmsindex (I've tried a few different MKVs containing different types of video) the script creator opens with a black (blank) preview. No video. Changing the "improve AVS opening" setting doesn't make any difference. If I close the preview and re-open it without closing the script creator, the video then displays.
(Edit: I just discovered using the "reload video" button in the preview window also causes the video to display, no need to re-open the preview)
I'm using ffms 2.22. There's no preview problem with MeGUI 2624, although I've no idea if it's all XP's fault.

The preview when indexing with L-Smash works normally, although keep in mind I'm using L-Smash version r784 (http://forum.doom9.org/showthread.php?t=167435&page=19#post1713408) because it plays with XP, just in case that makes a difference.

[hello_hello]

EDIT: A positive effect is that due to the improved error handler AviSynth should not be able to crash MeGUI anymore (like with FFM2 and fast cropping).

That was just cruel. I was so excited.
Next you'll be saying there's no such thing as Father Xmas. ;)

http://s17.postimg.org/495g1hflr/megui_crash1.gif
http://s7.postimg.org/87he094dn/megui_crash2.gif

I did discover when MeGUI is displaying a blank preview as I described above, it's very easy to crash MeGUI by cropping too quickly etc. When it's actually displaying video it requires more effort to cause it to crash.

Interestingly (or not) if I crop too quickly with ffms2 decoding, the video being displayed in the preview now tends to come and go (the preview goes temporarily black). I don't know if that'll help find the cause....

PS I'm still curious about the missing PAR (http://forum.doom9.org/showthread.php?p=1751249#post1751249).

[Zathor]

Mhm, it does work for me. Could you please post your "versions" information?

[hello_hello]

Certainly.

[Information] Log
-[Information] Versions
--[Information] [29/12/15 9:19:22 PM] MeGUI: 2627
--[Information] [29/12/15 9:19:22 PM] Operating System: Windows XP Professional x86 SP3 (5.1.196608.2600)
--[Information] [29/12/15 9:19:22 PM] .NET Framework: 4.0 (4.0.30319)
--[Information] [29/12/15 9:19:25 PM] AviSynth: 2.6.0.6 (31-03-2015) (inactive)
--[Information] [29/12/15 9:19:25 PM] AviSynth portable: 2.6.0.6 (21-09-2015) (active)
--[Information] [29/12/15 9:19:26 PM] AvisynthWrapper: 1.0.2626.0 (28-12-2015)
--[Information] [29/12/15 9:19:26 PM] Haali Matroska Splitter: 1.13.138.14 (14-04-2013)
--[Information] [29/12/15 9:19:26 PM] Haali DSS2: (14-04-2013)
--[Information] [29/12/15 9:19:26 PM] ICSharpCode.SharpZipLib: 0.85.5.452 (07-08-2008)
--[Information] [29/12/15 9:19:26 PM] MediaInfo: 0.7.80.0 (30-11-2015)
--[Information] [29/12/15 9:19:26 PM] MediaInfoWrapper: 0.7.61.0 (06-01-2013)
--[Information] [29/12/15 9:19:26 PM] MessageBoxExLib: 1.0.2218.28317 (19-12-2008)
--[Information] [29/12/15 9:19:26 PM] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
--[Information] [29/12/15 9:19:26 PM] 7z: 9.20 (18-11-2010)
-[Information] Update detection
--[Information] [29/12/15 9:19:26 PM] Connected to server: http://megui.org/auto/
--[Information] [29/12/15 9:19:26 PM] No package requires an update

It's odd because if I crop or resize when ffms2 is decoding (even just a single adjustment) it can make the preview go black. Sometimes just for a little bit, mostly until I "reload the video". It also turns the cursor to "busy" for a while so maybe it's related to the old "cropping too quickly can crash MeGUI" problem, only now it has a more visible effect on the preview.
All that's without having "apply auto preview" checked.
L-Smash is still behaving.

Would this help?

-[Error] Unhandled error
--[Information] [29/12/15 9:33:38 PM] Exception message: Object reference not set to an instance of an object.
--[Information] [29/12/15 9:33:38 PM] Stacktrace
---[NoImage] at System.Windows.Forms.UpDownBase.UpDownButtons.TimerHandler(Object source, EventArgs args)
---[NoImage] at System.Windows.Forms.Timer.OnTick(EventArgs e)
---[NoImage] at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
---[NoImage] at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
--[Information] [29/12/15 9:33:38 PM] Inner exception: null

[Zathor]

I still do intend to build a new PC. And it'll probably run Win7. And I'll try to do it this week while I'm on holiday, even though I've been saying that for a year.
So Father Christmas must exist - but I believe it not sooner than when you write that you have done it :-)

PS I'm still curious about the missing PAR (http://forum.doom9.org/showthread.php?p=1751249#post1751249).
Added in 2628 - no clue why it was left out.

Thanks for the problem report with the cropping/blank - I will start my old XP VM to see if I can reproduce it there. As it works in my W10 and W7 machines currently I assume it must be related to WXP as everything else is the same for me (except of the source file).

[hello_hello]

So Father Christmas must exist - but I believe it not sooner than when you write that you have done it

Although I will always make sure to keep the old dual core operational for you so I can continue testing MeGUI on XP forever and ever and ever and ever and ever and ever....... :)

[Barough]

What about updating the 7-Zip dll file. 7-Zip v15.13 is out.

[EDIT]
Noticed that MediaInfo 0.7.81 was just released

[LigH]

7-zip 15.14 already, stable release.

[Barough]

MKVToolNix v8.7.0 was just released

[LigH]

And qaac 2.58 fixes issues with mono audio since 2.56.

[Zathor]

Thanks for the news :-)
Except 7z the other new files are now online. 7z I need to verify first if changing the dlls is really worth the hassle.

I've found one peculiarness.
When indexing with ffmsindex (I've tried a few different MKVs containing different types of video) the script creator opens with a black (blank) preview. No video. Changing the "improve AVS opening" setting doesn't make any difference. If I close the preview and re-open it without closing the script creator, the video then displays.
I can confirm this behavior with XP and W7 using FFMS2 2.22 - I have not tried other FFMS2 or OS versions, but L-SMASH works. So it must be related to FFMS2 together with the new wrapper. I cannot do much there. Maybe I can load the video twice when FFMS2 is used as a workaround.

[Bluedan]

Hi everyone, it's been 2 or 3 years ago that I had time to do transcodings with MeGui.
Now that things have made progress I am heavily missing a guide that's up to date.
Even the wiki linked from the programme itself via help button isn't online anymore.
It is really hard to gather info on your own, for Megui has so much options.
I know it is not intended for beginners anyway, but I have been using this for years !

[StainlessS]

With hello_hello in mind I have compiled the wrapper also for XP. I hope it works :-)

Thanx Zathor, Hello_hello is not the only Stick-In-The-Mud. :)

[Zathor]

Hi everyone, it's been 2 or 3 years ago that I had time to do transcodings with MeGui.
Now that things have made progress I am heavily missing a guide that's up to date.
Even the wiki linked from the programme itself via help button isn't online anymore.
It is really hard to gather info on your own, for Megui has so much options.
I know it is not intended for beginners anyway, but I have been using this for years !

Please use https://en.wikibooks.org/wiki/MeGUI
But thanks for the reminder. I have to update the links.

Btw. anyone can help and update there something. A lot of the information is outdated.

[hello_hello]

It appears when cropping while ffms2 is decoding, there's some picture resizing taking place in the preview, even without the auto-preview enabled. It doesn't happen all the time, but I've never seen it before. When increasing the cropping slowly, sometimes the displayed cropping increases in the preview as it should, but sometimes the displayed cropping stays the same and the picture moves a bit instead (it's stretched or squished to meet the cropping line). The rest of the time it makes the preview go black.

I though I'd point that out in case it helps you track down the ffms2 cropping problem because cropping changing the size of the video in the preview seems to be something new. It might be something else entirely but I wouldn't know. I couldn't repeat any of that with L-Smash.

[hello_hello]

Thanx Zathor, Hello_hello is not the only Stick-In-The-Mud. :)

According to the latest stats I read (December 2015) just under 8% of Windows users are still running XP. Based on Microsoft's claim of 1.5 Billion Windows PCs, that's a total of 120 million sticks-in-the-mud.

I've pretty much decided I'm going to start heading towards switching to Linux. I can't see myself using Win10. I've got an unused copy of Win7 I can stick on the new PC while I the old one helps me become familiar with Linux, but at the moment I think Win7 will be the end of the road.