Bugs and issues with (as well as feature requests for) PySceneDetect are mainly handled through the issue tracker on Github. If you run into any bugs while using PySceneDetect, please feel free to create a new issue. Provide as much detail as you can - include an example that clearly demonstrates the problem (if possible), and make sure to include any/all relevant program output or error messages.
When submitting bug reports, please add the command-line options
-v debug -l BUG_REPORT.txt to the very beginning of the
scenedetect command you are using, and attach the generated
Before opening a new issue, please do search for any existing issues (both open and closed) which might report similar issues/bugs to avoid creating duplicate entries. If you do find a duplicate report, feel free to add any additional information you feel may be relevant.
The development of PySceneDetect is done on the Github Repo, guided by the feature roadmap. Code you wish to submit should be attached to a dedicated entry in the issue tracker (with the appropriate tags for bugfixes, new features, enhancements, etc...), and allows for easier communication regarding development structure. Feel free to create a new entry if required, as some planned features or bugs/issues may not yet exist in the tracker.
All submitted code should be linted with pylint, and follow the Google Python Style Guide as closely as possible. Also, ensure that you search through all existing issues (both open and closed) beforehand to avoid creating duplicate entries.
Note that PySceneDetect is released under the BSD 3-Clause license, and submitted code should comply with this license (see License & Copyright Information for details).
List of Contributors
The following list details some contributors people have made to the PySceneDetect project. In no way is this list complete, nor is the list maintained in any particular order. In addition to those listed below, a significant number of other contributors have greatly helped the development of PySceneDetect by reporting defects/bugs and providing adequate information in order to fix these issues.
A full list of contributions to the PySceneDetect source code can be found here. A full list of contributions to both PySceneDetect with respect to bug reports and fixes/pull requests can be derived from looking at the list of all issues and all pull request.
In addition to those mentioned below, thank you to everyone who has submitted an issue, bug report, and/or pull request (see the links above for complete lists), as well as for those who continue to help the ongoing development of PySceneDetect. Your contributions continue to improve PySceneDetect, highlight the assets and talents of the FOSS community, and help to make the project's goal of being the most accurate scene detection program/library become a reality.
- @elcombato - improvement of video processing performance due to reduced memory copy operations
- @marcelluzs - improvement of video processing performance when using the frame-skipping feature
- @Hellowlol - improvements to software architecture and API development
- Lyuboslav Petrov @bubalazi - performance improvements to detect-content and detect-threshold algorithms
- @r1b - proof-of-concept implementation of detect-histogram algorithm
- Walter Schwenger @wjs018 - implementation of
export-htmlcommand and various bugfixes
- @tonycpsu - enhancements to
- @charlesvestal - various bugfixes and improvements
- Joshua Coales @joshcoales - investigation and resolution of ffmpeg "frame bleed" issues (clips not getting cut at the proper split points)
Another way to view the contribution list is via libraries.io. Thank you all for your help, support, feedback, and direction on the project as a whole!