The latest ffmpeg versions include a workaround to deal with a certainpecularity in Canon DSLR footage: instead of decoding pictures with theproper resolution of 1920x1080 they decode it with 1920x1088 and add ablack bar at the bottom.

Needless to say, that this screws up things in a lot of areas within blender(proxy indices, mask animations etc.)

Since all blender versions besides Linux x86 32bit seem still to includeolder ffmpeg versions which still contain this bug, this patch addsa workaround for older versions until we have all versions on all platformsup to date.

* if you cut two strips of the same name class (MVI_XXXX.MOV and MVI_XXXX.001) the two new generated strips will end up with the same name. (easy test case: add a MOV file with it's accompanying audio track to the timeline and then cut both strips at once into two pieces)

* visible problem: your animation data will get messed up on the way, since the animation system doesn't know, which strip it should assign the animation.

Problem was caused by generating a new list of sequences within the cut_seq_list() function:

Since dupli_seq() can't see the members of the new list of sequences, itwon't be able to assign unique names in all cases.