Success with Celeron, semi-success with Core2Duo

[GoogleCodeExporter]

1. Following the instructions for a Celeron 2.4GHz Debian Etch machine
2. Following the instructions for a Core2Duo E4500 Debian Etch machine
3. CoreAVC (H264 decoding) works perfectly on both; but all the other
Windows-DLL based decoders are broken on the Core2Duo (perhaps because 
it has two cores?)

Decoding H264 content with CoreAVC works perfectly on both machines
(e.g. BBC 720p quicktime trailers). The other Windows-DLL based decoders
however, seem to become broken... Something to do with the setup 
process, perhaps...
E.g. when decoding WMV-HD content (which is not H264 content, and is
thus decoded by the Windows DirectShow filter), the decoding works fine
under the Celeron, but semi-breaks (draws random garbage alongside the
video) for the Core2Duo.

CoreAVC 1.3, Linux 2.6.23, Debian Etch.

Anyway, thanks for doing all this work! It considerably improves the
decoding of H264 content (and under the Core2Duo, it uses both cores
so it can decode even 1080p - something completely impossible with
ffmpeg)...

Original issue reported on code.google.com by happyuse...@gmail.com on 18 Jan 2008 at 9:28

[GoogleCodeExporter]

This version of the codec loader accurately reports the number of CPUs to the 
decoder
(MPlayer code always reports 1). This breaks several decoders, esp. the 
RealVideo
ones crash very often. Probably your problem has the same cause.
One solution would be to only report the correct CPU number if the codec is 
CoreAVC.

Original comment by reimar.d...@gmail.com on 27 Jan 2008 at 2:31

[GoogleCodeExporter]

I don't plan to fix this, as the patches are completely independent of CoreAVC, 
and
the issues they cause with other Codecs aren't something I can easily deal with.

Original comment by alannis...@gmail.com on 6 May 2008 at 3:50

• Changed state: WontFix