CoreCodec/H.264 Codec "CoreAVC"

[bob0r]

http://icanhascheezburger.files.wordpress.com/2007/04/469761052_6f055c51e9.jpg

@BetaBoy
I have reported my findings to BlackSun, a lot more work for dvbviewer is needed, and please fix the green frames issue.
Deblocking skip seems to work again, and fix the small typo in the settings window.

My advice: Do not release anything yet! :sly:

[BetaBoy]

thx... As Haali has indicated the The initial greenframe issue is not as easy as you may think to fix as it pertails to black level(iirc). The continued DVBViewer slowdown on the other hand is something we are already aware of.

http://www.lolcats.com/images/u/07/38/lolcatsdotcom8k6kwv7su7go3xqo.jpg

[silverwolf0]

I am having problems with playing back H.264 videos with coreavc. I have K-lite codec pack installed and it has coreavc 1.5 by default for playing h.264 files. However, videos will freeze sporadically when I play them, usually in fullscreen, and the only way to unfreeze is to cold boot my laptop. When I switch to FFDshow to play H.264 videos, all the freeze-ups disappear but the sound is a bit out of synch. Sometimes the voices are early and sometimes a bit late so it looks like bad lipsynching. When I play MKV files with subtitles, the subtitles go in tune with the sound, but out of synch with the video as well.

How should I solve this problem? I am currently still using coreavc 1.5 as I cannot stand watching the videos out of synch. However, having to coldboot is a constant annoyance also. Someone please help.

[Dark Shikari]

I have K-lite codec pack installed and it has coreavc 1.5 by default for playing h.264 files.So in other words you're asking for help with pirated software.
When I switch to FFDshow to play H.264 videos, all the freeze-ups disappear but the sound is a bit out of synch. Sometimes the voices are early and sometimes a bit late so it looks like bad lipsynching. When I play MKV files with subtitles, the subtitles go in tune with the sound, but out of synch with the video as well.Its called "your computer is too slow to play that 720p anime rip with FFDShow."

[Shinigami-Sama]

So in other words you're asking for help with pirated software.
Its called "your computer is too slow to play that 720p anime rip."

one post count wonder
why waste your breath?

[molitar]

So in other words you're asking for help with pirated software.
Its called "your computer is too slow to play that 720p anime rip with FFDShow."

I actually I use CCCP myself but I do not believe CoreAVC comes at all with K-lite codec pack as it's not listed in the release at all. Now CoreAAC does so I imagine he might be mistaking CoreAAC as CoreAVC and he doesn't have CoreAVC. If that is the case than the issue he is playing through the ffdshow which we all knows uses alot more CPU resources hence taking a faster computer to play the video file in sync. Or he has configured ffdhow to use CoreAVC as the default player he really needs to explain himself more clearly before anyone really can give him any useful information.

[JohnnyFu]

So where is the Christmas Edition BetaBoy ? :D

Merry Christmas to everyone out there.

[Shinigami-Sama]

I actually I use CCCP myself but I do not believe CoreAVC comes at all with K-lite codec pack as it's not listed in the release at all. Now CoreAAC does so I imagine he might be mistaking CoreAAC as CoreAVC and he doesn't have CoreAVC. If that is the case than the issue he is playing through the ffdshow which we all knows uses alot more CPU resources hence taking a faster computer to play the video file in sync. Or he has configured ffdhow to use CoreAVC as the default player he really needs to explain himself more clearly before anyone really can give him any useful information.

k-lite used to have coreavc back a few months ago I think
I know I've seen it on other's PCs, and they don't buy software

[ChronoCross]

Changelog 2.79 -> 2.80 | (2006-11-19)

* Updated ffdshow to revision 571
* Updated Xvid to version 1.2.0-dev build 2006-11-08
* Removed CoreAVC

[silverwolf0]

CoreAVC is still in the k-lite mega codec, or at least the latest one I downloaded from free-codecs.com


Don't get so antsy on me. I didn't know it was pirated until now. As far as I am concerned, most codec packs use open source or free codecs. Also, I monitor my CPU usage while playing a video in FFDshow and it only goes to around 30-40% with the CPU automatically downclocking to 800mhz since I set it to laptop/portable in my power configurations (speedstep, viewed through mobilemeter).

Sheesh.

[BetaBoy]

You too JF... funny u say that... we plan on releasing 1.6.5 (not calling it 1.6.2 as we had planned because of all the additional work thats been done.) over the holiday.

One last issue is the DVBViewer slow down... 1.6.5 will improve it for sure. But not as much as we would like. We are still working with the DVBViewer devs on this.

Additionally... one other thing to note is if we release a fix for the 'green bug' issue as there is question on how we should 'best' handle some streams when it's impossible to detect keyframes without external input.

[Yufi]

Any post-Christmas word on the linux version of CoreAVC? Still eagerly awaiting it so I can switch my HTPC back to MythTV and not have to deal with getting out of date patches working with mplayer.

[ADude]

Since DVBViewer usage is a small fraction of HT-PC software usage, wouldn't it make sense to release a version with all the fixes - except for DVBViewer fix - and then work on DVBViewer without the release hanging over your head ?

[Fraeon Lux]

Since DVBViewer usage is a small fraction of HT-PC software usage, wouldn't it make sense to release a version with all the fixes - except for DVBViewer fix - and then work on DVBViewer without the release hanging over your head ?

That was EXACTLY my thought. Why hold everyone else up for months because of some issues with DVBViewer specifically?

1.6.1 was slated to be promptly released after 1.6.0.

[ChronoCross]

That was EXACTLY my thought. Why hold everyone else up for months because of some issues with DVBViewer specifically?

1.6.1 was slated to be promptly released after 1.6.0.

because then you'll have the DVBViewer trolls doing the same thing your doing now. it's a lose lose situation for core. Might as well wait until everyone is happy

[clsid]

That's absolute nonsense. Why are you always defending every single decision that CoreCodec makes?

[CiNcH]

DVBViewer has no trolls!!! *g*

[bob0r]

I have solved my dvbviewer issues: Intel Q6600 :D
CoreAVC + Dvbviewer = black=black == bob0r happy!

Sadly i can no longer test coreavc+dvbviewer on my old system.

CoreAVC is still by FAR the best decoder SPEC wise!
- Colors flags are read
- Cropping flags are read
- ALL mbaff/paff encoders work
- Still the fastest, Cyberlink + Gforce 8800 GTS G92 is still slower than coreavc.

Most issues, which aren't really that bad are fixed now.
They are now working on the green-frames issue, but to be fair 1.5 still works fine :)

As for the new version:
- Deblocking was readded
- Dvbviewer itself is mostly the cause of the issues.
That only leaves the green frame issue, as possible other issues other users reported, but i never encountered those.

[ChronoCross]

That's absolute nonsense. Why are you always defending every single decision that CoreCodec makes?

why are you always bashing them?

[CiNcH]

- Dvbviewer itself is mostly the cause of the issues.

You got more infos about that? Or just an assumption?

[bob0r]

You got more infos about that? Or just an assumption?

From what i understood from the findings between coreavc and dvbviewer developer(s).

3.9.0 was much better with any coreavc than 3.9.1.
They are both working on it.

[clsid]

why are you always bashing them?
It is called constructive criticism.

[ChronoCross]

It is called constructive criticism.

Then mine is consumer support.

[Rectal Prolapse]

I agree with clsid. :P

Anyways, looking forward to an early release...

[ADude]

Anyways, looking forward to an early release...

http://www.guzer.com/pictures/tiredkitten.jpg

[3ngel]

A little OT Request for Core developers.

What about adding WVC1 support to the CoreAVC, or doing a separate optimized product?

ATM the only WVC1 codec (excluding PowerDVD) is the bad MS wich doesn't permit a smooth vision of 1080p WVC1 even on a high end dual core (especially on ATI wich doesn't have WVC1 GPU support).

More and more (almost all) HDDVD (and even bluray) use the WVC1 codec.

So what do you think about it?

I would gladly buy an optimized CoreVC1 product :)

[ACrowley]

A little OT Request for Core developers.

What about adding WVC1 support to the CoreAVC, or doing a separate optimized product?

ATM the only WVC1 codec (excluding PowerDVD) is the bad MS wich doesn't permit a smooth vision of 1080p WVC1 even on a high end dual core (especially on ATI wich doesn't have WVC1 GPU support).

More and more (almost all) HDDVD (and even bluray) use the WVC1 codec.

So what do you think about it?

I would gladly buy an optimized CoreVC1 product :)

I (and all guys i know)can play 1080p WVC1 or VC1 100% smooth with max 60% CPU Load on ym A64 X2 @5000 and Ati HD3870
You must have a bad Sytem Config , it 100% should be no Problem on a fast CPU/GPU

And HDDVD/Bluray are using not WVC1 ,theyre using VC1 :) WVC1 is just the MS implemention.
Same as H264 and x264

[3ngel]

Strangely enough, i'm not able to see smooth only VC1 contents that is HDDVD.

And yes i intended WVC1 as the AdvancedProfile of VC1 (used on HDDVD) that (as far as i know) is not supported by CoreAVC.

Anyway, can you tell me wich codec you use to see HDDVD?

I have an ATI 1950XT, and everywhere i've read all the tests (apart from PowerDVD) gives high cpu usage and not smooth vision for HDDVD, for this reason i asked.

You're using the MS codec?

Pheraps you're using GPU (wich seems to me is partially implemented on your card but i'm not sure about it)?
On ATI 19xx it is not supported for sure.

Thanks.

[Ice =A=]

Don't forget that with HDDVDs (and BluRay of course) a lot of computing power is needed for DRM only, so if one is watching a not-DRM-ed video that should play much better.
And implementing a DRM conform playback would mean a big deal of work anyway, so I have no problem if that is left out for now.

P.S.:
The newer ATI/AMD cards do have a much better video acceleration than older ones (if it's working).

[3ngel]

Yes i'm talking about non-drm content (for this reason i leave out powerdvd).

The newer ATI/AMD cards do have a much better video acceleration than older ones
And yes for this reason i was asking for an optimized VC1 codec :)

[langman10]

I am trying to read from .m2ts files taken by a Blu-Ray-recording camera using AviSynth but am getting errors. :confused: I'm sure it's something in my configuration, so any directions someone could point me in to troubleshoot would be greatly appreciated.

Here's what I've done:

Obtained and installed coreavc. This also installed haali media splitter. I made sure to select "enable opening of MPEG-TS".

(BTW I have debugviewer on during all of the following, and nothing is logged.)

When I open the .m2ts file in gspot, I get:
------------------------------------------
Container:FileType: MPEG-2 Transport Stream
Mime Type: video/mp2t

Render OK. The following combination of filters was used:
[Src}-->>--(A)-->[CoreAVC Video Decoder ]>--(B)-->[Video Renderer ]
[Src}-->>--(A)-->[AC3Filter ]>--(B)-->[Default DirectSound Device ]
------------------------------------------
And the file previews fine in GSpot.

When I open the .m2ts file in WMP11, it plays ok, though jerky because it's HD i believe.

When I open the .m2ts file in VLC, the file begins to play, but then freezes and crashes with the message:
VLC media player has encountered a problem and needs to close. We are sorry for the inconvenience.
When I click on technical details, it reads
AppName: vlc.exe AppVer: 0.8.6.0 ModName: libffmpeg_plugin.dll
ModVer: 0.0.0.0 Offset: 0020f586

I then made an .avs AviSynth script with one line: directshowsource("file.m2ts")

When I open the .avs file in gspot, I get:
------------------------------------------
Container:FileType: Unknown
Mime Type: Unknown

Render OK. The following combination of filters was used:
[Src}-->>--(A)-->[Color Space Converter ]>--(B)-->[Video Renderer ]
[Src}-->>--(A)-->[AC3Filter ]>--(B)-->[Default DirectSound Device ]
------------------------------------------
But when I go to preview in GSpot, GSpot crashes.

I opened the .avs in VirtualDubMod 1.5.10.2:
Using Avisynth 2.56, VirtualDubMod just disappears.
Using Avisynth 2.57, gets "Avisynth read error: AviSynth caught an access violation at 0x00e25980, attempting to read from 0x03bcbfc0"
Using AviSynth 2.58, VirtualDubMod crashes with:
VirtualDub has encountered a problem and needs to close. We are sorry for the inconvenience.
When I click on technical details, it reads
AppName: virtualdubmod.exe AppVer: 1.5.10.0 ModName: virtualdubmod.exe
ModVer: 1.5.10.0 Offset: 000b118d

I opened the .avs in WMP11:
Using AviSynth 2.56, WMP11 just disappears.
Using AviSynth 2.57, blocky red letters on black show "AviSynth caught an access violation at (can't make out), attempting to read from (can't make out)"
Using AviSynth 2.58, blocky red letters on black show "CAVIStreamSynth: System exception - Access Violation at 0x0, reading from 0x0"

I've tried SetMemoryMax(16) at the beginning of the .avs script...no change. Thanks in advance.

Specs:
Microsoft Windows XP Professional SP2
Xeon 2.66GHz Proc:2
RAM 3.5GB
CoreAVC Version 1.6.0.0

Langman

[Rectal Prolapse]

langman, is it possible you are trying to play a movie ripped from a BD+ disc? That won't work if that is the case because of the additional random encryption.

[langman10]

Thanks for the response, RP. No, these are files taken on what I believe is a Sony camera that records to Blu-Ray, which brings Sony's own pseudo-format of transport stream complete with an extra 4 bytes per packet.

Any other suggestions anyone? If it's not even possible to open/read .m2ts files using AviSynth+CoreAVC+DirectShowSource, let me know.

Langman

[Jay Bee]

What are you trying to do exactly? You post goes from WMP to VLC to AVISynth. Just trying to open the file, no matter how?

It should definitely work but I don't want to list all possible ways to open the file.

[langman10]

I guess I was trying to make up for the times when I get "You didn't post enough information" responses. :o Sorry.

As I said, I'm trying to open these .m2ts files using AviSynth. All the other info I gave is just to help diagnose what could be wrong with my setup. I want to create AVI files to edit with. I posted at CoreAVC's forum a week and a half ago, but maybe they're on holidays.

Here's the Cliffs Notes:
With a one-line AviSynth script of directshowsource("file.m2ts) I get errors/crashes in GSpot & VDubMod & WMP. The same .m2ts file opened directly in Gspot & WMP plays fine but crashes VLC.

This happens with all .m2ts files from multiple cameras.

Thanks in advance for any help.

[Jay Bee]

Ah ok. What you need to do is build the graph with graphedit and save it as a grf file. The graph is haali + coreavc + audio decoder but no renderers and make sure that in CoreAVC deinterlacing is off as it can cause crashes. Then make an avs file with directshowsource("file.grf"). And then obviously open the avs with vdub.

Hope it works.

[ACrowley]

"CAVIStreamSynth: System exception - Access Violation at 0x0, reading from 0x0"


I know this Error because i had i very often in my encodes
I could fix it by using the latest Avsiyth 2.58 alpha (070919)

i never had it again :)

[Sasovics]

I have the very same problem :(

I am trying to load AVC stream from EVO (HD-DVD source) to AviSyth using the following graph:


Haali Splitter(EVO file) -> CoreAVC Video Decoder

Then my AVS script is as follows:

DirectShowSource("feature.grf",video=true,audio=false,fps=23.976,framecount=xxxx)
ConvertToYV12 ()


But when I try to load the avs to WMP or MPC it gives me a red error message

"CAVIStreamSynth: System exception - Access Violation at 0x0, reading from 0x0"

However the filter setup plays fine within the graph ...

What am I doing wrong ???

EDIT: I've tried with both AviSynth v2.5.7 and v2.5.8, the result is the same :(

[langman10]

I have the very same problem :(

"CAVIStreamSynth: System exception - Access Violation at 0x0, reading from 0x0"

What am I doing wrong ???



I don't think we're doing anything wrong, Sasovics. I'm beginning to think the issue is with CoreAVC. I used AviSynth 2.58a 070917 like ACrowley suggested above (thanks!) and tried graphedit from Jay Bee's advice from above (Thanks!) and the results are pretty much the same. I think the issue is in version 1.6 of CoreAVC. Check out this thread (http://www.corecodec.com/forums/index.php?topic=544.0) at Core's site, especially the comments like "Coreavc is useless to me now." ;) Another indication is that Jay Bee's post above mentions that interlacing in CoreAVC crashes, but in 1.6 the ability to turn off deinterlacing was removed. Unfortunately, I can't find any way to rollback to 1.5. Ver 1.6.1 is said to be coming soon. We'll see.

Edit: Here's another clue that may be related: In ver 1.6's changes is included "Rewrite of the Directshow wrapper for better compability"

Langman

[Sasovics]

That's what I was afraid of.

So there is nothing we can do at this moment .. anyway, I found a workaround: I use FFDshow fileters instead, and they work well!! ;)

My graph is as follows:

Haali Splitter(AVC Source) -> ffdshow Video Decoder

Try it out! Should work for you as well!

[TheShadowRunner]

So hmm.. probably a dumb question but now that FFDshow uses multithreading (uses all cpu cores) in all newer builds (not only with certain XXL builds anymore), what is the advantage of CoreAVC over ffdshow?

As DXVA is yet to be seen in CoreAVC (after SO many years btw), I'm really beginning to wonder...

[ChronoCross]

So hmm.. probably a dumb question but now that FFDshow uses multithreading (uses all cpu cores) in all newer builds (not only with certain XXL builds anymore), what is the advantage of CoreAVC over ffdshow?

As DXVA is yet to be seen in CoreAVC (after SO many years btw), I'm really beginning to wonder...


ffdshow only supports slice based threading (which x264 no longer uses) so in effect ffdshow is still single threaded on anything done on the latest versions of x264.

As for why you can't use coreavc in directshowsource() you might consider changing what mode the deinterlacing is using. Try all 4 and see if any of them work (I would do it if I had any sources to do so)

Also try disabling cropping and VMR AR Correction

[_xxl]

fdshow only supports slice based threading
yes and cabac / reconstruction parallelism, the code decodes up to 128 macroblocks in one thread while doing prediction+idct+deblock of the previously decoded 128 blocks in another thread.

[Jay Bee]

So hmm.. probably a dumb question but now that FFDshow uses multithreading (uses all cpu cores) in all newer builds (not only with certain XXL builds anymore), what is the advantage of CoreAVC over ffdshow?

As DXVA is yet to be seen in CoreAVC (after SO many years btw), I'm really beginning to wonder...

CoreAVC still has much better performance than any other AVC decoder. With ffdshow you need a very fast, probably overclocked CPU to decode Blu-Ray streams.

Dxva is a mess where you need the perfect combination of GPU, driver version, OS version, PDVD version and most GPUs that claim support aren't spec compliant anyway (deblocking).

CoreAVC will just play without any problems as long as your CPU is fast enough. The only thing they really need to get fixed is deinterlacing and DVBViewer stuttering so that PCs can finally become a viable solution for AVC HDTV. But they said they're working on it.

[audyovydeo]

Dxva is a mess where you need the perfect combination of GPU, driver version, OS version, PDVD version and most GPUs that claim support aren't spec compliant anyway (deblocking).


You've coined the most exact description of DXVA to date !
Look how much time & ink has been lost by doom9ers alone on this marketing ploy.

cheers
audyovydeo

[3ngel]

At this point, i would like to add my experience and again the "same" ever more important request.

Now with the experience. I had a 1950XT, and tried to see an unprotected HD-DVD content, in realtime. Installed the only VC1 Microsoft decoder, started WMP11, the video is not fluid. Processor in only 50%. Now i read that 1950 supported only 3/4 acceleration for HD content so HD2600 is the only one to support full accelleration. So test HD2600, WMP Video Accelleration set explicity to "Max". Same result. No fluid. This is unbelievable.

Now i don't doubt that is the MS codec wich is no good and dont' use for some reason DXVA (and moreover does an even more bad job being the CPU only 50%). I read from various sources only PowerDVD fully supports HD accelleration.
I don't want to use nor buy PowerDVD. I would more gladly spent money on this codec.

So my requests, that are 3 (in order of importance).

1) Add to CoreAVC support for VC-1 codec found in HD-DVD, so content can be played at last decently on every player.

2) Add fully support to CoreAVC for GPU accelleration (wich would make playing of HD contents flawless)

3) Possibly a 64bit compile of CoreAVC?

I know some of this requests are long time made, but i give to occasion to just remember to devs the importance of HD support and GPU accelleration :)

Thanks

[Inventive Software]

@3ngel: Regarding 1), the clue is in the name of the product: CoreAVC. It only decodes H.264, or AVC content, not VC-1. VC-1 and AVC are 2 completely different codecs. I wouldn't put it past CoreCodec to release CoreVC1 in the future.

As I understand it, MS' VC-1 decoder does support DXVA in VC-1, and, I believe, multi-threaded decoding, but you need to use WMP11 to get the full benefit.

[3ngel]

Well, my intention was or to include it in CoreAVC or do a separate CoreVC1. I would spent anyway :)

Now, unfortunately i use exactly WMP11 (the codec is installed with the complete WMP11 package). So although paper says GPU decoding, multithread and so on, i see nothing of it all.

[ACrowley]

@3ngel: Regarding 1), the clue is in the name of the product: CoreAVC. It only decodes H.264, or AVC content, not VC-1. VC-1 and AVC are 2 completely different codecs. I wouldn't put it past CoreCodec to release CoreVC1 in the future.

As I understand it, MS' VC-1 decoder does support DXVA in VC-1, and, I believe, multi-threaded decoding, but you need to use WMP11 to get the full benefit.

WM11 Decoder should supports DXVA 1+2 and ofcourse multithreading
http://www.kmplayer.com/forums/showthread.php?p=25724#post25724
But it supports only DXVA for WMV.
I cant see any difference between DXVA on /Off for VC1 into other Containers like EVO or MKV.
But obviously for VC1 into WMV, you can Test it with WMV9PowerToy. DXVA is inactive for (W)VC1 into EVO, but active for (W)VC1 into WMV
WMVideoDecoder can be used via Directshow in any DShow Player. Including all Features. So not only in WMP :)
However..this is the wrong Thread

[3ngel]

So you're saying that the VC-1 DXVA acceleration is present but only supported in a WMV container? That's crazy :D but now i know i'll do a test :)

Sorry for the wrong thread, what's the right thread?

Thanks