Brandon Castellano

After re-reading @Tetsujinfr's comment I think as worded the original post is requesting something entirely differently. I had intended this to support detection on a smaller subset of the input...

I also found this project: https://github.com/ThomasWeckenmann/PyVfxShotDetect/tree/master/scenedetect May be useful when revisiting this.

+1 that this should be opt-in instead of opt-out by default. It would also be very useful to provide some functionality to suppress all log messages by passing a no-op...

Is there any way to repro this on x86 or does it have to be on an RPi? I had a look at the generated Cython code and it seems...

Oh sorry I meant specifically in the case where it hangs on `open` rather than #909 which hangs only when things are being destroyed.

Closing this issue out, as it's preferable to slowly push towards a more stable API rather than make a rapid breaking change like this. Each subsequent release should bring us...

Timecodes as of v0.6 are now obtained directly from the underlying VideoStream (via OpenCV VideoCapture or PyAV), but timecode calculations still assume a constant frame rate. This should improve accuracy...

As an update on this, there are no plans to do scene detection on GPU. There have been plenty of optimizations made since this issue was first released, so most...

I wasn't able to see any notable performance improvement, so I'll close this issue out. However, feel free to submit a pull request should you find any other optimizations. Thank...

Hopefully this use case can be covered in v0.6.2 with the use of the `load-scenes` command, which should work for both the `split-video` and `save-images` use case. Happy to reopen...