odd change in behaviour after recent MS Windows update
Posted: Wed Jul 20, 2022 1:50 am
Hello. Thanks for your lovely tools, I use them every day in an automated process which uses vbscript.
After a recent MS update to Win10Pro x64, I noticed the VB script is now freezing at DGIndexNV so I took a look.
It seems that the recent windows update may have changed some behaviours, given it worked up until a couple of days ago (coincidentally around the same time I updated DGIndexNV to the 244 release).
1. (trivial) Perhaps I never noticed before, but this line in a DOS box produces this visible output (cut and pasted from the DOS box)
where the output from DGIndexNV is on the same line and after the next command prompt and the cursor is sitting at character 1 of the following blank line.
When I hit enter, nothing happens though, so it's not being treated as an input.
It just seems ... unusual, compared to everything else.
2. Also perhaps I never noticed before, but this line in a DOS box produces this visible output (again, cut and pasted straight from the DOS box)
You may notice
a) the 1st line of output is on the next line similar to (1) above
b) the second line of output follows on a line by itself with the cursor on the line after it, blinking away at character 1 looking like it's waiting for DGIndexBV to finish.
c) the text lines Project and 100 may not be strictly necessary from this CLI command; would it be possible for DGIndexNV to finish its work silently then exit when it's done ?
Suggestions welcomed.
Whilst I'm here, and this is now actually my issue with using DGIndexNV ...
With this code snippet from a vbscript function,
and a command string like
It used to exit the first Do While loop normally when DGIndexNV was finished, but now after the ms update it just loops forever.
Same thing happens given this command
I backed down DGIndexNV from v244 to v241 and same thing happens, which is why I attribute the issue to the recent MS windows update.
Like I said, it used to work up until the MS windows update a couple of days ago.
Now I'll have to find another way
Suggestions welcomed. I understand if you decline
After a recent MS update to Win10Pro x64, I noticed the VB script is now freezing at DGIndexNV so I took a look.
It seems that the recent windows update may have changed some behaviours, given it worked up until a couple of days ago (coincidentally around the same time I updated DGIndexNV to the 244 release).
1. (trivial) Perhaps I never noticed before, but this line in a DOS box produces this visible output (cut and pasted from the DOS box)
Code: Select all
G:\HDTV\TEST>"C:\SOFTWARE\Vapoursynth-x64\DGIndex\DGIndexNV.exe" -version
G:\HDTV\TEST>DGIndexNV 241.0.0.0 (64 bit)
When I hit enter, nothing happens though, so it's not being treated as an input.
It just seems ... unusual, compared to everything else.
2. Also perhaps I never noticed before, but this line in a DOS box produces this visible output (again, cut and pasted straight from the DOS box)
Code: Select all
G:\HDTV\TEST>"C:\SOFTWARE\Vapoursynth-x64\DGIndex\DGIndexNV.exe" -i "D:\VRDTVSP-SCRATCH\test_file.QSF.mp4" -e -h -o "D:\VRDTVSP-SCRATCH\test_file.QSF.dgi"
G:\HDTV\TEST>Project
100
a) the 1st line of output is on the next line similar to (1) above
b) the second line of output follows on a line by itself with the cursor on the line after it, blinking away at character 1 looking like it's waiting for DGIndexBV to finish.
c) the text lines Project and 100 may not be strictly necessary from this CLI command; would it be possible for DGIndexNV to finish its work silently then exit when it's done ?
Suggestions welcomed.
Whilst I'm here, and this is now actually my issue with using DGIndexNV ...
With this code snippet from a vbscript function,
Code: Select all
cumulative_sleep = 0
set eac_exe_object = wso.Exec(eac_command_string)
Do While eac_exe_object.Status = 0 '0 is running and 1 is ending
Wscript.Echo "vrdtvsp_exec_a_command_and_show_stdout_stderr About to sleep for " & sleep_amount & " ms (slept " & (cumulative_sleep/1000) & " seconds so far)"
Wscript.Sleep sleep_amount
cumulative_sleep = cumulative_sleep + sleep_amount
Loop
WScript.StdOut.WriteLine("START StdOut: ")
Do Until eac_exe_object.StdOut.AtEndOfStream
eac_tmp = eac_exe_object.StdOut.ReadLine()
WScript.StdOut.WriteLine(eac_tmp)
Loop
WScript.StdOut.WriteLine("END StdOut: ")
WScript.StdOut.WriteLine("START StdErr: ")
Do Until eac_exe_object.StdErr.AtEndOfStream
eac_tmp = eac_exe_object.StdErr.ReadLine()
WScript.StdOut.WriteLine(eac_tmp)
Loop
WScript.StdOut.WriteLine("END StdErr: ")
eac_exe_status = eac_exe_object.ExitCode
WScript.StdOut.WriteLine("EXIT STATUS: " & eac_exe_status)
Code: Select all
"C:\SOFTWARE\Vapoursynth-x64\DGIndex\DGIndexNV.exe" -i "D:\VRDTVSP-SCRATCH\test_file.QSF.mp4" -e -h -o "D:\VRDTVSP-SCRATCH\test_file.QSF.dgi"
Same thing happens given this command
Code: Select all
"C:\SOFTWARE\Vapoursynth-x64\DGIndex\DGIndexNV.exe" -version
Like I said, it used to work up until the MS windows update a couple of days ago.
Now I'll have to find another way
Suggestions welcomed. I understand if you decline