2011/5/24 Samuel Mimram <smim...@gmail.com>: > On Tue, May 24, 2011 at 2:59 PM, David Baelde <david.bae...@ens-lyon.org> > wrote: >> On Tue, May 24, 2011 at 2:52 PM, Romain Beauxis <to...@rastageeks.org> wrote: >>> I've struggled with int64 in the ogg module because there granule >>> positions are in64 and I would not recommend it.. Let's wait until we >>> really need it :) >> >> That's what I was thinking too. However, I hadn't done the >> computation: 31bits is only good for 13 minutes of ticks at 44100Hz! >> It might be a good idea to revert to using seconds for cue_cut, and >> perhaps to consider switching units for ticks; with syntactic sugar, >> Int64 isn't so hard to manipulate, especially since we commonly use >> very few operations on ticks. > > Yep, I was surprised too the first time ;) Since 13 min is not that > huge I think we should really think about it. However, I am fine with > the int64 solution too...
On a related topic: what about generators? All duration values are in ticks, so an int. Does it mean that a buffer cannot contain more than 13 minutes at 44100 Hz?? Romain ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ Savonet-devl mailing list Savonet-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/savonet-devl