[FFmpeg-user] 10 bit DNXHD encoding

[Tracey Jaquith]

On Jan 16, 2013, at 6:46 AM, Dave Rice <dave at dericed.com> wrote:

> Hi,
> 
> I'd like to encode to 10 bit DNXHD but get an error. Below is my command and output. I think I may need to specifically state the bitrate but am not sure what options are available. Any suggestions on what other parameters are necessary to get this to work.
> Dave
> 
> ffmpeg -y -f lavfi -i mandelbrot -t 4 -c:v dnxhd -r ntsc -pix_fmt yuv422p10le -s 1920x1080 test.mov
> ffmpeg version 1.1.git Copyright (c) 2000-2013 the FFmpeg developers
> built on Jan 15 2013 21:00:56 with Apple clang version 3.1 (tags/Apple/clang-318.0.61) (based on LLVM 3.1svn)
> configuration: --prefix=/usr/local/Cellar/ffmpeg/HEAD --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-nonfree --enable-hardcoded-tables --enable-avresample --cc=cc --host-cflags= --host-ldflags= --enable-libx264 --enable-libfaac --enable-libmp3lame --enable-libxvid --enable-libfreetype --enable-ffplay --enable-libopenjpeg --extra-cflags='-I/usr/local/Cellar/openjpeg/1.5.1/include/openjpeg-1.5 '
> libavutil      52. 15.100 / 52. 15.100
> libavcodec     54. 89.100 / 54. 89.100
> libavformat    54. 60.101 / 54. 60.101
> libavdevice    54.  3.102 / 54.  3.102
> libavfilter     3. 32.100 /  3. 32.100
> libswscale      2.  1.103 /  2.  1.103
> libswresample   0. 17.102 /  0. 17.102
> libpostproc    52.  2.100 / 52.  2.100
> [lavfi @ 0x7f917b83d800] Estimating duration from bitrate, this may be inaccurate
> Input #0, lavfi, from 'mandelbrot':
> Duration: N/A, start: 0.000000, bitrate: N/A
>   Stream #0:0: Video: rawvideo (RGBA / 0x41424752), rgba, 640x480 [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc
> [dnxhd @ 0x7f917b886c00] video parameters incompatible with DNxHD
> Output #0, mov, to 'test.mov':
>   Stream #0:0: Video: dnxhd, yuv422p10le, 1920x1080 [SAR 3:4 DAR 4:3], q=2-1024, 200 kb/s, 90k tbn, 29.97 tbc
> Stream mapping:
> Stream #0:0 -> #0:0 (rawvideo -> dnxhd)
> Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height

Hi Dave!!  8-)

So have you tried the few params to counter that?
Like "-b:v 1000k  -r 25  -vf scale=640:480"  (or similar/desired values)?

-tracey