i should flag your post as offensive. oh wait, you're the boss :)

ffmpeg -i myfootage.mov
Video: h264, yuv420p, 1920x1080, 23.98 tbr, 23.98 tbn, 47.95 tbc
the clip report 1920x1080 in kdenlive.

ffprobe myfootage.mov
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'mvi_0581.mov':
Duration: 00:00:56.51, start: 0.000000, bitrate: 43769 kb/s
Stream #0.0(eng): Video: h264, yuv420p, 1920x1080, 23.98 tbr, 23.98 tbn, 47.95 tbc

ffprobe -version
FFprobe version SVN-r20090707, Copyright (c) 2007-2009 Stefano Sabatini
libavutil 49.15. 0 / 49.15. 0
libavcodec 52.20. 0 / 52.20. 1
libavformat 52.31. 0 / 52.31. 0
built on Jan 19 2010 21:59:04, gcc: 4.4.3 20100116 (prerelease)
FFprobe SVN-r20090707
libavutil 49.15. 0 / 49.15. 0
libavcodec 52.20. 0 / 52.20. 1
libavformat 52.31. 0 / 52.31. 0

now also true, vlc report the same footage as:
Resolution: 1920x1088
Display resolution: 1920x1080

ffplay the footage = no black border

surely the problem is on my side, but all i want to do: shoot / copy the footage in my computer / import in kdenlive / edit / encode / enjoy. no time to lie.

Hi,

my eos 550d definitly records 1088 lines. (some players read the header of the output files and some do not - thats why in some programs you see the bars and sometimes not).

I think that cropping does not affect any image quality so I crop it in kdenlive.

The black bars exist because your project settings do not match your source material. 1080 != 1088. Make a custom profile with 1920x1088 with sample aspect 1:1 and display aspect 1920:1088 and you will not have black bars. ffplay does not show black bars because it is a simple video player that does not need a "canvas" or "composition area" like a video editor. Similarly, if you use an image editor and start a new project with 1920x1088 and then paste into it an image that is 1920x1080, then you are going to have the white or black background appearing through somewhere.

i am transcoding to dnxhd, it works.
i guess my ffprobe is wrong and my source is really 1920x1088.
cheers

Did I understand correctly: The 550D indeed is recording 1088 pixels in height and not 1080? Other NLEs would throw the additional 8 pixels away, assuming it's only black, but we/ffmpeg don't here? And the solution is:

• Create a new project profile with height of 1088 pixels, or


• Use a 1080p project profile and apply the Crop effect on every 550D file

In the first case, cutting it down to 1080p again could easily be done by importing the 1088p kdenlive project in a new project with 1080p and simply apply the crop effect on the 1088p project, as in this video.

Correct?

edit: I noticed that applying a crop effect on a .kdenlive clip is not possible. Bug?

The answer to this question can be found by applying both MP4Box -info and ffprobe on the file and watch the result.

Hint: MP4Box gives the container's parameters, ffprobe the codec's parameters.

All this is at least confusing.

I think we should come to have a concise, clear and guiding message for users of that type of camera, which seems to be an increasingly popular one.

And also put this resulting info on the web site, where it could be found easily.

I'm not sure about the current state. Dan changed MLT to ignore the last 8 pixels some weeks ago. My brother recently tried to cut something with current MLT and it was 1088 again.

I can try to look at it this weekend if time allows.

This was fixed (treating 1088 as 1080 by cropping) in the 0.7.8 release. Since then, there was a regression that I just fixed tonight.

Hi,

I have the same problem but now with Nikon D1500, which I have bought a day ago.
I us kdnlive 0.8.0, mlt 0.7.2, ffmpeg 0.6.90

I was trying different setting and ffmpeg -i says differnet things than kdenlive.

eg. info from ffmpeg -i
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'DSC_0049.MOV':
Metadata:
major_brand : qt
minor_version : 537331968
compatible_brands: qt niko
creation_time : 2011-08-19 16:06:26
Duration: 00:00:33.12, start: 0.000000, bitrate: 20735 kb/s
Stream #0.0(eng): Video: h264 (High), yuvj420p, 1920x1080 [PAR 1:1 DAR 16:9], 19132 kb/s, 25 fps, 25 tbr, 25k tbn, 50 tbc
Metadata:
creation_time : 2011-08-19 16:06:26
Stream #0.1(eng): Audio: pcm_s16le, 48000 Hz, 2 channels, s16, 1536 kb/s
Metadata:
creation_time : 2011-08-19 16:06:26
At least one output file must be specified


As you can see it is 1920x1080 (as Nikon's manual says), but when I am trying put it into kdenlive I have got info that this file is 1920x1088 (!?)

I think the clip properties might still say it is 1088. However, there is special handling within MLT to treat it as 1080 to prevent the superficial black bars. vylaern, are you seeing the black bars?

With a 1088 source into a 1080P project a warning appears to say source doesn't match project, ignoring the helpful message, results in no black bars, however putting the 1088 source into a custom 1088 project, there is black bars top and bottom, so assume then that the special handling is MLT cropping the bottom 8 rows silently.

The helpful warnings can be a bit unhelpful at times. :-)

Perhaps this cases should be taken into account and not fire that warning message...

Another example is for framrate as well, such as deliberately importing a higher frame rate to playback slower for slow motion. We get a helpful message. With or without messages arguement works both ways.

For 1088, my own preference, which means very little, would be not to crop, warn its 1088 and use a 1088 project. It is incorrectly assumed that those 8 lines are black but they are actually recorded data. When considering why a camera does it why would it insert black lines when its simpler to just use data.

Again just my opinion and I'm sure reasons for doing the crop. Codecs such as CoreAVC you specifically tick the box to crop in codec settings, Apple Quicktime silently crops, Ffmpeg just gives you whats there. Maybe option to crop in project settings.

ddennedy > vylaern, are you seeing the black bars?

No, I don't see black bars either in computer or on TV from PS3.

The strange thing is, after rendering I have different resolutions - 1440x1080 (for HDV profile - PAL 1080 25p) and 1980x1080 (for H.264 profile), but on computer screen or on TV they looks identical, or I can even say than HDV looks better - but ffmpeg -i says, resollution for HDV its smaller 1440x1080 than H.264 1980x1080. I was using HD 1080p 25fps profile with oryginal clipc from Nikon D5100 - 1988x1080.

Bellow ffmpeg -i after rendering by HDV and H.264

Duration: 00:01:35.60, start: 1.400000, bitrate: 20477 kb/s
Program 1
Metadata:
service_name : Service01
service_provider: FFmpeg
Stream #0.0[0x100]: Video: mpeg2video (Main), yuv420p, 1440x1080 [PAR 4:3 DAR 16:9], 104857 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc
Stream #0.1[0x101]: Audio: mp2, 48000 Hz, stereo, s16, 384 kb/s

Duration: 00:01:35.64, start: 0.000000, bitrate: 10406 kb/s
Stream #0.0(und): Video: h264 (High), yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], 10041 kb/s, 25 fps, 25 tbr, 25 tbn, 50 tbc
Metadata:
creation_time : 1970-01-01 00:00:00
Stream #0.1(und): Audio: aac, 48000 Hz, stereo, s16, 359 kb/s