DiAVC decoder, yet another fast H.264 high profile decoder - Page 7

LoRd_MuldeR · 17th November 2009, 16:31

Quote:

Originally Posted by LoRd_MuldeR

Quote:

Originally Posted by schweinsz

I have deleted the restriction that only work on xp, 2000 and vista. The DiAVC should work on win7. You can try it now.

Okay. Will try and report back...

Sorry, same problem as before:
It seems DiAVCSetting.exe doesn't register the DiAVC.ax at all. At least it cannot be found by TimeCodec or by GraphStudio.

I can register it manually by running regsvr32.exe from an Admin console, but then TimeCodec will freeze at startup.
Same goes for GraphStudio, as soon as I insert your filter into the graph. Will have to unregister...

BetaBoy · 17th November 2009, 16:33

We just found the same thing out.... it breaks TimeCodec.

LoRd_MuldeR · 17th November 2009, 16:39

Quote:

Originally Posted by BetaBoy

We just found the same thing out.... it breaks TimeCodec.

Not only TimeCodec. GraphStudio will hang too (with 100% CPU load), as soon as I try to insert DiAVC

Well, it's still "alpha" for a reason. So problems are expected, I guess. Let's wait for the upcoming "Beta" release then.

Keiyakusha · 17th November 2009, 16:45

Ok I want to elaborate a bit what I said sometimes earlier. For example with this 1080p sample, I'm getting following speeds:
DiAVC: 89.1697
DivX: 82.8047
CoreAVC: 79.9550

About win7... works fine on 32bit system, with manual registering and DiAVCSetting.exe, with timecodec and graphstudio.

As for jumping playback, schweinsz, you really should test MPC-HC. It seems not every player affected. For example there is no such effect in KMPlayer.

LoRd_MuldeR · 17th November 2009, 16:54

Quote:

Originally Posted by Keiyakusha

About win7... works fine on 32bit system, with manual registering and DiAVCSetting.exe, with timecodec and graphstudio.

I'm on 64-Bit, so maybe that's the reason...

schweinsz · 17th November 2009, 17:04

Quote:

Originally Posted by LoRd_MuldeR

I'm on 64-Bit, so maybe that's the reason...

The DiAVC don't support the 64bit system. It will support the 64bit system in future.

squid_80 · 17th November 2009, 17:07

It should still work, there's no reason for it to go into an infinite loop.

schweinsz · 17th November 2009, 17:22

Quote:

Originally Posted by squid_80

It should still work, there's no reason for it to go into an infinite loop.

Do you mean that a 32-bit ax or dll can work on a 64-bit win7? On which conditions can the 32bit ax or dll run on a 64bit system? I never tested the DiAVC on 64-bit system. The initialization of the DiAVC use interrupt such as int 02dh or int 3 to prevent user to dubug it. Besides, are there some differences about the system function in kernel32.dll, ntdll.dll or advapi.dll between the 64-bit and the 32-bit windows? I must buy a new computer recently.

squid_80 · 17th November 2009, 17:36

A 32-bit directshow filter should run fine on any 64-bit windows (not just win7), provided a 32-bit player is used.

schweinsz · 17th November 2009, 17:45

Quote:

Originally Posted by squid_80

A 32-bit directshow filter should run fine on any 64-bit windows (not just win7), provided a 32-bit player is used.

But how about the system functions in kernel32.dll, ntdll.dll or advapi.dll? The DiAVC have a direct call to some functions in these dll?

LoRd_MuldeR · 17th November 2009, 17:49

Quote:

Originally Posted by schweinsz

But how about the system functions in kernel32.dll, ntdll.dll or advapi.dll? The DiAVC have a direct call to some functions in these dll?

64-Bit Windows has a 32-Bit Subsystem (WOW64). All the system DLL's exists in two versions, 32-Bit and 64-Bit.

The 64-Bit system folder is "C:\Windows\System32" and the 32-Bit system folder is "C:\Windows\SysWow64". Weird, but that's the way it is.

32-Bit applications (and of course also 32-Bit DLL's) will load the 32-Bit system DLL's and work flawlessly under 64-Bit Windows...

Cyber-Mav · 18th November 2009, 00:50

Quote:

Originally Posted by schweinsz

You can test some 1080p or 1080i contents, you will get the DiAVC is fastest especially for high-bitrate. I will release the beta version about 20 days later, it will 10% at least faster than the current version.

this is something i will be waiting for. looks like we got an excellent option for a free fast avc decoder comming up.
will the beta version run faster on older hardware such as amd athlonXP?

sneaker_ger · 18th November 2009, 01:02

In the start post schweinsz says that you'll need a CPU with SSE2 to run it. So an Athlon XP probably won't do.

Cyber-Mav · 18th November 2009, 15:32

Quote:

Originally Posted by sneaker_ger

In the start post schweinsz says that you'll need a CPU with SSE2 to run it. So an Athlon XP probably won't do.

ahh i havent tried it on my athlonxp machine. i need to make some time to test these decoders out on the athlonxp and see which one is best for old skool cpus.

schweinsz · 18th November 2009, 16:56

Quote:

Originally Posted by Cyber-Mav

ahh i havent tried it on my athlonxp machine. i need to make some time to test these decoders out on the athlonxp and see which one is best for old skool cpus.

The DiAVC require SSE2-enable cpu currently. I am trying to make the DiAVC to be the best H.264 decoder for netbooks or some others that have not a hardware decoder firstly. Perhaps I will code some MMX code to replace the current SSE2 code so that the DiAVC support some old cpu in future.

littleD · 18th November 2009, 22:15

Quote:

Originally Posted by schweinsz

The DiAVC require SSE2-enable cpu currently. I am trying to make the DiAVC to be the best H.264 decoder for netbooks or some others that have not a hardware decoder firstly. Perhaps I will code some MMX code to replace the current SSE2 code so that the DiAVC support some old cpu in future.

Cpus with only mmx arent suitable for anything. If you will support SSE that would be cool.

nm · 19th November 2009, 04:19

Quote:

Originally Posted by littleD

Cpus with only mmx arent suitable for anything. If you will support SSE that would be cool.

Unlike MMX, SSE1 is not really useful for decoding H.264, or pretty much any video format, since it only supports floating-point data. See this thread for some facts: http://lists.mplayerhq.hu/pipermail/...er/003776.html

littleD · 19th November 2009, 10:36

Ok, thanks.

schweinsz · 19th November 2009, 16:50

Quote:

Originally Posted by LoRd_MuldeR

64-Bit Windows has a 32-Bit Subsystem (WOW64). All the system DLL's exists in two versions, 32-Bit and 64-Bit.

The 64-Bit system folder is "C:\Windows\System32" and the 32-Bit system folder is "C:\Windows\SysWow64". Weird, but that's the way it is.

32-Bit applications (and of course also 32-Bit DLL's) will load the 32-Bit system DLL's and work flawlessly under 64-Bit Windows...

Could you share me some dll in the directory "C:\Windows\SysWow64"? These needed dll are ntdll.dll, kernel32.dll and advapi32.dll. This will help me much. I have not a x64 cpu.

LoRd_MuldeR · 19th November 2009, 18:46

Well, I think sharing proprietary DLL's from Microsoft Windows, DLL's that aren't explicitly marked as redistributables, would be a rule #6 violation.

Why you can't effort your own copy of 64-Bit Windows? Given that your are working on a commercial project and have "big" plans with it, this should be a relatively small investment

17th November 2009, 16:33	#122 \| Link
BetaBoy CoreCodec Founder Join Date: Oct 2001 Location: San Francisco Posts: 1,421	We just found the same thing out.... it breaks TimeCodec. __________________ Dan "BetaBoy" Marlin Ubiquitous Multimedia Technologies and Developer Tools http://corecodec.com

19th November 2009, 18:46	#140 \| Link
LoRd_MuldeR Software Developer Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,248	Well, I think sharing proprietary DLL's from Microsoft Windows, DLL's that aren't explicitly marked as redistributables, would be a rule #6 violation. Why you can't effort your own copy of 64-Bit Windows? Given that your are working on a commercial project and have "big" plans with it, this should be a relatively small investment __________________ Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊

17th November 2009, 16:45	#124 \| Link
Keiyakusha 契約者 Join Date: Jun 2008 Posts: 1,576	Ok I want to elaborate a bit what I said sometimes earlier. For example with this 1080p sample, I'm getting following speeds: DiAVC: 89.1697 DivX: 82.8047 CoreAVC: 79.9550 About win7... works fine on 32bit system, with manual registering and DiAVCSetting.exe, with timecodec and graphstudio. As for jumping playback, schweinsz, you really should test MPC-HC. It seems not every player affected. For example there is no such effect in KMPlayer.

17th November 2009, 17:07	#127 \| Link
squid_80 Registered User Join Date: Dec 2004 Location: Melbourne, AU Posts: 1,963	It should still work, there's no reason for it to go into an infinite loop.

17th November 2009, 17:36	#129 \| Link
squid_80 Registered User Join Date: Dec 2004 Location: Melbourne, AU Posts: 1,963	A 32-bit directshow filter should run fine on any 64-bit windows (not just win7), provided a 32-bit player is used.

18th November 2009, 01:02	#133 \| Link
sneaker_ger Registered User Join Date: Dec 2002 Posts: 5,565	In the start post schweinsz says that you'll need a CPU with SSE2 to run it. So an Athlon XP probably won't do.

19th November 2009, 10:36	#138 \| Link
littleD Registered User Join Date: Aug 2008 Posts: 343	Ok, thanks.