CoreCodec/H.264 Codec "CoreAVC"

[STaRGaZeR]

Yep, the memory leak is impressive.

Try the newest builds available at http://www.xvidvideo.ru/content/category/1/1/2/, you can also try the standalone DXVA filter in your player of choice.

[Cyber-Mav]

my word that link you gave stargazer is got a far newer version that what im using.

[smit]

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.

.

[leeperry]

am I the only one getting a slight freeze for a few seconds when I start a movie in CUDA mode ? running XP SP3 w/ the latest CoreAVC/KMPlayer betas.
it works fine in software mode....it feels as if there were some lag/latency to start the CUDA communication :confused:

I'm using Reclock in 24Hz and a winamp2 plugin in ffdshow, so it's like they were all trying to initiate simultaneously...freezing the system until they're all synchronised :o

even HR's jitter starts at +1000ms and quickly comes down to <8ms, so it means that the start was laggy to hell..

PS: a friend of mine also gets terrible jitter in HR when he starts a movie in CUDA mode.

[BetaBoy]

lee... I'm not seeing there here. Your running the new Beta Build?

[leeperry]

yup! there's some latency when the CUDA communication starts, is there a way this could be shortened?

[me7]

I installed the 182.06 drivers on my laptop (thanks to laptopvideo2go) and CUDA in now available in CoreAVC. Playback of low res and bitrate files works rather well but if I feed it some 1080p content the video stutters like hell.
Does someone know if mobile GPUs have 'inferior' VP2 units? My 8400M GS (G86) is supposed to have VP2, but the playback is far from smoth.

[buletti]

BetaBoy could you please give some more details about the requirements that have to be met to use CUDA respectively to get the green icon? The driver and hardware requirements are quite clear but I wonder if there are other requirements like output color spaces or demands regarding the used renderer.
In my usecase I decode H264 to YV12 and use FFDShow's raw video filter to apply heavy post processing via Avisynth prior to the rendering. I'd love to outsource the decoding to the GPU and save the CPU cores for the post processing. But until now the decoding had to be done in software as DxVA was not usable with this filter chain because of the close decoder-renderer coupling. So, I had high hopes that the new CUDA decoding would not have these restrictions anymore. But as I get it, the DxVA limitations do also apply to the CUDA implementation? Is this because the new coreAVC version is not doing any decoding in software on the GPU hardware but is relying on the hardware decoder like DxVA?

[leeperry]

But as I get it, the DxVA limitations do also apply to the CUDA implementation?
you can decode in CUDA and apply Avisynth PP in ffdshow, I do it all the time :p

[buletti]

I checked the trail version and it works with FFDShow and AviSynth :D For some streams I get the green icon, for some other streams I get the blue icon. I compared the streams with MediaInfo and checked profile, reference frame count, encoder options etc. but could not come up with a stream attribute that would determine the decoding path (except for interlaced streams which are software only atm). So, what are the prerequisites for a stream to be decodable via CUDA?

[zoose]

With the latest stable drivers (182.06) under XP SP3 with a GTX 260 I get decoding errors at around the 3 second mark with the following clip.

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

Works fine with:
CoreAVC software mode
MPC HC both DXVA and software decoders

[Guest]

Works fine in DGAVCDecNV, so it's not a CUDA decoding problem.

[chros]

VMR9 renderless bug: latest CoreAVC applies more level correction than it requires (darker) ... No problem with EVR Custom ... (using MPC-HC) (all options is Auto )
OS: WinXP

[SixKiller]

For me Cuda isnt working at all. The Option is enabled, and the newest 182.06 Drivers are installed. But the Icon never turns green, it stays blue, no matter what material i feed. HDTV 1080i or 720p. Bluray h.264 or reencoded x264 mkv. Always stays blue ...Any Ideas?

Btw using Vista x64 with 8800 GTX an c2Q @ 3.0 Ghz.

Greetings

Six

[Guest]

8800 GTX has VP1 and so won't work. See here:

http://en.wikipedia.org/wiki/PureVideo#Table_of_PureVideo_.28HD.29_GPUs

You need VP2 or better.

[Gleb Egorych]

VMR9 renderless bug: latest CoreAVC applies more level correction than it requires (darker) ... No problem with EVR Custom ... (using MPC-HC) (all options is Auto )
OS: WinXP
VMR7 is OK too (WinXP SP3).

Edit: It's strange, I don't have the problem with VMR9 renderless. CoreAVC settings: Input levels AUTO, Output levels FORCED TV, Forceware 182.06 Output levels FORCED PC. Both VMR7 and VMR9, both Cyberlink H.264 and CoreAVC have same picture. Seems like the bug is in CoreAVC Output Levels AUTO.

[yesgrey]

@BetaBoy,
I believe you know that YUV is not the correct designation (it's an analog format), that the digital format correct designation is YCbCr (to be exact, is Y'CbCr, but since we also don't use R'G'B', I think it's ok to drop the ' from the Y).
I think it would be a good idea if you use the correct designation in your decoder dialogs. It would help stop spreading this misinformation...;)

[BetaBoy]

@BetaBoy,
I believe you know that YUV is not the correct designation (it's an analog format), that the digital format correct designation is YCbCr (to be exact, is Y'CbCr, but since we also don't use R'G'B', I think it's ok to drop the ' from the Y).
I think it would be a good idea if you use the correct designation in your decoder dialogs. It would help stop spreading this misinformation...;)
Sure... this was a decision we made early on based on "what ppl know as ..." and YUV is what we decided (I think Haali had the final say on this one). I'll throw it around internally and see what they think.

[me7]

Am I the only one with a VP2 GPU who gets extreme stuttering (2~3 fps)? Here are the filters used by MPC-HC:
http://img26.imageshack.us/img26/4139/filters.th.jpg (http://img26.imageshack.us/my.php?image=filters.jpg) I don't see anything that could cause trouble.
System: Geforce 8400M GS (with desktop drivers, installed with modded nv_disp.inf from laptopvideo2go), T8300 (Penryn 2,4 GHz), 3GB Ram, Vista SP1 32bit

[yesgrey]

this was a decision we made early on based on "what ppl know as ..."
There was a time that "what ppl know as ..." the center of the universe was the Earth.:)
I also always called him YUV, until recently, when I realized that it was wrong. If nobody starts correcting it, people will continue to "know it as...". In ffdshow it was recently corrected (also by my suggestion), and it would be good if Haali also corrects it in his Renderer...;)

[Guest]

You're being pedantic. Historically you are correct, but time advances and usage evolves. Today, the term YUV is commonly used to describe formats that are encoded using YCbCr.

Anyway, it's pissing up a rope. I tried for a while to stop people from saying "I could care less" instead of the correct "I couldn't care less". Totally futile.

Go with the flow, the meaning is clear in the context used.

[yesgrey]

You're being pedantic.
I have posted my opinion without ofending anyone, just joked a little with the Earth example. If I have offended anyone, I apologize here, I did not intend that.
You could have wrote exactly what you had without this initial phrase, and I would agree with part of it, but you haven't.
So, use whatever you want, but don't start offending people. I'm done with this.

[Guest]

http://dictionary.reference.com/browse/thin-skinned

[leeperry]

I'm done with this.
easy buddy http://forum-images.hardware.fr/images/perso/julm3.gif

ffdshow is a tool aimed at power users, CoreAVC is a fast h264 decoder....not the same target...a major part of its users prolly got no idea what Y'CbCr actually is :D

like ppl calling 90-20Hz infrabass, infrabass is <20Hz if you wanna respect the true jargon :o

[Sagekilla]

If you wanna get technical, infrasound is frequencies below <20 Hz to respect the "true jargon" ;)




* Sorry for poking fun at you leeperry, I was just trying to show how pointless it is to get caught up in semantics. No offense :)

[leeperry]

If you wanna get technical, infrasound is frequencies below <20 Hz to respect the "true jargon" ;)
http://forum-images.hardware.fr/images/perso/julm3.gif


http://forum-images.hardware.fr/images/perso/justin_bridou.gif

[ADude]

Are there any performance improvements to the software decoder in 1.9.0 or is the hardware acceleration (and other fixes mentioned in the change list) the only difference ?

[leeperry]

ouh...the latest beta works like a charm :cool:

I've got some ski ORF1 german broadcasts in 720p@50 that were giving slight pixelation when seeking, but this is now history...also seeking in KMP is just as fast as in software mode, and I can't see much latency remaining when the movie starts. way to go! :p

:thanks:

[TheShadowRunner]

With CUDA enabled I sometimes have a green screen after switching resolutions "live" (while a movie is playing, needed for ReClock).
Happened at some point in full software mode in previous builds but was finally fixed in 1.8.5.0.
Hopefully, you (CoreCodec) can test this for the next 1.9.x version with CUDA enabled.
Thanks.
Later,

TSR

[tahir]

CUDA is greyed out at settings.

I have GeForce 8600GTS
Windows XP SP3
Driver version 181.22

in C:\windows\system32
nvcuda.dll 6.14.11.8122

what am i doing wrong ?

[BetaBoy]

* You will also need drivers 182.05 or higher from NVIDIA

[me7]

BetaBoy, are mobile GPUs (like my 84000M GS) even supported?

[lucassp]

Yes, your 8400M GS is supported.

http://en.wikipedia.org/wiki/Nvidia_PureVideo#Table_of_PureVideo_.28HD.29_GPUs

You can use GPU-Z to find out which GPU do you have:

http://www.techpowerup.com/downloads/SysInfo/GPU-Z/

[ADude]

Are there any performance improvements to the software decoder in 1.9.0 or is the hardware acceleration (and other fixes mentioned in the change list) the only difference ?

[DJ Bobo]

@ BetaBoy
I see the hardware requirements have been updated on the website to include the supported GPUs, but the main issue remains: the recommended hardware is set way too low! You're still recommending a P4 for 1080p videos! How do you guys test at CoreCodec?! I don't think you can recommend anything below a dual core for this. As said, my Athlon X2 @1.9GHz, which is roughly equivalent to a Pentium D @3.2GHz (I can't emphasize the D enough!), averages 70 to 75%. There is no way a P4 could handle this!

[ranpha]

@ BetaBoy
I see the hardware requirements have been updated on the website to include the supported GPUs, but the main issue remains: the recommended hardware is set way too low! You're still recommending a P4 for 1080p videos! How do you guys test at CoreCodec?! I don't think you can recommend anything below a dual core for this. As said, my Athlon X2 @1.9GHz, which is roughly equivalent to a Pentium D @3.2GHz (I can't emphasize the D enough!), averages 70 to 75%. There is no way a P4 could handle this!

If you have a supported GPU, you can get away with a Celeron 1.6Ghz even for a high-bitrate 1080p video, easily. Maybe the website should explicitly specify that for those that do not have supported GPUs, should have a dual-core or something like that.

[lucassp]

As said, my Athlon X2 @1.9GHz, which is roughly equivalent to a Pentium D @3.2GHz (I can't emphasize the D enough!), averages 70 to 75%. There is no way a P4 could handle this!

Back when I had a Athlon64 2800+ S754, I used to play 1080p content from Apple Trailers with an average of 80% of CPU load. I didn't have any complex videos to test with.

[DJ Bobo]

Here a graph showing the CPU charge when playing the Seven Pounds 1080p trailer (http://showcase7.divx.com/SevenPoundsTrailer[DivX7].mkv) from the DivX site:
http://img408.imageshack.us/img408/6706/cpuusage1080p.gif (http://imageshack.us)
* Durchschnitt = Average

This trailer should be pretty much representative for your typical DVD-9 1080p rip (80MB per minute)
I wouldn't recommend anything below an Athlon X2 3800+ or equivalent.

[adiabatic]

@ BetaBoy
I see the hardware requirements have been updated on the website to include the supported GPUs, but the main issue remains: the recommended hardware is set way too low! You're still recommending a P4 for 1080p videos! How do you guys test at CoreCodec?!

I had no problem playing 1080p content with a P4 2.4 and CoreAVC two years ago. There's every reason for me to think the decoder has gotten better in those two years. There's a lot of variety in bandwidth for 1080p though... I have some high-ref frame x.264 stuff that I know wouldn't play on that P4.

[tetsuox]

I have some high-ref frame x.264 stuff that I know wouldn't play on that P4.

Unless I'm mistaken, High Ref. frames uses more memory, not more CPU.

[~bT~]

I had no problem playing 1080p content with a P4 2.4 and CoreAVC two years ago. There's every reason for me to think the decoder has gotten better in those two years. There's a lot of variety in bandwidth for 1080p though... I have some high-ref frame x.264 stuff that I know wouldn't play on that P4.

1080p with p4 & coreavc (with cuda) should be fine.

i used to play them before on my p4 with coreavc.

[DJ Bobo]

I don't know what kind of trailers you were watching, but I remember having trouble playing 720p stuff on a P4@3GHz!! It would play alright until there is a lot going on on the screen.
Check the Apple 720p trailer in this page (http://www.apple.com/quicktime/guide/hd/bbc-nhk.html) for example (since some people here seem to consider Apple trailers as a reference!). Its bitrate comes close to what you would expect from a DVD-5 720p rip. The scene with a lot of people coming together at the end would choke the aforementioned P4, even when decoded with CoreAVC!
So even the 720p "recommended requirements" are too low. I would recommend here at least a P4@3.2GHz (or Athlon XP 3200+)
But 1080p is definitely out of the league of single-core CPUs!

CUDA is another story. The so called "recommended" requirements were there long before CUDA even existed.
I thought may be it's time for CoreCodec to update those recommendations to fit the reality, may be 2 recommendations: with and without CUDA?

[Shinigami-Sama]

I was playing downscale 1080p on my P4...
I needed to OC up to 3.4ghz to get it to play though, other wise it would drop frames all the time
rather than just every 30seconds or so

[carlo_0000]

and any chance to have dxva with ati cards (hd2400pro) in the next version ?

because i m still waiting for a codec for my mediacenter

cpu is not sse2 so powerdvd did not work with dxva
seperon2200+ soket A

and codec of mpchc do not work correctly with dvb (1080i) 720p/1080p is ok

and software decoder is to slow


I was playing downscale 1080p on my P4...
I needed to OC up to 3.4ghz to get it to play though, other wise it would drop frames all the time
rather than just every 30seconds or so

3.4ghz and stil to slow ?

on my athlon 64 2800+ (oc @ 2560mhz) gf5200 i can play 1080p with 8mbit/s videobitare and coreavc without lag (all programe and tray icon must be closed) cpu 90-96%

[Dark Shikari]

3.4ghz and stil to slow ?

on my athlon 64 2800+ (oc @ 2560mhz) gf5200 i can play 1080p with 8mbit/s videobitare and coreavc without lag (all programe and tray icon must be closed) cpu 90-96%An Athlon 64 is not a Pentium 4.

[Shinigami-Sama]

p4 sucks and that was with lavc
now I use dxva

[Dark Eiri]

Well, I can watch 720p video flawlessly with an AMD Turion TK-36, single core, 2.0 GHz with no lag at all, decoded with CoreAVC. No DXVA here. So I think there's something wrong with a Pentium 4 @ 3 GHz not playing it.

[Dark Shikari]

Well, I can watch 720p video flawlessly with an AMD Turion TK-36, single core, 2.0 GHz with no lag at all, decoded with CoreAVC. No DXVA here. So I think there's something wrong with a Pentium 4 @ 3 GHz not playing it.An Athlon 64 at 2Ghz is significantly faster than a P4 at 3Ghz.

And the above people were talking about a P4 playing 1080p, not 720p. 1080p is 2.25x harder to decode than 720p.

[Dark Eiri]

I was talking about this:

So even the 720p "recommended requirements" are too low. I would recommend here at least a P4@3.2GHz (or Athlon XP 3200+)

[DJ Bobo]

@ Dark Eiri
A Turion 2GHz is roughly equivalent to a 3.4GHz P4! so there is nothing wrong with a 3GHz P4 having problems ;)

@ Shinigami
DXVA doesn't always work, does it? ;)

@ carlo
An Athlon 64 isn't 2800+ anymore if overclocked to 2.5GHz, it is even faster than an Athlon 64 4000+!
Could you tell us your average load with the Seven Pounds trailer please? with a graph if possible. I can't imagine your CPU not maxing out.