record: set MTX_SEGMENT_DURATION in runOnRecordSegmentComplete

[moenodedev]

Provide MTX_SEGMENT_DURATION to the external command in the runOnRecordSegmentComplete hook. The duration of individual segments is useful when creating an HLS playlist.

Issue #2983

[moenodedev]

mediamtx.yml

pathDefaults:
  recordPartDuration: 500ms
  recordSegmentDuration: 1500ms  
  runOnRecordSegmentCreate: echo "path '$MTX_SEGMENT_PATH' duration '$MTX_SEGMENT_DURATION'"
  runOnRecordSegmentComplete: echo "$MTX_SEGMENT_PATH $MTX_SEGMENT_DURATION"

output

2024/06/09 18:03:57 INF [path skycam] runOnRecordSegmentCreate command launched
path './recordings/skycam/2024-06-09_18-03-57-411937.mp4' duration ''

2024/06/09 18:04:00 INF [path skycam] runOnRecordSegmentComplete command launched
path './recordings/skycam/2024-06-09_18-03-57-411937.mp4' duration '1.5'

[moenodedev]

The duration is also useful for monitoring

mediamtx.yml

pathDefaults:
  runOnRecordSegmentComplete: sh notify.sh "$MTX_SEGMENT_PATH" "$MTX_SEGMENT_DURATION"

notify.sh

#!/bin/bash

PATH=$1
DURATION=$2

if [ -z "$DURATION" ]; then
  echo "ERROR $PATH duration is blank"
  exit 2
elif [ $(echo "$DURATION < 10.0" | /usr/bin/bc) -ne 0 ]; then
  echo "WARNING $PATH duration is < 10.0"
  exit 1
fi

echo "SUCCESS $PATH duration is >= 10.0"
exit 0

output

2024/06/09 18:45:53 INF [path skycam] runOnRecordSegmentComplete command launched
WARNING ./recordings/skycam/2024-06-09_18-45-51-084911.mp4 duration is < 10.0

[aler9]

Hello, while the idea is good, this is implemented in a wrong way since MTX_SEGMENT_DURATION doesn't contain the real segment duration, but the maximum segment duration defined in the configuration.

[aler9]

replaced by #3456

[moenodedev]

Thank you!

[github-actions]

This issue is mentioned in release v1.8.3 🚀
Check out the entire changelog by clicking here