CompositeVideoClip([xxx]).rotate(90) ValueError: axes don't match array

[clotyxf]

Expected Behavior

Specifications

• Python Version: 3.6.3
• Moviepy Version: 1.0.1
• Platform Name: Centos
• Platform Version: 7.2

Actual Behavior

size = (640, 320)
fps = 24
bg_clip = mpy.ImageClip(img=image, fromalpha=True)
bg_clip = bg_clip.resize(size).set_duration(d).set_fps(fps )
bg_clip = mpy.CompositeVideoClip([bg_clip])
bg_clip.rotate(90)

ValueError: axes don't match array

change the angle to 89.99, is worked.

[rriokwok]

bg_clip.rotate(90, expand=False) would give what you want.

[misland]

        if (a==90) and expand:
            return np.transpose(im, axes=transpo)[::-1]
        elif (a==-90) and expand:
            return np.transpose(im, axes=transpo)[:,::-1]
        elif (a in [180, -180]) and expand:
            return im[::-1,::-1]

code in moviepy->video->fx->rotate.py,line 58~63,that's why 89.99 worked.
@clotyxf could you reopen this issue?89.99 shouldn't be the workaround
@tburrows13 hi,could you explain why,many thanks :)

[misland]

bg_clip.rotate(90, expand=False) would give what you want.

image will lose part of it when expand is set to true,so this should be the workaround

[misland]

I just copy the code in line 69 to line 59

if (a==90) and expand:
            return pil_rotater(im, a, resample=resample, expand=expand)
            # return np.transpose(im, axes=transpo)[::-1]

then it works fine,I don't know why we do this specialized processing when the angle is set to 90
@Earney

[tburrows13]

Hi, it definitely seems like it is a bug to do with RGBA images. See #781 and #990 for the same error message.

The reason why angles 90, -90, 180 and -180 are special is because they can be easily done by directly transposing the image array using numpy. More complicated rotations require pillow, which is an optional library, and may perform the rotations slower. However, if this bug cannot properly be fixed, then it might be worth using the pillow method as a fall back.

[tburrows13]

Fixed in #1335