As far I know for now, there exists no workaround and no registry entry, in order to get it working.
It’s really bad, since it’s been said, that this version is going to fix the seeking issues and the playback of CamCorder footage such as from the Canon HF10/100 or the Panasonic HDC-SD1/5/9/100.
As soon as a workaround is found, I will update this post. My personal favorite at the moment is, that there is the
NV12 color space scheme set per default, whereas XVideo (
YUV to operate. But I’m not an expert on that, and this is pure speculation. Nevertheless, it would be a very useful information to know how one can set these values in the registry anyhow.
Moreover it’s peculiar that the file size of CoreAVCDecoder.ax is now about 960K, whereas the previous version had 208K. Err… forgotten DEBUG switch at compile time?
[UPDATE] Since the 20th of October the Forum of CoreCodec isn’t accissable anymore. The links above lead to a build status site, that does not have anything in common with their forum. At the moment it’s completely not clear to me, what is going on there.
[UPDATE] Forum is back again. See also here: http://blog.mymediasystem.net/?p=178
[UPDATE] Somebody posted the issue at the core-avc-for linux porject under issue #62
It’s perhaps more interesting to see what happens here, since the guys at the CoreCodec forum seems to ignore the Linux community. It’s ironic, but the Linux community is _the_ community without a hardware acceleration support and really depends on this piece of software. If they do keep ignoring the needs of the Linux community, the ffmpeg-mt project will make sooner or later CoreAVC obsolete.
Read here the workaround on how to play back AVCHD footage without CoreAVC.