Custom Frame Rate Does not allow some Common Frame Rates #43006

Closed
opened 2014-12-24 21:18:16 +01:00 by Aaron Carlisle · 15 comments
Member

System Information

Windows 8.0 Intel HD 4600

Blender Version

Broken: (Blender 2.73RC)
Worked: (Unknown)

Short description of error

Custom Frame Rate Does not allow some Common Frame Rates. For example 60000/1001 which is needed for the DNxHD Codec

Exact steps for others to reproduce the error

  1. Open Blender
  2. Change Output too a video file e.g. H.264
  3. Under Encoding change format to something that supports codecs e.g. AVI
  4. Under codec choose DNxHD
  5. Try to render
  6. You get the fallowing error :Frame size: 1920x1080p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 60000/1001
  7. Try to change to that frame rate
**System Information** Windows 8.0 Intel HD 4600 **Blender Version** Broken: (Blender 2.73RC) Worked: (Unknown) **Short description of error** Custom Frame Rate Does not allow some Common Frame Rates. For example 60000/1001 which is needed for the DNxHD Codec **Exact steps for others to reproduce the error** 1. Open Blender 2. Change Output too a video file e.g. H.264 3. Under Encoding change format to something that supports codecs e.g. AVI 4. Under codec choose DNxHD 5. Try to render 6. You get the fallowing error :Frame size: 1920x1080p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 60000/1001 7. Try to change to that frame rate
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscriber: @Blendify

Added subscriber: @Blendify

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sergey Sharybin self-assigned this 2014-12-24 21:30:26 +01:00

This isn't a blender bug, it's just some codecs in combination with containers and other settings are not supported by FFmpeg. We're doing our best to provide reasonable description of the error provided by FFmpeg and in this case it doesn't work very well. You can see full error message from FFmpeg in the console when running blender with --debug-ffmpeg command line argument.

It is in our todo to simplify codecs selection, but it's not so trivial at all, especially since FFmpeg does not provide any information about what is supported and what is not before you actually starting to encode.

Thanks for the report anyway.

This isn't a blender bug, it's just some codecs in combination with containers and other settings are not supported by FFmpeg. We're doing our best to provide reasonable description of the error provided by FFmpeg and in this case it doesn't work very well. You can see full error message from FFmpeg in the console when running blender with --debug-ffmpeg command line argument. It is in our todo to simplify codecs selection, but it's not so trivial at all, especially since FFmpeg does not provide any information about what is supported and what is not before you actually starting to encode. Thanks for the report anyway.
Author
Member

Can't this be fixed by changing the limit of values for the frame rate

Can't this be fixed by changing the limit of values for the frame rate

No, because some codecs also requires specific values of frame dimensions.

No, because some codecs also requires specific values of frame dimensions.
Author
Member

But we have customs frames dimensions

But we have customs frames dimensions

Wait, must have misunderstood your previous comment then. What exactly did you mean?

Wait, must have misunderstood your previous comment then. What exactly did you mean?
Author
Member

The reason we can't render in this codec is because it requires a custom frame rate which exceeds the value limits. So if the value limits are changed the codec should work.

The reason we can't render in this codec is because it requires a custom frame rate which exceeds the value limits. So if the value limits are changed the codec should work.
Author
Member

Alright so a just realized that there is a way to get around this. Under presets there are some options one of them being the frame rate needed for this codec. However it would be better for the design if you could choose this manually also.

Alright so a just realized that there is a way to get around this. Under presets there are some options one of them being the frame rate needed for this codec. However it would be better for the design if you could choose this manually also.

Every single value which is controlled by the preset is controllable manually as well.

Every single value which is controlled by the preset is controllable manually as well.
Author
Member

Added subscriber: @Sergey

Added subscriber: @Sergey
Author
Member

@Sergey I realized that and it uses 60/ 1.001 which is different then the error message. So is it possible to change the error message?

@Sergey I realized that and it uses 60/ 1.001 which is different then the error message. So is it possible to change the error message?

As said in the very first comment, the error messages are being generated by FFmpeg we only trying to do out best in displaying them.

As said in the very first comment, the error messages are being generated by FFmpeg we only trying to do out best in displaying them.
Author
Member

Aliright thanks I guess this can be more of a todo then

Aliright thanks I guess this can be more of a todo then
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#43006
No description provided.