View Full Version : MeGUI: bug reports and feature requests
sneaker_ger
31st May 2018, 20:11
You are using a script with "hacked" 10 bit format. MeGUI is expecting "native" 10 bit format. x265 is confused as the y4m header says "8 bit" but you set "--input-depth 10".
Change script:
LoadPlugin("D:\Sonstiges\Videotools\MeGUI\tools\lsmash\LSMASHSource.dll")
vid = LSMASHVideoSource("Premiere.mov", format="YUV420P10")
vid = ConvertFromDoubleWidth(vid, bits=10)
aud = LSMASHAudioSource("Premiere.mov")
AudioDub(vid, aud)
Or use ffms2, it does that automatically.
You don't need "--input-depth" parameter at all with MeGUI as it is using Y4M pipe where this information is sent via header automatically.
Zathor
31st May 2018, 21:05
I am sorry for the issues the current transition to a support of high bit depth is causing. I am looking forward to any kind of feedback to change MeGUI where necessary.
Based on Taurus issue I have added this here:
2859 [x26x] flag a job as "error" if the number of frames of the input and output does not match
It is not mentioned there, but custom --frames or --seek values are taken into account
Taurus
1st June 2018, 07:37
Thanks Zathor!
I can report: No issues with ffmpeg so far anymore.
Tested on similar stuff like mentioned in a few posts above.
But I must admit, haven't got the time and cpu cycles to test on larger stuff.
Just 10min samples.
The last time when the slowdown happened it choked on the 28min sample.
I will report back when this issue happens again.
Thanks for looking into it.
Great job you're doing!
Edit: I've send you the windows crashreport via PM belonging to the logfile two day ago.
Strange, there was no error report on desktop.
Just a silent closing.....
LouieChuckyMerry
1st June 2018, 16:05
Happy Friday! I hope everyone is well (and a special thanks to Zathor) :) . After much help setting things up, here and elsewhere, I've been using the stand alone version of MeGUI for about three years without issue (unless I created the issue myself ;) ), with the devil.dll and SEt MT 2.6.0.4 version of AviSynth, and updating from the developmental server. I'll typically run a couple SelectRange(66,1000)'s so that I can choose a CRF that will output a bit rate in a certain range. I've not changed anything in my scripts other than the strength of SMDegrain. Lately I haven't been encoding much because I finally finished The Neverending Video Project a couple months ago; now I only encode remasters and the occasional new source. On 23 May 2018 I successfully encoded the remastered Blu-ray of The Matrix. Here's the log file:
http://www.mediafire.com/file/iq7lm96ikzd09z2/logfile-18-05-23_12-42-57.7z/file
Yesterday, 31 May 2018, I updated MeGUI in order to encode the remastered Blu-ray of Midnight Cowboy. Unfortunately, however, something went horribly wrong. My knowledge of video encoding is quite limited, but it seems to me that the switch from avs4x26x.exe to ffmpeg is the reason for the trouble. What happened is that the FPS dropped to about 10% of normal, and the output file's aspect ratio and quality (it became the crushed green screen acid flashback, I think something to do with the input bit depth?) became unwatchable. I reckon my command line is off for ffmpeg, and probably some other stuff, but I'm not sure how to fix things. Here's the recent log:
http://www.mediafire.com/file/225s04a6o12e75f/logfile-18-05-31_18-27-58.7z/file
If anyone would take the time to help me out I'd be forever appreciative :) . If necessary, then I'd revert to the last non-ffmpeg version and not update whatever would keep it using avs4x26x (but I'd probably need a bit of help with that, too). Thanks again for any help.
Happy Friday! I hope everyone is well (and a special thanks to Zathor) :) . After much help setting things up, here and elsewhere, I've been using the stand alone version of MeGUI for about three years without issue (unless I created the issue myself ;) ), with the devil.dll and SEt MT 2.6.0.4 version of AviSynth, and updating from the developmental server. I'll typically run a couple SelectRange(66,1000)'s so that I can choose a CRF that will output a bit rate in a certain range. I've not changed anything in my scripts other than the strength of SMDegrain. Lately I haven't been encoding much because I finally finished The Neverending Video Project a couple months ago; now I only encode remasters and the occasional new source. On 23 May 2018 I successfully encoded the remastered Blu-ray of The Matrix. Here's the log file:
http://www.mediafire.com/file/iq7lm96ikzd09z2/logfile-18-05-23_12-42-57.7z/file
Yesterday, 31 May 2018, I updated MeGUI in order to encode the remastered Blu-ray of Midnight Cowboy. Unfortunately, however, something went horribly wrong. My knowledge of video encoding is quite limited, but it seems to me that the switch from avs4x26x.exe to ffmpeg is the reason for the trouble. What happened is that the FPS dropped to about 10% of normal, and the output file's aspect ratio and quality (it became the crushed green screen acid flashback, I think something to do with the input bit depth?) became unwatchable. I reckon my command line is off for ffmpeg, and probably some other stuff, but I'm not sure how to fix things. Here's the recent log:
http://www.mediafire.com/file/225s04a6o12e75f/logfile-18-05-31_18-27-58.7z/file
If anyone would take the time to help me out I'd be forever appreciative :) . If necessary, then I'd revert to the last non-ffmpeg version and not update whatever would keep it using avs4x26x (but I'd probably need a bit of help with that, too). Thanks again for any help.
Have you tried upgrading to avisynth+ and feeding MeGUI real 10-bit video instead of using the stacked format?
Zathor
1st June 2018, 16:58
Here's the recent log:
http://www.mediafire.com/file/225s04a6o12e75f/logfile-18-05-31_18-27-58.7z/file
If anyone would take the time to help me out I'd be forever appreciative :) . If necessary, then I'd revert to the last non-ffmpeg version and not update whatever would keep it using avs4x26x (but I'd probably need a bit of help with that, too). Thanks again for any help.
custom command line: --demuxer raw --input-depth 16 --sar 1:1
your source file seems to be plain 8 bit and we are using y4m so please remove the "--demuxer raw --input-depth 16" from the command line and try it again.
custom command line: --demuxer raw --input-depth 16 --sar 1:1
your source file seems to be plain 8 bit and we are using y4m so please remove the "--demuxer raw --input-depth 16" from the command line and try it again.
He is filtering in stacked high bit depth hence it is no longer 8 bit.
Zathor
1st June 2018, 17:04
Mhm missed that one... yes, avs+ should be better.
LouieChuckyMerry
1st June 2018, 20:37
Gser & Zathor: would you please translate your responses :p . Seriously, thanks for the replies. I set up my MeGUI so long ago that I can't remember exactly how it works :rolleyes: . Guess I'm getting old. How would, possibly, avs+ be better? Would I still be able to use MeGUI as a front end, keeping all my custom scripts, etc?
doomleox999
2nd June 2018, 08:05
Before you open a complete folder make sure that a proper OneClick preset is selected which covers your audio language needs.
There is no option to choose or change the default language of the files. There's only settings for specific languages.
Zathor
2nd June 2018, 19:35
Gser & Zathor: would you please translate your responses :p . Seriously, thanks for the replies. I set up my MeGUI so long ago that I can't remember exactly how it works :rolleyes: . Guess I'm getting old. How would, possibly, avs+ be better? Would I still be able to use MeGUI as a front end, keeping all my custom scripts, etc?
first step - enable the option in the MeGUI settings to "always use the included AViSynth". that way avs+ is used after the next start of MeGUI. As I am not using the MT modes myself I do not know if you have there anything to change in the script. Just try it.
Zathor
2nd June 2018, 19:36
There is no option to choose or change the default language of the files. There's only settings for specific languages.
OK, then I misunderstood it. You do not want to select specific streams you want to change the language of exsting streams. This is sadly not possible.
LouieChuckyMerry
2nd June 2018, 22:00
first step - enable the option in the MeGUI settings to "always use the included AViSynth". that way avs+ is used after the next start of MeGUI. As I am not using the MT modes myself I do not know if you have there anything to change in the script. Just try it.
Thanks for the reply, Zathor, and Happy Saturday. I have a backup of my portable MeGUI, Version 2855, from a week ago. With this I was able to return to problem-free encoding by declining to update to Version 2859. With this same version and "Always use the included AviSynth" enabled, I was able to encode properly after removing the MT dialogue from the script, but the FPS were about half of normal (on my dual-core system). Finally, after updating to Version 2859, then updating ffmpeg to the newest version, my test encode failed. Here's the log:
[Error] Log
-[Information] Versions
--[Information] MeGUI: 2859 x86
--[Information] Update Check: Disabled
--[Information] System Information
---[Information] Operating System: Windows 7 Premium x64 SP1 (6.1.65536.7601)
---[Information] .NET Framework: 4.0 (4.0.0.0)
---[Information] .NET Framework: 4.7 (4.7.02558)
---[Information] Redistributables
----[Information] Microsoft Visual C++ 2010 x64: 10.0.40219
----[Information] Microsoft Visual C++ 2010 x86: 10.0.40219
----[Information] Microsoft Visual C++ 2015 x64: 14.0.23506
----[Information] Microsoft Visual C++ 2015 x86: 14.0.23026
---[Information] DPI: 100% (96/96)
---[Information] Monitor 1
----[Information] Resolution: 1600x900
----[Information] Primary Screen: True
--[Information] Component Information
---[Information] Haali Media Splitter: 1.13.138.14 (14-04-2013)
---[Information] Haali DSS2: (14-04-2013)
---[Information] ICSharpCode.SharpZipLib: 0.85.5.452 (07-08-2008)
---[Information] MediaInfo: 18.05.0.0 (08-05-2018)
---[Information] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
---[Information] 7z: 9.20 (18-11-2010)
--[Information] AviSynth Information
---[Information] AviSynth Wrapper
----[Information] Version: 1.0.2847.0
----[Information] Date: 06-05-2018
----[Information] Interface: 3
---[Information] AviSynth
----[Information] File Version: 2.6.0.5
----[Information] Date: 20-02-2015
----[Information] Name: Avisynth 2.6
----[Information] Version: AviSynth 2.60, build:Feb 20 2015 [03:16:45]
----[Information] AviSynth+: false
----[Information] MT: true
----[Information] Status: inactive
---[Information] AviSynth portable
----[Information] File Version: 0.1
----[Information] Date: 28-03-2018
----[Information] Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] Version: AviSynth 2.60, build:Feb 20 2015 [03:16:45]
----[Information] AviSynth+: false
----[Information] MT: true
----[Information] Status: active
-[Information] Update detection
--[Information] [02 Jun 18 16:39:19] Automatic update is disabled
--[Information] [02 Jun 18 16:39:19] Using cached update config and server: http://megui.org/auto/
--[Information] [02 Jun 18 16:39:19] No package requires an update
--[Information] [02 Jun 18 16:39:19] redist files copied: 2017_x86
--[Information] [02 Jun 18 16:39:28] There is 1 package which can be updated: FFmpeg
--[Information] [02 Jun 18 16:39:28] updating package FFmpeg as it is missing or outdated
--[Information] [02 Jun 18 16:39:52] redist files copied: 2017_x86
--[Information] [02 Jun 18 16:43:44] Marked file as obsolete: ffmpeg-3.4.2-32.7z
--[Information] [02 Jun 18 16:43:44] Marked file as obsolete: megui-core-2855-32.7z
-[Error] Log for job4 (video, ReEncZoo[400]-TrimTest.avs -> ReEncZoo[400]-TrimTest.264)
--[Information] [02 Jun 18 16:39:28] Started handling job
--[Information] [02 Jun 18 16:39:52] Preprocessing
--[Information] [02 Jun 18 16:39:52] AviSynth input script
---[NoImage] # Set DAR in encoder to 16 : 9. The following line is for automatic signalling
---[NoImage] global MeGUI_darx = 16
---[NoImage] global MeGUI_dary = 9
---[NoImage] ### SetMemoryMax(256),SetMTMode(3,3) if TIVTC ###
---[NoImage] # SetMemoryMax(1024)
---[NoImage] # SetMTMode(3,3)
---[NoImage] LoadPlugin("F:\[0]StandAloneApps\MeGUI-2500(core)2443(data)0.3.5(libs)[Portable]\tools\lsmash\LSMASHSource.dll")
---[NoImage] LWLibavVideoSource("D:\Temp\[0000]ReEncTemp\[1080p]Zoolander2[S]{2016}[1080p]\Zoolander2{2016}[1080p].mkv", format="YUV420P8")
---[NoImage] ###### !!!!!! CHECK AUDIO & VIDEO TYPES !!!!!! ######
---[NoImage] ## If Cropping-Decimating Then Add "--sar x:y"-"--fps xx.xxx" To The Cmd Line ##
---[NoImage] ### SetMTMode(5) If TIVTC, Then SetMTMode(2) ###
---[NoImage] # SetMTMode(2)
---[NoImage] #deinterlace
---[NoImage] #crop
---[NoImage] #denoise
---[NoImage] #resize
---[NoImage] #<sharpen>
---[NoImage] #<deband>
---[NoImage] #<dither>
---[NoImage] SMDegrain(TR=3,ThSAD=400,RefineMotion=True,Plane=0,Chroma=False,Lsb=True,Lsb_Out=True)
---[NoImage] F=DitherPost(Mode=-1)
---[NoImage] S=F.FastLineDarkenMod()
---[NoImage] D=MT_MakeDiff(S,F).Dither_Convert_8_To_16()
---[NoImage] Dither_Add16(Last,D,Dif=True,U=2,V=2)
---[NoImage] ### Add "SMode=1" To GradFun3, Someday ###
---[NoImage] GradFun3(Radius=16,Lsb_In=True,Lsb=True)
---[NoImage] ### Preview Source OR Send 16-bit Output To x264 10-bit ###
---[NoImage] Trim(11111,13111)
---[NoImage] # SelectRangeEvery(1000,66)
---[NoImage] # DitherPost()
---[NoImage] Dither_Out()
--[Information] [02 Jun 18 16:40:01] resolution: 3840x1080
--[Information] [02 Jun 18 16:40:01] frame rate: 24000/1001
--[Information] [02 Jun 18 16:40:01] frames: 2001
--[Information] [02 Jun 18 16:40:01] length: 00:01:23.458
--[Information] [02 Jun 18 16:40:01] aspect ratio: 16:9 (1.778)
--[Information] [02 Jun 18 16:40:01] color space: I420
--[Information] [02 Jun 18 16:40:01] custom command line: --demuxer raw --input-depth 16 --sar 1:1
--[Information] [02 Jun 18 16:40:01] Job command line: "cmd.exe" /c ""F:\[0]StandAloneApps\MeGUI-2500(core)2443(data)0.3.5(libs)[Portable]\tools\ffmpeg\ffmpeg.exe" -loglevel level+warning -i "D:\Temp\[0000]ReEncTemp\[1080p]Zoolander2[S]{2016}[1080p]\ReEncZoo[400]-TrimTest.avs" -strict -1 -f yuv4mpegpipe - | "F:\[0]StandAloneApps\MeGUI-2500(core)2443(data)0.3.5(libs)[Portable]\tools\x264\x264.exe" --output-depth 10 --preset veryslow --tune film --crf 20.0 --deblock 0:-1 --keyint 240 --bframes 5 --ref 6 --qpmax 69 --rc-lookahead 120 --merange 32 --no-fast-pskip --stitchable --demuxer raw --input-depth 16 --sar 1:1 --frames 2001 --output "C:\Users\JSLIII\Desktop\ReEncTemp\ReEncZoo[400]-TrimTest.264" --stdin y4m -"
--[Information] [02 Jun 18 16:40:01] Process started
--[Information] [02 Jun 18 16:40:01] Standard output stream
--[Error] [02 Jun 18 16:40:01] Standard error stream
---[Information] [02 Jun 18 16:41:33] [error] av_interleaved_write_frame(): Broken pipe
---[Information] [02 Jun 18 16:41:33] [error] Error writing trailer of pipe:: Broken pipe
---[Information] [02 Jun 18 16:41:33] y4m [info]: 3840x1080p 1:1 @ 24000/1001 fps (cfr)
---[Information] [02 Jun 18 16:41:33] x264 [info]: using SAR=1/1
---[Information] [02 Jun 18 16:41:33] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
---[Information] [02 Jun 18 16:41:33] x264 [info]: profile High 10, level 5.0, 4:2:0 10-bit
---[Error] [02 Jun 18 16:41:33] x264 [error]: malloc of size 26521408 failed
---[Error] [02 Jun 18 16:41:33] x264 [error]: x264_encoder_encode failed
---[Information] [02 Jun 18 16:41:33] aborted at input frame 91, output frame 0
--[Error] [02 Jun 18 16:41:33] Process exits with error: 0xFFFFFFFF (-1)
--[Information] [02 Jun 18 16:41:33] Job completed
I'm sure you're busy, so don't waste any time on my problem unless you can afford it ;) . With the backup of Version 2855 I was able to return my dual-core and my quad-core setups to proper functionality, with all their correct templates, etc., and I've turned off "Auto Update" so they should stay useable (I'll just manually update everything but the MeGUI version). I'd still be curious to know what's wrong, though, if any extra smart person(s) could shed any light.
LouieChuckyMerry
2nd June 2018, 22:01
Damn, I'd love to know why sometimes my replies stretch the length, left-to-right, of two or three screens.
videoh
2nd June 2018, 22:16
It's because one or more lines of your code is so long. That sets the window size. You need to break those lines manually. The convention is to put a \ at the end to indicate that it is to be combined with the next line. Like so:
This is a line with a \
manual break.
tebasuna51
3rd June 2018, 00:30
Or use QUOTE instead CODE, without problems for log's.
Thanks for the reply, Zathor, and Happy Saturday. I have a backup of my portable MeGUI, Version 2855, from a week ago. With this I was able to return to problem-free encoding by declining to update to Version 2859. With this same version and "Always use the included AviSynth" enabled, I was able to encode properly after removing the MT dialogue from the script, but the FPS were about half of normal (on my dual-core system). Finally, after updating to Version 2859, then updating ffmpeg to the newest version, my test encode failed. Here's the log:
I'm sure you're busy, so don't waste any time on my problem unless you can afford it ;) . With the backup of Version 2855 I was able to return my dual-core and my quad-core setups to proper functionality, with all their correct templates, etc., and I've turned off "Auto Update" so they should stay useable (I'll just manually update everything but the MeGUI version). I'd still be curious to know what's wrong, though, if any extra smart person(s) could shed any light.
That's because you only did the first step. Next you need Changebits(bitdepth) to whatever bit depth you wish to filter in and then use filters that support native avs+ formats. Dithertools is only for stacked high bit depth formats. You could still use stacked format filtering if you want but you would need to add ConvertFromStacked(bits=10) as the last part of your script-. For 10 bit sources you need FFMPEGsource to decode in real 10-bits. L-smash only supports interleaved and stacked formats.
Multithreading is simple in avs+, just add Prefetch(threads) to the end of the script.
@ LouieChuckyMerry:
Or, if both indentation and full width matter, use external pastebin services, just link the URL here.
There are other forum software which wrap code blocks in on-demand scroll boxes with a maximum width (as well as height, like here (https://forum.doom9.org/showthread.php?p=1843456#post1843456)), so it doesn't destroy the base layout.
LouieChuckyMerry
3rd June 2018, 22:26
That's because you only did the first step. Next you need Changebits(bitdepth) to whatever bit depth you wish to filter in and then use filters that support native avs+ formats. Dithertools is only for stacked high bit depth formats. You could still use stacked format filtering if you want but you would need to add ConvertFromStacked(bits=10) as the last part of your script-. For 10 bit sources you need FFMPEGsource to decode in real 10-bits. L-smash only supports interleaved and stacked formats.
Multithreading is simple in avs+, just add Prefetch(threads) to the end of the script.
Thanks for your reply, Gser. I'm not entirely clueless, but it's been three years since I took the time to test and setup my templates, and what's left of my mind's a bit hazy (plus the change from SEt's MT AviSynth to AviSynth+). If you could help me translate my standard template I think I could apply that to my other variations. Typically I encode a Blu-ray on my quad-core system with the following script (adjusting the strength of SMDegrain depending on the source):
SetMemoryMax(2048)
SetMTMode(3,7)
<input>
SetMTMode(2)
SMDegrain(TR=3,ThSAD=300,RefineMotion=True,Plane=0,Chroma=False,Lsb=True,Lsb_Out=True)
F=DitherPost(Mode=-1)
S=F.FastLineDarkenMod()
D=MT_MakeDiff(S,F).Dither_Convert_8_To_16()
Dither_Add16(Last,D,Dif=True,U=2,V=2)
GradFun3(Radius=16,Lsb_In=True,Lsb=True)
Dither_Out()
I also tick "Enable 10-Bits Encoding" and add "--demuxer raw --input-depth 16 --sar 1:1" to the x264 command line. I've always been very happy with these results. Is it even possible to use SMDegrain in AviSynth+?
LouieChuckyMerry
3rd June 2018, 22:27
It's because one or more lines of your code is so long. That sets the window size. You need to break those lines manually. The convention is to put a \ at the end to indicate that it is to be combined with the next line. Like so:
This is a line with a \
manual break.
Or use QUOTE instead CODE, without problems for log's.
@ LouieChuckyMerry:
Or, if both indentation and full width matter, use external pastebin services, just link the URL here.
There are other forum software which wrap code blocks in on-demand scroll boxes with a maximum width (as well as height, like here (https://forum.doom9.org/showthread.php?p=1843456#post1843456)), so it doesn't destroy the base layout.
:thanks: Now I've one less thing to think about ;) .
In AviSynth+ MT, multi-threading is already pre-configured for many known core and plugin functions. You may still tweak the MT mode per filter using SetFilterMTMode() if you really know it better...
Instead of using SetMTMode(mode[,threads /*in first call only*/]) in every place where the mode changes, you will usually trust in the predefined mode per filter, but you have to enable multi-threading for a number of threads at the very end of the script, using Prefetch(threads); more details in: AviSynth Wiki: AviSynth+ – MT notes (http://avisynth.nl/index.php/AviSynth%2B#MT_Notes)
Note: If you use both return clip and Prefetch, you have to think well about their placements.
thanks for your reply, gser. I'm not entirely clueless, but it's been three years since i took the time to test and setup my templates, and what's left of my mind's a bit hazy (plus the change from set's mt avisynth to avisynth+). If you could help me translate my standard template i think i could apply that to my other variations. Typically i encode a blu-ray on my quad-core system with the following script (adjusting the strength of smdegrain depending on the source):
I also tick "enable 10-bits encoding" and add "--demuxer raw --input-depth 16 --sar 1:1" to the x264 command line. I've always been very happy with these results. Is it even possible to use smdegrain in avisynth+?
Maybe SMDdegrain would work with LSFmod v.21 Modded Version by A.SONY.
setmemorymax(2048)
<input>
smdegrain(tr=3,thsad=300,refinemotion=true,plane=0,chroma=false,lsb=true,lsb_out=true)
f=ditherpost(mode=-1)
s=f.fastlinedarkenmod()
d=mt_makediff(s,f).dither_convert_8_to_16()
dither_add16(last,d,dif=true,u=2,v=2)
gradfun3(radius=16,lsb_in=true,lsb=true)
dither_out()
convertfromstacked(bits=16)
prefetch(7)
LouieChuckyMerry
4th June 2018, 16:18
Gser: I ticked "Always use the included AviSynth", restarted, and updated from the developmental server, but receive the error message "Script error: there is no function named "ConvertFromStacked" when I load your suggested script. I thought "ConvertFromStacked" was a built-in function, although I could surely be wrong.
Gser: I ticked "Always use the included AviSynth", restarted, and updated from the developmental server, but receive the error message "Script error: there is no function named "ConvertFromStacked" when I load your suggested script. I thought "ConvertFromStacked" was a built-in function, although I could surely be wrong.
Yes it is an inbuilt avs+ function.
LouieChuckyMerry
4th June 2018, 23:57
Yes it is an inbuilt avs+ function.
Any thoughts why I'm receiving the error message, then?
Best publish a whole log file from starting and closing MeGUI. It should contain the analysis of your system and the used AviSynth DLL, not much more.
LouieChuckyMerry
5th June 2018, 14:17
Best publish a whole log file from starting and closing MeGUI. It should contain the analysis of your system and the used AviSynth DLL, not much more.
Thanks, LigH. That's so simple I'm embarrassed :o . Seems I'm not using AviSynth+, even though I ticked "Always use included AviSynth":
[Information] Log
-[Information] Versions
--[Information] MeGUI: 2859 x86
--[Information] Update Check: development update server
--[Information] System Information
---[Information] Operating System: Windows 7 Premium x64 SP1 (6.1.65536.7601)
---[Information] .NET Framework: 4.0 (4.0.0.0)
---[Information] .NET Framework: 4.7 (4.7.02558)
---[Information] Redistributables
----[Information] Microsoft Visual C++ 2010 x64: 10.0.40219
----[Information] Microsoft Visual C++ 2010 x86: 10.0.40219
----[Information] Microsoft Visual C++ 2015 x64: 14.0.23506
----[Information] Microsoft Visual C++ 2015 x86: 14.0.23026
---[Information] DPI: 100% (96/96)
---[Information] Monitor 1
----[Information] Resolution: 1600x900
----[Information] Primary Screen: True
--[Information] Component Information
---[Information] Haali Media Splitter: 1.13.138.14 (14-04-2013)
---[Information] Haali DSS2: (14-04-2013)
---[Information] ICSharpCode.SharpZipLib: 0.85.5.452 (07-08-2008)
---[Information] MediaInfo: 18.05.0.0 (08-05-2018)
---[Information] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
---[Information] 7z: 9.20 (18-11-2010)
--[Information] AviSynth Information
---[Information] AviSynth Wrapper
----[Information] Version: 1.0.2847.0
----[Information] Date: 06-05-2018
----[Information] Interface: 3
---[Information] AviSynth
----[Information] File Version: 2.6.0.5
----[Information] Date: 20-02-2015
----[Information] Name: Avisynth 2.6
----[Information] Version: AviSynth 2.60, build:Feb 20 2015 [03:16:45]
----[Information] AviSynth+: false
----[Information] MT: true
----[Information] Status: inactive
---[Information] AviSynth portable
----[Information] File Version: 0.1
----[Information] Date: 28-03-2018
----[Information] Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] Version: AviSynth 2.60, build:Feb 20 2015 [03:16:45]
----[Information] AviSynth+: false
----[Information] MT: true
----[Information] Status: active
-[Information] Update detection
--[Information] [05 Jun 18 09:14:54] redist files copied: 2017_x86
--[Information] [05 Jun 18 09:14:54] Connected to server: http://megui.tmebi.de/test/
--[Information] [05 Jun 18 09:14:55] No package requires an update
Seems I'm not using AviSynth+, even though I ticked "Always use included AviSynth":
:eek: Seriously surprising. Let's hope Zathor has ideas, maybe a more verbose test build of MeGUI reporting more about the AviSynth DLL selection.
I hope you installed MeGUI outside of the UAC (i.e. not in C:\Program Files (x86)). If you did, that may prevent it from copying files.
@Zathor: Might be a good idea to include the installation path of MeGUI in the log.
LouieChuckyMerry
5th June 2018, 15:36
I hope you installed MeGUI outside of the UAC (i.e. not in C:\Program Files (x86)). If you did, that may prevent it from copying files.
I use the portable version of MeGUI. Perhaps that's part of the problem?
VoodooFX
5th June 2018, 17:40
Updated MEGUI from 283? to latest and there is some error, when using One-Click(on folder with multiple files), error is when Queue process Mode - oneclick. I guess it should create jobs for second video file, but it fails.
https://i.imgur.com/mQ8VFet.png
Zathor
5th June 2018, 22:04
Gser: I ticked "Always use the included AviSynth", restarted, and updated from the developmental server, but receive the error message "Script error: there is no function named "ConvertFromStacked" when I load your suggested script. I thought "ConvertFromStacked" was a built-in function, although I could surely be wrong.
It is not a core avs+ function, as for that the external dll "ConvertStacked.dll" has to be loaded. Add a LoadPlugin("MeGUIPath\tools\avs\plugins\ConvertStacked.dll") to your script and it should work.
Zathor
5th June 2018, 22:05
Updated MEGUI from 283? to latest and there is some error, when using One-Click(on folder with multiple files), error is when Queue process Mode - oneclick. I guess it should create jobs for second video file, but it fails.
https://i.imgur.com/mQ8VFet.png
Could you please upload the log?
Are you able to reproduce that?
hello_hello
5th June 2018, 23:36
Thanks, LigH. That's so simple I'm embarrassed :o . Seems I'm not using AviSynth+, even though I ticked "Always use included AviSynth":
You're not alone.
https://forum.doom9.org/showthread.php?p=1837914#post1837914
hello_hello
5th June 2018, 23:52
Zathor,
Is it necessary for the AVS Cutter to refuse to add cuts to a script more than once? Could complete refusal be replaced with a warning that cuts have already been added? There's times it might be necessary to add more than one lot of cuts to a script and at the moment it requires adding cuts, closing the AVS Cutter completely and then re-opening the script.
Possibly the ability to add cuts a second time could be disabled until the preview is refreshed after the first lot of cuts has been added, or the preview could be automatically refreshed when cuts are added, effectively resetting it rather than having to close and open the AVS Cutter.
Another small annoyance...
If you open a script with the AVS Cutter, it appears to check the total frame count and refuses to allow you to enter a frame number beyond the last frame. There's times when that's annoying because you can manually change something in a script and re-load it in the AVS Cutter preview and proceed/continue to add cuts, unless it increases the frame count, in which case the cuts added are limited to the original frame range.
Thanks.
PS Is MeGUI being a bit oddly when encoding sources indexed with Lsmash for anyone else?
For some reason, after one of the recent updates, the info displayed in the job queue takes quite a while to acknowledged an encode has started, even though the window displaying the encoding process is open and it's clearly progressing. The log queue continues to display "waiting" and appears to be frozen, because no jobs can be started until it changes from "waiting" to "processing", and a couple of time MeGUI has frozen completely "waiting" for a job to commence that's already running. It seems to only happen with Lsmash.
VoodooFX
6th June 2018, 00:39
Could you please upload the log?
Are you able to reproduce that?
Yes, here is log (after oneclick error I aborted audio job):
https://pastebin.com/gNijDJmS
btw I get same error " 4 is not valid for 'index' " when I edit x265 preset in oneclick and try to save it(clicking around presets error sometimes disappears, still I dunno why or when).
LouieChuckyMerry
6th June 2018, 01:08
It is not a core avs+ function, as for that the external dll "ConvertStacked.dll" has to be loaded. Add a LoadPlugin("MeGUIPath\tools\avs\plugins\ConvertStacked.dll") to your script and it should work.
You're not alone.
https://forum.doom9.org/showthread.php?p=1837914#post1837914
Adding "LoadPlugin... ConvertStacked.dll" to the script gained me one more line, 33, thanks. Now I receive the error message "Script error: there is no function named "Prefetch" (... , line 34)". Could this be related to the issue hello_hello mentioned? The open-then-close log I posted shows the same thing:
--[Information] AviSynth Information
---[Information] AviSynth Wrapper
----[Information] Version: 1.0.2847.0
----[Information] Date: 06-05-2018
----[Information] Interface: 3
---[Information] AviSynth
----[Information] File Version: 2.6.0.5
----[Information] Date: 20-02-2015
----[Information] Name: Avisynth 2.6
----[Information] Version: AviSynth 2.60, build:Feb 20 2015 [03:16:45]
----[Information] AviSynth+: false
----[Information] MT: true
----[Information] Status: inactive
---[Information] AviSynth portable
----[Information] File Version: 0.1
----[Information] Date: 28-03-2018
----[Information] Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] Version: AviSynth 2.60, build:Feb 20 2015 [03:16:45]
----[Information] AviSynth+: false
----[Information] MT: true
----[Information] Status: active
Also, I'm not sure if SMDegrain would even work in AviSynth+, but the script I modified for AviSynth+ (with the help of Gser) doesn't throw an error until the last line, Prefetch(7), which is well past the SMDegrain line.
Edit: Ahhh, I'm using 64 Bit Windows 7.
MeGUI as such is more or less "portable" anyway, you just unpack it from a ZIP archive, and you should unpack it anywhere else, just not in the usual "Program Files" directories protected by the UAC. Where does it reside in your system?
While it is in a generic directory, it should be able to copy a DLL on demand so that its local AviSynth+ DLL is preferred over any AviSynth? DLL installed in your Windows system. I would suggest Zathor to add some debugging around this mechanism for those where it seems to fail.
Windows 7 in 64 bit is fine; if you don't use the 64 bit of MeGUI, the general version will use the 32 bit version of AviSynth (log reports "MeGUI: 2859 x86", and SEt's MT version is only available in 32 bit, so it's obvious).
BTW, "Prefetch(7)" is funny, are 7 threads the maximum for your specific script's memory consumption? And yes, Prefetch() is a function specific to AviSynth+ MT.
hello_hello
6th June 2018, 08:04
Adding "LoadPlugin... ConvertStacked.dll" to the script gained me one more line, 33, thanks. Now I receive the error message "Script error: there is no function named "Prefetch" (... , line 34)". Could this be related to the issue hello_hello mentioned?
Open a script with nothing but Version() and see what it says.
tebasuna51
6th June 2018, 10:49
Zathor,
Is it necessary for the AVS Cutter ...
Zathor, maybe you can change also the Audio Cutter tool based in the .clt file created with the AVS Cutter with the MkvMerge method showed here. (https://forum.doom9.org/showthread.php?p=1842802#post1842802)
- MkvMerge is already in the MeGUI package and you can forget the old BeSplit.exe not needed for MeGUI at all.
- MkvMerge is actualized frequently and support much more audio formats than BeSplit.
- You need only one job to obtain the output, with BeSplit you need one for split and a second to join.
LouieChuckyMerry
6th June 2018, 14:34
MeGUI as such is more or less "portable" anyway, you just unpack it from a ZIP archive, and you should unpack it anywhere else, just not in the usual "Program Files" directories protected by the UAC. Where does it reside in your system?
I have it on a RAMDisc, F:\, with all my other audio-video programs. When I started learning about encoding it seemed like a good idea to have independent discs for the executable files (F:\), the source files (D:\), and the output files (C:\). Perhaps I was overthinking things ;) .
Windows 7 in 64 bit is fine; if you don't use the 64 bit of MeGUI, the general version will use the 32 bit version of AviSynth (log reports "MeGUI: 2859 x86", and SEt's MT version is only available in 32 bit, so it's obvious).
Yes, I've been using SEt's (:thanks:) 32 bit MT version for some years, until trying to figure out AviSynth+.
BTW, "Prefetch(7)" is funny, are 7 threads the maximum for your specific script's memory consumption? And yes, Prefetch() is a function specific to AviSynth+ MT.
In the beginning I used Groucho2004's awesome AVSMeter (:thanks:) to test for the best MT configuration, and I found that on my quad-core system SetMTMode(3,7) gave me better results than SetMTMode(3,8). Not that I know why :rolleyes: .
Open a script with nothing but Version() and see what it says.
It shows: AviSynth 2.60, build:Feb 20 2015 [03:16:45] © 2000-2014 Ben Rudiak-Gould, et al. http://www.avisynth.org
PS Is MeGUI being a bit oddly when encoding sources indexed with Lsmash for anyone else?
For some reason, after one of the recent updates, the info displayed in the job queue takes quite a while to acknowledged an encode has started, even though the window displaying the encoding process is open and it's clearly progressing. The log queue continues to display "waiting" and appears to be frozen, because no jobs can be started until it changes from "waiting" to "processing", and a couple of time MeGUI has frozen completely "waiting" for a job to commence that's already running. It seems to only happen with Lsmash.
I've not experienced any freezing, but perhaps it takes a bit longer to proceed from "waiting" to "processing" lately. It's always taken much longer for LSmash scripts to load-begin processing than FFMS scripts on both my Win 7 64 bit systems, but I prefer it because, for whatever reason, FFMS sometimes "acts up" whereas LSmash doesn't.
Zathor
6th June 2018, 22:00
It shows: AviSynth 2.60, build:Feb 20 2015 [03:16:45] © 2000-2014 Ben Rudiak-Gould, et al. http://www.avisynth.org
I do not know what is going on there. Could you please check if you do have a avisynth.dll in your MeGUI folder (in the root) when MeGUI is running and this dll is from 2018?
doomleox999
6th June 2018, 23:07
OK, then I misunderstood it. You do not want to select specific streams you want to change the language of exsting streams. This is sadly not possible.
I found a way. You just have to change the default language in MeGUI settings, as simple as that.
LouieChuckyMerry
7th June 2018, 01:50
I do not know what is going on there. Could you please check if you do have a avisynth.dll in your MeGUI folder (in the root) when MeGUI is running and this dll is from 2018?
There's an AviSynth.dll in the root MeGUI folder and Windows Properties says the "Product name" is "AviSynth+ 0.1 (r2664, MT, i386)" and the "Date modified" is "28 March 18 15:04".
hello_hello
7th June 2018, 03:06
It shows: AviSynth 2.60, build:Feb 20 2015 [03:16:45] © 2000-2014 Ben Rudiak-Gould, et al. http://www.avisynth.org
Sorry if that makes me feel a bit better. I suspected it was probably happening to other people, only nobody else had noticed yet.
When I tested old MeGUI versions, it seems the problem was introduced around the time the extra Avisynth info was added to the log file. That may be just co-incidence, but it took me a long time to notice too.
I've not experienced any freezing, but perhaps it takes a bit longer to proceed from "waiting" to "processing" lately. It's always taken much longer for LSmash scripts to load-begin processing than FFMS scripts on both my Win 7 64 bit systems, but I prefer it because, for whatever reason, FFMS sometimes "acts up" whereas LSmash doesn't.
Maybe it's because my PC's old and it's a slow script and it's been a while since I encoded any 1080p video, but I don't recall such a large delay time between MeGUI starting encoding and realising it had started encoding. The progress window is really slow to respond to changes in encoding speed, so maybe it's related to that (I wish it was responsive enough to show you sudden changes in encoding speed instead of slow enough to show you something that probably happened 20 minutes ago).
This was what I meant though. 100 frames have been encoded and the job queue still hasn't caught up (job5 running).
I'm using an old XP compatible version of LSmash, but even so, this feels like something new.
PS. I just ran a short encode (100 frames) of the same video, only without any filtering aside from resizing in the script, and when it'd finished encoding the job queue still showed "waiting". When I tried deleting the job from the queue manually, MeGUI found a new excuse to crash. :)
https://s22.postimg.cc/bxwqle201/waiting.gif
hello_hello
7th June 2018, 11:07
Another feature request for Zathor.....
When you select an encoder preset, open the encoder configuration and then change something, upon clicking "okay" MeGUI asks if you'd like to save the changes to the preset. Not having clicked the "Update" button first, I'm usually pretty confident I don't want to save the changes to the preset, so would it be possible to add a "don't ask me again" checkbox to the message window?
The question seems rather redundant to me anyway, given there's an obvious update button for when you do want to update the preset, and 90% of the time I'd be making temporary changes to an existing preset rather than loading the defaults and starting from scratch anyway, and being asked all the time is $&#% annoying. :)
Thanks.
Zathor
7th June 2018, 22:32
There's an AviSynth.dll in the root MeGUI folder and Windows Properties says the "Product name" is "AviSynth+ 0.1 (r2664, MT, i386)" and the "Date modified" is "28 March 18 15:04".
OK, what is happening is that that avisynth.dll cannot be used by MeGUI. Therefore the script calls the system installed dll which is the old AviSynth from 2015.
The question therefore is why the avisynth.dll in the MeGUI folder is not autoloaded. How do you start MeGUI? With a double click on the MeGUI.exe?
Also avs+ needs the vcredist 2017 which you do not have installed. It should be copied by MeGUI but could you please try to install:
https://aka.ms/vs/15/release/vc_redist.x86.exe
VoodooFX
8th June 2018, 00:18
@Zathor
What about that (https://forum.doom9.org/showthread.php?p=1843714#post1843714) error?
tebasuna51
8th June 2018, 09:56
What about that (https://forum.doom9.org/showthread.php?p=1843714#post1843714) error?
Maybe MediaInfo found another subtitle corrupt here:
---[Information] Text
-[Information] ID: 7
-[Information] StreamOrder: 6
-[Information] Codec: S_TEXT/UTF8
-[Information] LanguageString: Portuguese
---[Information] Text
-[NoImage] InvalidArgument=Value of '4' is not valid for 'index'.
Try remux your mkv source with MkvToolNixGUI before, and repeat the MeGUI recode.
wiggaz
8th June 2018, 13:34
Hello,
I did few tests between the old version (2836) and the latest (2859), and ffmpeg is indeed slower.
We are talking about fps decimals but, since we enjoy every single increase, that's become significally important, I think.
Here's some logs:
1080p crf (first 2836 then 2859)
https://pastebin.com/iet3XFmg
576p 2pass (first 2836 then 2859)
https://pastebin.com/pMCsZuU8
What you think?
Thanks in advance
LouieChuckyMerry
8th June 2018, 15:03
Also avs+ needs the vcredist 2017 which you do not have installed. It should be copied by MeGUI but could you please try to install:
https://aka.ms/vs/15/release/vc_redist.x86.exe
Happy Friday! I've downloaded and installed the above 2017 vcredist.
OK, what is happening is that that avisynth.dll cannot be used by MeGUI. Therefore the script calls the system installed dll which is the old AviSynth from 2015.
The question therefore is why the avisynth.dll in the MeGUI folder is not autoloaded. How do you start MeGUI? With a double click on the MeGUI.exe?
I've portable MeGUI in a folder on a RAMDisc and pinned to the Win 7 64 bit start menu. I tried double-clicking on MeGUI.exe but receive the same "No Function Prefetch" error, so it seems to still be reverting to the installed 2015 avisynth.dll.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.