Log in

View Full Version : CoreAVC - Nothing conects in Graphedit?


homerpez
4th June 2007, 14:07
I was trying to see if I could gain a speed improvement using the coreavc filter vs. the ffdshow one, converting from HD-DVD .evo file to x264...

Unfortunately, while ffdshow connects easily in Graphedit (Haali Splitter --> ffdshow video encoder), I can't find anything that will connect to COREAVC!

I've tried Haali splitter, Haali AR splitter, filesource(Async), Sonic HD demuxer, and any combination of them it seems. Whenever I drag the arrow over to COREAVC, It always comes up with the error "The filters cannot agree on a connection".

I just need one way to properly get .EVO -> COREAVC to show up in the encoder graph... can someone offer some assistance?

(This is maddening for a second reason - I just upgraded to an Intel E6600... it's faster for all other things, but SLOWER than my AMD 4200 was on x264 encodes... weird in and of itself, but this is a separate issue)

The short version of this question is: to encode to x264...

HAALI SPLITTER --> FFDSHOW --> AVISYNTH = WORKS

??????????????? --> COREAVC --> AVISYNTH = WHAT WORKS?

Thanks in advance!:thanks:

clsid
4th June 2007, 16:11
CoreAVC is a H.264 decoder. If your HD-DVD source contains VC-1 video, then it obviously is not going to work.

homerpez
4th June 2007, 16:30
CoreAVC is a H.264 decoder. If your HD-DVD source contains VC-1 video, then it obviously is not going to work.

Hmm... ok, I guess my confusion was that I assumed that "AVC", 'VC1" and "H264" were all MPEG variants and would be accellerated by the same thing, but......... I guess CoreAVC doesn't do VC1 from what you say.

If this is the case, I'm stuck with ffdshow as the decoder (which works for me, it's just... slow). I'm still pretty curious why my E6600 is just as slow as a AMD 4200x2 when processing H264... I guess it just does, and there's no special trick or decoder I can use.

Thanks for the tip...

clsid
4th June 2007, 16:32
VC-1 is made by Microsoft. It is a variant of WMV3.

Use Microsoft's own DMO decoder. Either directly or indirectly via ffdshow (wmv9). Using ffdshow's libavcodec is slower and probably also worse quality.

homerpez
4th June 2007, 16:50
It's remarkable how I can read 100+ pages of help and threads here and learn nothing, and in 15 minutes in this thread I've learned more than I have in months. This is good. :)

I just loaded up the EVO file, using WMV DMO instead of ffdshow... hit the "play" button in V-Dub, and I can already see how it processes faster. BIG THANKS!!!!

So, I'm guessing now that CoreAVC simply has no place in my re-encodes... I don't think Blu-Ray uses H264 either... it's also VC1?

clsid
4th June 2007, 17:28
The standards allow both H.264 and VC-1 (and I think also MPEG-2). It is up to the producer of the disc to decide which format to use.

homerpez
4th June 2007, 23:37
Thanks again...

As it turns out, I discovered that the VFW version of X264 had to be updated, the old version was ignoring multiple threads (and slowing down encodes by half). So having solved that, my thirst for something like CoreAVC is less and less...

I'll keep these in mind when I attempt Blu-Ray (just got a drive, in a very unwise purchase). It looks like I can always use FFDShow as a fallback for either VC1 or H264.

KoD
5th June 2007, 10:37
Just so you know, people nowadays don't like to use vfw applications like Vdub for encoding.