Skip to content

Conversation

@reinecke
Copy link
Collaborator

Adding docstrings to ImageSequenceReference CPP bindings.

reinecke and others added 3 commits December 17, 2019 16:52
…dation#602)

Added ImageSequenceReference MediaReference subclass schema.
…oundation#633)

* * Added initial support for `ImageSequenceReference`

* * Added sample otio file with `ImageSequenceReference`
* Added test for creating an rv session file with the sample file above

* * Use the `frame_zero_padding` from the `ImageSequenceReference` in stead of `start_frame` for frame substitution base

* * renamed _in and _out variables

* * lint fix
@codecov-io
Copy link

codecov-io commented Jan 21, 2020

Codecov Report

Merging #639 into imagesequence will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@              Coverage Diff               @@
##           imagesequence     #639   +/-   ##
==============================================
  Coverage          83.04%   83.04%           
==============================================
  Files                 74       74           
  Lines               2860     2860           
==============================================
  Hits                2375     2375           
  Misses               485      485
Flag Coverage Δ
#py27 82.95% <100%> (ø) ⬆️
#py36 83.02% <100%> (ø) ⬆️
#py37 83.02% <100%> (ø) ⬆️
Impacted Files Coverage Δ
...entimelineio-bindings/otio_serializableObjects.cpp 94.95% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cce5c7e...a048817. Read the comment docs.

…rror and NotImplementedError and made ImageSequenceReference provide a more helpful exception message when trying to get a frame url from a zero rate or zero duration instance.
@reinecke reinecke changed the title Added docstrings for ImageSequenceReference. Docstring/error messaging improvements for ImageSequenceReference Jan 24, 2020
Frame step sets number of frames to "skip". For instance, if
``start_frame`` is 1 and ``frame_step`` is 2, then the frame
number sequence will be 1, 3, 5, 7, etc.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment is great. The only thing I would add to it is a (admittedly pedantic) note about how the timing is implemented. IE played back at constant rate, but starting with the first frame in the sequence, which is on the screen for the time range [0, 1/rate), then the next image is shown for [1/rate, 2/rate) etc. This maps image files on disk to time ranges in the media time.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also any limitations on what the rate can be set to would be good to note here

@ssteinbach
Copy link
Collaborator

This change looks like its good to go but needs to be rebased again, (sorry!). Then we should land it.

@ssteinbach
Copy link
Collaborator

Hey @reinecke can you rebase this PR? It would be great to land this. Sorry about the delay!

@reinecke
Copy link
Collaborator Author

The docstrings covered in this PR were actually addressed in this commit: 2a1551e

The Error handling updates have been split into #783

@reinecke reinecke closed this Aug 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants