Problem with CoreAVC & gg releases

[dago2682]

I get some pixelation while using CoreAVC 1.9.5+Latest CCCP,any suggestions on how to fix this issue?.

[Cryonosis]

gg put up an announcement about it on their website. . . Uhm, forgive the tinyurl link, but gg likes the more colorful side of the English language, as it were.

http://tinyurl.com/ygdv492

Basically, you need to wait for an update to coreavc.

[dago2682]

@Cryonosis So this issue dosn´t have a fix yet....
Oh well,thx for the quick reply.

[Cryonosis]

Since I don't use CoreAVC or CCCP, I can't offer much more than that; I had just remembered running across that announcement before when I saw your post.

I suppose in the meantime, you could try using something else to play the files. I haven't had any problems with gg's releases on Media Player Classic - Home Cinema.

[jpwong]

I'm not sure CCCP has a problem. I'm using CCCP and don't have this issue. When you say CoreAVC+CCCP do you mean you're using CoreAVC for the video and CCCP for the audio? Try telling CCCP to decode the video as well, and it should fix up the problems.

[dago2682]

@Cryonosis I already use MPHC,CoreAVC is a codec and a very good one usually,this is the first time it has given me any problems.
I like it because it uses a lot less resources compared to when i let CCCP handle video decoding.

@jpwong yeah,thats exactly what i´m doing.
I´lll try what you say tomorrow and post results.

[emptyeighty]

Originally Posted by dago2682

@Cryonosis I already use MPHC,CoreAVC is a codec and a very good one usually,this is the first time it has given me any problems.
I like it because it uses a lot less resources compared to when i let ffdshow handle video decoding.

Fixed that for ya.

Also there's multithreading in CCCP's ffdshow since the 2009-09-09 release (CCCP settings, 1st page, check the "mt" box), which gives quite a speed boost on multi-core CPUs. It's still not as fast as CoreAVC though.

[Dark Shikari]

DivX's decoder is currently equal to or faster than CoreAVC and doesn't have the issue that CoreAVC does. So just use that instead.

[emptyeighty]

Originally Posted by Dark Shikari

DivX's decoder is currently equal to or faster than CoreAVC and doesn't have the issue that CoreAVC does. So just use that instead.

Here's how.

[SeijiSensei]

As an alternative, you can always try SMPlayer. It's entirely self-contained so it won't interfere with other codecs and players.

[DragoZERO]

Or, you could just use the old ffdshow, the one that you were using before installing CCCP's update.

[sneaker]

CoreAVC 2.0 is supposed to come out this week and is said to fix the issue. But the upgrade won't be free for owners of CoreAVC 1.x.

[emptyeighty]

Originally Posted by DragoZERO

Or, you could just use the old ffdshow, the one that you were using before installing CCCP's update.

What are you talking about? This thread is about CoreAVC failing, not ffdshow (which CCCP uses).

[DragoZERO]

Originally Posted by emptyeighty

What are you talking about? This thread is about CoreAVC failing, not ffdshow (which CCCP uses).

I'm talking about fixing the problem until CoreAVC fixes it or if you don't want to pay (if they charge) for the update. The problem arose from updating ffdshow. So if you go back to the old one, when it worked, there would be no problem.

[sneaker]

Where did you get the idea that the problem arose from updating ffdshow? You'd be the first one I've heard of having these problems.

There are/were two problems with the new "weightp=2" option introduced recently in x264.
1.) CoreAVC <=1.9.5, Flash Player and Apple TV are known to not support it
2.) revisions < 1342 of x264 had a buggy implementation resulting in non-compliant output which would break even more decoders, like some DXVA ones. ffdshow should be fine anyways.

[DragoZERO]

Originally Posted by sneaker

Where did you get the idea that the problem arose from updating ffdshow? You'd be the first one I've heard of having these problems.

There are/were two problems with the new "weightp=2" option introduced recently in x264.
1.) CoreAVC <=1.9.5, Flash Player and Apple TV are known to not support it
2.) revisions < 1342 of x264 had a buggy implementation resulting in non-compliant output which would break even more decoders, like some DXVA ones. ffdshow should be fine anyways.

The first post said the problem arose using the new CCCP, so if you use the old one then...

I thought the new ffdshow was different and was causing problems? I found the old ffdshow to perform faster than the new one. Or am I confusing the encoder and decoder? Is the problem that gg is using a new encoder that CoreAVC doesn't support properly? And I just made myself into a total moron and jerk?

I'll go sit in the corner for a while.

[sneaker]

The first post said the problem appears when using the newest CCCP and CoreAVC. Since CoreAVC is only able to decode H.264 it's pretty clear that the thread starter uses CoreAVC for H.264 decoding and not ffdshow.
I just wanted to make that 100% clear since many people will have that problem and we shouldn't spread false information, making people try to downgrade ffdshow or similar things not fixing that problem.

[emptyeighty]

Originally Posted by DragoZERO

I thought the new ffdshow was different and was causing problems?

There's this bug in "newer" ffmpeg/ffdshow (by now it's old), but it only affects seeking and also only streams made with very old x264. Other than that i don't know of any. Do you?

I found the old ffdshow to perform faster than the new one.

How did you test this? Newer ffdshow with multithreading surely is faster on multi-core systems. I haven't seen any reports of non-multithreaded ffdshow being slower either..

[jpwong]

Originally Posted by DragoZERO

The first post said the problem arose using the new CCCP, so if you use the old one then...

Originally Posted by jpwong

When you say CoreAVC+CCCP do you mean you're using CoreAVC for the video and CCCP for the audio?

Originally Posted by dago2682

@jpwong yeah,thats exactly what i´m doing.

CCCP isn't being used for anything other than playing the audio. There should be no need to downgrade, just tell it to let ffdshow handle the video as well. CPU useage will be higher, but it sounds like that the OP doesn't have any issues with it, it's just that CoreAVC was doing the same job with lower load until this issue came up.

[dago2682]

Using FFdshow to decode the video fixed the issue.
Thank you all