Log in

View Full Version : MeGUI: bug reports and feature requests


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 [94] 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147

Barough
31st August 2015, 20:41
Thnx 4 the VOB fix Zathor :)

Barough
2nd September 2015, 18:27
LigH have released new x265 compiles, v1.7+470
http://forum.doom9.org/showpost.php?p=1736824&postcount=2664

LigH
2nd September 2015, 20:01
No need to update x265 each time, not even each "merge with stable". Really "revolutionary" changes or serious bug fixes are rare.

LigH
3rd September 2015, 19:49
I just had a confusing reaction on a rarely used PC. I tried to convert a small AviSynth script to an Xvid AVI. MeGUI loaded the script and displayed a preview window. I created a job pair in the queue and started it ... MeGUI completely locked up, I had to use a task manager to kill the process.

Another try: The started job immediately quit. The log revealed that xvid_encraw was unable to load the avi/avs. Why not? MeGUI displayed the preview, so it should work...

I copied the command line from the log and executed it in the console: Same error message. Hmm. No working AviSynth installed in the system? Can VirtualDub open the script? No, it can't find a matching AVI file handler. Indeed. No AviSynth installed.

So it means that xvid_encraw won't work with a "portable AviSynth package" in MeGUI? Is it possibly only useful for the preview?

Zathor
3rd September 2015, 22:47
It did work in the past when this feature was introduced. Since then several changes to xvid have been made. I need to test it myself.

Barough
3rd September 2015, 22:54
No problems here when MeGUI uses the 'included AviSynth' on an Xvid AVI encode

kalehrl
6th September 2015, 10:03
@Zathor
Could you please look at this post:
http://forum.doom9.org/showthread.php?p=1737437#post1737437

Zathor
6th September 2015, 14:59
Please post the whole log. At least the version block and the script.

kalehrl
6th September 2015, 15:26
x264 error:
[Error] Log
-[Warning] Versions
--[Information] [6.9.2015. 10.54.25] MeGUI: 2582
--[Information] [6.9.2015. 10.54.25] Operating System: Windows 10 Professional x64 (10.0.0.10240)
--[Information] [6.9.2015. 10.54.25] .NET Framework: 4.0 (4.0.0.0)
--[Information] [6.9.2015. 10.54.25] .NET Framework: 4.6 (4.6.00079)
--[Information] [6.9.2015. 10.54.25] AviSynth: 2.6.0.6 (31-03-2015)
--[Information] [6.9.2015. 10.54.25] AvisynthWrapper: (02-01-2009)
--[Warning] [6.9.2015. 10.54.25] Haali Matroska Splitter not installed properly.
--[Warning] [6.9.2015. 10.54.25] Therefore DSS2() and certain functions of FFVideoSource() and the HD Streams Extractor may also not work.
--[Warning] [6.9.2015. 10.54.25] Please download and install it from http://haali.su/mkv/
--[Information] [6.9.2015. 10.54.25] Haali DSS2: not installed
--[Information] [6.9.2015. 10.54.25] ICSharpCode.SharpZipLib: 0.85.5.452 (07-08-2008)
--[Information] [6.9.2015. 10.54.25] MediaInfo: 0.7.76.0 (06-08-2015)
--[Information] [6.9.2015. 10.54.25] MediaInfoWrapper: 0.7.61.0 (06-01-2013)
--[Information] [6.9.2015. 10.54.25] MessageBoxExLib: 1.0.2218.28317 (19-12-2008)
--[Information] [6.9.2015. 10.54.25] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
--[Information] [6.9.2015. 10.54.25] 7z: 9.20 (18-11-2010)
-[Information] Update detection
--[Information] [6.9.2015. 10.54.25] Using cached update config and server: http://megui.tmebi.de/test/
--[Information] [6.9.2015. 10.54.25] No package requires an update
-[Error] Log for job1 (video, 20131112_-_TOP_GEAR_cut_out-muxed.mkv.avs -> 20131112_-_TOP_GEAR_cut_out-muxed.mkv.mkv)
--[Information] [6.9.2015. 10.54.45] Started handling job
--[Information] [6.9.2015. 10.54.45] Preprocessing
--[Information] [6.9.2015. 10.54.45] Avisynth input script
---[NoImage] LoadPlugin("D:\Programs\MeGUI\tools\lsmash\LSMASHSource.dll")
---[NoImage] LWLibavVideoSource("D:\Dreambox\movie\cuttermaran\20131112_-_TOP_GEAR_cut temp files\20131112_-_TOP_GEAR_cut_out-muxed.mkv")
---[NoImage] #deinterlace
---[NoImage] #crop
---[NoImage] #resize
---[NoImage] #fft3dgpu()
---[NoImage] KNLMeansCL(device_type="GPU")
--[Information] [6.9.2015. 10.54.45] resolution: 704x396
--[Information] [6.9.2015. 10.54.45] frame rate: 25/1
--[Information] [6.9.2015. 10.54.45] aspect ratio: 16:9 (1.778)
--[Information] [6.9.2015. 10.54.45] Job command line: "D:\Programs\MeGUI\tools\x264\avs4x264mod.exe" --preset slow --crf 19.0 --sar 1:1 --output "C:\Users\kaleh\Desktop\20131112_-_TOP_GEAR_cut_out-muxed.mkv.mkv" "C:\Users\kaleh\Desktop\20131112_-_TOP_GEAR_cut_out-muxed.mkv.avs"
--[Information] [6.9.2015. 10.54.45] Process started
--[Information] [6.9.2015. 10.54.45] Standard output stream
--[Error] [6.9.2015. 10.54.45] Standard error stream
---[Error] [6.9.2015. 10.54.46] avs [error]: Script error: there is no function named "KNLMeansCL"
---[Information] [6.9.2015. 10.54.46] (C:\Users\kaleh\Desktop\20131112_-_TOP_GEAR_cut_out-muxed.mkv.avs, line 7)
--[Error] [6.9.2015. 10.54.46] Process exits with error: 0xFFFFFFFF (-1)
--[Warning] [6.9.2015. 10.54.46] The 64 bit mode of x264 is enabled. Depending on the error it may help to disable it in the MeGUI settings.
--[Information] [6.9.2015. 10.54.46] Job completed

LigH
6th September 2015, 15:42
MeGUI will probably use its own plugins directory, independent of the default for the AviSynth installation in the system. If you want to use plugins not maintained by MeGUI (like KNLMeansCL), you should add an explicit "LoadPlugin" in your AviSynth script. At least to be on the safe side...

kalehrl
6th September 2015, 19:02
I tried adding it but it still errors out.
I can encode in xvid just fine with KNLMeansCL, but when using x264, there is this error.

AMED
8th September 2015, 03:29
You'll probably get the same load plugin error as i got HERE (http://forum.doom9.org/showthread.php?p=1733189#post1733189) with KNLMeansCL.

hello_hello
8th September 2015, 12:59
MeGUI will probably use its own plugins directory, independent of the default for the AviSynth installation in the system. If you want to use plugins not maintained by MeGUI (like KNLMeansCL), you should add an explicit "LoadPlugin" in your AviSynth script. At least to be on the safe side...

The portable version of Avisynth+ checks the registry for the location of the Avisynth auto-loading plugins folder and loads the plugins within, so if you have Avisynth installed it'll auto-load the same plugins folder (at least it does when running XP).
It can also auto-load plugins from it's own plugins folder.

You'll probably get the same load plugin error as i got HERE (http://forum.doom9.org/showthread.php?p=1733189#post1733189) with KNLMeansCL.

According to Dependancy Walker, KNLMeansCL requires msvcr120, msvcp120 and vcomp120.dll
If you tell MeGUI to use the included Avisynth and restart it, you should find msvcr120 and msvcp120 in the MeGUI folder (that's what happens for me). I think you said you only copied the first one so it might have something to do with KNLMeansCL not producing errors when the included Avisynth is used.

I'm not sure about vcomp120.dll and if it's always required. Maybe only for KNLMeansCL(device_type="GPU")
MeGUI doesn't seem to include it. You'd probably need to install Visual C++ Redistributable Package for Visual Studio 2013 (http://www.microsoft.com/en-us/download/details.aspx?id=40784)

I tried adding it but it still errors out.
I can encode in xvid just fine with KNLMeansCL, but when using x264, there is this error.

I tested the current version and an older version of KNLMeansCL with both Xvid and x264 encoding and it's working fine here (XP with both MeGUI's "included" and the installed version of Avisynth). Odd......

kalehrl
8th September 2015, 13:30
I installed Visual Studio 2013 because KNLMeansCL wouldn't work in avspmod.
I'm using windows 10 pro. I wonder if there is a conflict between opencl which x264 uses and KNLMeansCL.

AMED
8th September 2015, 19:39
I'm not sure about vcomp120.dll and if it's always required. Maybe only for KNLMeansCL(device_type="GPU")
MeGUI doesn't seem to include it. You'd probably need to install Visual C++ Redistributable Package for Visual Studio 2013 (http://www.microsoft.com/en-us/download/details.aspx?id=40784)The script works fine with AVSMeter so I would assume that all the .dlls has been install correctly? It also works when using the AVS creator as well. I'm also on Windows 10 Pro so maybe there is a link?

Groucho2004
9th September 2015, 17:29
The script works fine with AVSMeter so I would assume that all the .dlls has been install correctly?
Yes. If runtime libraries were missing it would not work.
"VComp*.dll" are Microsofts OpenMP support libraries, used for example by plugins like KNLMeansCL and eedi3. I highly recommend the all-in-one runtime installer which can be found here (http://www.wincert.net/forum/topic/9790-aio-microsoft-visual-bcfj-redistributable-x86x64/).

AMED
12th September 2015, 22:38
hmm, just tried KNLMeansCL v0.64 (https://github.com/Khanattila/KNLMeansCL/releases) and it's working fine with MeGUI.

kalehrl
13th September 2015, 08:35
Just updated knlmeans and still get the same error:
-[Error] Log for job1 (video, 20131112_-_TOP_GEAR_cut_out-muxed.mkv.avs -> 20131112_-_TOP_GEAR_cut_out-muxed.mkv.mkv)
--[Information] [13.9.2015. 09.31.10] Started handling job
--[Information] [13.9.2015. 09.31.10] Preprocessing
--[Information] [13.9.2015. 09.31.10] Avisynth input script
---[NoImage] LoadPlugin("D:\Programs\MeGUI\tools\lsmash\LSMASHSource.dll")
---[NoImage] LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\KNLMeansCL.dll")
---[NoImage] LWLibavVideoSource("D:\Dreambox\movie\cuttermaran\20131112_-_TOP_GEAR_cut temp files\20131112_-_TOP_GEAR_cut_out-muxed.mkv")
---[NoImage] #deinterlace
---[NoImage] #crop
---[NoImage] #resize
---[NoImage] #fft3dgpu()
---[NoImage] KNLMeansCL()
--[Information] [13.9.2015. 09.31.10] resolution: 704x396
--[Information] [13.9.2015. 09.31.10] frame rate: 25/1
--[Information] [13.9.2015. 09.31.10] aspect ratio: 16:9 (1.778)
--[Information] [13.9.2015. 09.31.10] Job command line: "D:\Programs\MeGUI\tools\x264\avs4x264mod.exe" --preset slow --crf 19.0 --sar 1:1 --output "C:\Users\kaleh\Desktop\20131112_-_TOP_GEAR_cut_out-muxed.mkv.mkv" "C:\Users\kaleh\Desktop\20131112_-_TOP_GEAR_cut_out-muxed.mkv.avs"
--[Information] [13.9.2015. 09.31.10] Process started
--[Information] [13.9.2015. 09.31.10] Standard output stream
--[Error] [13.9.2015. 09.31.10] Standard error stream
---[Error] [13.9.2015. 09.31.10] avs [error]: LoadPlugin: unable to load "C:\Program Files (x86)\AviSynth\plugins\KNLMeansCL.dll", Proc not found. Update library version?
---[Information] [13.9.2015. 09.31.10] (C:\Users\kaleh\Desktop\20131112_-_TOP_GEAR_cut_out-muxed.mkv.avs, line 2)
--[Error] [13.9.2015. 09.31.10] Process exits with error: 0xFFFFFFFF (-1)
--[Warning] [13.9.2015. 09.31.10] The 64 bit mode of x264 is enabled. Depending on the error it may help to disable it in the MeGUI settings.
--[Information] [13.9.2015. 09.31.11] Job completed
I don't get it! Preview opens successfully but when I try to encode, it dies. Xvid works fine but not x264.

AMED
13th September 2015, 08:56
All I did was install the runtimes that Groucho2004 suggested and then update the plugin (and a reboot).

Zathor
13th September 2015, 13:58
Just updated knlmeans and still get the same error:
I don't get it! Preview opens successfully but when I try to encode, it dies. Xvid works fine but not x264.
What happens when you open the AVS file in another program (e.g. VirtualDub)?

Another topic: I switch for the moment to the regular AviSynth for the included AviSynth. AviSynth+ will return when the development continues and the builds are more stable. So everyone who needs MT has to install/copy that manually.

EDIT:
2584 [Update] clean package directory during update

hello_hello
13th September 2015, 15:51
Zathor, there's a small OneClick setup behaviour oddness.

If you have a OneClick profile where video encoding is disabled, when you select it, under the Advanced config tab the "display aspect ratio" option becomes greyed out. After changing back to a OneClick profile where video re-encoding is enabled though, the "display aspect ratio" option remains greyed out until you close the OneClick encoder and re-open it.

Unless I'm missing something I still think there's a small rounding error when calculating the aspect error while using a custom input display aspect ratio (as displayed in the script creator). Unless MeGUI simply isn't storing custom aspect ratios accurately enough. Currently it only displays them to 3 decimal places. Here's an example based on the mpeg4 PAL 16:9 pixel aspect ratio (as that's what I'm using it for).

I create a custom display aspect ratio of 20:11, which is an aspect ratio of 1.81818181818181...... MeGUI displays it as "20:11 (1.818)".
I select it as the Input display aspect ratio and resize to exactly 20:11 dimensions. 680x374 as an example (374*20/11=680).
The aspect error should be zero but MeGUI displays a small aspect error (ie 0.0005%). It's nothing significant, but it'd be nice if it was correct.

One other small request.... Currently there's a single option for clearing all the user selected aspect ratios, which is a little annoying when you have several and only want to remove one. Any chance of a right click option to remove them individually, or something similar?

Cheers.

kalehrl
13th September 2015, 19:17
All I did was install the runtimes that Groucho2004 suggested and then update the plugin (and a reboot).
I installed Visual C++ 2013 only which is the one required by knlmeans. I don't think I will install all those other C++ things just to get knlmeans working. Without Visual C++ 2013, knlmeans wouldn't work at all in avspmod or megui preview. I guess it's back to fft3dgpu for me for denoising which is much faster than knlmeans.

Zathor
13th September 2015, 19:53
[...] small request....
Thanks, written down to my list. As usual no ETA as these are no (game breaking) bugs.

mandeep145
14th September 2015, 04:03
Please sort out this not getting proper update

[Error] Log
-[Information] Versions
--[Information] [9/14/2015 8:29:52 AM] MeGUI: 2525
--[Information] [9/14/2015 8:29:52 AM] Operating System: Windows XP Professional x86 SP3
--[Information] [9/14/2015 8:29:52 AM] .Net Framework: 2.2.30729
--[Information] [9/14/2015 8:29:52 AM] .Net Framework: 4.0.30319
--[Information] [9/14/2015 8:29:53 AM] AviSynth: 2.6.0.6 (31-03-2015)
--[Information] [9/14/2015 8:29:53 AM] AvisynthWrapper: (02-01-2009)
--[Information] [9/14/2015 8:29:53 AM] Haali Matroska Splitter: 1.13.138.14 (14-04-2013)
--[Information] [9/14/2015 8:29:53 AM] Haali DSS2: not installed
--[Information] [9/14/2015 8:29:53 AM] ICSharpCode.SharpZipLib: 0.85.5.452 (07-08-2008)
--[Information] [9/14/2015 8:29:53 AM] LinqBridge: 1.0.0.0 (27-05-2009)
--[Information] [9/14/2015 8:29:53 AM] MediaInfo: 0.7.72.0 (07-01-2015)
--[Information] [9/14/2015 8:29:53 AM] MediaInfoWrapper: 0.7.61.0 (06-01-2013)
--[Information] [9/14/2015 8:29:53 AM] MessageBoxExLib: 1.0.2218.28317 (19-12-2008)
--[Information] [9/14/2015 8:29:53 AM] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
--[Information] [9/14/2015 8:29:53 AM] 7z: 9.20 (18-11-2010)
-[Error] Update detection
--[Information] [9/14/2015 8:29:53 AM] Using cached update config and server: http://megui.org/auto/stable/
--[Information] [9/14/2015 8:29:53 AM] There is 1 package which can be updated: FDK-AAC
--[Error] [9/14/2015 8:29:54 AM] Component not found: C:\Program Files\MeGUI\tools\fdkaac\fdkaac.exe

http://i.imgur.com/q7aNzpg.png

Barough
14th September 2015, 06:41
Please sort out this not getting proper update

FDK-AAC is NOT available through the update server(s) due to license stuff.

mini-moose
14th September 2015, 10:35
I noticed megui now has r785(20150802) on updates.

I can't find any infos as to how it's different from the older 785. Anyone knows?

mandeep145
14th September 2015, 13:23
FDK-AAC is NOT available through the update server(s) due to license stuff.


so how do i get the file bro ?

LigH
14th September 2015, 13:50
Either you know someone close who compiles it and can give you a non-public copy ... or you may have to compile it for yourself.

No panic; there is a batch file which will download a whole compiler environment and the sources, and start compiling automatically. Just run the batch. That simple. It will cost you some amount of intermediate harddisk space, though (up to a few GB, depending on the specific solution).

You can use fdkaac_autobuild.zip from the qaac cabinet (https://sites.google.com/site/qaacpage/cabinet); or if you want even more (warning: a lot more!), try the media-autobuild_suite (https://github.com/jb-alvarado/media-autobuild_suite/)...

Zathor
14th September 2015, 17:28
I noticed megui now has r785(20150802) on updates.
I can't find any infos as to how it's different from the older 785. Anyone knows?
And now r789 is uploaded
Usually newer compiles have newer included libraries (like libav, lsmash).

so how do i get the file bro?

When you try to update it there should be a popup pointing you in the correct direction with this text:

MeGUI cannot find FDK-AAC on your system or it is outdated. Due to the licensing the component is not included on the MeGUI update server. Therefore please download the file on your own, extract & compile it and set the path to the exe in the MeGUI settings ("Settings\External Program Settings"). Would you like to download it now?

Zathor
16th September 2015, 19:24
Currently I am struggling a little bit with the way how packages should be updated. In the current implementation it can happen that files are locked (e.g. x264 encoding running) and therefore packages cannot be updated. There are now two ways
- leave it as it is = zero effort
- modify the whole update handling in the way that all packages will only be extracted/updated during a restart of MeGUI = bigger change as a lot has to be moved to the updater program
The proper way is the second one but is this really needed? What do you think?

Zathor
16th September 2015, 20:52
2588 [Update] improved restart handling
2587 remove unnecessary runtime files at startup
2586 [Update] if a package needs to be enabled in the settings it will not be shown in the update window
2585 [DGIndexIM/NV] copy license.txt to the other indexer if possible

These commits - especially 2588 - are only briefly related to this restart topic from my post before (for AviSynth it could happen that the package requested a restart which did not happen). So the question is still valid if I should change the restart system.

AMED
17th September 2015, 06:24
I personally think that fixing up the profile saving\loading logic is more important. Nothing worse than MeGUI crashing or freezing mid encode and you have to kill the process only to find that it has nuked all your profiles.

Would it be easier to just disable the use of the updater if there is a worker in progress?

kalehrl
17th September 2015, 09:01
If one file in a folder cannot be encoded or there is an error with it, all other files in that folder are skipped when using one click encoder and adding the whole folder to be encoded.
I added 4 folders with video files to be encoded in xvid and in the 2nd folder there was an error with one file:
error: The process cannot access the file 'G:\BackupWinD\Films\xxxxxx\Sezona 2\xxx - 07 - WHAT LIES AHEAD.mkv.lwi' because it is being used by another process.
All other files in the remaining 3 folders were successfully encoded but not a single file in the 2nd folder. I will send Zathor log file via pm.

Zathor
17th September 2015, 18:13
The oneclick process is divided in two major parts: source preparation (extracting, indexing, ...) and encoding (audio/video, muxing). New jobs for new files are created at the end of the first part. So it looks like;
- source preparation file 1
- jobs for encoding file 1 are created
- jobs for source preparation file 2 are created
- encoding file 1
- source preparation file 2
- ....

If the source preparation part fails it stops. This is the intended behavior as the indexing job does not know which files need to be processed lateron. Only possible change would be to create all "source preparation" steps of a folder at once but then all source files will be extracted first (which may be a problem for the storage space) and then all files are encoded (therefore the first file will be ready later). I may add an option to select these second work order but it will not be the default one.

kalehrl
17th September 2015, 18:23
Any idea why the file failed in the first place?
I don't remember any program other than MeGUI using xxx - 07 - WHAT LIES AHEAD.mkv.lwi.

Zathor
17th September 2015, 22:10
Any idea why the file failed in the first place?
I don't remember any program other than MeGUI using xxx - 07 - WHAT LIES AHEAD.mkv.lwi.
Sorry, no clue

Would it be easier to just disable the use of the updater if there is a worker in progress?
Easier, yes - but when e.g. a filter is in access by the video preview than this will not help :(

I personally think that fixing up the profile saving\loading logic is more important. Nothing worse than MeGUI crashing or freezing mid encode and you have to kill the process only to find that it has nuked all your profiles.
2589 [Profile] "Load Defaults" resets the selected profile (before it was the scratchpad one)
improved profile saving
profiles will be saved to disk also when a profile is changed

kalehrl
18th September 2015, 15:31
One worker seems to be idling while encoding.
I had to press start once again so that I would have 2 files being encoded at the same time.

hello_hello
18th September 2015, 19:06
Feature request:

Could we please have the old behaviour when modifying/saving presets returned (pre 2589)?

I have an encoder preset I want to use, but I just want to change the CRF value (for example). Previously I could do so and the existing preset's settings would be copied to scratchpad. Now I either need to save a whole new preset, or over-write the existing preset, just to change one setting for a particular encode. The current behaviour seems like a step backwards to me, and I'm not sure what the point of having the scratchpad option is any longer. It's not even used when the default settings are loaded. I'll confess Zathor, the new behaviour doesn't make as much sense to me. :(

I've rolled back to version 2584 for the moment. What was wrong with the way the preset system worked until now?

Thanks.

Zathor
18th September 2015, 19:44
Sorry, I did not had that use case in mind. This part of the change will be reverted in the next build.

hello_hello
19th September 2015, 13:10
Cheers. I felt guilty posting with a negative reaction to your hard work, because it's very much appreciated. Thanks!

Octo-puss
19th September 2015, 16:17
Couldn't MeGUI start using system temp folder by default? I am trying to process ~100GB avi file with file indexer and it simply "kills" the regular HDD it is saved on after about 20 minutes. It just doesn't progress any further. Reading such humongous file and writing to the same disk at the same time doesn't really seem to work.

Zathor
19th September 2015, 17:29
Couldn't MeGUI start using system temp folder by default? I am trying to process ~100GB avi file with file indexer and it simply "kills" the regular HDD it is saved on after about 20 minutes. It just doesn't progress any further. Reading such humongous file and writing to the same disk at the same time doesn't really seem to work.
Which tasks/jobs do you speak about?
The system temp folder may be a bad choice so the user should select the temp drives. In OneClick mode no (big) file should be read & written on the same disk if selected properly.

Zathor
19th September 2015, 17:40
Cheers. I felt guilty posting with a negative reaction to your hard work, because it's very much appreciated. Thanks!

Thanks for your always constructive feedback!

2590 [Profile] improved profile saving II
fixed missing option to save to scratchpad (regression of 2589)

Octo-puss
19th September 2015, 19:04
Which tasks/jobs do you speak about?
The system temp folder may be a bad choice so the user should select the temp drives. In OneClick mode no (big) file should be read & written on the same disk if selected properly.
I simply opened AVS script creator, then selected file indexer, and when the file started processing, it gradually slowed down to crawl and I even had to shut MeGUI down once because the disk choked so badly the progression stopped.
You could add a global option to either enable system temp folder or specify a custom one.

hello_hello
19th September 2015, 19:57
I simply opened AVS script creator, then selected file indexer, and when the file started processing, it gradually slowed down to crawl and I even had to shut MeGUI down once because the disk choked so badly the progression stopped.
You could add a global option to either enable system temp folder or specify a custom one.

You can already do both.
In MeGUI's options there's one to specify the default output directory.
When you open file with the File Indexer you can specify the location where the index file should be saved (audio being extracted should be extracted to the same location).

The one exception might be indexing with L-Smash. At the moment the index file is created in the same directory as the source file then copied to the specified directory for the output files. I'd imagine that's some sort of limitation with the L-Smash indexer that prevents the index file from being written directly to the output directory, but Zathor can probably shed some light there.

I think the L-Smash indexer always indexes any audio whether it's required or not (as opposed to ffms2, where MeGUI configures it not to index the audio if it's not selected in the File Indexer). For large files, especially those with multiple audio streams, that might slow the indexing process.

I just tried a quick test with a 3GB MKV with 2 audio streams. Indexing time was 25 seconds for a 58mb index file (it appears to have indexed at least one of the audio streams even though no audio was selected in the file indexer).
After I remuxed the same video as an MKV without audio, indexing took 16 seconds for a 10mb index file.
For very large files containing audio, indexing the audio could make quite a difference.

Maybe Zathor will know if it's possible to tell L-Smash not to index audio unless it's required.

Octo-puss
19th September 2015, 20:00
I have no idea what L-SMASH is, but it could be the case. I tried selecting different output folder (different physical disk) and it still took maybe 40 minutes (115GB file, sure, but the read speed is easily 80MB/s for that one).

hello_hello
19th September 2015, 20:08
Thanks for your always constructive feedback!

2590 [Profile] improved profile saving II
fixed missing option to save to scratchpad (regression of 2589)

Thanks Zathor!

Changing a preset gives the option to save the changes to scratchpad again, which is nice.
It'll just take little while to get used to the "load defaults" function not loading the defaults in scratchpad as it did. I don't think that's a big deal either way. Maybe it'll be better as it is once I'm used to it.....

Thanks again!

hello_hello
19th September 2015, 20:20
I have no idea what L-SMASH is, but it could be the case. I tried selecting different output folder (different physical disk) and it still took maybe 40 minutes (115GB file, sure, but the read speed is easily 80MB/s for that one).

What type of file?
Depending on the file type, different indexers are used. There's a list when you open a file with the File Indexer and sometimes you can choose a different indexer (depending on the source file type).

40 minutes does sound like a long time, but depending on the file type and what's inside (multiple audio streams), it may not be for a 115GB file.

Octo-puss
19th September 2015, 20:29
I said it already, avi. All I know I clicked on file indexer, that's all I ever used. Sorry I don't understand the specifics of MeGUI very much, I learned one way to encode video years ago and just do that without really caring what it actually does.

LigH
20th September 2015, 07:28
I said it already, avi.

This is no satisfying amount of information. Never trust in a filename extension, there is always a chance that it has been renamed for the craziest reasons (e.g. people don't know how to assign a media player to an unassigned but correct extension so that it will start playing after a double-click in the Explorer).

To help us helping you, do an analysis of this source file using MediaInfo, and post the result in "Text" format in a CODE block (or in a pastebin service).

If you are sure that it is an AVI because you made it, you may also know which codec was used; 115 GB is really huge, so it possibly contains completely uncompressed video. It would be a pity to have uncompressed RGB video saved, what a waste of space, and furthermore it is not the optimal color space as source for modern video codecs. This would also explain why the Indexer takes aged to build an index: It will write keyframe data for really every frame, because completely uncompressed video consists of keyframes everywhere. Such a video is hard to handle by L-SMASH Source. In this case only, AviSource is to be preferred.