Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Image Sequences are played at trimmed (source_range?) rate instead of ImageSequence's rate() value. #128

Open
ggarra13 opened this issue Oct 29, 2023 · 0 comments
Open

Image Sequences are played at trimmed (source_range?) rate instead of ImageSequence's rate() value. #128

ggarra13 opened this issue Oct 29, 2023 · 0 comments

Comments

@ggarra13
Copy link
Contributor

ggarra13 commented Oct 29, 2023 •
edited
Loading

When a video track has a video rate different (higher) than an image sequence's rate, the image sequence is played at the speed of the video rate instead of at the speed specified in otio::ImageSequenceReference's rate() value. I think this may be a bug.

Find attached a simple .otio file with BART first as a movie (at 30 FPS) and the BART as .jpg (at 24 FPS). Playback of this .otio file results in empty frames at the end of the .jpg sequence. Note that the audio is properly resampled to extend to the end.

bad_seq.otio.txt
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ggarra13