Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Video Encoding > MPEG-4 Encoder GUIs

Reply
 
Thread Tools Search this Thread Display Modes
Old 14th June 2018, 10:37   #6261  |  Link
StainlessS
HeartlessS Usurer
 
StainlessS's Avatar
 
Join Date: Dec 2009
Location: Over the rainbow
Posts: 5,792
Quote:
Originally Posted by Zathor View Post
I tried to reproduce that but failed. Could you please describe in more detail how do you get it to crash?
Well, the scripts I use often have a long (a couple of seconds) scan where auto border cropping & auto contrast scanning is done (scans about 40 frames from clip, evenly spread thoughout clip duration, and then the crop/contrast is set.
MeGUI does its own multiple scans of the script during both load and then again when clicking on AutoEncode. So for each of the MeGUI scans, the script does its own scan (occurs at script start up), so MeGUI may be busy for about 10 seconds after script load, and it is during this time that the preview window pops up.
There seems to have been some recent (within about 2 or 3 months) mod to MeGUI source that displays the preview window before the MeGUI multiple scans of script starts, and as the batcher clicks the ALT\F4 close button as soon as the preview window pops up, so when MeGUI blits the graphic to the window, it has already been closed, Bang, Crash Wallop.

Before the problem arose, the window would only show up after MeGUI multiple scans had completed, and so the batcher would not close the window, because it was not there.

That is how it seems to me.

EDIT: Above is not an XP issue, it will occur on any OS (if a batcher is used, or the user is super quick at closing the window, I have not as yet managed to be quick enough to click it manually fast enough to crash it).
__________________
I sometimes post sober.
StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace

"Some infinities are bigger than other infinities", but how many of them are infinitely bigger ???

Last edited by StainlessS; 14th June 2018 at 10:41.
StainlessS is online now   Reply With Quote
Old 14th June 2018, 11:46   #6262  |  Link
hello_hello
Registered User
 
Join Date: Mar 2011
Posts: 3,634
StainlessS,
out of curiosity, do you have any problems with Avisynth plugins causing MeGUI to crash on XP?

If dither.dll or avspt.dll 1.27.2 are used in a script MeGUI always crashes when closing the preview, while version 1.27.1 is fine. MAA2() also does the same, although I haven't bothered trying to work out which plugin is to blame as I rarely use it.

I'm curious if that's peculiar to my XP installation.

Cheers.
hello_hello is offline   Reply With Quote
Old 14th June 2018, 22:01   #6263  |  Link
LouieChuckyMerry
Registered User
 
LouieChuckyMerry's Avatar
 
Join Date: Feb 2014
Posts: 230
Quote:
Originally Posted by Zathor View Post
Could you upload please both logs? (versions part is sufficient)
Long story short, I've been switching between a portable MeGUI, Version 2855, that still works correctly with SEt's MT AviSynth 2.6.0.5 and then updating that to Version 2860 to try and sort out why AviSynth+ doesn't work (then deleting this entire folder and replacing it with the Version 2855 that works when I've something to encode). What I typed in post #6243 was copied-and-pasted from the log (the fact that AviSynth+ was true), but now I can't repeat it . The last updating of Version 2855 to Version 2860, then ticking "Log debug information", then restarting now shows [Information] AviSynth+: false. I don't know why. Also, when it stated true I could load my scripts that worked with SEt's MT and they would run but output the acid flashback stacked video with extremely high bit rate and extremely low FPS. Now, I can't even load a SEt script, MeGUI simply crashes. Here's the crash log:

Quote:
Preliminary log file only. During closing of MeGUI the well formed log file will be written.

-[Information] Versions
--[Information] MeGUI: 2860 x86
--[Information] Update Check: development update server
-[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] 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++ 2017 x86: 14.14.26429
-[Information] Redistributables
-[Information] DPI: 100% (96/96)
-[Information] Resolution: 1600x900
-[Information] Primary Screen: True
-[Information] Monitor 1
--[Information] System Information
-[Information] Update detection
-[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] Component Information
--[Information] [14 Jun 18 16:55:30] Using cached update config and server: http://megui.org/auto/
-[Information] Version: 1.0.2847.0
-[Information] Date: 06-05-2018
-[Information] Interface: 3
-[Information] AviSynth Wrapper
--[Information] [14 Jun 18 16:55:30] No package requires an update
-[Information] File Version: 2.6.0.5
-[Information] File Date: 20-02-2015
-[Information] File Name: Avisynth 2.6
-[Information] File Path: c:\windows\system32\avisynth.dll
-[Information] AviSynth Version: AviSynth 2.60, build:Feb 20 2015 [03:16:45]
-[Information] AviSynth+: false
-[Information] AviSynth MT: true
-[Information] AviSynth
--[Information] AviSynth Information
-[Information] MediaInfoWrapper
--[Information] [14 Jun 18 16:55:38] sessions open: 1, id: 109528: File: File: D:\Temp\[0000]ReEncTemp\[1080p]Zoolander2[S]{2016}[1080p]\ReEncZoo[1,100]-TrimTest.avs
-[Information] AviSynthWrapper
--[Information] [14 Jun 18 16:55:38] sessions open: 1, id: 106226: D:\Temp\[0000]ReEncTemp\[1080p]Zoolander2[S]{2016}[1080p]\ReEncZoo[1,100]-TrimTest.avs
LouieChuckyMerry is offline   Reply With Quote
Old 15th June 2018, 02:54   #6264  |  Link
Zathor
Registered User
 
Join Date: Nov 2009
Posts: 2,275
Quote:
Originally Posted by LouieChuckyMerry View Post
Long story short, I've been switching between a portable MeGUI, Version 2855, that still works correctly with SEt's MT AviSynth 2.6.0.5 and then updating that to Version 2860 to try and sort out why AviSynth+ doesn't work (then deleting this entire folder and replacing it with the Version 2855 that works when I've something to encode). What I typed in post #6243 was copied-and-pasted from the log (the fact that AviSynth+ was true), but now I can't repeat it . The last updating of Version 2855 to Version 2860, then ticking "Log debug information", then restarting now shows [Information] AviSynth+: false. I don't know why. Also, when it stated true I could load my scripts that worked with SEt's MT and they would run but output the acid flashback stacked video with extremely high bit rate and extremely low FPS. Now, I can't even load a SEt script, MeGUI simply crashes. Here's the crash log:
Do you have ticked the "always use the included avisynth" checkbox?
And when it crashes, what error message do you get?
Zathor is offline   Reply With Quote
Old 15th June 2018, 03:10   #6265  |  Link
Zathor
Registered User
 
Join Date: Nov 2009
Posts: 2,275
Quote:
Originally Posted by StainlessS View Post
Well, the scripts I use often have a long (a couple of seconds) scan where auto border cropping & auto contrast scanning is done (scans about 40 frames from clip, evenly spread thoughout clip duration, and then the crop/contrast is set.
MeGUI does its own multiple scans of the script during both load and then again when clicking on AutoEncode. So for each of the MeGUI scans, the script does its own scan (occurs at script start up), so MeGUI may be busy for about 10 seconds after script load, and it is during this time that the preview window pops up.
There seems to have been some recent (within about 2 or 3 months) mod to MeGUI source that displays the preview window before the MeGUI multiple scans of script starts, and as the batcher clicks the ALT\F4 close button as soon as the preview window pops up, so when MeGUI blits the graphic to the window, it has already been closed, Bang, Crash Wallop.

Before the problem arose, the window would only show up after MeGUI multiple scans had completed, and so the batcher would not close the window, because it was not there.

That is how it seems to me.

EDIT: Above is not an XP issue, it will occur on any OS (if a batcher is used, or the user is super quick at closing the window, I have not as yet managed to be quick enough to click it manually fast enough to crash it).
Again, I would need more details to be able to reproduce it. E.g. can you share the script? Is there an error in the log?
Zathor is offline   Reply With Quote
Old 15th June 2018, 12:27   #6266  |  Link
StainlessS
HeartlessS Usurer
 
StainlessS's Avatar
 
Join Date: Dec 2009
Location: Over the rainbow
Posts: 5,792
Quote:
E.g. can you share the script? Is there an error in the log?
Share Script, well not really, consists of maybe a dozen scripts, some quite significant in length, and a bucket load of plugins.
Error in the log, not concerning the error, just (from memory) a "MeGUI has crashed" style message box.

I was wrong, preview window does not show before MeGUI double scanning (based on below test script), but I seem to recall
that it does show the window borders with plain grey where graphic would be, and then crash before graphic blitted to the window.

I have not been able to reproduce the crash with a short test script, below, but if I put in a Sleep(10000) command ie sleep for 10 seconds
into the Batcher code, before close ALT/F4 close button then it does not crash.

Test script that failed to prompt the crash
Code:
Colorbars(Pixel_type="YV12").ShowFrameNumber.KillAudio
SAMPLES=2048    # Enought to have a longish timeout
FC=Framecount
Step=FrameCount/SAMPLES
RT_DebugF("Script Open Scan commence",name="Crash.avs: ")
#GScript("""
    z=0.0
    For(i=0,FC-1,Step) {    # Time Waster
        current_frame=i
        z=z+AverageLuma
    }
#""")
RT_DebugF("Scan complete, returning clip",name="Crash.avs: ")
Return Last
DebugView result
Code:
00000001    0.00000000  RemoveDirt 0.9                              # AutoLoaded plugins
00000002    1.12014675  SSETools 0.1
00000003    1.18845010  RT_DebugF: Init_ExternalPlugins
00000004    1.20852351  RT_DebugF: .\FFMS2000_CPP\ffms2.dll LOADED
00000005    1.23122072  Crash.avs: Script Open Scan commence
00000006    27.22969246 Crash.avs: Scan complete, returning clip    # End of scan 1 before Preview
00000007    27.60651970 RemoveDirt 0.9
00000008    28.72829628 SSETools 0.1
00000009    28.79436684 RT_DebugF: Init_ExternalPlugins
00000010    28.81436348 RT_DebugF: .\FFMS2000_CPP\ffms2.dll LOADED
00000011    28.83756065 Crash.avs: Script Open Scan commence
00000012    54.90752029 Crash.avs: Scan complete, returning clip    # End of scan 2 Preview shows after this (crashes after this usually)
00000013    57.81261444 RemoveDirt 0.9
00000014    58.93026733 SSETools 0.1
00000015    58.99621582 RT_DebugF: Init_ExternalPlugins
00000016    59.01642990 RT_DebugF: .\FFMS2000_CPP\ffms2.dll LOADED
00000017    59.03916550 Crash.avs: Script Open Scan commence
00000018    85.08772278 Crash.avs: Scan complete, returning clip    # End of AutoEncode scan
I shall try to find a fix within the Batcher, maybe try a 1 second delay, see if that works.

Anyway, sorry for bothering you, and nice work in reducing the MeGUI pre-scan count to 2 before Preview (was some time ago about 7),
and 1 scan for the AutoEncode (was about 5 I think).
EDIT: The crash seems to happen more often on a P4 3.0 GHz (with HyperThreading) than on my Quad Core Duo 2.4 GHz.

EDIT:
Quote:
Originally Posted by hello_hello View Post
StainlessS,
out of curiosity, do you have any problems with Avisynth plugins causing MeGUI to crash on XP?
Never had any problems with MeGUI and other dll's at all (although I dont usually use dither and the other dll which I'm not familiar with).
EDIT: I assume that your 'avspt.dll' should actually be 'avstp.dll', which I do have (but dont offhand know what it does, something to do with dither I think).
__________________
I sometimes post sober.
StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace

"Some infinities are bigger than other infinities", but how many of them are infinitely bigger ???

Last edited by StainlessS; 15th June 2018 at 12:41.
StainlessS is online now   Reply With Quote
Old 15th June 2018, 14:21   #6267  |  Link
hello_hello
Registered User
 
Join Date: Mar 2011
Posts: 3,634
Quote:
Originally Posted by StainlessS View Post
Never had any problems with MeGUI and other dll's at all (although I dont usually use dither and the other dll which I'm not familiar with).
EDIT: I assume that your 'avspt.dll' should actually be 'avstp.dll', which I do have (but dont offhand know what it does, something to do with dither I think).
Interesting. I just re-installed an old image of XP because the one I was using was nearly five years old and started blue-screening the other day, but the problem still exists. I might have to re-install XP from scratch to see what happens. Or just bite the bullet and download Linux Mint and never look back.

Yes, it should have been avstp.dll. It comes with the dither plugin. Something about internal plugin multi-threading, from memory.

Cheers.
hello_hello is offline   Reply With Quote
Old 15th June 2018, 14:57   #6268  |  Link
LouieChuckyMerry
Registered User
 
LouieChuckyMerry's Avatar
 
Join Date: Feb 2014
Posts: 230
Quote:
Originally Posted by Zathor View Post
Do you have ticked the "always use the included avisynth" checkbox?
D'oh! Good thing you're the developer, Zathor, and Happy Friday . Anyway, now that you've pointed out the obvious, here are the version logs you requested earlier, all from portable MeGUI on a RAMDisk, F:\.

NOTE: At first, after updating and ticking "Always use included AviSynth" then restarting, the log would still show ----[Information] AviSynth+: false. However, after a bit of checking, it turns out that ffmpeg wasn't updating because the package was disabled. Once I manually updated ffmpeg, from Version 3.4 to Version 4.0, and restarted the log shows ----[Information] AviSynth+: true. This is probably why there was an issue before, with the one time true but other time false, because I remember manually updating ffmpeg the first time but I didn't update it the second time.

First, Version 2855 working well with SEt's MT AviSynth:

Quote:
[Information] Log
-[Information] Versions
--[Information] MeGUI: 2855 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++ 2017 x86: 14.14.26429
---[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: active
---[Information] AviSynth portable
----[Information] File Version: 0.1
----[Information] Date: 28-03-2018
----[Information] Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] Status: inactive
-[Information] Update detection
--[Information] [15 Jun 18 09:18:34] Automatic update is disabled
--[Information] [15 Jun 18 09:18:34] Using cached update config and server: http://megui.tmebi.de/test/
--[Information] [15 Jun 18 09:18:34] There is 1 package which can be updated: MeGUI
Second, the previous version updated and with "Always use included AviSynth" ticked:

Quote:
[Warning] Log
-[Warning] Versions
--[Information] MeGUI: 2860 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++ 2017 x86: 14.14.26429
---[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)
--[Warning] 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] File Date: 20-02-2015
----[Information] File Name: Avisynth 2.6
----[Information] File Path: c:\windows\system32\avisynth.dll
----[Information] AviSynth Version: AviSynth 2.60, build:Feb 20 2015 [03:16:45]
----[Information] AviSynth+: false
----[Information] AviSynth MT: true
----[Information] AviSynth Status: active
---[Warning] AviSynth portable
----[Information] File Version: 0.1
----[Information] File Date: 28-03-2018
----[Information] File Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] File Path: f:\[0]standaloneapps\megui-2500(core)2443(data)0.3.5(libs)[portable]\avisynth.dll
----[Warning] AviSynth Status: inactive - portable AviSynth build cannot be used. The loaded DLL is: c:\windows\system32\avisynth.dll
-[Information] Update detection
--[Information] [15 Jun 18 09:31:42] Using cached update config and server: http://megui.org/auto/
--[Information] [15 Jun 18 09:31:43] No package requires an update
Finally, the previous but with "Log debug information" ticked, too:

Quote:
[Information] Log
-[Information] Versions
--[Information] MeGUI: 2860 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++ 2017 x86: 14.14.26429
---[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] File Date: 20-02-2015
----[Information] File Name: Avisynth 2.6
----[Information] File Path: c:\windows\system32\avisynth.dll
----[Information] AviSynth Version: AviSynth 2.60, build:Feb 20 2015 [03:16:45]
----[Information] AviSynth+: false
----[Information] AviSynth MT: true
----[Information] AviSynth Status: inactive
---[Information] AviSynth portable
----[Information] File Version: 0.1
----[Information] File Date: 28-03-2018
----[Information] File Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] File Path: f:\[0]standaloneapps\megui-2500(core)2443(data)0.3.5(libs)[portable]\avisynth.dll
----[Information] AviSynth Version: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] AviSynth+: true
----[Information] AviSynth MT: true
----[Information] AviSynth Status: active
-[Information] Update detection
--[Information] [15 Jun 18 09:38:28] Using cached update config and server: http://megui.org/auto/
--[Information] [15 Jun 18 09:38:28] No package requires an update
LouieChuckyMerry is offline   Reply With Quote
Old 15th June 2018, 15:50   #6269  |  Link
StainlessS
HeartlessS Usurer
 
StainlessS's Avatar
 
Join Date: Dec 2009
Location: Over the rainbow
Posts: 5,792
Quote:
Originally Posted by hello_hello View Post
I might have to re-install XP from scratch to see what happens. Or just bite the bullet and download Linux Mint and never look back.

Yes, it should have been avstp.dll. It comes with the dither plugin. Something about internal plugin multi-threading, from memory.
If you use WususOfflineUpdate, then be aware that M$ seems to have deliberately broken it a bit (for a new install of XPSP3).
So, if you have an old version of Wusus [EDIT: Offline Update], use that before trying to update with a newer one.
Otherwise it seems that you have to go through updates in date order and install manually (about a hundred or so), and then it will work ok.

Mint is pretty good, but I'm not sure, I may switch to Fedora (or LMDE).

Yep, I thought that plugin was something to do with multi-threading, now I know.
__________________
I sometimes post sober.
StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace

"Some infinities are bigger than other infinities", but how many of them are infinitely bigger ???

Last edited by StainlessS; 16th June 2018 at 10:09.
StainlessS is online now   Reply With Quote
Old 15th June 2018, 21:59   #6270  |  Link
manolito
Registered User
 
manolito's Avatar
 
Join Date: Sep 2003
Posts: 2,228
Quote:
Originally Posted by StainlessS View Post
If you use WususOfflineUpdate, then be aware that M$ seems to have deliberately broken it a bit (for a new install of XPSP3).
So, if you have an old version of Wusus, use that before trying to update with a newer one.
No, this time it is not Microsoft's fault. WSUSOffline( NOT Wusus) v. 9.21 is the very last version which can retrieve Win XP updates, it is still available at the author's website:
http://download.wsusoffline.net/wsusoffline921.zip

Just for fun I tested it again, and it still downloads all the latest WinXP updates from the Microsoft servers without errors.


Cheers
manolito
manolito is offline   Reply With Quote
Old 15th June 2018, 22:07   #6271  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 5,487
WSUS = Windows Server Update Services

If you have a workgroup or domain with Windows server(s), you can let it download update packages once or the local network, and set up workstation PCs to download their update packages from your local server instead of Microsoft servers.
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid

Last edited by LigH; 15th June 2018 at 22:10.
LigH is offline   Reply With Quote
Old 16th June 2018, 10:06   #6272  |  Link
StainlessS
HeartlessS Usurer
 
StainlessS's Avatar
 
Join Date: Dec 2009
Location: Over the rainbow
Posts: 5,792
Quote:
it still downloads all the latest WinXP updates from the Microsoft servers without errors.
Yes, but will get 'stuck' if trying to update a brand new XP32SP3 install.
One of the problems indicated below (I've experienced more than one prob)
Code:
2018-05-07	20:00:02:359	 832	12c	PT	+++++++++++  PT: Synchronizing server updates  +++++++++++
2018-05-07	20:00:02:359	 832	12c	PT	  + Offline serviceId = {8FFD129A-DD86-4A5D-933C-5F9985975929}
2018-05-07	20:00:02:359	 832	12c	PT	WARNING: Cached cookie has expired or new PID is available
2018-05-07	20:00:37:031	 832	12c	Agent	WARNING: Failed to evaluate Installed rule, updateId = {2190702A-4B98-4A80-90FF-0C6DB43C13CC}.200, hr = 8024E001
2018-05-07	20:01:30:515	 832	12c	PT	+++++++++++  PT: Synchronizing extended update info  +++++++++++
2018-05-07	20:01:30:515	 832	12c	PT	  + Offline serviceId = {8FFD129A-DD86-4A5D-933C-5F9985975929}
2018-05-07	20:01:30:515	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:640	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:640	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:640	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:640	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:640	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:640	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:640	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:640	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:656	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:703	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07	20:02:13:718	 832	12c	OfflSnc	WARNING: Failed to add file to the FileLocationList with 0x80240013
Goes on for hours like that before I quit, tried a number of things including updating the agent, I unfortunately did not keep the old version I had [EDIT: the complete download version from v9.2.1 from about 6 months ago].

EDIT:
Quote:
this time it is not Microsoft's fault. WSUSOffline( NOT Wusus) v. 9.21
Last version is actually v9.2.4 (which I have, the actual old file you need is I think the wsusscn2.cab file).
__________________
I sometimes post sober.
StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace

"Some infinities are bigger than other infinities", but how many of them are infinitely bigger ???

Last edited by StainlessS; 16th June 2018 at 10:19.
StainlessS is online now   Reply With Quote
Old 16th June 2018, 21:06   #6273  |  Link
manolito
Registered User
 
manolito's Avatar
 
Join Date: Sep 2003
Posts: 2,228
Quote:
Originally Posted by StainlessS View Post
Yes, but will get 'stuck' if trying to update a brand new XP32SP3 install.
Alright, I misunderstood your previous post, I thought you were saying that the download from the M$ servers was broken.

But I still believe that something must be wrong at your end, I spent some hours trying to reproduce your errors, but I couldn't, everything works just fine here.


This is what I did:

Dowloaded WSUSOfflineInstaller 9.24 (thanks for the hint), downloaded the updates and put the whole stuff on a USB stick.

Formatted the target partition (to FAT32)

Did a clean install of WinXP 32 SP3 Professional Corporate Edition. This installation CD had been slipstreamed to include SP3, but otherwise no tweaks like NLite or injecting SATA (AHCI) drvers.

Ran the UpdateInstaller from the previously created USB stick. Except for a few updates which were skipped because they were blacklisted all of the 134 updates were installed without issues, no errors like the ones you posted. (The small number of only 134 is because I deselected all the dotNet stuff.)

What does that mean?
Obviously your WinXP language is English while mine is German. I do not believe that this could make a difference.

What about your WinXP installation CD? Did you apply any fancy tweaks to it?


Whatever, at least for me the WSUSOffline app still works nicely for WinXP.


Cheers
manolito

Last edited by manolito; 17th June 2018 at 08:38.
manolito is offline   Reply With Quote
Old 17th June 2018, 14:46   #6274  |  Link
StainlessS
HeartlessS Usurer
 
StainlessS's Avatar
 
Join Date: Dec 2009
Location: Over the rainbow
Posts: 5,792
Was slipstreamed SP2, and then SP3, into standard setup disk (pro GOLD, ie SP0), (but with Internet Explorer 8.0 [no idea why, I dont use it at all]
and also WMP 11.0 [dont use that either], nothing else I think).
I also set up a load of stuff including Visual Studio 2008, before using WSUSOffline,
Thanks Mani, I'll give it another go with WSUS updates applied first.

EDIT: To Below,
I updated the XP downloaded updates again via W10 Home, and noticed an error message (only in console window, not logged to log file),
that some *.txt md5 hash files were giving an "Access Denied" error message.
So having noticed this, I decided to download the entire update set again (with 9.2.4 about 5GB for chosen stuff [XP32+64]), and re-tried
the XP targetting, (I install all DotNet, from 1.1, 2.0, 3.5 [includes v3.0] and 4.0), but NOT CPP files, no remote desktop, no
Silverlight, no updated certificate things. [EDIT: + Powershell 2.0]
Installed just fine, 159 updates in total. Still got the "Failed to add file" type errror messages in windowsUpdate.log (not the
WSusOfflineUpdate.log), but only 30 seconds worth, and did not really take any more time than it should have.
All hunky dory now, my downloads were just messing up due to MD5 hash stuff.

EDIT: I saw no indication to what file/files the "Failed to add file" stuff referred to.
__________________
I sometimes post sober.
StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace

"Some infinities are bigger than other infinities", but how many of them are infinitely bigger ???

Last edited by StainlessS; 23rd June 2018 at 21:05.
StainlessS is online now   Reply With Quote
Old 17th June 2018, 18:55   #6275  |  Link
manolito
Registered User
 
manolito's Avatar
 
Join Date: Sep 2003
Posts: 2,228
Did another test, this time "the works". Source CD was WinXP 32 SP3 Pro Corporate (SP3 slipstreamed into an earlier CD), and also injected the Intel IASTOR AHCI drivers. Of course the AHCI drivers were not used because my computer only has an IDE HDD interface, and the BIOS does not know a thing about SATA or AHCI.

For the update installation this time I selected everything except the WMP update. (dotNet, IE8, VC redist, DirectX) The dotNet stuff slowed down the update to a crawl (the whole dotNet update stuff is a major PITA IMO, whoever programmed this crap at Microsoft should be sent to a Singapore prison and receive at least 20 cane strokes on the bare).

But still, everything went well, all updates were installed without any error messages. So I feel that I am well prepared for a fresh install of WinXP...


Cheers
manolito

(Tomorrow it's off to Scotland, I won't post for the next 2 weeks...)
manolito is offline   Reply With Quote
Old 22nd June 2018, 21:22   #6276  |  Link
Zathor
Registered User
 
Join Date: Nov 2009
Posts: 2,275
Code:
2863 [AviSynth]             changed default value of "always use the included AviSynth" to enabled
                            unload avisynthwrapper during startup detection to ensure that the portable build is used if required
2862 [Xvid]                 improved workaround to be able to use Xvid in portable AviSynth mode
2861 [OneClick]             fixed an out of bounds error. bug #919
Zathor is offline   Reply With Quote
Old 23rd June 2018, 20:13   #6277  |  Link
Zathor
Registered User
 
Join Date: Nov 2009
Posts: 2,275
Quote:
Originally Posted by StainlessS View Post
The only problem I'm having is using MeGUI_AutoEncode_Batcher, which uses AutoIt code to add avs scripts to the Auto Encode queue.
Problem arises when Preview Window is opened (after avs script load) and the batcher clicks close Button (little x close alias ALT/F4).
Seems that the problem arises due to close button being clicked before MeGUI is ready, ie MeGUI is still doing its multiple scanning
of Avs script and has not as yet presented the clip graphic in the preview window, when close button is clicked it crashes MeGUI.
(the Batcher is un-affected).
That should be fixed with 2865:

Code:
2865 [AviSynth]             improved error handling
2864 [L-SMASH Indexer]      added high bit depth support
Zathor is offline   Reply With Quote
Old 23rd June 2018, 20:55   #6278  |  Link
StainlessS
HeartlessS Usurer
 
StainlessS's Avatar
 
Join Date: Dec 2009
Location: Over the rainbow
Posts: 5,792
Quote:
That should be fixed with 2865:
Thanx Z, much obliged, I'll give it a try soon. (I was testing some stuff to detect change from inital central dialog box average color, in any pixel,
or if some timeout occurred).

Manolito, added edit four posts earlier.
__________________
I sometimes post sober.
StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace

"Some infinities are bigger than other infinities", but how many of them are infinitely bigger ???

Last edited by StainlessS; 23rd June 2018 at 21:02.
StainlessS is online now   Reply With Quote
Old 24th June 2018, 11:36   #6279  |  Link
hello_hello
Registered User
 
Join Date: Mar 2011
Posts: 3,634
Quote:
Originally Posted by Zathor View Post
2863 [AviSynth] changed default value of "always use the included AviSynth" to enabled
unload avisynthwrapper during startup detection to ensure that the portable build is used if required
MeGUI (2865) doesn't always copy Avisynth.dll to the MeGUI folder when it's being told to use the included Avisynth.

When Avisynth.dll in the system32 folder is version 2.6, MeGUI does not copy Avisynth.dll to the MeGUI folder, and if I copy it there myself before starting MeGUI, it's removed when MeGUI starts.

Quote:
--[Warning] 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.6
----[Information] File Date: 31-03-2015
----[Information] File Name: Avisynth 2.6
----[Information] File Path: c:\windows\system32\avisynth.dll
----[Information] AviSynth Version: AviSynth 2.60, build:Mar 31 2015 [16:38:54]
----[Information] AviSynth+: false
----[Information] AviSynth MT: false
----[Information] AviSynth Status: active
---[Warning] AviSynth portable
----[Information] File Version: 0.1
----[Information] File Date: 28-03-2018
----[Information] File Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] File Path: c:\program files\megui\avisynth.dll
----[Warning] AviSynth Status: inactive - portable AviSynth build cannot be used. The loaded DLL is: c:\windows\system32\avisynth.dll
When I replace Avisynth.dll in the system32 folder with Avisynth+, MeGUI does copy Avisynth.dll to the MeGUI folder. I'm pretty sure it's actually using it, as when it's using the dll in the system32 folder the dll is normally locked and can't be deleted until I close MeGUI, but I can delete it.

Quote:
--[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: 0.1
----[Information] File Date: 28-03-2018
----[Information] File Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] File Path: c:\windows\system32\avisynth.dll
----[Information] AviSynth Version: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] AviSynth+: true
----[Information] AviSynth MT: true
----[Information] AviSynth Status: inactive
---[Information] AviSynth portable
----[Information] File Version: 0.1
----[Information] File Date: 28-03-2018
----[Information] File Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] File Path: c:\program files\megui\avisynth.dll
----[Information] AviSynth Version: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] AviSynth+: true
----[Information] AviSynth MT: true
----[Information] AviSynth Status: active
This time with Avisynth.dll removed from the system32 folder before starting MeGUI (Avisynth.dll is copied to the MeGUI folder and MeGUI can open scripts).

Quote:
---[Information] AviSynth
----[Information] AviSynth Status: not installed
---[Information] AviSynth portable
----[Information] File Version: 0.1
----[Information] File Date: 28-03-2018
----[Information] File Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] File Path: c:\program files\megui\avisynth.dll
----[Information] AviSynth Version: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] AviSynth+: true
----[Information] AviSynth MT: true
----[Information] AviSynth Status: active
Hopefully this isn't an XP-specific thing.

Cheers.
hello_hello is offline   Reply With Quote
Old 24th June 2018, 12:32   #6280  |  Link
Zathor
Registered User
 
Join Date: Nov 2009
Posts: 2,275
The fix in 2863 was intended for the issue LouieChuckyMerry had. He conformed that it was working when "show debug information" was enabled so I have enabled that now by default for that part. However I noticed that I changed it a bit and I do not know if it therefore still works as expected.

MeGUI calls AviSynth not directly (it uses avisynthwrapper.dll for that) but that does not change much. By default when searched for the AviSynth.dll it should open the one in the calling directory and then in the system directories (more details here: https://msdn.microsoft.com/en-us/lib...sktop/ms682586).

For you it seems that when the 2.6 from the system32 is loaded this is still used even when the avisynth.dll is now in the calling folder. But interestingly with AVS+ it seems to work.

The workaround implemented for LouieChuckyMerry did force an unload (and load) of avisynth.dll and avisynthwrapper.dll which seems to have fixed that for him.

If the wrong avs is used, could you please try to encode an avs file with version() inside e.g. with x264 to see which version is used there?
Zathor is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 02:23.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2018, vBulletin Solutions Inc.