[Bf-committers] MAXFRAME overflows

[Ton Roosendaal]

Hi,

I'm not aware of an Orange requirement for a bumped up MAXFRAME. We  
only did 11 minutes of animation, and 30k frames with 24/sec is over 20  
minutes.

Although bumping the max up to a larger value (MAXINT even) is fine,  
you cannot do this without changing in the code all shorts as still in  
use for frame indications (dont forget buttons!). That's a tedious  
job... there's quite some. :)

Next to that, we really need a good generic limits management in  
Blender... a lot of MIN/MAX settings are also there to facilitate easy  
user input by sliding buttons. A button with an integer range going  
into the millions isn't easy to set then anymore. Not even to mention  
it would help to have a button allowing to input time code or seconds.

So; yes, move it back to 30k for now, and invite someone to recode all  
shorts as used now first.

-Ton-


On 29 Apr, 2006, at 3:28, Joe Eagar wrote:

> Joe Eagar wrote:
>> Ken Hughes wrote:
>>> MAXFRAME and MAXFRAMEF got bumped from 30000 to 300000 during  
>>> sequencer changes; this has broken some things which are using  
>>> shorts to store those values (came across this in action constraint  
>>> code).
>>>
>>> I'd roll this commit back to the previous value, but haven't looked  
>>> to see if there anything which needs the new values.  Can anyone  
>>> comment?
>> Orange needed it.  Anything longer then 30000 seconds needed it.   
>> This is Peter Schaile's area of maintenance, I wouldn't mess with it.  
>>  Limiting the sequencer to processing 17 minute movies isn't good.
> Ooop, not 30000 seconds! I meant 30000 frames. :)
>
> joeedh
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-committers
>
>
>
------------------------------------------------------------------------ 
--
Ton Roosendaal  Blender Foundation ton at blender.org  
http://www.blender.org