Displaying 4 results from an estimated 4 matches for "fps_d".
Did you mean:
fps_n
2008 Nov 21
2
[Schrodinger-devel] ogg dirac granulepos in oggz tools
2008/11/15 David Flynn <davidf+nntp at woaf.net>:
> On 2008-11-14, Conrad Parker <conrad at metadecks.org> wrote:
>> It seems oggz chop, merge and sort will need some attention to deal
>> with the Dirac granulepos and dependency ordering, so let's leave them
>> for the next release.
>
> ok. -- may be worth having them 'warn' if they are operating
2008 Nov 21
0
ogg dirac granulepos in oggz tools
...of skeleton
particularly rigorous[1].
Actually, i don't even know what the definition of granule_rate applies
to when a granule_shift is present[2]. Is it the whole number or the higher
word. If we assume it is the higher word, i believe the granulerate would
need to be 2*(1<<9)*fps_n/fps_d; in order to allow dumb tools to get things
vaguely right.
Ie, if you were to perform a remux by:
foreach logical_stream s:
foreach page with GP64 != 0xffff_ffff_ffff_ffff:
page.muxing_time <- granule_rate * page.GP64
output_order <- sort_and_interleave (all logical_streams) using x....
2008 Nov 25
0
ogg dirac granulepos in oggz tools
...gt;
>> Actually, i don't even know what the definition of granule_rate applies
>> to when a granule_shift is present[2]. Is it the whole number or the higher
>> word. If we assume it is the higher word, i believe the granulerate would
>> need to be 2*(1<<9)*fps_n/fps_d; in order to allow dumb tools to get things
>> vaguely right.
>
> a granule is a frame, field, sample etc., and granulerate is framerate,
> samplerate etc.
Err, yes -- just that GPH+L + 1 doesn't advance time by one picture
> Yeah; I've been thinking we should at least...
2008 Nov 21
6
ogg dirac granulepos in oggz tools
...y rigorous[1].
>
> Actually, i don't even know what the definition of granule_rate applies
> to when a granule_shift is present[2]. Is it the whole number or the higher
> word. If we assume it is the higher word, i believe the granulerate would
> need to be 2*(1<<9)*fps_n/fps_d; in order to allow dumb tools to get things
> vaguely right.
a granule is a frame, field, sample etc., and granulerate is framerate,
samplerate etc.
> [1] Mostly with regard to a hypothetical 'timeline' -- but these are
> questions for some later time.
Yeah; I've been thinki...