[Bf-committers] Confusing Render, File Format and Encoding presets

[Remo Pini]

>From almost every other app, I'm used to a 3 decimal value, i.e. 
30.000
23.974
300.000
...

I'm sure there is a data type that can deal with this number... even if
it is an int being displayed divided by 1000...

It should be freely settable to any valid value (i.e. 0.001 ->
9999.999). Since there are cameras out there with framerates around
3200, it should allow for those values as well...

Just my 2c...

Remo

> -----Original Message-----
> From: bf-committers-bounces at blender.org [mailto:bf-committers-
> bounces at blender.org] On Behalf Of Troy Sobotka
> Sent: Sonntag, 23. Januar 2011 6:50
> To: bf-blender developers
> Subject: Re: [Bf-committers] Confusing Render,File Format and Encoding
> presets
> 
> On Jan 14, 2011 3:14 PM, "Damir Prebeg" <blend.factory at gmail.com>
wrote:
> > Is there any special reason why actual frame rate is calculated from
> > framerate and framerate base and not simply one float value for
> > framerate (eg. FPS: 23.976 instead of FPS:24 and Base:1.001)?
> 
> A float value isn't accurate enough to maintain sync.
> 
> > implementation of aspect ratio lock and one simple floating point
> > framerate.
> 
> What would be better here is to perhaps have a combo box that allows
> standard framerates to be selected. Off the top of my head: 24, 24
NTSC, 25,
> 30, 30 NTSC, etc.
> 
> Even then, it is adding complexity via an additional setting.
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers