CoreCodec/H.264 Codec "CoreAVC"

[squid_80]

CoreAVC won't allow itself to be loaded while running under a debugger. It's not actually the root cause of your problem.

[Sagekilla]

Hm. I'll try decoding with ffmpegsource instead. I've been trying to do it solely through CoreAVC (for speed reasons) though.

[littleD]

@ littleD
The Apple trailer I posted above is just fine for testing 720p.

If so, then it plays fine on sempron 2600 1.8 gh. There were just small slowdowns with red trees and ending city. But its playable with deblocking on. Nice video btw.
==
But im not sure if its representative 720p source as has specific properties. E.g. no CABAC.

[DJ Bobo]

@ DW
Of course. Look further behind how to download and play the Apple trailers without having QuickTime (this is about CoreAVC's performance after all).

There were just small slowdowns with red trees and ending city
That's exactly why this trailer is interesting. It is full 16:9, has 30fps (which makes up for the lack of CABAC) and simulates high-bitrate action scenes at the end pretty well.
Nice video btw
Yes it is :D

[cdv1010]

Hello everybody, I have a Geforce 8400M GS laptop video card. When I turn on CUDA options, I can't play 1080p mkv files(frame rate only <5) although i can play it nearly smooth (about 18~20 fps) without CUDA.
My CPU is core2 duo 1,4Ghz. Have anyone got solution for this situation?

[Cyber-Mav]

Hello everybody, I have a Geforce 8400M GS laptop video card. When I turn on CUDA options, I can't play 1080p mkv files(frame rate only <5) although i can play it nearly smooth (about 18~20 fps) without CUDA.
My CPU is core2 duo 1,4Ghz. Have anyone got solution for this situation?

solution is media player classic home cinema.

[me7]

Hello everybody, I have a Geforce 8400M GS laptop video card. When I turn on CUDA options, I can't play 1080p mkv files(frame rate only <5) although i can play it nearly smooth (about 18~20 fps) without CUDA.
My CPU is core2 duo 1,4Ghz. Have anyone got solution for this situation?

I had the same problem, I solved it by using Overlay Mixer.
Using MPCHC with VMR or EVR caused the same problem.

[BetaBoy]

We are compiling a release for CoreAVC v1.9.5 as we speak that now features CUDA Interlaced support and addresses all of the known issues and even adds new input colorspace options. Also for our OEM/CE customers or potential licensee's we have also added NVIDIA CUDA support to the latest CoreAVC SDK, for more info you can email: licensing AT corecodec DOT com

Once we QA the final release package we will unleash it.... so likely right after the weekend.

[ajp_anton]

Is there an x64 version coming?

[BetaBoy]

In CoreAVC 2.0 yes

[Shakey_Jake33]

For the interested, there's now an official mobile driver that supports CUDA on the CUDA page

http://www.nvidia.com/object/cuda_get.html

[hajj_3]

We are compiling a release for CoreAVC v1.9.5 as we speak that now features CUDA Interlaced support and addresses all of the known issues and even adds new input colorspace options. Also for our OEM/CE customers or potential licensee's we have also added NVIDIA CUDA support to the latest CoreAVC SDK, for more info you can email: licensing AT corecodec DOT com

Once we QA the final release package we will unleash it.... so likely right after the weekend.

Great news, hopefully out any day then:)

[BetaBoy]

ok... QA has passed. Here are the release details.

CoreAVC H.264 Video Codec - Version 1.9.5.0 (20090316)
- Add: NVIDIA CUDA accelerated decoding for interlaced streams (MBAFF and PAFF)
- Add: Input stream colorspace override options
- Fix: CUDA matrix handling and DPB management improvements
- Fix: SEI messages were sometimes discarded
- Fix: Seeking problems with Canon HF100 streams
- Fix: Use faster asynchronous memory transfers between CPU<->GPU for CUDA

Note three things with CUDA:
- CUDA does not support lossless AVC
- There is a 16 ref frames limit that is caused by CUDA relying on direct3d. Technically our implementation supports higher ref's so if NVIDIA fixed that in their driver, those streams would start working.
- The next driver release from NVIDIA will address a CUDA cropping issue (content with a height of 368 and 1088 is automatically clipped to 360 and 1080).

Notifications for the update download will begin to go out soon. Please post some results or any bugs you might have found.

[Dark Shikari]

- There is a 16 ref frames limit that is caused by CUDA relying on direct3d. Technically our implementation supports higher ref's so if NVIDIA fixed that in their driver, those streams would start working.Doesn't the spec already limit you to 16 reference frames? Or are you referring to the case of interlaced, where the spec allows 32 reference fields?

[BetaBoy]

Doesn't the spec already limit you to 16 reference frames? Or are you referring to the case of interlaced, where the spec allows 32 reference fields?

Correct.

[squid_80]

16 ref frame limitation = streams with 16 reference frames aren't supported with CUDA. Streams with <16 should be ok.

[tetsuo55]

16 ref frame limitation = streams with 16 reference frames aren't supported with CUDA. Streams with <16 should be ok.

Wait.

so a stream with 15 ref frames does work and a stream with 16 ref frames does not?

What about bframes, these too have a spec based limit of 16

Does a 16ref frames 16bframes + bpyramids file work?

[squid_80]

Wait.

so a stream with 15 ref frames does work and a stream with 16 ref frames does not?Correct.What about bframes, these too have a spec based limit of 16CUDA has no additional b-frame limitation.Does a 16ref frames 16bframes + bpyramids file work?No, because 16 reference frames aren't supported.
I spoke a bit about the technical reasons in this post (http://forum.doom9.org/showthread.php?p=1192953#post1192953).

[BetaBoy]

tetsuo55... in other words, if CUDA were not tied to DirectX there would be no limitation.

[tetsuo55]

Does DirectX 11 remove this limitation?
What about if you use DMO instead of directshow?

So this file should work: 15 ref frames, 16 bframes+bpyramids (because bframes don't matter for cuda?)
What is the resolution limit? 4096x2304?
What about the bitrate limit, is it 960MBIT/S

Does 15 ref frames still work at that high resolution?

[squid_80]

Does DirectX 11 remove this limitation?Not to my knowledge.What about if you use DMO instead of directshow?That wouldn't make any difference.So this file should work: 15 ref frames, 16 bframes+bpyramids (because bframes don't matter for cuda?)Right.What is the resolution limit? 4096x2304?
What about the bitrate limit, is it 960MBIT/S

Does 15 ref frames still work at that high resolution?
CoreAVC is currently limited to 2048x2048. If there is insufficient available memory on the video card software decoding will be used.

[Cyber-Mav]

how much video memory is required for 2048x2048 resolution decoding?

[tetsuo55]

CoreAVC is currently limited to 2048x2048.

Does that resolution still work with 15 ref frames?

Also what is the bitrate limit?

[CiNcH]

Still wrong field order for 1080i.

[BetaBoy]

Ok.. emails going out now for 1.9.5.

[Inventive Software]

The reliance of CUDA on DirectX is one more reason for them to switch to OpenCL I suppose.

[lucassp]

It would be really nice if OpenCL would offer access to VPx/UVD, but I really doubt that.

[LoRd_MuldeR]

Ok.. emails going out now for 1.9.5.

Got it. Thanks :)

[BetaBoy]

The reliance of CUDA on DirectX is one more reason for them to switch to OpenCL I suppose.
We will support OpenCL in CoreAVC and CorePlayer as well. What's going to be interesting is to see what works best in the long run since NVIDIA plans to support both efforts.

[BetaBoy]

Got it. Thanks :)

Great.... let me know if you run into any issues. But our regression testing has come up clean... so we don't expect many bumps with this release. But if needed we have 1.9.6 and upward to take care of them. However we would like for there to be only one more release prior to going to 2.0.... as the demands for CoreAVC 64bit on windows as well as our release for Linux is getting greater every day.

[Cyber-Mav]

betaboy does your internal testing of coreavc 64bit show any speed difference compared to 32bit?

[halsboss]

<dummy alert>
1. looked at the 1st page and the last couple of pages and coreavc.com and didn't recognise an answer ... does it come with an mp4/mkv splitter sort of like halli , or do I need to obtain one of those too to play MP4s with MPC ?
2. people here seem to use this codec, so I guess it's a recommended reputable one (if so I'll buy it) ?
</dummy alert>

[Shinigami-Sama]

<dummy alert>
1. looked at the 1st page and the last couple of pages and coreavc.com and didn't recognise an answer ... does it come with an mp4/mkv splitter sort of like halli , or do I need to obtain one of those too to play MP4s with MPC ?
2. people here seem to use this codec, so I guess it's a recommended reputable one (if so I'll buy it) ?
</dummy alert>

it comes with haali

its good, I'm waiting on 2.0 myself
grab a trail and see if its worth buying yourself

[lych_necross]

Yeah, no more blocking/corruption when I seek in files!!! :) Is the version of Haali's splitter different from the one posted on haali.net?

[Gleb Egorych]

BetaBoy, is it hardware/driver limitation that mixed progressive/interlaced content is not properly deinterlaced in "hardware deinterlace" mode? I wrote that here (http://forum.doom9.org/showthread.php?p=1249189#post1249189)

[deets]

all works with cuda on interlaced material now, i can watch my ITV HD games via dbviewer and claw back a few CPU % :)

edit: one thing, i would love to know how to get the purevideo deinterlacing via hardware to work with coreavc

[Dark Eiri]

Well, with 1.9.5, again, CoreCodec proves it does an excellent job! Up to this moment, it could play flawlessly, in CUDA, pretty much everything I throw at it! If it's some old encode with 16 ref-frames, it falls back to software mode, so it's really spot on! I was thinking to go ATi HD4870 for my next upgrade... well, guess I'll go GTX 260 now :D

edit: one thing, i would love to know how to get the purevideo deinterlacing via hardware to work with coreavc

Set the output to NV12 and it's sure to work.

[Disabled]

betaboy does your internal testing of coreavc 64bit show any speed difference compared to 32bit?
At least BetaBoy said something like that some time ago (I didn't find the posting though).

2. people here seem to use this codec, so I guess it's a recommended reputable one (if so I'll buy it) ?
I suggest you at least wait until a statement about v2.0 was made, else you would have to pay again in a short time if you want continued support.
You might try DivX7 though, its free and if it plays your videos CoreAVC will give you not much more (unless you need GPU acceleration for encoding or together with subtitle rendering)

[Kurtnoise]

A dummy question: where are located in the registry the CoreAVC settings ?

ok, found it but not in the registry :: User\xxx\AppData\Roaming\CoreAVC.ini


:thanks:

[BetaBoy]

Kurtnoise, yeah we store it in an ini to KISS it and only store whats absolutely needed in the registry to keep it (the registry) as clean as possible.

[deets]

I was thinking to go ATi HD4870 for my next upgrade... well, guess I'll go GTX 260 now :D



Set the output to NV12 and it's sure to work.

ot but i put in an order for a 4870 then quickly cancelled when i saw the 260 had dropped in price, partly due to the hardware advantages with nvidia

edit: and the deinterlacing didnt work, well not as i wished anyway. ffdshow handles the hardware deinterlacing fine and gives me a nice bobbed output but coreavc doesnt seem to do the same

[Dark Eiri]

Hey, BetaBoy, what's the chance of CodeCodec developing a VC-1 or even MPEG-2 codec with CUDA support? That would be awesome!

[Cyber-Mav]

mpeg2 decoding works great using nvidia purevideo decoder from nvidia. as for vc-1 you can decode that already in hardware with purevideo 3 (vpu3) capable gpu from nvidia.


also this 1.9.5 version is working great for me, no more crazy colours or blocking. i use cuda mode permanently now and its fantastic. old opteron 144 @ 1.8ghz with 8600gt = awsome media center machine now. no need to shell out on huge hardware upgrades now just to play hd video.

[Dark Eiri]

as for vc-1 you can decode that already in hardware with purevideo 3 (vpu3) capable gpu from nvidia.

But with no filters or even subtitles outside MPC.

[halsboss]

Very pleased with my purchase of the pro. It plays the immensely moving MattHardingDancing2008_720p.mp4 nicely.
Thanks.

[smit]

When version 1.9 was released i wrote about audio problems with spdif connection.
Using the latest build i`m having masive audio dropouts when i`m sending SPDIF to an external amp.

As it seems there is a problem with the latest Haali spliter and CUDA.
When i enable MPC-HC`s internal splitter in conjunction with CUDA everything is ok.

Hardware
Mobo Gigabyte GA-MA78GM-S2H - http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?ProductID=2758
VGA Gigabyte GV-NX86T512H - http://www.gigabyte.com.tw/Products/VGA/Products_Overview.aspx?ProductID=2604

Software
Vista 32bit
MPC-HC 1.2.908 final and 1.2.989 beta
CoreAVC 1.9
AC3 filter 1.51a
Slysoft Reclock 1.8.3.4


I tried many combinations and different options in my software setup but audio dropouts continued to occur quite frequently..I changed AC3filter to reencode the signal.I disabled Reclock.I did every possible combination i could think.I must add that it is the same for DTS and DD.

Only when i disable Haali or CUDA the sound is ok.

.

With 1.9.5 things are vastly improved and somehow changed.
Occasionally i`m having audio dropouts.Very few now (congrats) but annoying none the less.

The situation is changed from before.Now it has nothing to do with the splitter (Haali or MPC HC) and it is due to cuda solely.
If i disable Cuda i have no dropouts but when i enable it i`m having audio dropouts at random intervals.DD and DTS behave the same.


Keep up the good work!

.

[leeperry]

I'm having terrible jitter in HR w/ the latest official build, the latest beta before that worked a lot smoother...it hiccups every few seconds now, and works fine if I disable CUDA :o

I guess I should update my XP drivers though, but it's such a pain to recreate all the custom resolutions...which vanish after one reboot, so you have to create them twice :rolleyes:

[cyberbeing]

I guess I should update my XP drivers though, but it's such a pain to recreate all the custom resolutions...which vanish after one reboot, so you have to create them twice :rolleyes:
I assume that means you are using driver sweeper or cleaner to do a clean install of your driver.

If you export the CUST_MODE binary value from the registry beforehand, import CUST_MODE back into the registry after you have installed the new driver, and reboot, your custom resolutions will be back without having to input them again.

[leeperry]

I assume that means you are using driver sweeper or cleaner to do a clean install of your driver.

If you export the CUST_MODE binary value from the registry beforehand, import CUST_MODE back into the registry after you have installed the new driver, and reboot, your custom resolutions will be back without having to input them again.
yeah I tried that and I always use DriverCleaner too ;)
but it only worked fot my primary display(CRT), not secondary(pj)...and each time I input them on the pj, they vanish after the first reboot :rolleyes:
so I don't update frenetically anymore, like I did w/ the ATi drivers...I can tell you that :D

anyway, what are the best drivers for CoreAVC 1.95 on XP SP3 w/ a G92? the latest stable 182.08?

[ADude]

Is there any reason to update to 1.9.5 if one is not using CUDA ?