as I understand it, we need to add the ability to change parameters not only based on the confName parameter, but also on the source -> type parameter in each specific stream, because the type is different, there is rtspSource and there is rtspSession

{
      "name": "2222222222222222222222222222222222222222222222222222222222",
      "confName": "2222222222222222222222222222222222222222222222222222222222",
      "source": {
        "type": "rtspSource",
        "id": ""
      },
      "ready": true,
      "readyTime": "2024-09-02T10:24:46.565974242+03:00",
      "tracks": [
        "H264"
      ],
      "bytesReceived": 0,
      "bytesSent": 0,
      "readers": []
    }

{
      "name": "mystream",
      "confName": "all_others",
      "source": {
        "type": "rtspSession",
        "id": "d2cda1ab-4b44-4a45-a760-4facff809d4f"
      },
      "ready": true,
      "readyTime": "2024-09-02T10:24:24.167664431+03:00",
      "tracks": [
        "H264"
      ],
      "bytesReceived": 2099677,
      "bytesSent": 273508,
      "readers": []
    }

Hello, yes, lots of users want to control the individual record setting of paths linked to a shared configuration. We just have to think about a viable architecture for doing this, because i cannot think about a unique solution.

Currently, the server works with a top-bottom approach in which settings are stored in "path configurations", and paths cannot change settings on their own. The advantage of this is that multiple paths can be updated at the same time, by just changing a parameter in the "path configuration".

A completely opposite strategy would be to copy "path configurations" inside paths when they are created, and allow paths to change their settings independently from configurations. The disadvantage of this is that it wouldn't be possible anymore to update paths by just updating their path configuration, since changes would have no effect.

Probably the best solution is a middle way in between.

Hello everyone. Dear and mighty aler9, please tell me if you have any ideas or plans for implementing this? Thank you.

As workaround I do :

First call /v3/config/paths/add${path} with {record: true } to create configuration

Then call /v3/config/paths/patch${path} with {record: true } to update it if already exists.

Then call /v3/paths/get/${path} and check confName == name and if not get rtsp session id

Kick RTSP session with call /v3/rtspsessions/kick/${id} to reconnect client and use new configuration