To help functional testing, LaughFE's internal adjustment times are exposed.

Recap: when a laugh is detected by LaughFE, the time of the laugh itself it not
used directly; instead, the resulting Feature has some time prepended to try to
capture the thing that caused the laugh.

When functional testing the FEs we set up specially-crafted videos with features
at known points, so to make sure the LaughterFE is tested correctly we adjust
the tests by the amount of time the FE adjusts by so that it properly tests the
intended behaviour.

@see:
 - feature_extractors.py::LaughterFeatureExtractor

Video file with silent audio (generated with sox) -- should produce no features
since "-inf" are filtered by the FE

Functional tests for LoudAudioFeatureExtractor

Currently uses one manually-generated video with blank audio except between
15-20s where 1-2 sine tones are present

Only has a single property at present: SAMPLE_DIR for the path to where
sample videos are stored

TestVideoActivityFEFunctional now inherits from this instead of unittest.TestCase

Tests VAFE using a manually-created 30 seconds video with activity between
15 and 20 seconds.

Relatively quick!

Since it no longer simply produces videos this name is preferred

Also update tests to use updated module name

Uses unittest.mock.path to patch out call to matplotlib.pyplot.savefig()

TODO: better, more-granular tests of the bits of functionality here

mocks out calls to ffmpeg for obvious reasons

Extract method _run_no_output for two calls to ffmpeg

Fix feature.path → feature.source.path after Feature API change

Includes:
 - MockInterval
 - MockFeature
 - MockSource

Gets utils coverage up to 100% (for now)

@see: 0a08af4

Problems fixed:

 - Feature repr did not include feature_extractor since that API was changed
 - Intervals that were equivalent were not equal, so Features were not properly
   sorted or equal

Covers:
 - to_json
 - move_end
 - update_duration
 - unhappy path exceptions (mostly init)

Gets test coverage for this module to 100%! (for now)

This was done so the collection of loudnesses from an audio file could be mocked
in testing, but improves readability

TODO: review number of params and consider further refactoring

TestLoudAudioFeatureExtractor -- init only

TestSourceMedia is a mockinobject so

TODO: rename

Initialset of tests for LaughterFeatureExtractor and
RandomFeatureExtractor

Handles serialisation of custom classes via to_json() method if present

Outputs a representation of the Features extrated by the pipeline

Intent is to write a FE that takes the output so that a pipeline can be
're-run'

Output JSON could also be used with external tools

Annotate features, label axes

Creates a plot showing where in source video(s) the pipeline features
came from

This pvaes the way for parts of the pipeline that do not produce videos,
such as JSON, images, clips etc

TODO: rename module video_producers → producers

Runs a command returns stout as string, defined to aid testing

facilitates test mocking

Parses JSON, eg that output by the pipeline or defined manually and
produces Features that can be (re-)used with the pipeline

Take the mean of non-overlapping windows of scores

    Input:  list of tuples in the format (time, score)
    Output: list of tuples in the format (time, mean_score)
            (reduced set)

Drops lowest n% (default:33%) of scdet scores, since it scores every
frame

Python being what it is, this could be a single line in another method
but pulling it out into another function:

 - makes explicit what we are doing and lets us document why
 - makes for easier testing

Uses ffmpeg's scdet under the hood apropos of recommendation on
ffmpeg-user ML [1]

[1]: https://ffmpeg.org/pipermail/ffmpeg-user/2024-August/058535.html

Uses pyloudnorm under the hood to determine the loudness of the supplied
media file (handles videos transparently)

TBC: some sort of limiter on the number produced

TBC

TBC

This adds functionality that permits nearby Features to be considered
overlapping, in addition to Features which actual overlap

@see utils.py::Feature

BREAKING CHANGE: source now refers to a Source object, the FE that
created the Feature is now referred to by feature_extractor; path is
dropped

This should be more consistent, plus we needed a reference to the
original Source kept around anyway -- path worked but a Source object is
more consistent and explicit about intent

This lets us serialise properly

associated TODO: make precision configurable