Port of NNEDI under new v2.6 AVS API - Page 3

jpsdr · 27th April 2015, 09:30

I don't have Win8/Win10, and frankly don't intent to. Does the crash happens with all versions ? Are you using the last build (check the date on my github release) ?
If yes to, both, eventualy you can provide a VirtualDub crash log file, and i'll see if it's happening in one of the ASM part code, in that case, it may be possible that i can fix it if it's a bug in the ASM. But don't get too much hope, there is unfortunately a high possibilty that fixing this may be out of my field skills, as it seems more to be OS dependant, and in that case unfortunately it's totaly out of my knowledge.

stax76 · 27th April 2015, 09:47

I'm on Win7 too, I ported StaxRip to 64-Bit, Win8 users had crashes I didn't had so I installed Win10 preview in vmware player, I saw the crashes then and installed Visual Studio 2015 preview and debugged it, there were 4-5 occurrences where interop code was bad. The only small problem was that the IDE was very slow due to the virtual environment. You could setup multi boot, it's not very difficult. Win10 isn't bad, potentially Windows will be much more expensive in the future, if that wouldn't be likely I would switch to Win10 right now, many people here switched already, I hope there are more news on Build conference starting tomorrow.

stax76 · 27th April 2015, 14:13

A user reported nnedi3 works on Win8, could the crash I got be because I was using vmware?

jpsdr · 28th April 2015, 00:38

I don't even know what vmware is...

28th April 2015, 01:46

Quote:

Originally Posted by jpsdr

I don't even know what vmware is...

It's a company that makes some of the most widely-used virtualization software.

jpsdr · 28th April 2015, 09:08

Ok. It's possible it may be the cause.
The only thing i can do for now, as i've said, is to check a Virtuabldub crash log, and see if it's happening in one of the ASM code i've ported out, it's the only place with bug introduced risk. If it's not here, this is totaly out of my field knowledge.
I've been very lucky that port worked almost only with putting ASM functions in outside files.

jpsdr · 29th April 2015, 08:49

Out of curiosity, try with opt=1 in nnedi.

stax76 · 29th April 2015, 09:29

opt=1 is working with vmware!

edit:

what makes the file size that large (13,1 MB)?

jpsdr · 29th April 2015, 19:08

The neural network datas.
Id opt=1 is working, it means it crashes in the ASM functions. Providing me a Virtualdub crash log file have higher chances to help figure out what is wrong. With it, there is a little hope.

stax76 · 29th April 2015, 20:24

It crashes StaxRip and MPC-BE but not VirtualDub!

jpsdr · 30th April 2015, 08:37

Argh....

Virtualdub provides disassembled code where crash occured, which could have told me on what part was the crash. But without this...
In that case, i must sadly confess that i have no clue of what to do...

Does crash also happen with 32 bit version (under vmware) ?

Edit : And on the 13.1MB, 12.9MB are the neural network datas.

jpsdr · 6th May 2015, 09:04

@stax76
I'm using the last stable release of AVS+, r1576. Do you use this version ? If not, can you test with r1576 ?

stax76 · 6th May 2015, 09:44

I did test r1576 and also Win10 natively (without vmware), problem persist.

jpsdr · 6th May 2015, 12:21

I don't have time these days, but later, i'll check the ASM code in case in see something.
Can you try the "old" Tritical's build just out of curiosity : http://forum.doom9.org/showthread.php?t=147695 ?

stax76 · 6th May 2015, 12:36

Quote:

Can you try the "old" Tritical's build just out of curiosity

Same result, without opt=1 mpc-be x64 crashes on Win10.

jpsdr · 6th May 2015, 13:06

Are you using the "vectorcall_" instead of standard "fastcall_" for compiling your StaxRip 64b port ?

stax76 · 6th May 2015, 13:19

I use VB.NET and interface with AviSynth using the avifile API, only thing I saw was win32exception, I tried to attach a debugger but it didn't yield to anything, in the system log I found some info:

Quote:

Fehlerbucket 86074866829, Typ 4
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 85948023432

Problemsignatur:
P1: StaxRip.exe
P2: 1.3.1.1
P3: 554a041b
P4: nnedi3.dll
P5: 0.9.4.7
P6: 550421cb
P7: c0000005
P8: 000000000000fede
P9:
P10:

Angefügte Dateien:
C:\Users\frank\AppData\Local\Temp\WERFA59.tmp.WERInternalMetadata.xml
C:\Users\frank\AppData\Local\Temp\WER622.tmp.appcompat.txt
C:\Users\frank\AppData\Local\Temp\WER6CF.tmp.hdmp
C:\Users\frank\AppData\Local\Temp\WER2535.tmp.WERDataCollectionFailure.txt

Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_StaxRip.exe_b72abc897b1e0ecd8d22d975322fdbcbd313f93_a07971f2_cab_20277c46

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: d0f7bfad-401a-4a32-9ee9-89b9afdcde02
Berichtstatus: 8
Bucket mit Hash: d59ed2b9785e003d6467e1e13724dc70

Quote:

Name der fehlerhaften Anwendung: StaxRip.exe, Version: 1.3.1.1, Zeitstempel: 0x554a041b
Name des fehlerhaften Moduls: nnedi3.dll, Version: 0.9.4.7, Zeitstempel: 0x550421cb
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000000fede
ID des fehlerhaften Prozesses: 0x21ec
Startzeit der fehlerhaften Anwendung: 0x01d087f647effd06
Pfad der fehlerhaften Anwendung: D:\Projekte\GitHub\staxrip\bin\StaxRip.exe
Pfad des fehlerhaften Moduls: D:\Projekte\GitHub\staxrip\bin\Tools\Plugins\nnedi3\nnedi3.dll
Berichtskennung: 429aaf55-ee38-40c4-aec7-6dc86532b124
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

jpsdr · 7th May 2015, 12:23

Unfortunately, i'm not able to get informations from this. I'm concerned by the fact that also the old Tritical's version is crashing. It's realy more troublesome, meaning that maybe issue is in the ASM code itself, and not caused by an error i could have done during the port.
You have no issues with the 32 bit version ?
And VDub working perfectly fine...!!
I think in two weeks i may have time to recheck the ASM code, in case there is errors in my port.
But at first glance, it's not looking good...

VDub works fine, old Tritical's version also crashing... bad... very bad...

stax76 · 7th May 2015, 12:54

I use x64 exclusively everywhere so it's difficult for me to test. I would have to download and setup everything. Is there a big performance difference between c and asm path? QTGMC uses nnedi3 and still works.

jpsdr · 7th May 2015, 13:25

I don't have benchmark, and can't do for now, my video dedicated PC is encoding, and there is at least one day left. But as i remember when i've done test, performance issue is noticeable i think just sliding a file with VDub (or is it disabling internal mutli-threading... i have doubts finaly...) with an avs script with only one line using only nnedi3_rpow2.

27th April 2015, 09:47	#42 \| Link
stax76 Registered User Join Date: Jun 2002 Location: On thin ice Posts: 6,837	I'm on Win7 too, I ported StaxRip to 64-Bit, Win8 users had crashes I didn't had so I installed Win10 preview in vmware player, I saw the crashes then and installed Visual Studio 2015 preview and debugged it, there were 4-5 occurrences where interop code was bad. The only small problem was that the IDE was very slow due to the virtual environment. You could setup multi boot, it's not very difficult. Win10 isn't bad, potentially Windows will be much more expensive in the future, if that wouldn't be likely I would switch to Win10 right now, many people here switched already, I hope there are more news on Build conference starting tomorrow. Last edited by stax76; 27th April 2015 at 09:54.

29th April 2015, 09:29	#48 \| Link
stax76 Registered User Join Date: Jun 2002 Location: On thin ice Posts: 6,837	opt=1 is working with vmware! edit: what makes the file size that large (13,1 MB)? Last edited by stax76; 29th April 2015 at 09:55.

30th April 2015, 08:37	#51 \| Link
jpsdr Registered User Join Date: Oct 2002 Location: France Posts: 2,316	Argh.... Virtualdub provides disassembled code where crash occured, which could have told me on what part was the crash. But without this... In that case, i must sadly confess that i have no clue of what to do... Does crash also happen with 32 bit version (under vmware) ? Edit : And on the 13.1MB, 12.9MB are the neural network datas. Last edited by jpsdr; 30th April 2015 at 08:44.

27th April 2015, 09:30	#41 \| Link
jpsdr Registered User Join Date: Oct 2002 Location: France Posts: 2,316	I don't have Win8/Win10, and frankly don't intent to. Does the crash happens with all versions ? Are you using the last build (check the date on my github release) ? If yes to, both, eventualy you can provide a VirtualDub crash log file, and i'll see if it's happening in one of the ASM part code, in that case, it may be possible that i can fix it if it's a bug in the ASM. But don't get too much hope, there is unfortunately a high possibilty that fixing this may be out of my field skills, as it seems more to be OS dependant, and in that case unfortunately it's totaly out of my knowledge.

27th April 2015, 14:13	#43 \| Link
stax76 Registered User Join Date: Jun 2002 Location: On thin ice Posts: 6,837	A user reported nnedi3 works on Win8, could the crash I got be because I was using vmware?

28th April 2015, 00:38	#44 \| Link
jpsdr Registered User Join Date: Oct 2002 Location: France Posts: 2,316	I don't even know what vmware is...

28th April 2015, 09:08	#46 \| Link
jpsdr Registered User Join Date: Oct 2002 Location: France Posts: 2,316	Ok. It's possible it may be the cause. The only thing i can do for now, as i've said, is to check a Virtuabldub crash log, and see if it's happening in one of the ASM code i've ported out, it's the only place with bug introduced risk. If it's not here, this is totaly out of my field knowledge. I've been very lucky that port worked almost only with putting ASM functions in outside files.

29th April 2015, 08:49	#47 \| Link
jpsdr Registered User Join Date: Oct 2002 Location: France Posts: 2,316	Out of curiosity, try with opt=1 in nnedi.

29th April 2015, 19:08	#49 \| Link
jpsdr Registered User Join Date: Oct 2002 Location: France Posts: 2,316	The neural network datas. Id opt=1 is working, it means it crashes in the ASM functions. Providing me a Virtualdub crash log file have higher chances to help figure out what is wrong. With it, there is a little hope.

29th April 2015, 20:24	#50 \| Link
stax76 Registered User Join Date: Jun 2002 Location: On thin ice Posts: 6,837	It crashes StaxRip and MPC-BE but not VirtualDub!

6th May 2015, 09:04	#52 \| Link
jpsdr Registered User Join Date: Oct 2002 Location: France Posts: 2,316	@stax76 I'm using the last stable release of AVS+, r1576. Do you use this version ? If not, can you test with r1576 ?

6th May 2015, 09:44	#53 \| Link
stax76 Registered User Join Date: Jun 2002 Location: On thin ice Posts: 6,837	I did test r1576 and also Win10 natively (without vmware), problem persist.

6th May 2015, 12:21	#54 \| Link
jpsdr Registered User Join Date: Oct 2002 Location: France Posts: 2,316	I don't have time these days, but later, i'll check the ASM code in case in see something. Can you try the "old" Tritical's build just out of curiosity : http://forum.doom9.org/showthread.php?t=147695 ?

6th May 2015, 13:06	#56 \| Link
jpsdr Registered User Join Date: Oct 2002 Location: France Posts: 2,316	Are you using the "vectorcall_" instead of standard "fastcall_" for compiling your StaxRip 64b port ?

7th May 2015, 12:23	#58 \| Link
jpsdr Registered User Join Date: Oct 2002 Location: France Posts: 2,316	Unfortunately, i'm not able to get informations from this. I'm concerned by the fact that also the old Tritical's version is crashing. It's realy more troublesome, meaning that maybe issue is in the ASM code itself, and not caused by an error i could have done during the port. You have no issues with the 32 bit version ? And VDub working perfectly fine...!! I think in two weeks i may have time to recheck the ASM code, in case there is errors in my port. But at first glance, it's not looking good... VDub works fine, old Tritical's version also crashing... bad... very bad...

7th May 2015, 12:54	#59 \| Link
stax76 Registered User Join Date: Jun 2002 Location: On thin ice Posts: 6,837	I use x64 exclusively everywhere so it's difficult for me to test. I would have to download and setup everything. Is there a big performance difference between c and asm path? QTGMC uses nnedi3 and still works.

7th May 2015, 13:25	#60 \| Link
jpsdr Registered User Join Date: Oct 2002 Location: France Posts: 2,316	I don't have benchmark, and can't do for now, my video dedicated PC is encoding, and there is at least one day left. But as i remember when i've done test, performance issue is noticeable i think just sliding a file with VDub (or is it disabling internal mutli-threading... i have doubts finaly...) with an avs script with only one line using only nnedi3_rpow2.