MeGUI: bug reports and feature requests

[Zathor]

LoadPlugin("E:\D\software\megui\tools\dgindex\DGDecode.dll")
DGDecode_Mpeg2Source("F:\DVD_VOLUME\VIDEO_TS\iziwdfnu.2ow\VTS_01_PGC_02_1.d2v")



Thanks, so it does crash when opening the basic avs script. Could you add those two lines into an AVS script and open it in the AVS script creator? What happens?

Use for your tests this new version: http://megui.org/megui_debug.zip

[sumirecccp]

>>zathor




[Error] Log
-[Information] Versions
--[Information] [2017/05/09 4:21:41] MeGUI: 2732
--[Information] [2017/05/09 4:21:41] Operating System: Windows 10 Enterprise x64 (10.0.0.15063)
--[Information] [2017/05/09 4:21:41] .NET Framework: 4.0 (4.0.0.0)
--[Information] [2017/05/09 4:21:41] .NET Framework: 4.7 (4.7.02046)
--[Information] [2017/05/09 4:21:41] Haali Media Splitter: 1.13.138.14 (14-04-2013)
--[Information] [2017/05/09 4:21:41] Haali DSS2: not installed
--[Information] [2017/05/09 4:21:41] ICSharpCode.SharpZipLib: 0.85.5.452 (07-08-2008)
--[Information] [2017/05/09 4:21:41] MediaInfo: 0.7.95.0 (04-05-2017)
--[Information] [2017/05/09 4:21:41] MediaInfoWrapper: 0.7.61.0 (06-01-2013)
--[Information] [2017/05/09 4:21:41] MessageBoxExLib: 1.0.2218.28317 (19-12-2008)
--[Information] [2017/05/09 4:21:41] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
--[Information] [2017/05/09 4:21:41] 7z: 9.20 (18-11-2010)
--[Information] AviSynth Wrapper
---[Information] [2017/05/09 4:21:41] Version: 1.0.2721.0
---[Information] [2017/05/09 4:21:41] Date: 29-04-2017
---[Information] [2017/05/09 4:21:41] Interface: 3
--[Information] AviSynth
---[Information] [2017/05/09 4:21:41] File Version: 2.6.0.5
---[Information] [2017/05/09 4:21:41] Date: 20-02-2015
---[Information] [2017/05/09 4:21:41] Name: Avisynth 2.6
---[Information] [2017/05/09 4:21:41] Version: AviSynth 2.60, build:Feb 20 2015 [03:16:45]
---[Information] [2017/05/09 4:21:41] AviSynth+: false
---[Information] [2017/05/09 4:21:41] MT: true
---[Information] [2017/05/09 4:21:41] Status: inactive
--[Information] AviSynth portable
---[Information] [2017/05/09 4:21:41] File Version: 0.1
---[Information] [2017/05/09 4:21:41] Date: 16-03-2017
---[Information] [2017/05/09 4:21:41] Name: AviSynth+ 0.1 (r2455, MT, i386)
---[Information] [2017/05/09 4:21:41] Version: AviSynth+ 0.1 (r2455, MT, i386)
---[Information] [2017/05/09 4:21:41] AviSynth+: true
---[Information] [2017/05/09 4:21:41] MT: true
---[Information] [2017/05/09 4:21:41] Status: active
-[Information] Update detection
--[Information] [2017/05/09 4:21:41] Automatic update is disabled
--[Information] [2017/05/09 4:21:41] Using cached update config and server: http://megui.tmebi.de/test/
--[Information] [2017/05/09 4:21:41] There is 1 package which can be updated: x265
-[Information] AviSynth
--[Information] [2017/05/09 4:21:50] sessions open: 1, id: 234156
---[NoImage] F:\DVD_VOLUME\VIDEO_TS\New AviSynth Script.avs
---[NoImage] 場所 System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
---[NoImage] 場所 System.Environment.get_StackTrace()
---[NoImage] 場所 MeGUI.AviSynthClip.HandleAviSynthWrapperDLL(Boolean bUnload, String script)
---[NoImage] 場所 MeGUI.AviSynthClip..ctor(String func, String arg, AviSynthColorspace forceColorspace)
---[NoImage] 場所 MeGUI.AviSynthScriptEnvironment.OpenScriptFile(String filePath, AviSynthColorspace forceColorspace)
---[NoImage] 場所 MeGUI.AvsFile..ctor(String script, Boolean parse)
---[NoImage] 場所 MeGUI.AvsFile.OpenScriptFile(String fileName)
---[NoImage] 場所 MeGUI.MediaInfoFile.CorrectSourceInformation(MediaInfo& oInfo, String strFile, LogItem infoLog, Int32 iPGCNumber, Int32 iAngleNumber)
---[NoImage] 場所 MeGUI.MediaInfoFile.GetSourceInformation(String file, LogItem oLog, Int32 iPGCNumber, Int32 iAngleNumber)
---[NoImage] 場所 MeGUI.MediaInfoFile..ctor(String file, Int32 iPGCNumber, Int32 iAngleNumber)
---[NoImage] 場所 MeGUI.MediaInfoFile..ctor(String file)
---[NoImage] 場所 MeGUI.MainForm.openFile(String file, MediaInfoFile& iFile)
---[NoImage] 場所 MeGUI.VideoEncodingComponent.videoInput_FileSelected(FileBar sender, FileBarEventArgs args)
---[NoImage] 場所 MeGUI.FileBar.triggerEvent()
---[NoImage] 場所 MeGUI.FileBar.setFilename(String filename)
---[NoImage] 場所 MeGUI.core.util.DragDropUtil.<>c__DisplayClass2_0.<RegisterSingleFileDragDrop>b__1(Object sender, DragEventArgs e)
---[NoImage] 場所 System.Windows.Forms.Control.OnDragDrop(DragEventArgs drgevent)
---[NoImage] 場所 System.Windows.Forms.Control.System.Windows.Forms.IDropTarget.OnDragDrop(DragEventArgs drgEvent)
---[NoImage] 場所 System.Windows.Forms.DropTarget.System.Windows.Forms.UnsafeNativeMethods.IOleDropTarget.OleDrop(Object pDataObj, Int32 grfKeyState, POINTSTRUCT pt, Int32& pdwEffect)
---[NoImage] 場所 System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
---[NoImage] 場所 System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
---[NoImage] 場所 System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
---[NoImage] 場所 System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
---[NoImage] 場所 System.Windows.Forms.Application.Run(Form mainForm)
---[NoImage] 場所 MeGUI.MainForm.Main(String[] args)
--[Information] [2017/05/09 4:21:50] sessions open: 0, id: 234156, close: True
---[NoImage] 場所 System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
---[NoImage] 場所 System.Environment.get_StackTrace()
---[NoImage] 場所 MeGUI.AviSynthClip.HandleAviSynthWrapperDLL(Boolean bUnload, String script)
---[NoImage] 場所 MeGUI.AviSynthClip.Dispose(Boolean disposing)
---[NoImage] 場所 MeGUI.AviSynthClip..ctor(String func, String arg, AviSynthColorspace forceColorspace)
---[NoImage] 場所 MeGUI.AviSynthScriptEnvironment.OpenScriptFile(String filePath, AviSynthColorspace forceColorspace)
---[NoImage] 場所 MeGUI.AvsFile..ctor(String script, Boolean parse)
---[NoImage] 場所 MeGUI.AvsFile.OpenScriptFile(String fileName)
---[NoImage] 場所 MeGUI.MediaInfoFile.CorrectSourceInformation(MediaInfo& oInfo, String strFile, LogItem infoLog, Int32 iPGCNumber, Int32 iAngleNumber)
---[NoImage] 場所 MeGUI.MediaInfoFile.GetSourceInformation(String file, LogItem oLog, Int32 iPGCNumber, Int32 iAngleNumber)
---[NoImage] 場所 MeGUI.MediaInfoFile..ctor(String file, Int32 iPGCNumber, Int32 iAngleNumber)
---[NoImage] 場所 MeGUI.MediaInfoFile..ctor(String file)
---[NoImage] 場所 MeGUI.MainForm.openFile(String file, MediaInfoFile& iFile)
---[NoImage] 場所 MeGUI.VideoEncodingComponent.videoInput_FileSelected(FileBar sender, FileBarEventArgs args)
---[NoImage] 場所 MeGUI.FileBar.triggerEvent()
---[NoImage] 場所 MeGUI.FileBar.setFilename(String filename)
---[NoImage] 場所 MeGUI.core.util.DragDropUtil.<>c__DisplayClass2_0.<RegisterSingleFileDragDrop>b__1(Object sender, DragEventArgs e)
---[NoImage] 場所 System.Windows.Forms.Control.OnDragDrop(DragEventArgs drgevent)
---[NoImage] 場所 System.Windows.Forms.Control.System.Windows.Forms.IDropTarget.OnDragDrop(DragEventArgs drgEvent)
---[NoImage] 場所 System.Windows.Forms.DropTarget.System.Windows.Forms.UnsafeNativeMethods.IOleDropTarget.OleDrop(Object pDataObj, Int32 grfKeyState, POINTSTRUCT pt, Int32& pdwEffect)
---[NoImage] 場所 System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
---[NoImage] 場所 System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
---[NoImage] 場所 System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
---[NoImage] 場所 System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
---[NoImage] 場所 System.Windows.Forms.Application.Run(Form mainForm)
---[NoImage] 場所 MeGUI.MainForm.Main(String[] args)
--[Information] [2017/05/09 4:21:50] sessions open: 1, id: 230854
---[NoImage] F:\DVD_VOLUME\VIDEO_TS\New AviSynth Script.avs
---[NoImage] 場所 System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
---[NoImage] 場所 System.Environment.get_StackTrace()
---[NoImage] 場所 MeGUI.AviSynthClip.HandleAviSynthWrapperDLL(Boolean bUnload, String script)
---[NoImage] 場所 MeGUI.AviSynthClip..ctor(String func, String arg, AviSynthColorspace forceColorspace)
---[NoImage] 場所 MeGUI.AviSynthScriptEnvironment.OpenScriptFile(String filePath, AviSynthColorspace forceColorspace)
---[NoImage] 場所 MeGUI.AvsFile..ctor(String script, Boolean parse)
---[NoImage] 場所 MeGUI.AvsFile.OpenScriptFile(String fileName)
---[NoImage] 場所 MeGUI.MainForm.openFile(String file, MediaInfoFile& iFile)
---[NoImage] 場所 MeGUI.VideoEncodingComponent.videoInput_FileSelected(FileBar sender, FileBarEventArgs args)
---[NoImage] 場所 MeGUI.FileBar.triggerEvent()
---[NoImage] 場所 MeGUI.FileBar.setFilename(String filename)
---[NoImage] 場所 MeGUI.core.util.DragDropUtil.<>c__DisplayClass2_0.<RegisterSingleFileDragDrop>b__1(Object sender, DragEventArgs e)
---[NoImage] 場所 System.Windows.Forms.Control.OnDragDrop(DragEventArgs drgevent)
---[NoImage] 場所 System.Windows.Forms.Control.System.Windows.Forms.IDropTarget.OnDragDrop(DragEventArgs drgEvent)
---[NoImage] 場所 System.Windows.Forms.DropTarget.System.Windows.Forms.UnsafeNativeMethods.IOleDropTarget.OleDrop(Object pDataObj, Int32 grfKeyState, POINTSTRUCT pt, Int32& pdwEffect)
---[NoImage] 場所 System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
---[NoImage] 場所 System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
---[NoImage] 場所 System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
---[NoImage] 場所 System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
---[NoImage] 場所 System.Windows.Forms.Application.Run(Form mainForm)
---[NoImage] 場所 MeGUI.MainForm.Main(String[] args)
--[Information] [2017/05/09 4:21:51] sessions open: 0, id: 230854, close: True
---[NoImage] 場所 System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
---[NoImage] 場所 System.Environment.get_StackTrace()
---[NoImage] 場所 MeGUI.AviSynthClip.HandleAviSynthWrapperDLL(Boolean bUnload, String script)
---[NoImage] 場所 MeGUI.AviSynthClip.Dispose(Boolean disposing)
---[NoImage] 場所 MeGUI.AviSynthClip..ctor(String func, String arg, AviSynthColorspace forceColorspace)
---[NoImage] 場所 MeGUI.AviSynthScriptEnvironment.OpenScriptFile(String filePath, AviSynthColorspace forceColorspace)
---[NoImage] 場所 MeGUI.AvsFile..ctor(String script, Boolean parse)
---[NoImage] 場所 MeGUI.AvsFile.OpenScriptFile(String fileName)
---[NoImage] 場所 MeGUI.MainForm.openFile(String file, MediaInfoFile& iFile)
---[NoImage] 場所 MeGUI.VideoEncodingComponent.videoInput_FileSelected(FileBar sender, FileBarEventArgs args)
---[NoImage] 場所 MeGUI.FileBar.triggerEvent()
---[NoImage] 場所 MeGUI.FileBar.setFilename(String filename)
---[NoImage] 場所 MeGUI.core.util.DragDropUtil.<>c__DisplayClass2_0.<RegisterSingleFileDragDrop>b__1(Object sender, DragEventArgs e)
---[NoImage] 場所 System.Windows.Forms.Control.OnDragDrop(DragEventArgs drgevent)
---[NoImage] 場所 System.Windows.Forms.Control.System.Windows.Forms.IDropTarget.OnDragDrop(DragEventArgs drgEvent)
---[NoImage] 場所 System.Windows.Forms.DropTarget.System.Windows.Forms.UnsafeNativeMethods.IOleDropTarget.OleDrop(Object pDataObj, Int32 grfKeyState, POINTSTRUCT pt, Int32& pdwEffect)
---[NoImage] 場所 System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
---[NoImage] 場所 System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
---[NoImage] 場所 System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
---[NoImage] 場所 System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
---[NoImage] 場所 System.Windows.Forms.Application.Run(Form mainForm)
---[NoImage] 場所 MeGUI.MainForm.Main(String[] args)
-[Error] MediaInfo
--[Error] [2017/05/09 4:21:50] Error parsing media file F:\DVD_VOLUME\VIDEO_TS\New AviSynth Script.avs
---[NoImage] System exception - Access Violation
---[NoImage] (F:\DVD_VOLUME\VIDEO_TS\New AviSynth Script.avs, line 1)

[Zathor]

So it does crash there as well? Then it is an incompatibility outside of MeGUI which I cannot influence. Interestingly it does crash for you, while it does not crash for me.

[sumirecccp]

>>Zathor
let other people to test it too. I have no ploblem with "always use included avisynth" unchecked, but will crash when it is checked.

[Morku]

MeGUI x64 always wants to reinstalling DGIndexIM. Why is that so?
MeGUI x86 is not affected.

[hello_hello]

If you (incl. sumirecccp) tell me which X does not work or is missing I will check it.

Maybe we were talking about different X buttons.
Are these ones supposed to do something? They don't seem to clear anything for me. Same in AutoEncode. I think the X button in the audio section in the main window works.

https://s27.postimg.org/9zq4gnl5v/Onc_Click.gif

[LigH]

I never used the OCE ... but maybe they are used to remove accidently added streams? So they only work when you clicked the '+' tab at least once? I don't have any material here right now...

[Zathor]

I never used the OCE ... but maybe they are used to remove accidently added streams? So they only work when you clicked the '+' tab at least once? I don't have any material here right now...
They have been used to clean the "name" information in ancient times. I have them now removed in OneClick + the Muxers as they are useless.

Thanks to Morku + hello_hello:
2637 [Muxer] + [OneClick] removed unnecessary "X" buttons
2636 [Update] x64: fixed detection of the DGIndexIM package

Btw.. hello_hello, did you had time to test the "test" build?

[hello_hello]

Btw.. hello_hello, did you had time to test the "test" build?

No, sorry, I've been visiting the real world, but I'll switch over to it now and report back with any exciting discoveries.

Cheers.

[Zathor]

No, sorry, I've been visiting the real world, but I'll switch over to it now and report back with any exciting discoveries.
Hope you enjoyed the real world. Take your time!

[dissory]

I've been using MeGUI and found the one-click profile really helpful. One thing I noticed was that when transcoding audio e.g. FLAC -> AAC within video files, it doesn't retain attributes such as audio title name or language in the new video file with the transcoded audio. I'm not sure if the same happens with video but it does with audio.

Is it possible to make it so the attributes/metadata of the original audio stream are also transferred to the transcoded stream?

[Zathor]

Could you upload a sample file please?

[hello_hello]

Zathor,
I've briefly played around with the test version of MeGUI 2737 you linked to.
So far it's been behaving itself in respect to locking files..... naturally.... but the new Worker setup (which I'm still trying to get my head around) appears to have broken the right click "run in new temporary worker" option, which is killing me, and a little request while you're at it if I may.....

When right clicking on a job in the queue, each right click options effect only the selected job(s), aside from Abort. It aborts all running jobs which has caught me out a few times because it's inconsistent behaviour and I've clicked through the prompt without thinking. I think the same applies to the buttons at the bottom of the queue window.

I'll keep playing, eagerly awaiting the addition of a "pause" button for encoding in the next update. ;)

Cheers.

[Zathor]

So far it's been behaving itself in respect to locking files..... naturally.... but the new Worker setup (which I'm still trying to get my head around) appears to have broken the right click "run in new temporary worker" option, which is killing me, and a little request while you're at it if I may.....

Thanks for the feedback. The "temporary worker" issue is unintentional - I will have a look tomorrow and (hopefully) fix it.

When right clicking on a job in the queue, each right click options effect only the selected job(s), aside from Abort. It aborts all running jobs which has caught me out a few times because it's inconsistent behaviour and I've clicked through the prompt without thinking. I think the same applies to the buttons at the bottom of the queue window.

I'll keep playing, eagerly awaiting the addition of a "pause" button for encoding in the next update. ;)

Yes, I will have a look as well at the abort button. The confusion may be that abort is intended for the worker and the others for jobs. But as mentioned, I will check it.

Pause is a different story.

[StainlessS]

awaiting the addition of a "pause" button for encoding in the next update. ;)

Pause is a different story.

+1 on the Pause button (many moons been wantin' that) , but, how you gonna pause eg x264.exe ?,

On Sinclair QL (circa 1984/85) a task could be indefinitely suspended, perhaps Windows has not yet reached that maturity.

EDIT: QL Rom, ~24->26KB[EDIT: Maybe 28KB], totally preemptive multitasking OS, with builtin Pascal like, Super Basic lang, and rudimentary
windowing system, totally written by one man, ie Tony Tebby, Sinclair's head engineer at the time (Later left Sinclair and started QJump software).

[dissory]

Could you upload a sample file please?

The files I have are somewhat large so it will take me quite long to upload.

Is it possible the input and transcoded output file mediainfos will help you?

[Zathor]

The files I have are somewhat large so it will take me quite long to upload.

Is it possible the input and transcoded output file mediainfos will help you?

Let us try it.

[Zathor]

So far it's been behaving itself in respect to locking files..... naturally.... but the new Worker setup (which I'm still trying to get my head around) appears to have broken the right click "run in new temporary worker" option, which is killing me, and a little request while you're at it if I may.....
I had now the chance to test it myself. Temporary Workers still work as long as the rule set is fullfiled. I assume you want to overrule the rule set with temporary workers?

[hello_hello]

Zathor,
I don't know it it's my XP PC or not but if you'd care to look.....

Today I was opening a bunch of files in succession with the file indexer, pasting the same text into the script creator, and occasionally clicking the preview button before saving the script and adding it to the queue. I was indexing the jobs five at a time (in succession, so the result was five instances of the script creator open with a preview), pasting the desired text into each, clicking save to close and add to the queue, then indexing the next five. They were low resolution sources. I did that for 20 or so source files until MeGUI clapped out with an error message saying ffms2 couldn't be loaded due to lack of memory when I tried to index.

From there it'd do very little. It threw an out of memory error when I tried to save the log file and when I shut it down so it didn't write a log that was even remotely useful, but I did manage to manually copy a slab of entries from the "Avisynth" section and I checked a bunch of the previously opened source files and they were mostly locked. The Avisynth entries in the log specifying "closed" were few and far between (I should have taken a screenshot of that too). The part of the log file I copied doesn't seem to contain any.

If nothing seems obvious I wouldn't stress too much. This PC's overdue for a reformat. I could probably even use a downgrade to Windows 7 while I'm at it, but in case it's an obvious bug and fixable....

The zip file just includes the section of log file I managed to salvage and a screenshot. http://www.filedropper.com/meguilog

[Zathor]

New test build uploaded.
- temporary workers ignore now the worker rule set
- jobs can be suspended (and then resumed :))

The suspend feature is a "quicky". While it does seem to work - I have tested audio & video encodings - any kind of deeper test or polishing is missing. E.g. currently it is only available from within the progress window. However any kind of feedback is appreciated!

[hello_hello]

I had now the chance to test it myself. Temporary Workers still work as long as the rule set is fullfiled. I assume you want to overrule the rule set with temporary workers?

Yeah. I'm just used to being able to switch to the job queue and right click to run a job regardless of the worker situation and what's already running. It'd be good if temporary workers continued to work independently of the normal workers, but maybe I just need to understand the new setup better. I right clicked as usual to see a "no jobs waiting" message (or something along those lines) instead of the job in question just running as it normally would, especially as I was just trying to run an analysis pass (to find a hybrid NTSC source) while an encode was running.

So the maximum parallel jobs for a particular type/worker (one that's running) limits the temporary worker's ability to run new jobs?
I haven't played with it much yet but what if I have a worker configured for 2 parallel encoding jobs. Is there any way to only run one using that worker so I can then run a second encoding job in a temporary worker at my leisure, or will I need to create another worker?

[Zathor]

Today I was opening a bunch of files in succession with the file indexer, pasting the same text into the script creator, and occasionally clicking the preview button before saving the script and adding it to the queue. I was indexing the jobs five at a time (in succession, so the result was five instances of the script creator open with a preview), pasting the desired text into each, clicking save to close and add to the queue, then indexing the next five. They were low resolution sources. I did that for 20 or so source files until MeGUI clapped out with an error message saying ffms2 couldn't be loaded due to lack of memory when I tried to index.
Based on the screenshot you really run out of memory. However based on the log - if the last entry is the recent one - no avisynth thread was open at that time as the number of sessions was 0. It may be a memory leak in one of the avisynth plugins (e.g. ffms2). You can try to open again a number of avisynth threads and watch nearby the memory usage. When you close an avisynth thread the memory should go down again.

[Zathor]

So the maximum parallel jobs for a particular type/worker (one that's running) limits the temporary worker's ability to run new jobs?
I haven't played with it much yet but what if I have a worker configured for 2 parallel encoding jobs. Is there any way to only run one using that worker so I can then run a second encoding job in a temporary worker at my leisure, or will I need to create another worker?
No, as written above this was a not desired feature (or bug) and a new build is already available where you can start as many temporary worker as you would like ignoring the automatic worker rules.

[hello_hello]

The suspend feature is a "quicky". While it does seem to work - I have tested audio & video encodings - any kind of deeper test or polishing is missing. E.g. currently it is only available from within the progress window. However any kind of feedback is appreciated!

I'll have to play with that one a bit later but personally the only type of job I'm particularly interested in pausing is a video encoding one. The rest aren't usually CPU intensive or time consuming enough that it's an issue to wait until they finish in order to do something else.

[hello_hello]

Based on the screenshot you really run out of memory. However based on the log - if the last entry is the recent one - no avisynth thread was open at that time as the number of sessions was 0.

Yeah, I shut the two open instances of the script creator down before taking the screen shot to see if I'd get any memory back.
Any hints in that log file regarding locked source files?

It may be a memory leak in one of the avisynth plugins (e.g. ffms2). You can try to open again a number of avisynth threads and watch nearby the memory usage. When you close an avisynth thread the memory should go down again.

I'll give it a try, although that'll probably be a job for tomorrow so I can get something achieved today.

Cheers.

[Zathor]

Any hints in that log file regarding locked source files?
Sadly not

[hello_hello]

Based on the screenshot you really run out of memory. However based on the log - if the last entry is the recent one - no avisynth thread was open at that time as the number of sessions was 0. It may be a memory leak in one of the avisynth plugins (e.g. ffms2). You can try to open again a number of avisynth threads and watch nearby the memory usage. When you close an avisynth thread the memory should go down again.

I've saved the log file to date and I'm running some encodes but would this be normal? Seems the trick might be to not add too many jobs in succession before starting an encode so I can have some memory back.

After indexing the first file (ffms2) and adding the job to the queue.

https://s2.postimg.org/ezoygquc9/memory1.gif

After indexing and adding the sixth job:

https://s2.postimg.org/9pjzpga3d/memory2.gif

Immediately after starting encoding by right clicking on the last added job and selecting "run in temporary worker"

https://s2.postimg.org/dafv8oemx/memory3.gif

After MeGUI has added a job to the queue does the source file normally remain locked? I don't recall that being the case but the reason for the steps above was also to see if the files will be unlocked when encoding is done.... in an hour or so.... as according to Unlocker MeGUI has locked each one several times.

https://s2.postimg.org/k9tx81el5/unlocker.gif

I'll report back....

[hello_hello]

Here's a full log file Zather, http://www.filedropper.com/meguilogs
after having encoded the sixth file I added to the queue in my previous memory tests. After encoding finished, I checked that file with with Unlocker:

https://s16.postimg.org/bgy2qg3c5/Unlocker.gif

If the log file doesn't tell you anything, I'll just keep giving Unlocker a workout.

PS. I had intended to index each job, save the script, then add it to the queue for encoding before moving onto the next one, but I forgot to add the first two scripts to the queue until I'd indexed the third source file because I was busy watching memory usage, if that helps clarify the order I did things.

Thanks for all the hard work!

[hello_hello]

Zathor, I had a quick play with the new "suspend" function..... WhoooooHooooo!!!

A couple of thoughts, although you've probably thought them already....
The clock should stop and the fps guesstimate should do likewise.

Actually I'd like to see the fps guestimate far more responsive to changes in encoding speed. Currently if encoding speed was to drop by 50% it'd take minutes to be reflected in the progress window, but anyway....

WhoooooHooooo!!! Thanks Zathor!

[rhaz]

Both latest builds from dev server of MeGUI x32 and x64 crash when applying m2PA=true to your avs script and hitting Preview. MeGUI eats 100% CPU until it crashes.

Most basic scripts e.g.

LoadPlugin("ffms2.dll")
FFVideoSource("video.mkv", cachefile="video.ffindex", fpsnum=30000, fpsden=1001)
LoadPlugin("TIVTC.dll")
tdecimate(mode=2, rate=25, m2PA=true)

How do I fix/debug this?

[Zathor]

Please post the "versions" part of the log. Also try to run that AVS e.g. in VirtualDub (if you have AviSynth installed)

[rhaz]

Please post the "versions" part of the log. Also try to run that AVS e.g. in VirtualDub (if you have AviSynth installed)


You're right, Vdub also crash. So what's going on? How do I apply m2PA=true?

[Zathor]

Are you using the new TIVTC from the recent avisynth_plugins pack of MeGUI = 1.0.8? If yes there may be the chance that printerf can fix it. Please post your problem here:
https://forum.doom9.org/showthread.php?t=82264&page=66
or send him a PM.

[Groucho2004]

You're right, Vdub also crash. So what's going on? How do I apply m2PA=true?
Define crash. Is there an error message? Have you read the documentation for m2PA? Here:
m2PA -

Will override the default read-ahead maximum of 100 for mode 2. This will allow the
one pass mode (metrics not available from an input file) to produce the same results
as if the metrics were available.

**NOTE: the cycle size could very well be in the 1000's or 10000's, so there is the
possibility setting m2PA=true could mean the processing will stall for quite
some time (5-10 minutes or more) when a new cycle starts!!! Please check the
largest cycle size that will be used using debug=true before setting m2PA=true!

true = override the default maximum
false = don't

Default: false (bool)


Run the script with AVSMeter and check memory usage.

[hello_hello]

You're right, Vdub also crash. So what's going on? How do I apply m2PA=true?

Is it crashing or just appearing to freeze because it's taking a long time to open? When m2PA=true it can take a while to open, and each time it reaches the end of a particular cycle everything will come to a halt again until it's analysed the next one.
You could swap TIVTC.dll for the old and well tested version to see what happens (assuming your MeGUI setup is using the far more recent version 1.06 or 1.08). http://avisynth.nl/index.php/TIVTC

Probably best not to apply m2PA=true though. Use a metrics file instead. It's easy enough.

LoadPlugin("ffms2.dll")
FFVideoSource("video.mkv", cachefile="video.ffindex", fpsnum=30000, fpsden=1001)
LoadPlugin("TIVTC.dll")
tdecimate(mode=4, Output="D:\some file.txt")

Create something like the above script and add it to the job queue using the "Queue Analysis Pass" button. Run it and the metrics file will be created. An analysis pass is pretty quick. Probably not any slower than using m2PA=true without a metrics file but usually more convenient.

Then modify the above script to the following and add it to the job queue for encoding:

LoadPlugin("ffms2.dll")
FFVideoSource("video.mkv", cachefile="video.ffindex", fpsnum=30000, fpsden=1001)
LoadPlugin("TIVTC.dll")
tdecimate(mode=2, rate=25, Input="D:\some file.txt")

When you add the analyses job/script to the queue, MeGUI checks it and an incomplete metrics file will be created. It'll be over-written when the analyses pass is run, but when that's completed, be careful not to load or preview the analyses script again or the metrics file will be be over-written with an incomplete version when MeGUI checks the script and you'll need to run the analysis pass again.

As a side note, if the source is 29.970fps as your script indicates, it more likely that you'd want to decimate it to 23.976fps. I'm not saying that's definitely the case, just that it's more common.

[j8ee]

Does anybody else see the x265 encoder running under normal priority (8) even though priority is set to low in the status window, and avs4x26x.exe is running with low (4) priority? It's hard to see, but looking in process explorer it might be that avs4x26x is started in normal/8, but then switches to 4 just after x265 is started. Using MeGUI 2637.

edit: Feature request - it would be good if the file indexer could handle filenames that include the pgc number when extracted with dvdencrypter. Not often needed, but it would be convenient.

[dissory]

One example (where 'Title' property of audio streams are not transferred to the transcoded output file):

[Zathor]

One example (where 'Title' property of audio streams are not transferred to the transcoded output file):

Thanks, it is fixed in 2638 (not online yet).

Does anybody else see the x265 encoder running under normal priority (8) even though priority is set to low in the status window, and avs4x26x.exe is running with low (4) priority? It's hard to see, but looking in process explorer it might be that avs4x26x is started in normal/8, but then switches to 4 just after x265 is started. Using MeGUI 2637.
Which build are you using? This should have changed in 2627.

Feature request - it would be good if the file indexer could handle filenames that include the pgc number when extracted with dvdencrypter. Not often needed, but it would be convenient.
More details please :)

[j8ee]

/.../


Which build are you using? This should have changed in 2627.


More details please :)

Using build 2637.

When extracting in ifo mode with dvddecrypter, normally the files look like:
VTS_01_0.IFO ; VTS_01_1.VOB ; VTS_01 - Chapter Information - OGG.txt ; VTS_01 - Stream Information.txt

When pgc numbers are included, the files are:
VTS_01_0.IFO ; VTS_01_PGC_01_1.VOB ; VTS_01_PGC_01 - Chapter Information - OGG.txt ; VTS_01_PGC_01 - Stream Information.txt

and when trying to use the file indexer on files ripped with pgc numbers included, opening VTS_01_0.IFO the file indexer can't find the VTS_01_PGC_01_1.VOB file.

[Zathor]

Using build 2637.

Then please in more details what you see when and how the default priority is configured (low?).

Because for me it does work. I have default priority to low, all processes start with low. If I then switch in the progress window to normal all 3 processes switch to normal.

Maybe it helps when you post your log (versions part).

[j8ee]

[Information] Versions
-[Information] [2017-05-13 19:22:27] MeGUI: 2737
-[Information] [2017-05-13 19:22:27] Operating System: Windows 10 Home x64 (10.0.0.14393)
-[Information] [2017-05-13 19:22:27] .NET Framework: 4.0 (4.0.0.0)
-[Information] [2017-05-13 19:22:27] .NET Framework: 4.6.x (4.6.01586)
-[Information] [2017-05-13 19:22:27] Haali Media Splitter: 1.13.138.14 (14-04-2013)
-[Information] [2017-05-13 19:22:27] Haali DSS2: (14-04-2013)
-[Information] [2017-05-13 19:22:27] ICSharpCode.SharpZipLib: 0.85.5.452 (07-08-2008)
-[Information] [2017-05-13 19:22:27] MediaInfo: 0.7.95.0 (04-05-2017)
-[Information] [2017-05-13 19:22:27] MediaInfoWrapper: 0.7.61.0 (06-01-2013)
-[Information] [2017-05-13 19:22:27] MessageBoxExLib: 1.0.2218.28317 (19-12-2008)
-[Information] [2017-05-13 19:22:27] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
-[Information] [2017-05-13 19:22:27] 7z: 9.20 (18-11-2010)
-[Information] AviSynth Wrapper
--[Information] [2017-05-13 19:22:27] Version: 1.0.2721.0
--[Information] [2017-05-13 19:22:27] Date: 29-04-2017
--[Information] [2017-05-13 19:22:27] Interface: 3
-[Information] AviSynth
--[Information] [2017-05-13 19:22:27] not installed
-[Information] AviSynth portable
--[Information] [2017-05-13 19:22:27] File Version: 0.1
--[Information] [2017-05-13 19:22:27] Date: 16-03-2017
--[Information] [2017-05-13 19:22:27] Name: AviSynth+ 0.1 (r2455, MT, i386)
--[Information] [2017-05-13 19:22:30] Version: AviSynth+ 0.1 (r2455, MT, i386)
--[Information] [2017-05-13 19:22:30] AviSynth+: true
--[Information] [2017-05-13 19:22:30] MT: true
--[Information] [2017-05-13 19:22:30] Status: active

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

Sorry, it was build 2737 apparently. I looked around for the version number and the changelog listed 2637 at the top, so I thought it was that. (And now, exactly _now_ I see that the version number is visible in the window title...)

The conhost process have always been priority 4 before when I have looked, don't know why that is different now on the screenshot - weird. When starting a separate encode in a temperary worker, avs4x26x runs in 4, conhost 4, and x265 in 8.

The processes all change priority immediately and to the intended value when switching in the drop down menu. For how long have that setting changed the priority instantly? Surely it hasn't "always" been like that? I haven't touched the priority setting after the latest upgrade anyway, probably not at all for several months, but I'm sure the encoders have been running at low all the time before.

[Zathor]

SInce 2727 also child processes will change the priority. however for me also the first job startup is already correct.

[LouieChuckyMerry]

Zathor: :thanks:

[olmicx]

Hello
How can i add this settings? I using Megui 2525. Can you help me please?
aq=3:0.80 / aq-sensitivity=10.00 / aq-factor=1.00:1.00:1.00 / aq2=0 / aq3=0

[sneaker_ger]

Those options are not part of the vanilla x264 that comes with MeGUI. Probably something like (outdated?) x264 tMod (https://astrataro.wordpress.com/category/encode/x264/x264-bin/) was used. You need to replace x264, not let MeGUI overwrite it and manually set those custom command-line options.

[LigH]

1) Why use an outdated MeGUI version? Switch the update server to "development" to get the most current.

2) Which encoder do these options belong to? Neither x264 nor x265, as far as I read in their documentation (at least unmodified versions).

[olmicx]

1) Why use an outdated MeGUI version? Switch the update server to "development" to get the most current.

2) Which encoder do these options belong to? Neither x264 nor x265, as far as I read in their documentation (at least unmodified versions).

1) Upgraded 2715

2) Some of the groups (TayTO, EDP, WiKi, EPiC) using this settings on their movie sharings. Because of that i want to test this settings. If there is good effects on quality i am going to use this settings too

[hello_hello]

Hello
How can i add this settings? I using Megui 2525. Can you help me please?
aq=3:0.80 / aq-sensitivity=10.00 / aq-factor=1.00:1.00:1.00 / aq2=0 / aq3=0

AQ mode 3 was added to the vanilla x264 years ago https://mailman.videolan.org/pipermail/x264-devel/2014-December/010949.html
but it seems to have been somewhat ignored. It's never been added to MeGUI's encoder configuration. You can only select Adaptive Quantiser Mode - Disabled (0), Variance AQ (1) or Auto-Variance AQ (2).

aq=3:0.80 should be easy enough to achieve by adding --aq-mode 3 to the custom command line section of the encoder configuration and setting Adaptive Quantiser Strength to 0.8 under the rate control tab. When you'd want to do either, I'm not sure, but that's how you'd do it.

I agree the rest of the settings are specific to an old, modded version of x264. https://forum.doom9.org/showthread.php?t=170599
They're not settings the vanilla x264 writes. If they're still relevant they're obviously not user-adjustable.

[tebasuna51]

1) Upgraded 2715

2) Some of the groups (TayTO, EDP, WiKi, EPiC) using this settings on their movie sharings. Because of that i want to test this settings. If there is good effects on quality i am going to use this settings too

The current MeGUI version is 2737 and x264 r2744 (Komisar).

You can test aq=3:0.80, like hello_hello say:
--aq-mode 3 --aq-strength 0.8

but, AFAIK, than:
/ aq-sensitivity=10.00 / aq-factor=1.00:1.00:1.00 / aq2=0 / aq3=0

aren't supported by x264 r2744 (Komisar), you need replace it.

[olmicx]

The current MeGUI version is 2737 and x264 r2744 (Komisar).

You can test aq=3:0.80, like hello_hello say:
--aq-mode 3 --aq-strength 0.8

but, AFAIK, than:
/ aq-sensitivity=10.00 / aq-factor=1.00:1.00:1.00 / aq2=0 / aq3=0

aren't supported by x264 r2744 (Komisar), you need replace it.

This groups used x264 core 148 r2705+54 9f484c1 t_mod_Custom [8-bit@all X86_64]
Where can i download this x264 version?