| Age | Commit message (Collapse) | Author |
|---|
|
|
|
content.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the names from the UI for content ratios.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
With a 29.97 source I had problems because the earliest decoder position was
one DCPTime quantum ahead of the last audio time; this looks like it was due to
the content-to-DCP time conversion using 1.001 as the ratio for 30/29.97 rather than
1.001001; I haven't investigated why. This all needs more careful consideration...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
with subs (which fails).
|
|
|
|
an inconsistent chain / private key set.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This call just doesn't take multi-stream into account. Removing it does
not trip any tests so I think it may be superfluous...
|
|
|
|
|
|
|
|
One regression here is that /1/01/1 will be seen as greater than /1/2/1
as the numbers are now coalesced so the comparsion would be 1011 cf 121.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
