Bugzilla Bug 199448

When using blender-2.45 with ffmpeg flag, and most recent
ffmpeg-0.4.9_p20070616-r2, adding any *.avi file as an input for texture (or
source in 'sequence') results in corrupted image (attatchments).

Reproducible: Always

Steps to Reproduce:
1. emerge =blender-2.45
2. emerge =media-video/ffmpeg-0.4.9_p20070616-r2
3. add .avi file as texture source
Actual Results:  
Corrupted image instead of actual movie.


Last working configuration (and workaround):
media-video/ffmpeg-0.4.9_p20070616 (no swscaler)

and modified blender-2.45:
--- blender-2.45.ebuild 2007-09-22 01:14:57.000000000 +0200
+++ blender-2.45.ebuild.1       2007-11-17 16:38:13.000000000 +0100
@@ -58,7 +58,6 @@
        cd ${S}
        epatch ${FILESDIR}/blender-2.37-dirs.patch
        epatch ${FILESDIR}/blender-2.44-scriptsdir.patch
-       epatch ${FILESDIR}/blender-2.44-swscale.patch

        if use ffmpeg ; then
                cd ${S}/extern

I think, that this swscale patch is not taking care of input, because output to
ffmeg works fine.

Created an attachment (id=136172) [details]
Source frame

Created an attachment (id=136174) [details]
Corrupted image (same source as previous attatchment) in blender

that's annoying, instruct me on how to reproduce the issue please.

Start blender, choose "4-sequence" window sheme (center-top list), and move
mouse cursor to middle window. Then press space, and click "movie", choose a
file, place it somewhere in the window, then move the time slider over the clip
and observe the results in preview (black window on top right, middle mouse
pans the view).

Created an attachment (id=136183) [details]
Fixed patch.

Ok, found it!:)

There was an error in old version of this patch. In ffmpeg_fetchibuf() pixel
formats were in wrong order. I've noticed it while comparing new code to the
old commented-out.

patch update committed, thanks again