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

kieranrk

31st March 2011, 01:30

Too bad, too sad. It's too late for CoreCodec to try to remain relevant with their sub-standard products.

Lets just ignore their licensing business, right?

BetaBoy

31st March 2011, 09:33

thewebchat thx for your opinion and fud. But I think our customers and OEM partners might think otherwise and we thank them for their continued support.

hajj_3

31st March 2011, 11:11

what app can i use to check the fps with?

Virtual_ManPL

31st March 2011, 13:23

Will this bug be fixed in CoreAVC 2.5 release ?
http://forum.doom9.org/showthread.php?p=1390600#post1390600
That should be fixed.

I got reports that it's not fixed in version 2.5.1 :(

NikosD

31st March 2011, 13:56

Updated benchmark results with CoreAVC v2.5.1 (CPU & DXVA) vs CoreAVC v2.0 & others here:

http://forum.doom9.org/showthread.php?t=159486

Two comments:

1) CoreAVC v2.5.1 CPU is the fastest codec. Second best is CoreAVC again (previous version v2.0)

2) CoreAVC v2.5.1 DXVA has almost identical results with MPC-HC DXVA & FFDShow DXVA

eddman

31st March 2011, 15:01

I'm confused. Is 2.5's DXVA path Radeon only?

CruNcher

31st March 2011, 17:58

Nope its suited for both ATI/NVIDIA

CUDA support is only for NVIDIA though is almost useless (Playback) except for the to much reference bitstream case their it can help enourmously without losing hardware accelleration to display such streams on Nvidia Cards :) though it has a overhead compared to DXVA on Windows so it shouldn't be enabled by default and CoreAVC should get a Adaptive mode where it depending on the Bitstream can switch from DXVA/CUDA/SOFTWARE.
Mainconcept are the first ones who borrowed the idea from ffdshow and MPC-HC (the idea came from doom9) and implemented this Adaptive mode switching from DXVA to SOFTWARE if necessary to avoid Playback problems in their commercial decoder.

eddman

31st March 2011, 20:25

Thank you, CruNcher.

BetaBoy

31st March 2011, 21:11

We hope to have DXVA adaptive switching done within the next 2 releases.

hajj_3

31st March 2011, 22:37

so what can we expect in the next release?

BetaBoy

31st March 2011, 23:13

These are planned...

- DXVA Fallback when the stream isn't compatible
- DXVA Handling mid-stream resolution changes
- Different handling of quant matrices for ATI/NVidia
- Long slice mode / intel support
- Clean up/merge DXVA defines

However you can now add a fix to the 'seeking Open GOP issue' as we are going to add it as an option to turn it on or off, as it will effect seeking speed in directshow if on.

hajj_3

31st March 2011, 23:45

could you clarify what the intel support is, i've got a core i5 laptop, would i see any benefit? Do you think you can make the cpu decoding any better than it is now or have you pushed it to it's limit as my single core 32bit intel core solo 1.83ghz laptop still uses alot of cpu for 720p files and higher bitrate 720p is 100% cpu and jerky.

pankov

1st April 2011, 00:29

Guys,
I've just switched from ATI to NVidia and I have a question about frequencies/clocks and power consumption:
Is it normal that my new GeForce GTX460 switches to max 3D core/shader/memory clocks when I use CUDA decoding?
My old integrated NV9400 could decode the same H.264 video files so I can't believe that this new card which has 10 times the computing power will need to go in full power mode to decode them.
Currently I'm very disappointed because with full 3D clocks the card goes hot very quickly and the fans start to get loud. My old ATI 5750 (in DXVA mode) was switching clocks from the idle/desktop ones but not to the max ones and it's temperature raised just a little.
Can I control what frequencies/clocks does the card use for CUDA decoding? ... or at least for a given application ... or at least is there a way to switch power profiles via command line?

PaxRoma

1st April 2011, 04:49

Maccara

1st April 2011, 10:03

The teams are looking into the field order... but they already commented on how you get random field order changes when starting and seeking and how most renderers break.

On my system (XP x64, AMD, ATI 4850) I noticed this is also dependent on the splitter used. (Re-seeking a few times usually fixes this also)

With MP4 files (VMR9 renderless)
Haali: after seek random field ordering
MPC-HC internal splitter: same problem
LAV : OK (haven't managed to get wrong field order yet)

Anakunda

1st April 2011, 10:26

Hello, I Installed this codec for a try, and got following problem: KMPlayer won't use it's default codec anymore, instead ffdshow(libavcodec) is used to decode played AVC, resulting in improper AR including other impropernss. Anybody who also faced this problem knows why directshow is used although in KMPlayer internal codec is preferred?
Anyway do I need to use CoreAVC if I don't have speed issues with HD video? (In fact I have a small freezing on FullHD videos but I don't own much of them so it's not such a problem).

desta

1st April 2011, 11:19

tried coreAVC 2.5.1 to play x264 1080p movie and the picture will be jerky/stutter every 15-30 secs in full screen.Audio is not jerky but the picture is. This does not seem to happen in windowed mode. Is there a way to fix this. I have
Windows 7 Ultimate - N53JF Asus laptop. Nvidia driver 267.76
Player: WMP Decoder: CoreAVC CUDA on Splitter: Haali. Laptop is being used as a HTPC hooked up to a Sony TV
You might want to try downgrading your Nvidia drivers. Going back to 258.96 worked for me.

If it works I'm not suggesting this as a permanent fix, but just to test. If it does work though then obviously there's either a problem with the drivers or coreavc. I'm still waiting for anyone from the corecodec team to get back to me about it (even from the customer portal).

BetaBoy

1st April 2011, 16:14

Desta.... we are looking into your report, thanx.

Fadeout

1st April 2011, 17:02

I tried to see if it fixed the problem of OP and ED not working in certain anime that use different files/chapters. It does (while default DXVA would give problems).

On the other side there are blocks of colors everywhere, while standard DXVA works without any problems.

This on a ATI 4850.

BetaBoy

2nd April 2011, 10:58

Strike the option for the opengop fix as it will be on by default, as seeking speed is no excuse to ignore the spec.

Virtual_ManPL

2nd April 2011, 13:30

I would gladly see fix for this bug (http://forum.doom9.org/showthread.php?p=1390600#post1390600) in next version...

Any plans on this BetaBoy ?

Anakunda

2nd April 2011, 13:48

nobody knows why CoreAVC steals KMPlayer internal AVC codec?

Episodio1

2nd April 2011, 15:30

LOL ANAkunda... But you got late, April 1st was yesterday. ;)

Anakunda

2nd April 2011, 16:26

that's no LOL

ChronoCross

2nd April 2011, 18:31

nobody knows why CoreAVC steals KMPlayer internal AVC codec?

Got anything to back that up?

@BetaBoy

BTW it's good to see that 1.25 years of QC and this release was still buggy as hell. Might want to fire your QC team.

Anakunda

2nd April 2011, 18:36

Got anything to back that up?

Got something to back that up, but wanna know why CoreAVC interfers with KMPs codecs.

me7

2nd April 2011, 20:21

Got something to back that up, but wanna know why CoreAVC interfers with KMPs codecs.

Do you mean to say that Core AVC steals code from KMPlayer or that it forces itself to be loaded on playback instead of some internal decoder?
You previous post sounds like the former.

Anakunda

2nd April 2011, 20:29

Do you mean to say that Core AVC steals code from KMPlayer or that it forces itself to be loaded on playback instead of some internal decoder

Yes this is it. Registering CoreAVC codec forces KMP to use directshow extern codec instead of internal dependless I have chosen to prefer it.

BetaBoy

2nd April 2011, 20:46

Might want ....
The teams did and amazing job testing and considering the vast amount of work that went into CoreAVC v2.5, some of which your not even seeing yet.

Bugs are common place with major milestones... and we are following through with fast releases for 2.5 and 2.6 to adapt to this. We thank the beta teams for all their hard work with testing.

Otherwise on kmplayer... Pls refrain from FUD... post reg diff's to show we have done something diff from 2.0 to 2.5.. but from a short look at the code commits, we have not touched anything related to file association/type since 2.0 in the installer unless Haali did something with his. Ill ping the team on it.

BetaBoy

2nd April 2011, 21:35

I would gladly see fix for this bug (http://forum.doom9.org/showthread.php?p=1390600#post1390600) in next version...
madshi and I spoke about this several pages back.

CruNcher

3rd April 2011, 10:33

http://forum.doom9.org/showpost.php?p=1489508&postcount=1196

No bad result :)

http://www.multiupload.com/PYBILYB30E <- file tested

Actually this happens with almost every .m2ts stream and Haali + CoreAVC 2.5.1 DXVA @ least slice borders become always visible (NVidia VP2)
most x264 streams are fine (no slices no mbaff)

http://img43.imageshack.us/img43/2044/sliceborders.png

The more i look through my database the more streams i find that show strange results with CoreAVC DXVA and Nvidia, so i guess that you say for ATI UVD cards only currently has a valid reason so Nvidia user better switch to the green tray icon even if its a tad slower http://forum.doom9.org/showpost.php?p=1489410&postcount=48 that way you avoid seeing such rendering problems as above for some streams and of course the complete to much reference frames block attack ;)

BetaBoy

3rd April 2011, 15:27

Thx for the report CruNcher!

Fadeout

3rd April 2011, 16:44

PaxRoma

3rd April 2011, 16:48

You might want to try downgrading your Nvidia drivers. Going back to 258.96 worked for me.

If it works I'm not suggesting this as a permanent fix, but just to test. If it does work though then obviously there's either a problem with the drivers or coreavc. I'm still waiting for anyone from the corecodec team to get back to me about it (even from the customer portal).

still not working after the downgrade. Weird thing is that this picture stutter/jerk only happen in full screen mode.

CruNcher

5th April 2011, 20:58

Dan maybe some of your CoreCodec guys has a answer to this and know where the bottleneck might be (at least you worked a heavy time on implementing NVCUVID into CoreAVC with Nvidia) :) ?
http://forum.doom9.org/showpost.php?p=1490026&postcount=67
or do i get it wrong and the playback behavior is what should be expected on XP and G92 (VP2) ? compared to VMR7/9 windowed ?

Pyroshock

6th April 2011, 00:46

Nope, I have that problem with ATI.

Not those bars, but those blocks of colors everywhere on the image. See this:
http://img402.imageshack.us/i/45370501.jpg/

Works fine in MPC-HC DXVA and CoreAVC CPU. Is bugged with CoreAVC DXVA.

I have the same problem with my ATI card, and only when DXVA is enabled. My Blu-ray movies will have annoying blocky bands, or terrible glitches. It doesn't happen on lower bitrate files though, around 15,000 seems to be where it starts.

http://i.imgur.com/UdRKI.jpg
http://i.imgur.com/AAl2k.jpg
http://i.imgur.com/m0IUf.jpg

My card is a Mobility Radeon HD 4670.

Episodio1

6th April 2011, 02:38

CRUNCHER, i sent you a PM the other day, but I got no reply. :(

How did you get that M2TS from Canal+? Did you extract it straight from the official DVR ?

CruNcher

6th April 2011, 03:37

Sorry missed it, it's not by me its a sample floating around dunno how it was acquired from the source

BetaBoy

6th April 2011, 08:59

neograniceni

6th April 2011, 15:12

still not working after the downgrade. Weird thing is that this picture stutter/jerk only happen in full screen mode.

The same problem here. 257.21 works OK.

BetaBoy

6th April 2011, 15:33

Thanks for the hint, I uploaded and the link is at

http://www.mediafire.com/?lmnu387cdk0572r

Bug confirmed. We have not done a fix yet, but it is DXVA related.

desta

6th April 2011, 22:43

Desta.... we are looking into your report, thanx.
Thanks, but the last time I heard anything from support was March 29th.

BetaBoy

7th April 2011, 07:59

Thanks, but the last time I heard anything from support was March 29th.

That's because I replied to you here. The support staff monitors this thread daily.

Anakunda

7th April 2011, 16:49

I have found a HD video that causes CoreAVC to crash. Using it together with KMPlayer and Haali Splitter. Can I generate an diagnostic report, or change some settings to be able play this video with CoreAVC?

toomyzoom

9th April 2011, 19:25

I feel like wasting $10 for this pathetic performance in DXVA. I got the same problem like http://forum.doom9.org/showpost.php?p=1489520&postcount=6232. On the same video, MPC-HC's internal DXVA decoder gave no problems. It does a better job than Coreavc. Moreover, CoreAVC's DXVA mode can't be used together with MadVR renderer, only EVR or EVR-CP. Taking too long to release an unfinished product.
Even with CUDA, there are a lot of playback problems that's not even exist in 2.0. Coreavc 2.5.1 takes forever to load and sometimes just stuck at opening the videos.

Anakunda

9th April 2011, 19:27

and sometimes just stuck at opening the videos.

exactly

madshi

9th April 2011, 19:38

Moreover, CoreAVC's DXVA mode can't be used together with MadVR renderer, only EVR or EVR-CP.
That's not really Core's fault, though. madVR simply doesn't support DXVA (yet?).

CruNcher

9th April 2011, 19:45

I guess you both ask the guy who develops it, who was it again, wasn't it this German guy geez cant remember his Online name maradshi ? ;)

toomyzoom

9th April 2011, 20:01

That's not really Core's fault, though. madVR simply doesn't support DXVA (yet?).

Hi madshi, I hope you can make MadVR support DXVA. EVR-CP gave me terrible black level and sharpness.

BetaBoy

9th April 2011, 22:35

exactly

Pls post samples of any such videos for us to look at

As far as DXVA is concerned... Give us a little time to address both the bug reports and upcoming dxva specific features we have planned in the todo. We will continue to push out fast releases as they pass QA.... and to that you can likely expect a new version this coming week if all goes well.

Our timeline is short for finishing DXVA (3 months) compared to almost a year of preparations and work to get it to where we are at now.... We thank everyone for their continued support and the D9 community for some amazing feedback.