Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Progress callbacks on long running adapters #648
Projects
Comments
|
hey @jminor i want to work on this issue kindly let me know how to get started |
|
Perhaps you could search for a similar feature in other Python software to see what specific patterns seem to work well elsewhere. Or, if you already have something in mind, you could propose a specific enhancement to the OTIO adapter system. Ideally the mechanism you propose would be flexible enough to work in otioconvert and otioview. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some adapter operations are time consuming, and tool authors would like to provide progress estimations. A progress callback, presumably with a percentage or other measure would enable this.
Specifically, we are looking for a proposal for an optional argument to the standard
read_from_fileandwrite_to_filefunctions that specifies a callback function. The callback function could take a % done amount, and maybe an informational string.The slowest adapter we have currently is the AAF adapter, so that would be a good use case to ensure this is working as intended.