Opened 12 years ago

Last modified 11 years ago

#1069 open defect

Canon Powershot playback / conversion

Reported by: lennie Owned by:
Priority: minor Component: undetermined
Version: git-master Keywords: h264 mov
Cc: Blocked By:
Blocking: Reproduced by developer: yes
Analyzed by developer: no


I get the following errors when playing or converting this file from a Canon Powershot HS100 camera:

[h264 @ 0x160f940]mb_type 33 in I slice too large at 73 58
[h264 @ 0x160f940]error while decoding MB 73 58
[h264 @ 0x160f940]concealing 1176 DC, 1176 AC, 1176 MV errors
[h264 @ 0x160f940]dquant out of range (-61) at 60 4
[h264 @ 0x160f940]error while decoding MB 60 4
[h264 @ 0x160f940]concealing 7669 DC, 7669 AC, 7669 MV errors
[h264 @ 0x160f940]mb_type 55 in P slice too large at 41 22
[h264 @ 0x160f940]error while decoding MB 41 22
[h264 @ 0x160f940]concealing 5528 DC, 5528 AC, 5528 MV errors
[h264 @ 0x160f940]P sub_mb_type 12 out of range at 12 13
[h264 @ 0x160f940]error while decoding MB 12 13
[h264 @ 0x160f940]concealing 6637 DC, 6637 AC, 6637 MV errors
[h264 @ 0x160f940]out of range intra chroma pred mode at 65 8
[h264 @ 0x160f940]error while decoding MB 65 8
[h264 @ 0x160f940]concealing 7184 DC, 7184 AC, 7184 MV errors
frame= 0 fps= 0 q=0.0 size= 10kB time=10000000000.00 bitrate= 0.0kbit
[h264 @ 0x160f940]dquant out of range (-30) at 70 7
[h264 @ 0x160f940]error while decoding MB 70 7
[h264 @ 0x160f940]concealing 7299 DC, 7299 AC, 7299 MV errors
[h264 @ 0x160f940]AVC: Consumed only 97276 bytes instead of 217112
[h264 @ 0x160f940]cbp too large (4294967295) at 35 41
[h264 @ 0x160f940]error while decoding MB 35 41
[h264 @ 0x160f940]concealing 3254 DC, 3254 AC, 3254 MV errors
[h264 @ 0x160f940]mb_type 50 in P slice too large at 85 63
[h264 @ 0x160f940]error while decoding MB 85 63
[h264 @ 0x160f940]concealing 564 DC, 564 AC, 564 MV errors

Not sure if this is a bug as the file plays with "colored blocks" in Media Player Home Cinema, Quicktime and Windows Media Player but does play properly in the included Viewer/Editor supplied by Canon which uses Lead Tools.

Attachments (2)

MVI_0584-cut.avi (457.0 KB ) - added by lennie 12 years ago.
Clip from Canon Powershot HS100
ffmeg.log (5.7 KB ) - added by lennie 12 years ago.
Captured command line output

Download all attachments as: .zip

Change History (15)

by lennie, 12 years ago

Attachment: MVI_0584-cut.avi added

Clip from Canon Powershot HS100

comment:1 by Carl Eugen Hoyos, 12 years ago

Keywords: Canon Powershot removed

Please add the ffmpeg command line together with the complete, uncut console output.
The file you attached does not contain h264 video, was the file recorded with the camera?

comment:2 by lennie, 12 years ago

Sorry I attached the wrong file (the output file). The clip is a .MOV file from the Canon Powershot 100 HS but the input file (1 second long) is too large (~8MB). Is there anywhere else I can upload the clip to so you can test it?

I'm running it from WinFF but will try to extract out the full command line and command line output for you as well.

by lennie, 12 years ago

Attachment: ffmeg.log added

Captured command line output

comment:3 by lennie, 12 years ago

Here is the command line from WinFF:

"C:\Program Files (x86)\WinFF\ffmpeg.exe" -y -i "C:\media\Artifacts\MVI_0584-cut.MOV" -f avi -r 29.97 -vcodec libxvid -vtag XVID -s 1920x1080 -aspect 16:9 -maxrate 10000k -b:v 8000k -qmin 3 -qmax 5 -bufsize 4096 -mbd 2 -bf 2 -acodec libmp3lame -ar 48000 -ab 128k -ac 2 "c:\media\MVI_0584-cut.avi"

comment:4 by Carl Eugen Hoyos, 12 years ago

(I am not a native speaker - do you have a suggestion for a more understandable replacement for "together"?)

Please see for upload information or upload the sample to

Is the problem only reproducible if you also encode audio? If not, please use -an.
Is the problem only reproducible with libxvid or also if you use an internal encoder?
(Or in other words: Is the problem reproducible with ffmpeg -i MVI_0584-cut.MOV -an -qscale 2 out.avi ?)

Unrelated: Please note that the internal mpeg4 encoder is said to produce better results than libxvid. If you have a counter-example, please open a ticket.

comment:5 by lennie, 12 years ago

I uploaded 2 video clips to the VideoLAN File server ( as direct FTP access is blocked here at my work. The filenames are:


Hopefully you can also access these files for ffmpeg purposes. I also verified that the green blocks & lines appear in the MPLayer output when these videos are played (so it is a problem with the Quicktime decoder - doesn't matter what the output compressor is).

comment:6 by Carl Eugen Hoyos, 12 years ago

The videos show nearly identical artefacts with QuickTime, are you sure the Canon viewer shows the same amount of frames as all other players? (Can you confirm that the artefacts are only shown at the beginning of the video?)

comment:7 by lennie, 12 years ago

It is difficult to tell how many frames are being shown with the Canon viewer/editor (it has about 1 second granularity in "seeking" and "status". I can tell you that the artifacts tend to occur at the start of videos - but do have one clip where it happens near the end of the clip. Another clue is that this doesn't happen on many clips. I shot about 1000 clips of 5-20 seconds and only about 4-5 had artifacts like this. I suspect that the Canon Powershot camera is using some fields/features which are not supported by ffmpeg/Mplayer as well as Quick time - I was very surprised when I used the Canon .MOV editor (and exported to an .AVI) that the video appeared normally (with no artifacts). That is how I got the DVD authored but want to track down where the error is (and how the Lead Tools .MOV decoder doesn't have problems). I also have a ticket with Canon support to see if the problem is on their side but wanted to see what the Open Source community could do to fix/explain the artifacts.

comment:8 by Carl Eugen Hoyos, 12 years ago

Keywords: h264 added
Version: git-master

Could you provide the exported AVI for one of the two samples you uploaded? That would allow to compare if all frames are exported.

comment:9 by lennie, 12 years ago

The first one appears to "freeze" until after the artifact has passed (interesting) so tried the 2nd sample.

I uploaded 2 .AVIs (Motion JPEG) for the 2nd sample. By default the Canon software exports at 15 fps (so I forced it to output 30 fps) and uploaded that .AVI as well.

I am a Win32 software deveoper but haven't yet configured my environment so I can [re]build ffmpeg from source. Do you do your development on Ubuntu (or Windows with mingw & MSYS)?

comment:10 by Carl Eugen Hoyos, 12 years ago

I don't like Ubuntu, but I am currently happy with a very ancient OpenSuse release.

comment:11 by Carl Eugen Hoyos, 12 years ago

Keywords: mov added
Priority: normalminor
Reproduced by developer: set
Status: newopen

When decoding green-lines-blocks-from-canon-100-hs.MOV, FFmpeg shows artefacts for the first twelve frames (except frame one and two), no artefacts (and no decoding errors) are shown from frame 13 on. Both green-lines-blocks-from-canon-100-hs.avi and green-lines-blocks-from-canon-100-hs-30.avi start with frame 13, so I am not convinced the artefacts can be avoided, but starting with frame 13 may be possible.

(The original sample has ~24fps, the tool you used duplicates / drops frames similar to FFmpeg if another frame rate than the original is requested.)

comment:12 by Michael Niedermayer, 11 years ago

Are these files still in incoming ? i cant find them

Note: See TracTickets for help on using tickets.