CoreCodec/H.264 Codec "CoreAVC" [Archive] - Page 117

Cyber-Mav

17th March 2010, 18:57

On a side note we are also working on finalizing our CoreASP (DivX) directshow filter (and OEM SDK) for a QA release internally... the initial public release will be afterwards. No CUDA on the initial release, but it is planned.

i once asked if corecodec would expand the cuda support to cover the functions of the new nvidia VP4 processor (it has hardware mpeg4-asp (divx xvid) decoding support) and you betaboy said that you wont be going down that route since you want to stick to a pure AVC platform.

now your going back on your stance?

eddman

19th March 2010, 18:54

i once asked if corecodec would expand the cuda support to cover the functions of the new nvidia VP4 processor (it has hardware mpeg4-asp (divx xvid) decoding support) and you betaboy said that you wont be going down that route since you want to stick to a pure AVC platform.

now your going back on your stance?

You do know that coreavc and coreasp are two different products, right? Betaboy said that coreavc would remain an avc only codec, that's all.

Mixer73

25th March 2010, 14:14

Dumb question I know but is there any way to hack iTunes to use CoreAVC as a codec? Playback of h264 in iTunes SUCKS!!!

laserfan

25th March 2010, 19:35

iTunes SUCKS!!!
I completely agree!!! ;)

Blue_MiSfit

25th March 2010, 21:20

That's because iTunes uses QuickTime, and QuickTime in windows (in general) is epic lulz.

I can't imagine there's a way to make iTunes use DirectShow or something like libavcodec.

~MiSfit

ChronoCross

26th March 2010, 03:54

HAs anyone had trouble with CoreAVC where deeking takes forever? I just tried DivX's new codec and seeking is instant while CoreAVC is delayed by 1-2 seconds.

Dark Shikari

26th March 2010, 04:03

HAs anyone had trouble with CoreAVC where deeking takes forever? I just tried DivX's new codec and seeking is instant while CoreAVC is delayed by 1-2 seconds.Do they both do frame-accurate seeks?

It might be that CoreAVC is seeking to the frame, while DivX is rounding to the nearest keyframe.

ChronoCross

26th March 2010, 23:58

Do they both do frame-accurate seeks?

It might be that CoreAVC is seeking to the frame, while DivX is rounding to the nearest keyframe.

Could be, it was more of a casual observer notice than a in depth analysis.

hydra3333

27th March 2010, 22:33

Over at http://forum.doom9.org/showthread.php?p=1386569#post1386569 it looks like new haali coming up soon. Will updated version of coreavc be released with it inside when it is released ?

roozhou

3rd April 2010, 17:17

@BetaBoy:
Found a new bug in CUDA decoding.

OS: WinXP SP3
CPU: Single-core Sempron 2500+(754)
Video Card: 8500GT 128M

When decoding 1920x1080 AVC videos, it shows distorted image after the first GOP. It plays OK with MPC-HC DXVA and ffdshow DXVA, and all SW decoders including CoreAVC

With old nVidia drivers, 8500GT card with 128M on-board vram cannot decode 1920x1080 AVC video with HW acceleration. I got this information from the video card vender one years ago. With some tests I found that neither DXVA nor CUDA could decode AVC w/ width>=1856. e.g. 1920x800 doesn't work but 1440x1080 works.

It seems this issue was fixed in 196.21 driver though not mentioned in driver's changelog. DXVA works perfectly on 1920x1080 video with 196.21 and latest 197.13, but still no luck for CoreAVC CUDA. Could you investigate on this problem?

Cyber-Mav

3rd April 2010, 21:04

i believe you need a graphics card with 256mb memory onboard to do the cuda decoding properly.

Keiyakusha

3rd April 2010, 21:31

eddman

4th April 2010, 12:00

On a side note we are also working on finalizing our CoreASP (DivX) directshow filter (and OEM SDK) for a QA release internally... the initial public release will be afterwards. No CUDA on the initial release, but it is planned.

How much would CoreASP cost? Also, any chance on seeing a new CoreAAC and CoreVorbis? I don't really like ffdshow. It's been in beta for too long.

me7

4th April 2010, 13:38

i believe you need a graphics card with 256mb memory onboard to do the cuda decoding properly.

I can do it on my 128mb 8400M GS but only with "Overlay Mixer" as renderer.

roozhou

4th April 2010, 13:59

I can do it on my 128mb 8400M GS but only with "Overlay Mixer" as renderer.
I am also using Overlay Mixer.

@Cyber-Mav
CUDA decoding does not use stream processor but uses the PureVideo unit which is also used by DXVA.

eddman

4th April 2010, 14:24

CUDA has nothing to do with purevideo.

LoRd_MuldeR

4th April 2010, 14:28

CUDA has nothing to do with purevideo.

That is right. However CoreAVC doesn't use CUDA. They did not implement a custom H.264 decoder as CUDA kernel. Instead they use the "hardwired" PureVideo decoder chip.

And they access the decoder chip through the CUDA Video API (CUVID), instead of through DXVA. That's why they call it "CUDA", although CUDA isn't involved in fact.

The advantage of accessing the PurVideo decoder chip though the CUVID API is that you can get the decoded frames back to host memory, something which DXVA can't do easily.

Also implementing your own H.264 decoder as CUDA kernel would be pointless with PureVideo available, because nothing beats a dedicated decoder chip efficiency-wise.

LoRd_MuldeR

4th April 2010, 14:38

This is a wierd way to use the purevideo engine. Why they didn't use DXVA in the first place?

It's not wierd at all. DXVA is a playback-only technology. It only works in combination with a suitable renderer (e.g. EVR) and the renderer won't return the decoded frames to the software.

If you want to process the decoded frames in a software (e.g. Avisynth) instead of presenting them on the screen, then DXVA isn't suitable. But CUVID does it easily.

Furthermore DXVA has some harsh restrictions on which H.264 levels/profiles are supported. AFAIK these restrictions don't exist for CUVID, so it allows using the full capabilities of the decoder chip.

BTW: Somebody claimed you can get back the frames from DXVA by implementing a custom renderer, but that's certainly more work and potentially less stable than simply using CUVID.

kieranrk

4th April 2010, 17:19

It's not wierd at all. DXVA is a playback-only technology. It only works in combination with a suitable renderer (e.g. EVR) and the renderer won't return the decoded frames to the software.

The newer version of DXVA for Vista upwards is not playback-only. This is why ffmpeg can use it for input and ffdshow can run full post-processing on it.

8th April 2010, 10:58

The newer version of DXVA for Vista upwards is not playback-only. This is why ffmpeg can use it for input and ffdshow can run full post-processing on it.
I followed the ffdshow development thread back then and they seemed to have problems getting the decoded video back to main memory fast enough (http://forum.doom9.org/showthread.php?p=1367471#post1367471), so they had to disable this feature. CUVID seems to make this much easier.

FFmpeg's DXVA2 input support is news to me (I thought it was output-only, like the VDPAU implementation). Is it fast?

turbojet

12th April 2010, 19:56

While doing some benchmarks I ran into surprising results from graphstudio decoder performance of CoreAVC 2.0 with null renderer.

32 bit: 00:00:02.775 work time, 500.3729 fps
64 bit: 00:00:02.917 work time, 472.7088 fps

While libav, ffmpeg-mt, wmv9 (from wmp12) and libmpeg2 64 bit is running about 5% faster then 32 bit with the same benchmark.

Does anyone have any idea why 64 bit coreavc is slower than 32 bit? Are there plans to improve the performance of coreavc 64 bit?

archy141

14th April 2010, 13:06

I intend to use CoreAVC 2.0 as the decoder with HDConvertToX to rip my Blu-Ray collection onto a media server as X264 MKV files.

Can someone tell me what settings the Input & Output Levels on the configuration page of CoreAVC should be set to. The video files are to be streamed using a PS3 & viewed on a 50" Pioneer Plasma TV (36bit deep colour supported). I do not want to get colours crushed etc. Please offer guidance.

BetaBoy

19th April 2010, 23:55

CruNcher

20th April 2010, 08:57

BetaBoy is this reproduceable on your side ? Win XP
http://forum.doom9.org/showthread.php?p=1393211#post1393211

BetaBoy

21st April 2010, 00:40

That has been fixed as well.

Keiyakusha

24th April 2010, 21:34

Any chance for better support for h264 streams with variable resolution?
With different scenarios CoreAVC shows corruption or crashes. ffdshow seems to handle them right. Tested in graphstudio.

BetaBoy

24th April 2010, 23:53

Any chance for better support for h264 streams with variable resolution?
With different scenarios CoreAVC shows corruption or crashes. ffdshow seems to handle them right. Tested in graphstudio.

It's been fixed and will be in the next release.

hajj_3

25th April 2010, 10:16

I don't suppose you are able to give an ETA on the next version?

7ekno

25th April 2010, 11:51

Next version being 2.1?!?

Sorry, haven't seen a download in the "support" section of the login site for a while, so was just checking !

7ek

archy141

26th April 2010, 00:53

Someone please..

What settings should the Input & Output Levels on the configuration page of CoreAVC be for playback on a Plasma TV to avoid colours crushing etc..? Auto/PC/TV ?

Keiyakusha

26th April 2010, 01:59

archy141
If you have some particular problem with levels - give more info about what you using for playback.
If there is no problems - leave everything at defaults.
Also you can try to set Input as TV and output to "whatever works for you"

BetaBoy

5th May 2010, 23:19

We are looking for a few 'well rounded' testers with multiple OS's config's to test CoreAVC's new support for both DXVA 1 and DXVA 2. Email: info AT corecodec DOT com with your system config (OS, Video card, etc.) and what apps you use now with DXVA support. Thx in advance!!

merlinmage

8th May 2010, 14:17

I have one question about the usage of CoreAVC:

Currently I use the CCCP codec pack with ffdshow as the default decoder. Now I installed CoreAVC 2.0 and want every H264 video source to be encoded with it. It is enough to change only the default decoder to CoreAVC in the CCCP settings to make the codec work?

Like this:

http://www.abload.de/img/unbenanntno4g.png

Virtual_ManPL

8th May 2010, 17:37

How about fixing these bugs in v2.1 ?
At last this first one, cause IMO is very important...

1. http://forum.doom9.org/showthread.php?p=1390600#post1390600
2. http://forum.doom9.org/showthread.php?p=1347803#post1347803

squid_80

8th May 2010, 17:40

Virtual_ManPL

8th May 2010, 19:11

Maybe... so how about improving CoreAVC to not show this "bad frames" like MPC-HC or DiAVC decoder ? ;)

pankov

9th May 2010, 13:34

PM me with the ticket # and I'll get the team on it here this morning to see what the hold up is.
Betaboy,
this bug is still not addressed. It's more than 4 months now and I still haven't receive any answer from you or the core team.
Recently I upgraded my main PC which uses ATI Video card to Windows 7 and I get the same wrong field order problem with it.
How is anybody else using hardware deinterlacing in Win7 and Zoomplayer?
What could be wrong in my setup??

BetaBoy

19th May 2010, 23:01

FYI... a new Haali Splitter has been released that addresses the VC-1 and TS issues as well as it now adds support for 'WebM' content. See: http://haali.su/mkv/

clsid

19th May 2010, 23:07

Great news!

Is CoreAVC 2.1 following soon?

shon3i

19th May 2010, 23:39

Thanks for new Splitter, still have issues with VC-1 and DTS-MA audio (audio is not recognized at all), while is completly normaly working H264 + DTS-MA combination.

i confirm that Mp4 synch is fixed
and TrueHD tracks are recognized fine.

BetaBoy

20th May 2010, 01:08

Great news!

Is CoreAVC 2.1 following soon?

Technically we are done with DXVA 1 and DXVA 2... but are working on specific 'flavors' of DXVA 2 now that are causing QA to take longer then anticipated.... well that and with us working with Google on WebM has taken away our focus a bit.

hajj_3

20th May 2010, 08:46

strange, just tried playing a .webm file with WMP on win7 x64 after installing the new haali splitter, unfortunately it won't play :(

Astrophizz

20th May 2010, 09:47

You have to have a decoder in addition to the splitter ;)

hubblec4

22nd May 2010, 14:12

FYI... a new Haali Splitter has been released that addresses the VC-1 and TS issues as well as it now adds support for 'WebM' content. See: http://haali.su/mkv/

yeah, but new issues were in this build. the DTS-MA were not regonzied corectly.

BetaBoy

22nd May 2010, 15:09

Its a step is a step..... I have pinged Haali on the issue.

Virtual_ManPL

22nd May 2010, 17:17

BetaBoy any chances that these bugs which I mentioned (even on PM) will be fixed in next version ?
Or at least only first one, because it's serous problem...

BetaBoy

22nd May 2010, 20:31

BetaBoy any chances that these bugs which I mentioned (even on PM) will be fixed in next version ?
Or at least only first one, because it's serous problem...

Squid has already stated that your streams are invalid.

pankov

22nd May 2010, 22:46

BetaBoy,
what about my problem?
It's more than half an year now and the problem is still present. The worst part is that I don't get any answers neither here nor through PMs nor at the CoreCodec ticket system.
What's going on?

HI
I've been using CoreAVC since it's first version and was pretty pleased with it's performance and quality. Recently I noticed that I have problems with the Hardware Deinterlacing when used with VMR9 or EVR. I thought the problem was either with my hardware or windows installation since it was more than 3 years old XP Professional. Recently I did reinstall my XP (SP3) with all updates and most recent drivers and DirectX and .NET 3.5 and sadly the problem is still there.
With EVR I don't get any deinteralacing ... which I suppose is normal since I use it in WinXP ... can somebody confirm/deny this?
With VMR9 it seams like there is problem with the field order - I don't see any jaggies but there is no fluid motion but total jerkiness.
With Overlay Mixer or Halli everything is butter smooth.
On this PC I use Gigabyte P35 mobo + Intel Quad Q9400 + ATI 4670.
To isolate the hardware as the source of the problem I build a totally different PC with NVidia GF9400 chipset and I decided to put Windows 7 on it.
The problem is still there and sadly in Win7 Overlay Mixer doesn't work (which I think I read somewhere that is normal) so I'm very frustrated now.

What can I do to get smooth playback of interlaced H264 content (50Hz 1080i - EurosportHD / BBC HD)?
What do you guys/gals use?

If needed I can provide samples but I doubt the files are the problem.