Add GET/POST/DELETE Record on demand API

[yelodevopsi]

Describe the feature

First off - fantastic work @aler9 and all contributing developers . This is a really wonderpiece of a media-stack 👏

I see that the record to disk on apparently all active streams are the only way to activate recording, and is great for surveillance.

However we have a bit different need:

• Is there any manual start/stop recording feature in the pipeline currently?

Its important that it don't interfere with the global settings ofc.

I'm thinking of extending the current Recordings API with a POST and PUT

• POST http://localhost:9997/v3/recordings/{name}/start - Start recording by path-name Response: Some recording-session-id

• PUT http://localhost:9997/v3/recordings/{name}/stop/{session-id} - End recording segment by path-name Response: Ok/bool?

Needed configs for mediamtx.yml

# This is the max time if /start is triggered but not /stop
recordTriggeredMaxDuration: 1h

If this is currently not in progress, could anyone direct me to where the triggering of recording is being done in the code, so I maybe have time create a PR in the future? 🙏

[eravellaSC]

Isn't this already possible by changing the single path configuration, setting record to true / false?

[yelodevopsi]

Isn't this already possible by changing the single path configuration, setting record to true / false?

I was just going to test/suggest this myself 🙃 i use runOnDemand param with a gstreamer pipeline attached.

Should the runOnDemandRestart param be set to yes/no if this record changes?

[yelodevopsi]

This is fantastic 😅 Works as intended. Thanks.

Closing this <3