Re: [VLC] Ati Radeon XPress 1250

Top Page

Reply to this message
Author: signal3
Date:  
To: dmo-discussion
Subject: Re: [VLC] Ati Radeon XPress 1250
On Mon, Jan 24, 2011 at 7:33 PM, signal3 <signal3@???> wrote:

> Ah, okay... I'll try to reproduce the problem again.
>
>
> On Mon, Jan 24, 2011 at 6:19 PM, Christian Marillat <marillat@???>wrote:
>
>> signal3 <signal3@???> writes:
>>
>> [...]
>>
>> > Setting up vlc-nox (0.8.6.h-4+lenny2.3) ...
>> > Setting up vlc (0.8.6.h-4+lenny2.3) ...
>>
>> The problem seems to be with unstable packages, vlc 1.1.x
>>
>> Christian
>>
>>
> Found some extra drive space (usually don't mess w/ SID) and managed to

reproduce this problem (using SID+dmo on my x1250 based motherboard). I
think the issue is with libswscale (not libavc*).

Mostly because vlc complains:

swScaler: pal8 is not supported as output pixel format
[0x8bcc4bc] swscale scale error: could not init SwScaler and/or allocate
memory

Not to mention, the problem goes away by doing "sudo dpkg --force-depends -P
libswscale0" (i.e. removing the dmo package) and then "sudo dpkg -i
libswscale0_4%3a0.5.2-6_i386.deb" (i.e. installing the SID package).

My guess is somewhere between v0.5.2 and v0.6.1 of building and packing
ffmpeg's swscale library a regression was introduced (or a feature was not
ported to 3dnow/radeon). Can't say if this is ffmpeg/libswscaler's fault or
just the dmo package of it.

Probably worth it to "git clone git://git.ffmpeg.org/ffmpeg.git" and bisect
between 0.5.2 and 0.6.1 to find out which commit is causing the pain; unless
of course the problem was with dmo's configure+build (not upstream).

Any thoughts?