CoreCodec/H.264 Codec "CoreAVC"

[nussman]

Of course this is related to CoreAVC decoder.
DVBViewer Splitter works fine with other DXVA decoder like Powerdvd, Arcsoft, Microsoft, ...

[molitar]

Betaboy, is the issue being addressed that we can not switch screens with the latest CoreAVC when using DXVA?

[BetaBoy]

Yes... we are looking into a fix.

[CruNcher]

Dan did you look into this http://forum.doom9.org/showpost.php?p=1496944&postcount=6326 it happens also in Software Decoding other Decoder recover fine after the error only CoreAVC becomes unstable dropping frames after it regularly till the end.

[flapane]

BetaBoy do you also have any hints for us with hdtv dvb issues as posted above?
Thanks

[BetaBoy]

CruNcher... thx for the files and info... we are looking into that as well.

[nussman]

I uploaded a testfile (1080i50) with some screenshots so you can test the deinterlacing issue and the dxva problem with dvbviewer splitter.

http://www.file-upload.net/download-3423885/coreavc_dxva_test.zip.html

P.S. My System: Win7 32bit, Ati HD5670 (latest driver)

[CiNcH]

with some screenshots
So what's the conclusion of these screenshots? The TV image is too small to determine whether fields are swapped...

Are fields swapped with all three splitters? Guess not?

Here is how I interpret the screenshots:

With DVBSource we see a jitter of 20ms at the renderer, which is exactly the duration of one frame at 50 fps which is constructed of one field.

With Haali Media Splitter everything seems fine? At least according to the EVR statistics.

[nussman]

The conclusion should be that Betaboy or the other dev's see what i did.

Fields swapped with all three splitters.
With my testfile (quick sport- real interlaced content) the issue is obviously.
Imho there is no need of other screenshots to show it ...

[dead_screem]

I uploaded a testfile (1080i50) with some screenshots so you can test the deinterlacing issue and the dxva problem with dvbviewer splitter.

http://www.file-upload.net/download-3423885/coreavc_dxva_test.zip.html

P.S. My System: Win7 32bit, Ati HD5670 (latest driver)
a question about this for tech people.
Mediainfo detects his sample as "Interlaced", does this mean PAFF? as mediainfo will Show MBAFF if it is. Mediainfo also detects TFF field order, Is interlace filed order even specified in the h264/avc stream or is it specified in the ts container only? If it is not in the stream does that mean CoreAVC always assumes BFF? (which would really warrant a field order Auto/TFF/BFF option if it is always assuming one order...) If it is only specified in the ts container, could haali or other splitters pass on the correct field order to the decoder?

Also media info doesnt show filed order for the mbaff files ive seen, is this because they were actually mbaff progressive or some other reason?

[flapane]

Of course this is related to CoreAVC decoder.
DVBViewer Splitter works fine with other DXVA decoder like Powerdvd, Arcsoft, Microsoft, ...

Here's also a screenshoot of WinTV with the CoreAVC blue tray icon even if DXVA is enabled.
HD5670 also here.
http://i.imgur.com/4Neoys.jpg (http://i.imgur.com/4Neoy.jpg)

[dipl_ing]

Same issue here with DVBVIEWER and HD channel.
Hope to get a bugfix soon.

[desta]

In fact I did say we were looking into your report. Thank you supplying the additional info.Nearly 3 weeks since your last reply and still nothing. Infact, 2 months since I first raised a ticket.

[desta]

Are your support on some sort of wind up?!

Just received this email:

CoreCodec, Inc.

This is a notification to let you know that we are changing the status of your ticket #XXXXXX to Closed as we have not received a response from you in over 72 hours.

Subject: Jerky playback with Coreavc 2.5
Department: CoreAVC
Priority: Medium
Status: Closed

----
The CoreCodec Team
http://CoreCodec.com

I have been waiting since 29th March to hear back anything from your backwards support. Each time I've mentioned it here, all I'm told is "we're looking into it" or "they don't reply via the portal as they monitor the forums"... really??! What forums do they monitor, pray tell, because they don't seem to have a clue what's going on here.

Worst service ever!

[flapane]

all I'm told is "we're looking into it"

I wish I received a "we're looking into it" as well... All I got was... nothing :)

[pankov]

Are your support on some sort of wind up?!

Just received this email:
CoreCodec, Inc.

This is a notification to let you know that we are changing the status of your ticket #XXXXXX to Closed as we have not received a response from you in over 72 hours.

Subject: Jerky playback with Coreavc 2.5
Department: CoreAVC
Priority: Medium
Status: Closed

----
The CoreCodec Team
http://CoreCodec.com



I have been waiting since 29th March to hear back anything from your backwards support.
....
Today I received the same ridiculous e-mail only in my case it's about ticket 175597 - Wrong field order.
Why would CoreCodec close a ticket which they haven't solved or even bothered to respond to.
I'm really disappointed with their support.
:(

[BetaBoy]

I closed the ticket... I did state we were "looking" into the potential issue 3x to you here on D9. Please have patience while we continue to work hard on the next few releases.

[pankov]

BetaBoy,
I just thought it's strange to close an unresolved ticket especially with such a reason "...we have not received a response from you in over 72 hours". How am I supposed to know that I'm supposed to respond to something since you've never bothered to write anything there?
And about being patient - don't you think that an year and almost a half is patient enough? About a field order problem? I may oversimplify things but I can't believe that it's so hard to implement a proper field order detection ... or if it's really that hard - simply make it an option for the user to choose ... it's not that CoreAVC makes a mistake in the detection from time to time - it's always wrong so a simple option should solve it ... I hope. If you have more information on the subject that will help me understand the complexity of the problem, please, do say, cause it's very frustrating to be left in the dark. "we are looking into it" isn't enough.

[dead_screem]

betaboy, could you post an update on these statuses

still CoreAVC is the only support ticket option... No CoreAAC and no General (should there be others?)

the Corecodec forums are busted I think someone else here mentioned, apparently it's impossible to post.
And forgot password doesn't work for the corecodec forum, or possibly it works but comcast can't receive it?

[BetaBoy]

No CoreAAC and no General (should there be others?)


CoreAAC department database bug fixed. Thx for the report, you can post tickets again to it.

[BetaBoy]

"we are looking into it" isn't enough.
Sorry that's not good enough for you, but we are looking at your reports. When we have more to report we will post to your ticket or here on D9. Thank you for your help.

[desta]

I closed the ticket... I did state we were "looking" into the potential issue 3x to you here on D9. Please have patience while we continue to work hard on the next few releases.
2 months!!

It's really not worth doing the "I told you 3 times" routine, when you and your own support don't know what the other is doing!

I first went to your support and got no response, so came here and had to give the same info I'd already given to them. When I did eventually hear from your support it was to ask a question you had already asked. Despite the fact I had already said it and they already apparently "monitor the forums" I gave the info again. I then supplied additional info to support, which... guess what... I had to give again to you here.

You told me your support is looking into it. Doubtful. You told me "30+ beta testers" cannot duplicate my results. I'm not having issues with a beta... though it might as well be. Try getting your support to do it instead. Look through this very thread and you'll see other customers who have the same or very similar problems and those that even had to roll back their Nvidia drivers to fix it.

[BetaBoy]

I first went to ..
This has nothing to do with Support atm as its out of their hands... it has to do with the engineers duplicating and finding the issue first. While we have had a few reports of this the engineers and the all beta testers have not come across it.

We will continue to see what the issue might be.

[Audionut]

engineers

Plural? :eek:

[upyzl]

forget to update 2.5.5 info here?

[CiNcH]

This shit is in such a bad shape... no support in DVBViewer with DVB Source at all, still no proper deinterlacing, no on-the-fly format change in DXVA mode...

Are you serious guys? Come on! Now you tweet that you are working on 10-bit support for CoreAVC 3.0? You just can't be serious!

[BetaBoy]

We are more then capable to multi-task. We are continuing to work on DXVA features and reported issues. This includes us adding support for 10bit to both CoreAVC 3.0 and CoreMVC.

[flapane]

Lack of dxva acceleration while watching DVB HDTV should be a priority (and it isn't just because I have this problem, too), just my two cents... Hope you're working on it.

[BetaBoy]

We are and other features for the next release.

[flapane]

Thanks

[molitar]

Wonders if a fix will ever come out with the lock up when switching screens is ever going to be fixed. I have had to stop using CoreAVC completely because of this very horrendous bug.

[cyberbeing]

Now that coding CoreAVC 9/10-bit support is well underway, is it clear whether you plan to support actual 10-bit output (to madVR for example) from the get-go, or will all high bit-depth output be dithered down to 8-bit?

[BetaBoy]

We completed 10 bit support in CoreAVC 3.0 last week and are on assembly optimization's now and looking into DXVA GMA support. We also just finished adding MVC 3D support to Haali's Splitter for CoreMVC which should be out around the same time or soon after CoreAVC 3.0 next month.

[cyberbeing]

So will CoreAVC 3.0 always be doing 10-bit to 8-bit conversion similar to FFDShow/libav w/ swscale, or will it actually be able to output 10-bit as 10-bit or 16-bit? Not immediately important for 3.0, but it would be nice to have it supported at some point. If you can beat FFDShow in the turtle race to support high bit-depth output, that would be a bonus. I assume CoreAVC has the advantage of a clean codebase to implement such a thing.

[BetaBoy]

The CoreAVC 3.0 SDK Library (for OEM's) will output 10-bit yuv (Technically 3.0 already supports 16-bit as well). However, the directshow filter will initially dither the output to 8-bit... We are working on adding some additional output options like you mentioned on 10/16 as 3.0 progresses, including 4:4:4 and 4:2:2 support. We are trying to keep up with the x264 features set ;-)

[Barlow]

With all this talk about CoreAVC 3.0 I'm wondering whether DXVA will still be fixed in 2.X. Because as it is now, it's unusable for me (Radeon 4850) as a lot of files cause the decoder to stop decoding. I reported this a while back.
I hope it will still be fixed as this makes the whole 2.5/2.6 series pointless :(

[Maccara]

With all this talk about CoreAVC 3.0 I'm wondering whether DXVA will still be fixed in 2.X.
Probably not.

[nussman]

and are on assembly optimization's now and looking into DXVA GMA support.
Please dont forget about the deinterlacing issue.

Without fixing this problem your decoder is completly useless for any real interlaced content.

[molitar]

The issue hasn't been fixed that I seen with 2.5.x where switching to full screen doesn't crash the player. And your already talking about 3.x.

[BetaBoy]

molitar... I have asked you before, but pls stop spamming the thread. We have your report on the issue, thank you.

[josephwright]

Please dont forget about the deinterlacing issue.

Without fixing this problem your decoder is completly useless for any real interlaced content.

Yes please fix the deinterlace field order issue. I purchased CoreAVC for use with UK Freesat HD content but it's been unusable due to this. After reading through this thread I find it incredible that such a simple core issue has remained unresolved for so long.

[BetaBoy]

You think this is 'simple'? It's not... if it were we would have a work around for it. But to be clear here.... EMR7 = Fine with no issues.... VMR9/EVR has a bug that allows field order to become random at times in directshow/dxva/xp (play, pause, etc.). The staff here along with Haali himself has confirmed the VMR9 bug and that CoreAVC sets the field order properly when playback begins like it should.

MS had released a patch that was supposed to fix the issue, but it did not fix it for everyone.

NOTE: Try the hotfix here to see if it helps: http://support.microsoft.com/kb/919071

[Chumbo]

I noticed today that CoreAVC does not play back correctly nor deinterlace streams captured with the Hauppauge HD PVR 1212. I just don't get any smooth playback of these with DXVA or without. Here's the MediaInfo info on one of the files. Let me know if you guys want a sample. I'm using an ATI HD 5670.
General
Unique ID : 198612688816049830842616612295414293371 (0x956B6997CE0FF7CE81B1037D4AF6A37B)
Complete name : E:\Media\video.mkv
Format : Matroska
Format version : Version 2
File size : 101 MiB
Duration : 1mn 16s
Overall bit rate : 11.0 Mbps
Encoded date : UTC 2011-07-03 17:09:05
Writing application : mkvmerge v4.8.0 ('I Got The...') built on May 24 2011 03:12:58
Writing library : libebml v1.2.0 + libmatroska v1.1.0

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L4.0
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Muxing mode : Container profile=Unknown@0.0
Codec ID : V_MPEG4/ISO/AVC
Duration : 1mn 16s
Bit rate mode : Variable
Bit rate : 10.4 Mbps
Maximum bit rate : 20.0 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 60.000 fps
Original frame rate : 30.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Top Field First
Bits/(Pixel*Frame) : 0.084
Stream size : 95.4 MiB (95%)
Color primaries : BT.709-5, BT.1361, IEC 61966-2-4, SMPTE RP177
Transfer characteristics : BT.709-5, BT.1361
Matrix coefficients : BT.709-5, BT.1361, IEC 61966-2-4 709, SMPTE RP177

Audio
ID : 2
Format : AC-3
Format/Info : Audio Coding 3
Mode extension : CM (complete main)
Codec ID : A_AC3
Duration : 1mn 16s
Bit rate mode : Constant
Bit rate : 384 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 3.52 MiB (3%)
Language : English

[BetaBoy]

I noticed today that CoreAVC does not play back correctly nor deinterlace streams captured with the Hauppauge HD PVR 1212. I just don't get any smooth playback of these with DXVA or without. Here's the MediaInfo info on one of the files. Let me know if you guys want a sample. I'm using an ATI HD 5670.


What OS? What renderer?

[Chumbo]

What OS? What renderer?
Win7U64 using MPC-HC x64 with EVR Custom Pres.

[EDIT] I went ahead and uploaded a sample (http://www.mediafire.com/?z6bg69q1nqiwgri) anyway. I also get different results playing the files. My desktop has a HD 4800 series card and laptop has a HD 5700 series mobility. Laptop hardware deint is a little better.

[josephwright]

You think this is 'simple'? It's not... if it were we would have a work around for it. But to be clear here.... EMR7 = Fine with no issues.... VMR9/EVR has a bug that allows field order to become random at times in directshow/dxva/xp (play, pause, etc.). The staff here along with Haali himself has confirmed the VMR9 bug and that CoreAVC sets the field order properly when playback begins like it should.

MS had released a patch that was supposed to fix the issue, but it did not fix it for everyone.

NOTE: Try the hotfix here to see if it helps: http://support.microsoft.com/kb/919071

Hi BetaBoy,

I think we are talking about different problems.

The problem I am refering to is not 'random'. In my experience all UK DVB h.264 streams get deinterlaced incorrectly when using hardware deinterlacing. I believe this problem has been reported numerous times within this thread. To highlight a few of these:

pankov's posts numbered 4984, 5840, 6122, 6125, 6172, 6328 & 6369.

CiNcH's posts 6126 & 6127.

nussman's posts 6303 & 6358.

Just to confirm this issue only occurs when 'hardware' is selected as the deinterlacing option in the CoreAVC configuration panel. The symptom is nasty jaggies on sharp diagonal edges. I have attached cropped images of the same scene decoded with both CoreAVC and Microsoft codecs. Both were using EVR and hardware dxva deinterlacing (ati vector adaptive). I'm not certain if the problem is field order related, although that would make sense going by the way it looks. If it is the field order then pankov's suggestion of an "Auto/TFF/BFF" configuration option would seem like a easy way to deal with it.

I am using these codecs within Mediaportal to play live/recorded UK h.264 DVB streams (BBC HD, BBC ONE HD, ITV HD, CHANNEL 4 HD). OS is Win7 32 bit, GPU is an ATI 5570GT (same results with both 11.4 and 11.6 drivers).

Please let me know if I provide any more info to help you fix this issue.

[BetaBoy]

josephwright.... please send the attachment to: betaboy AT corecodec DOT com

Thank you for all your help and we will review what you sent.

[The Seeker]

When I bought CoreAVC 2.0, I was of the understanding that I was purchasing a lifetime license. Why is it that I now have to pay to upgrade to 3.0 when it's released?

[BetaBoy]

Nothing has changed in upgrades and how we handle them for milestone releases, other that with 3.0 we have had a longer period of time spent on the 'Core' work (almost 2 years) Meaning what that while 2.x shares the same 'cores' they are not the same and we have made huge investments in making our code more modular and highly optimizing 'anything' assembly. In return we added 10bit support, that instead of slowing playback (FFmpeg saw a 1-2% hit when they added 10-bit), it has actually improved performance playback for some CPU instruction sets.

Bottom line its a milestone release... 2.x got you 2.x updates, not 3.x.

We thank you for your continued support.

[pankov]

BetaBoy,
can you tell us a little more about your plans.
Will CoreMVC be a separate product which we'll have to buy separately or it will be part of the new CoreAVC 3.x? If it's the first will there be any discount if we buy one more license for CoreAVC now or it'll be better to wait?
I'm willing to support your work and buy a new license but I'm kind of reluctant to buy CoreAVC only for the added 10-bit support. I've hoped for something more ... may be fix the deinterlace issue ;)