*********************************************************************** ``scenedetect`` 🎬 Package *********************************************************************** ======================================================================= Overview ======================================================================= The `scenedetect` API is easy to integrate with most application workflows, while also being highly extensible. See the `Quickstart`_ and `Example`_ sections below for some common use cases and integrations. The `scenedetect` package contains several modules: * :ref:`scenedetect.scene_manager 🎞️ `: The :class:`SceneManager ` acts as a way to coordinate detecting scenes (via `SceneDetector` instances) on video frames (via :ref:`VideoStream ` instances). This module also contains functionality to export information about scenes in various formats: :func:`save_images ` to save images for each scene, :func:`write_scene_list ` to save scene/cut info as CSV, and :func:`write_scene_list_html ` to export scenes in viewable HTML format. * :ref:`scenedetect.detectors 🕵️ `: Detection algorithms: * :mod:`ContentDetector `: detects fast changes/cuts in video content. * :mod:`ThresholdDetector `: detects changes in video brightness/intensity. * :mod:`AdaptiveDetector `: similar to `ContentDetector` but may result in less false negatives during rapid camera movement. * :ref:`scenedetect.video_stream 🎥 `: Video input is handled through the :class:`VideoStream ` interface. Implementations for common video libraries are provided in :mod:`scenedetect.backends`: * OpenCV: :class:`VideoStreamCv2 ` * PyAV: :class:`VideoStreamAv ` * MoviePy: :class:`VideoStreamMoviePy ` * :ref:`scenedetect.video_splitter ✂️ `: Contains :func:`split_video_ffmpeg ` and :func:`split_video_mkvmerge ` to split a video based on the detected scenes. * :ref:`scenedetect.frame_timecode ⏱️ `: Contains :class:`FrameTimecode ` class for storing, converting, and performing arithmetic on timecodes with frame-accurate precision. * :ref:`scenedetect.scene_detector 🌐 `: Contains :class:`SceneDetector ` interface which detection algorithms must implement. * :ref:`scenedetect.stats_manager 🧮 `: Contains :class:`StatsManager ` class for caching frame metrics and loading/saving them to disk in CSV format for analysis. Also used as a persistent cache to make multiple passes on the same video significantly faster. * :ref:`scenedetect.platform 🐱‍💻 `: Logging and utility functions. Most types/functions are also available directly from the `scenedetect` package to make imports simpler. .. warning:: The PySceneDetect API is still under development. It is recommended that you pin the `scenedetect` version in your requirements to below the next major release: .. code:: python scenedetect<0.7 .. _scenedetect-quickstart: ======================================================================= Quickstart ======================================================================= To get started, the :func:`scenedetect.detect` function takes a path to a video and a :ref:`scene detector object`, and returns a list of start/end timecodes. For detecting fast cuts (shot changes), we use the :class:`ContentDetector `: .. code:: python from scenedetect import detect, ContentDetector scene_list = detect('my_video.mp4', ContentDetector()) ``scene_list`` is now a list of :class:`FrameTimecode ` pairs representing the start/end of each scene (try calling ``print(scene_list)``). Note that you can set ``show_progress=True`` when calling :func:`detect ` to display a progress bar with estimated time remaining. Next, let's print the scene list in a more readable format by iterating over it: .. code:: python for i, scene in enumerate(scene_list): print('Scene %2d: Start %s / Frame %d, End %s / Frame %d' % ( i+1, scene[0].get_timecode(), scene[0].get_frames(), scene[1].get_timecode(), scene[1].get_frames(),)) Now that we know where each scene is, we can also :ref:`split the input video ` automatically using `ffmpeg` (`mkvmerge` is also supported): .. code:: python from scenedetect import detect, ContentDetector, split_video_ffmpeg scene_list = detect('my_video.mp4', ContentDetector()) split_video_ffmpeg('my_video.mp4', scene_list) This is just a small snippet of what PySceneDetect offers. The library is very modular, and can integrate with most application workflows easily. In the next example, we show how the library components can be used to create a more customizable scene cut/shot detection pipeline. Additional demonstrations/recipes can be found in the `tests/test_api.py `_ file. .. _scenedetect-detailed_example: ======================================================================= Example ======================================================================= In this example, we create a function ``find_scenes()`` which will load a video, detect the scenes, and return a list of tuples containing the (start, end) timecodes of each detected scene. Note that you can modify the `threshold` argument to modify the sensitivity of the :class:`ContentDetector `, or use other detection algorithms (e.g. :class:`ThresholdDetector `, :class:`AdaptiveDetector `). .. code:: python from scenedetect import SceneManager, open_video, ContentDetector def find_scenes(video_path, threshold=27.0): video = open_video(video_path) scene_manager = SceneManager() scene_manager.add_detector( ContentDetector(threshold=threshold)) # Detect all scenes in video from current position to end. scene_manager.detect_scenes(video) # `get_scene_list` returns a list of start/end timecode pairs # for each scene that was found. return scene_manager.get_scene_list() Using a :class:`SceneManager ` directly allows tweaking the Parameters passed to :meth:`detect_scenes ` including setting a limit to the number of frames to process, which is useful for live streams/camera devices. You can also combine detection algorithms or create new ones from scratch. For a more advanced example of using the PySceneDetect API to with a stats file (to save per-frame metrics to disk and/or speed up multiple passes of the same video), take a look at the :ref:`example in the SceneManager reference`. In addition to module-level examples, demonstrations of some common use cases can be found in the `tests/test_api.py `_ file. ======================================================================= Functions ======================================================================= .. automodule:: scenedetect :members: ======================================================================= Module Reference ======================================================================= .. toctree:: :maxdepth: 3 :caption: PySceneDetect Module Documentation :name: fullapitoc api/detectors api/backends api/scene_manager api/video_splitter api/stats_manager api/frame_timecode api/scene_detector api/video_stream api/platform ======================================================================= Logging ======================================================================= PySceneDetect outputs messages to a logger named ``pyscenedetect`` which does not have any default handlers. You can use :func:`scenedetect.init_logger ` with ``show_stdout=True`` or specify a log file (verbosity can also be specified) to attach some common handlers, or use ``logging.getLogger('pyscenedetect')`` and attach log handlers manually. ======================================================================= Migrating From 0.5 ======================================================================= PySceneDetect 0.6 introduces several breaking changes which are incompatible with 0.5. See :ref:`Migration Guide ` for details on how to update your application. In addition, demonstrations of common use cases can be found in the `tests/test_api.py `_ file.