Try one of the settings below. The commandline is for ffmbc but should
still apply to ffmpeg too and the example below is using a jpeg (shouldn't
matter):

And what Nathan said!!!

*DNXHD*

"ffmpeg.exe" -y -f image2 -r 23.976 -i
"222_020-010_plate_el1_v001_wje.1%03d.jpg" -vcodec dnxhd -b 36M -r 23.976
-color_primaries bt709 -color_transfer bt709 -color_matrix bt709 -pix_fmt
yuv422p -threads 8 "commandline_ffmbc_dnxhd_36_8bit.mov"

"ffmpeg.exe" -y -f image2 -r 23.976 -i
"222_020-010_plate_el1_v001_wje.1%03d.jpg" -vcodec dnxhd -b 115M -r 23.976
-color_primaries bt709 -color_transfer bt709 -color_matrix bt709 -pix_fmt
yuv422p -threads 8 "commandline_ffmbc_dnxhd_115_8bit.mov"

"ffmpeg.exe" -y -f image2 -r 23.976 -i
"222_020-010_plate_el1_v001_wje.1%03d.jpg" -vcodec dnxhd -b 175M -r 23.976
-color_primaries bt709 -color_transfer bt709 -color_matrix bt709 -pix_fmt
yuv422p -threads 8 "commandline_ffmbc_dnxhd_175_8bit.mov"

"ffmpeg.exe" -y -f image2 -r 23.976 -i
"222_020-010_plate_el1_v001_wje.1%03d.jpg" -vcodec dnxhd -b 175M -r 23.976
-color_primaries bt709 -color_transfer bt709 -color_matrix bt709 -pix_fmt
yuv422p10 -threads 8 "commandline_ffmbc_dnxhd_175_10bit.mov"


On Mon, Jun 18, 2012 at 2:25 PM, Nathan Rusch <nathan_ru...@hotmail.com>wrote:

>   This is sort of a shot in the dark, but DNxHD only supports a few
> bitrates (36, 145, and 220 Mb/s). It may be that the ffmpeg implementation
> of the encoder requires you to explicitly pass the bitrate.
>
> -Nathan
>
>
>  *From:* Jacob Harris <ja...@jacobharris.org>
> *Sent:* Monday, June 18, 2012 2:02 PM
> *To:* nuke-users@support.thefoundry.co.uk
> *Subject:* [Nuke-users] DNxHD ffmpeg error
>
> I'm looking for some DNxHD ffmpeg help. I've stripped a more complicated
> command down to its barebones to try and get rid of this error. The error
> is:
>
> Error while opening encoder for output stream #4:0 - maybe incorrect
> parameters such as bit_rate, rate, width or height
>
> As soon as I change 'dnxhd' to anything else, like 'dpx', it works. Is
> this an Avid codec issue? I'm pretty sure the included libavcodec has the
> lastest codecs in it. Is this an installation issue? An ffmpeg bug? User
> friggin' error?
>
>
>
>
> Here's the long-form output:
>
>
> jacobharris@devmac001 : ~/ffmpeg
> $ ./ffmpeg -i ~/sequence.*.dpx -vcodec dnxhd -f mov ~/movie.mov
> ffmpeg version git-2012-06-09-04e2ac4 Copyright (c) 2000-2012 the FFmpeg
> developers
> built on Jun  8 2012 19:09:52 with gcc 4.2.1 (Apple Inc. build 5646)
> configuration: --disable-yasm
> libavutil      51. 56.100 / 51. 56.100
> libavcodec     54. 25.100 / 54. 25.100
> libavformat    54.  6.101 / 54.  6.101
> libavdevice    54.  0.100 / 54.  0.100
> libavfilter     2. 78.101 /  2. 78.101
> libswscale      2.  1.100 /  2.  1.100
> libswresample   0. 15.100 /  0. 15.100
> [image2 @ 0x10100f200] Stream #0: not enough frames to estimate rate;
> consider increasing probesize
> Input #0, image2, from '/home/jacobharris/sequence.1001.dpx':
> Duration: 00:00:00.04, start: 0.000000, bitrate: N/A
>    Stream #0:0: Video: dpx, rgb48le, 2276x1138 [SAR 1200:1200 DAR 2:1], 25
> tbr, 25 tbn, 25 tbc
> File '/home/jacobharris/movie.mov' already exists. Overwrite ? [y/N] y
> w:2276 h:1138 pixfmt:rgb48le tb:1/25 sar:1200/1200 sws_param:flags=2
> [ffmpeg_buffersink @ 0x100f13fa0] No opaque field provided
> [buffer @ 0x100f14900] w:2276 h:1138 pixfmt:rgb48le tb:1/25 sar:1200/1200
> sws_param:flags=2
> [ffmpeg_buffersink @ 0x100f14c00] No opaque field provided
> [buffer @ 0x100f15540] w:2276 h:1138 pixfmt:rgb48le tb:1/25 sar:1200/1200
> sws_param:flags=2
> [ffmpeg_buffersink @ 0x100f15840] No opaque field provided
> [buffer @ 0x100f16140] w:2276 h:1138 pixfmt:rgb48le tb:1/25 sar:1200/1200
> sws_param:flags=2
> [ffmpeg_buffersink @ 0x100f16440] No opaque field provided
> [buffer @ 0x100f16d60] w:2276 h:1138 pixfmt:rgb48le tb:1/25 sar:1200/1200
> sws_param:flags=2
> [ffmpeg_buffersink @ 0x100f17060] No opaque field provided
> [format @ 0x100f172e0] auto-inserting filter 'auto-inserted scaler 0'
> between the filter 'Parsed_null_0' and the filter 'format'
> [auto-inserted scaler 0 @ 0x100f17660] w:2276 h:1138 fmt:rgb48le
> sar:1200/1200 -> w:2276 h:1138 fmt:yuv422p sar:1/1 flags:0x4
> [dnxhd @ 0x101067800] video parameters incompatible with DNxHD
> Output #0, image2, to '/home/jacobharris/sequence.1002.dpx':
>    Stream #0:0: Video: dpx, rgb48le, 2276x1138 [SAR 1200:1200 DAR 2:1],
> q=2-31, 200 kb/s, 90k tbn, 25 tbc
> Output #1, image2, to '/home/jacobharris/sequence.1003.dpx':
>    Stream #1:0: Video: dpx, rgb48le, 2276x1138 [SAR 1200:1200 DAR 2:1],
> q=2-31, 200 kb/s, 90k tbn, 25 tbc
> Output #2, image2, to '/home/jacobharris/sequence.1004.dpx':
>    Stream #2:0: Video: dpx, rgb48le, 2276x1138 [SAR 1200:1200 DAR 2:1],
> q=2-31, 200 kb/s, 90k tbn, 25 tbc
> Output #3, image2, to '/home/jacobharris/sequence.1005.dpx':
>    Stream #3:0: Video: dpx, rgb48le, 2276x1138 [SAR 1200:1200 DAR 2:1],
> q=2-31, 200 kb/s, 90k tbn, 25 tbc
> Output #4, mov, to '/home/jacobharris/movie.mov':
>    Stream #4:0: Video: dnxhd, yuv422p, 2276x1138 [SAR 1:1 DAR 2:1],
> q=2-1024, 200 kb/s, 90k tbn, 25 tbc
> Stream mapping:
> Stream #0:0 -> #0:0 (dpx -> dpx)
> Stream #0:0 -> #1:0 (dpx -> dpx)
> Stream #0:0 -> #2:0 (dpx -> dpx)
> Stream #0:0 -> #3:0 (dpx -> dpx)
> Stream #0:0 -> #4:0 (dpx -> dnxhd)
> Error while opening encoder for output stream #4:0 - maybe incorrect
> parameters such as bit_rate, rate, width or height
>
> ------------------------------
> _______________________________________________
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
>
> _______________________________________________
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
_______________________________________________
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Reply via email to