Hello Thanks a lot for your detailed reply. It all makes sense now ! I've just started using profile definition in the XML because the "crop" filter would not properly guess the crop settings without it ; but I did not understand before that there was a default 4:3 profile.
So removing command line arguments fixed it. Wonderful program and non less wonderful support ! All the best geoffroy 2014/1/6 Dan Dennedy <d...@dennedy.org>: > On Mon, Jan 6, 2014 at 8:01 AM, Geoffroy Montel > <geoffroy.montel...@gmail.com> wrote: >> Hello list, >> >> I'm running into a problem where the rendered video is not the >> requested width : 682 instead of 640. >> >> * The MELT XML file starts with >> >> <mlt LC_NUMERIC="en_US.UTF-8"> >> <profile width="640" height="360" display_aspect_num="16" >> display_aspect_den="9" sample_aspect_num="1" sample_aspect_den="1"/> >> >> etc. >> >> * I'm generating the video with the following command line >> >> melt file.xml -consumer avformat:file.mp4 r=24 s=640x360 strict=experimental >> >> * ffprobe seems to say the format is 640x360 as requested >> >> ffprobe version N-59046-g1d0995e Copyright (c) 2007-2013 the FFmpeg >> developers >> built on Dec 13 2013 15:19:36 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5) >> configuration: --prefix=/opt/melt --enable-gpl --enable-version3 >> --enable-shared --enable-debug --enable-pthreads >> --enable-runtime-cpudetect --disable-doc --enable-libtheora >> --enable-libvorbis --enable-libmp3lame --enable-libx264 >> --enable-libvpx >> libavutil 52. 58.100 / 52. 58.100 >> libavcodec 55. 45.101 / 55. 45.101 >> libavformat 55. 22.100 / 55. 22.100 >> libavdevice 55. 5.102 / 55. 5.102 >> libavfilter 3. 92.100 / 3. 92.100 >> libswscale 2. 5.101 / 2. 5.101 >> libswresample 0. 17.104 / 0. 17.104 >> libpostproc 52. 3.100 / 52. 3.100 >> Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'file.mp4': >> Metadata: >> major_brand : isom >> minor_version : 512 >> compatible_brands: isomiso2avc1mp41 >> encoder : Lavf55.22.100 >> Duration: 00:04:59.99, start: 0.000000, bitrate: 515 kb/s >> Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, >> 640x360 [SAR 16:15 DAR 256:135], 382 kb/s, 24 fps, 24 tbr, 12288 tbn, > > The sample aspect ratio is that of MLT profile dv_pal. Quicktime is > showing you the video resolution it is using after converting it to > sample aspect ratio 1:1. > >> 48 tbc (default) >> Metadata: >> handler_name : VideoHandler >> Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 48000 Hz, >> stereo, fltp, 128 kb/s (default) >> Metadata: >> handler_name : SoundHandler >> >> * but MacOSX finder says the video dimensions are 682 x 360, and when >> I launch the video with either Quicktime or VLC, there are black >> borders on the left and on the right. >> >> I'm using melt v0.9.1, ffmpeg version N-59046-g1d0995e >> >> Have I done something wrong with the profile definition or the command line ? >> Many thanks in advance for your help ! > > You are making things more confusing by adding s=640x360 to the > consumer, which affects the profile. You see, there is always a > profile, and without specifying one at the melt command line, it > attempts to do an auto-profile. Then, it sees a profile in the XML. > Then, it gets additional profile information from the consumer > property you set. As you see, things can get complicated. When you > specify the avformat "s" property it thinks you are trying to take a > project authored in one profile and trying to output in a different > way. For example, you can take a 16:9 project with some things like > coordinates and sizes expressed in absolute pixel positions and > re-render that at a broadcast resolution, 4:3 with letterbox. In that > case, it loads the project as a virtual clip into a new composition > where the virtual clip has its profile expressed in the XML, and the > new composition has its own profile, which in this case is dv_pal with > a resolution override (but nothing else overridden). In short, you > need to either remove s= and let the XML profile element stand on its > own, or add aspect=@16/9 and progressive=1. > > -- > +-DRD-+ ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
