diff options
| author | James Taylor <user234683@users.noreply.github.com> | 2021-08-28 09:32:30 -0700 |
|---|---|---|
| committer | Jesús <heckyel@hyperbola.info> | 2021-08-29 22:50:10 -0500 |
| commit | aacbf07ad726a4ef9bd79da33e4675dcf31bbad8 (patch) | |
| tree | d2909e83dc5f613e75c2b3944b54cd02cb3ccc67 /youtube/yt_data_extract/everything_else.py | |
| parent | 9d3ebca622f7eddd3539e4532957dcf8487feb72 (diff) | |
| download | yt-local-aacbf07ad726a4ef9bd79da33e4675dcf31bbad8.tar.lz yt-local-aacbf07ad726a4ef9bd79da33e4675dcf31bbad8.tar.xz yt-local-aacbf07ad726a4ef9bd79da33e4675dcf31bbad8.zip | |
av-merge: Use tickEnd+1 when calculating segment time ranges
tickEnd is inclusive, so two segments might have the following
ticks:
-- Segment 0 --
tickStart: 0
tickEnd: 44099
-- Segment 1 --
tickStart: 44100
tickEnd: 88199
When doing calculations in seconds about segment extent, there
were gaps between segment 0's end and segment 1's beginning. This
sometimes resulted in errors of not finding the corresponding
segment index inside these gaps.
Using (tickEnd+1)/this.sidx.timeScale is the correct method.
Signed-off-by: Jesús <heckyel@hyperbola.info>
Diffstat (limited to 'youtube/yt_data_extract/everything_else.py')
0 files changed, 0 insertions, 0 deletions