Replies: 1 comment 1 reply
-
Feel free to file a feature request or convert this into an issue, I'm open to supporting this use case. This is a good idea, it's not possible with all detectors, but if we consider doing a two-pass approach for most, then it's fine. It's worth exploring how the API might need to change for this. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
It would be awesome if scene_manager.detect_scenes() could be run with a sub frame range on an existing scene manager instance, so that multiple chunks could be run in parallel while sill referencing the first frame of the clip (e.g. when using ContentDetector). In other words run batches in a way that the resulting stats in the scene maneger instance match the ones you' get if you run the entire clip in one go.
Maybe this is already possible somehow?
I am currently writing a UI for this and would like to speed up the detection as much as possible.
EDIT:
I am realising this is detecting scenes for sub ranges is already possible but the challenge is to make share the scene manager instance across threads. Will keep testing..
Beta Was this translation helpful? Give feedback.
All reactions