You are not logged in. Please login or register.
SmoothVideo Project → Using SVP → Svpflow2 causes Virtualdub crash
... and this after months of running many scripts sometimes many per day. Is there anyone here that can interpret a Vdub crash dump? (See attached.) I've created hundreds of Avisynth scripts that use Svpflow2 indirectly through Interframe and GameDropFix both versions 4 and 5, and I've NEVER gotten this. It gets to a certain point in a certain video and blows up. (And it's relatively early in the video, about 3600 frames.)
Are you using svpflow2.dll from SVP4?
File Size 670 720 bytes
File version 4.0.0.136
___
The same error about"AvisynthPluginInit2" was early discussed here: Recent crashes
Are you using svpflow2.dll from SVP4?
File Size 670 720 bytes
File version 4.0.0.136___
The same error about"AvisynthPluginInit2" was early discussed here: Recent crashes
Apparently not. My file version is 2.0.2.0, size 647,680.
I use InterFrame and GameDropFix in my scripts, and that's all. I've never been aware of how to be on a mailing list for news of needed updates. If you can direct me to more current svp*.dlls (as well as confirm that I need two of them, svpflow1.dll and svpflow2.dll), I'll appreciate. And would there be any needed changes to InterFrame or GDF? FYI, my script function avsi files as well as svp (and other) dlls are in C:\Program Files (x86)\AviSynth\plugins
Windows 10, 64-bit, but all video software is intentionally 32-bit.
(I did skim over that thread, and felt comforted that I was not alone in "sudden crashes without explanation", but much of it was cryptic to me.)
You can use information from official SVP changelog. See chapters about SVPflow.
SVPFlow plugins are not compatible to AviSynth 2.5 since version 4.0.0.132 - 2016-03-18.
AviSynth 2.6 is supported.
What version of AviSynth are you using?
As wroted in given topic "AvisynthPluginInit2" error was connected to Intel GPUs and some MTModes.
What GPU are you using?
You can use information from official SVP changelog. See chapters about SVPflow.
SVPFlow plugins are not compatible to AviSynth 2.5 since version 4.0.0.132 - 2016-03-18.
AviSynth 2.6 is supported.
What version of AviSynth are you using?And you are right. I think GDF needs to be updated to use with latest SVPFlow plugin.
A few months back I got wind of the need (I forget in what context) to change to 2.6
And I've been thinking I would volunteer to start a new thread devoted to GDF 4 and 5, with current source for both. (Yes 4 is still needed.)
As wroted in given topic "AvisynthPluginInit2" error was connected to Intel GPUs and some MTModes.
What GPU are you using?
It is Nvidia in every PC. I didn't know there was anything else. Several different cards/adapters. Nvidia is driver in each. Some have only 16 cuda cores; one has 192.
I'm not good at knowing or remembering what MTModes are or do, but I do believe that the two I always use are necessary and I have them in nearly every script at certain spots:
SetMTMode(3,threads) # very near the top
SetMTMode(2) # very near the bottom, right before the InterFrame call.
Are you using svpflow2.dll from SVP4?
File Size 670 720 bytes
File version 4.0.0.136___
The same error about"AvisynthPluginInit2" was early discussed here: Recent crashes
The change log shows this for SVPflow:
SVPflow - 4.0.0.137 - 2016-08-25
How am I supposed to get it? Pick the download for "Svp 4 Free" which gives me the file svp4-free-online.exe, and run it?
Yes, you can find svpflow1/2.dll in plugins folder from SVP 4 Free installed.
I will look what I can do to make GDF scripts compatible to avisynth 2.6
My file version is 2.0.2.0, size 647,680
Last svpflow2.dll from SVP 3.1.7 has version 2.0.3.0. You can get it from SVP 3 folder. Or you can take file linked below.
Try it. The error can be fixed there.
Yes, you can find svpflow1/2.dll in plugins folder from SVP 4 Free installed.
I will look what I can do to make GDF scripts compatible to avisynth 2.6
My file version is 2.0.2.0, size 647,680
Last svpflow2.dll from SVP 3.1.7 has version 2.0.3.0. You can get it from SVP 3 folder. Or you can take file linked below.
Try it. The error can be fixed there.
A couple things puzzle me.
Both of my GDF functions are working with Avisynth 2.6. So if they are working, I assume that makes them "compatible".
Not clear why you are recommending SVP 3.1.7 when earlier you seem to be implying I should get 4.
Uh, maybe you misspoke. As the current GDF functions DO work with Avisynth 2.6, maybe you meant to say "make them compatible with SVP4.
Thank you for that 2.0.3.0 svpflow2.dll. However, it also blows up and at the same spot as 2.0.2.0. Mind you, I had set the other video aside and continued working on others. However, another one blew up today. It was this one that drove me to download your 2.0.3.0 dll. On this 2nd video, it blew up in the same spot no matter which svpflow2 I used (2.0.2.0 or 2.0.3.0). I am attaching the Vdub crashinfo.
I've been wondering if you could explain why this would work for hundreds of videos of all shapes and sizes, then all of a sudden start crashing on a few.
The only things I can think of that these 2 videos have in common and different from the rest are:
1. They are screen captures from a source I have not captured before. (But some from the same source have processed fine.)
2. One is 736p and the other is 808p. I don't know if those are odd in some way. The ratio is very close to 1.777777.
It also seems odd that it would be far into the file, like after 30 minutes' worth of video.
Be sure to notice when I have posted twice, so you don't accidentally not read the prior one. (It's easy to assume that the last post someone made is all they said. I've done that myself.)
I also wondered if you suggested 3.1.7 instead of 4, perhaps if GDF won't work at all with 4. I do need GDF 4 and 5 to both keep working as is.
(And I'm sorry I cannot make all of my thoughts in one post. I don't thnk of things until a few min. later.)
It's ok. I see. Of course dlls from SVP4 would be better.
I've read all your posts. The error in SVPFlow2.dll 2.0.3.0 is the same: Access violation in AvisynthPluginInit2.
Did you try SVPFlow1/2.dll from SVP4?
Your suggestions about video framesaize can be possible cause. It needs to be checked.
To make me help you: can you post your avs-script here?
If GDF4/5 are already work with Avisynth 2.6 then it is good!
I mean, it need to be updated to work with Avisynth 2.6 and with last versions of used Avisynth plugins.
I didn't go for SVP4 yet as I don't have a clear confirmation from you that the existing GDF4 and GDF5 will still work with it (even if not optimum).
If the script will help, I can attach. But don't you need all functions I call? If so, then I'll have to collect all my avsi files and attach them too. Shall I do all that or is just the main .avs enough? Uh, I'll attach the main script now, and await further request from you.
Just to warn you. You might find my style of avs coding odd or difficult. That's okay, as for me my style works well.
TCmullet
Thank you. I will look your script. It can take some time.
But You already can try updated GDFv5.01.
TCmullet
Thank you. I will look your script. It can take some time.
But You already can try updated GDFv5.01.GDFv4 needs some more time.
Thanks, but I need to know if it's safe to use SVP4's dll. That is, can GDF4 and 5.0 still work as they've been working all along? I can't afford to break my system as I'm in middle of doing many videos as rapidly as possible. I am postponing (for a bit) those 2 videos that blow up, as I have many more that won't.
Well, now I'm greatly stymied. Was going to try SVP4free. I rename my svp dlls carefully. Was planning to make renamed copies of things after getting the new svpflow2.dll.
However, after running the installer, I searched my system (using AgentRansack) and there was NO new svpflow*.dll added to my system! What the heck's going on??
See svpflow1/2.dll files in folder SVP 4\plugins
can GDF4 and 5.0 still work as they've been working all along?
GDFv5 works without crashes on several my videos I tested yesterday.
I didn't compare 5.0 vs 5.1 face-to-face. But I think quality and speed must stay the same.
See svpflow1/2.dll files in folder SVP 4\plugins
There is no plugins folder inside of C:\Program Files (x86)\SVP 4. The only folders there are:
i18n
iconengines
imageformats
licences
platforms
utils
Maybe you didn't grasp the meaning of what I reported. Agent Ransack is a thorough file-finder. It found many versions of svpflow*.dll on my PC, as I have various copies (with various suffixes added to the names to help me identify them). But there was no new ones. There must be something defective with your installer. It did not create a plugins folder.
As a former programmer (who wishes he still had the income of a programmer), my gut tells me your bug MAY relate to the fact that when your installer prompted me for WHICH player that SVP would affect, I deselected everything as I do not presently want any of my players to be affected by SVP. (I only wanted to get the dlls.) Is it possible that your installer only creates the plugins folder if I pick one or more players?
> Is it possible that your installer only creates the plugins folder if I pick one or more players?
yeah, obviously it installs only what is needed
avs 32-bit plugins <=> directshow 32-bit players
avs 64-bit plugins <=> directshow 64-bit players
vs 64-bit plugins <=> mpv || libmpv || vlc
vlc 64-bit plugin <=> vlc
luckily for you there's a per-component installation option
luckily for you there's a per-component installation option
Yes, I found it now. When I get to the spot, I pick "Add or remove components". Then I see that "[DS_32] Core for DirectShow 32-bit" has a tool tip (shown at the right) saying "SVP core libraries (SVPflow)..." So I select that. I select 32-bit even though my PC is 64-bit, as my Avisynth is 32-bit. (I made all my video processing software 32-bit as I heard that's much safer/reliable.)
NOW svpflow1 and 2 ARE there in a plugins folder.
Svpflow1.dll is 4.0.0.132
Svpflow2.dll is 4.0.0.136
I will install these (copy these) to my Avisynth plugins folder and attempt the two scripts (the two videos) that have been blowing up.
Chainik wrote:luckily for you there's a per-component installation option
Yes, I found it now. When I get to the spot, I pick "Add or remove components". Then I see that "[DS_32] Core for DirectShow 32-bit" has a tool tip (shown at the right) saying "SVP core libraries (SVPflow)..." So I select that. I select 32-bit even though my PC is 64-bit, as my Avisynth is 32-bit. (I made all my video processing software 32-bit as I heard that's much safer/reliable.)
NOW svpflow1 and 2 ARE there in a plugins folder.
Svpflow1.dll is 4.0.0.132
Svpflow2.dll is 4.0.0.136
I will install these (copy these) to my Avisynth plugins folder and attempt the two scripts (the two videos) that have been blowing up.
Both videos completed successfully. Thanks so much!
As an aside, you might be wondering why I would refrain from letting SVP into any of my players. It's simply that I always want my players to reflect exactly what's in the file, so I can know the quality/attributes of the file. I hate it when players "improve" a video, which misleads me about the nature of the file. Of course I realize my usage of players is a bit odd.
Both videos completed successfully. Thanks so much!
Congratulations!
Suddenly, days after svpflow2 began to be working great on all my videos, I hit a video that is crashing very early in it's file. Have rebooted and restarted. Always blows up now on this video. Here's the dump. Svpflow2.dll is 4.0.0.136. Hope you can figure this out, please.
VirtualDub crash report -- build 35491 (release)
--------------------------------------
Disassembly:
689e3720: 0000 add [eax], al
689e3722: f30f6f4680 movdqu xmm0, [esi-80h]
689e3727: f30f6f4e90 movdqu xmm1, [esi-70h]
689e372c: f30f6f56a0 movdqu xmm2, [esi-60h]
689e3731: f30f6f5eb0 movdqu xmm3, [esi-50h]
689e3736: f30f6f66c0 movdqu xmm4, [esi-40h]
689e373b: f30f6f6ed0 movdqu xmm5, [esi-30h]
689e3740: f30f6f76e0 movdqu xmm6, [esi-20h]
689e3745: f30f6f7ef0 movdqu xmm7, [esi-10h]
689e374a: 660fe74280 movntdq [edx-80h], xmm0
689e374f: 660fe74a90 movntdq [edx-70h], xmm1
689e3754: 660fe752a0 movntdq [edx-60h], xmm2
689e3759: 660fe75ab0 movntdq [edx-50h], xmm3
689e375e: 660fe762c0 movntdq [edx-40h], xmm4
689e3763: 660fe76ad0 movntdq [edx-30h], xmm5
689e3768: 660fe772e0 movntdq [edx-20h], xmm6
689e376d: 660fe77af0 movntdq [edx-10h], xmm7
689e3772: 81f980000000 cmp ecx, 00000080
689e3778: 7d96 jge 689e3710
689e377a: 8bc1 mov eax, ecx
689e377c: c1e804 shr eax, 04h
689e377f: c1e004 shl eax, 04h
689e3782: 03d0 add edx, eax
689e3784: 03f0 add esi, eax
689e3786: 2bc8 sub ecx, eax
689e3788: c1e804 shr eax, 04h
689e378b: 0faef8 sfence
689e378e: ff2485b061a468 jmp dword ptr [eax*4+68a461b0]
689e3795: 81f980000000 cmp ecx, 00000080
689e379b: 7d03 jge 689e37a0
689e379d: eb69 jmp 689e3808
689e379f: 90 nop
689e37a0: 81e980000000 sub ecx, 00000080
689e37a6: 660f6f06 movdqa xmm0, [esi]
689e37aa: 660f6f4e10 movdqa xmm1, [esi+10h]
689e37af: 660f7f02 movdqa [edx], xmm0
689e37b3: 660f7f4a10 movdqa [edx+10h], xmm1
689e37b8: 660f6f5620 movdqa xmm2, [esi+20h] <-- FAULT
689e37bd: 660f6f5e30 movdqa xmm3, [esi+30h]
689e37c2: 660f7f5220 movdqa [edx+20h], xmm2
689e37c7: 660f7f5a30 movdqa [edx+30h], xmm3
689e37cc: 660f6f6640 movdqa xmm4, [esi+40h]
689e37d1: 660f6f6e50 movdqa xmm5, [esi+50h]
689e37d6: 660f7f6240 movdqa [edx+40h], xmm4
689e37db: 660f7f6a50 movdqa [edx+50h], xmm5
689e37e0: 660f6f7660 movdqa xmm6, [esi+60h]
689e37e5: 660f6f7e70 movdqa xmm7, [esi+70h]
689e37ea: 81c680000000 add esi, 00000080
689e37f0: 660f7f7260 movdqa [edx+60h], xmm6
689e37f5: 660f7f7a70 movdqa [edx+70h], xmm7
689e37fa: 81c280000000 add edx, 00000080
689e3800: 81f980000000 cmp ecx, 00000080
689e3806: 7d98 jge 689e37a0
689e3808: 8bc1 mov eax, ecx
689e380a: c1e804 shr eax, 04h
689e380d: c1e004 shl eax, 04h
689e3810: 03d0 add edx, eax
689e3812: 03f0 add esi, eax
689e3814: 2bc8 sub ecx, eax
689e3816: c1e804 shr eax, 04h
689e3819: ff24858061a468 jmp dword ptr [eax*4+68a46180]
Built on Althena on Sun Oct 27 15:59:07 2013 using compiler version 1400
Windows 6.3 (Windows 7 x64 build 9600) []
Memory status: virtual free 2092M/4096M, commit limit 49150M, physical total 24574M
EAX = 00400000
EBX = 4ff6bf20
ECX = 000001ce
EDX = 0eae68c0
EBP = 0eae6840
ESI = 4ffb2fe0
EDI = 0eae6b0e
ESP = 16fbfbcc
EIP = 689e37b8
EFLAGS = 00010202
FPUCW = 027f
FPUTW = ffff
Crash reason: Access Violation
Crash context:
An out-of-bounds memory access (access violation) occurred in module 'svpflow2'...
...reading address 4FFB3000.
Pointer dumps:
EAX 00400000: 00905a4d 00000003 00000004 0000ffff 000000b8 00000000 00000040 00000000
EBX 4ff6bf20: 83838385 88848383 9090908a 90909090 91919190 878b8d91 83838386 83838383
EDX 0eae68c0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
ESI 4ffb2fe0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
EDI 0eae6b0a: 80969696 87878780 87878787 88888887 89898988 89898989 89898989 89898989
ESP 16fbfbc8: 00000000 0eae6840 16fbfc68 689ccd31 0eae6840 4ffb2f60 000002ce 7f137aa6
16fbfbe8: 15c8ff88 0000000d 0ea5a74e 0ea5a480 4ff24120 00000194 000002ce 4ffb2f60
16fbfc08: 00000190 000002ce 00000194 00000194 00d1a3e0 16fbfd4c 68a191f0 00976580
16fbfc28: 15494880 15fc7258 0abd0c80 3b1f0120 3b238aa0 3b0d4020 0e098020 0099e0e8
EBP 0eae6840: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
0eae6860: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
0eae6880: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
0eae68a0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Thread call stack:
689e37b8: svpflow2!_AvisynthPluginInit3@8 [689a0000+3fa30+3d88]
689ccd31: svpflow2!svpGetVersion [689a0000+14110+18c21]
689d8ee6: svpflow2!svpGetVersion [689a0000+14110+24dd6]
689cf32d: svpflow2!svpGetVersion [689a0000+14110+1b21d]
77eb5c0c: ntdll!RtlAllocateHeap [77e70000+45b00+10c]
69a834b8: AviSynth!avs_delete_script_environment [69a10000+6f220+4298]
77eb5b32: ntdll!RtlAllocateHeap [77e70000+45b00+32]
77ede5fc: ntdll!NtWaitForSingleObject [77e70000+6e5f0+c]
770badf9: KERNELBASE!WaitForSingleObjectEx [76ff0000+cad60+99]
69a834b8: AviSynth!avs_delete_script_environment [69a10000+6f220+4298]
69a8227b: AviSynth!avs_delete_script_environment [69a10000+6f220+305b]
69a87786: AviSynth!DllCanUnloadNow [69a10000+75120+2666]
763362c4: KERNEL32!BaseThreadInitThunk [76320000+162a0+24]
77ed0fd9: ntdll!RtlSubscribeWnfStateChangeNotification [77e70000+60ba0+439]
77ed0fa4: ntdll!RtlSubscribeWnfStateChangeNotification [77e70000+60ba0+404]
-- End of reportSmoothVideo Project → Using SVP → Svpflow2 causes Virtualdub crash
Powered by PunBB, supported by Informer Technologies, Inc.