rtsp to hls on demand without predefined paths

[unkn0wnpp]

Question

Hello. Having a couple of cameras with RTSP and H264/H265, their IPs in MySQL database. I want to get streams from these cameras on demand - by python getting needed IP and credentials, ask mediamtx and receiving stream, without adding all cameras in config. How to get this?
Is there any way to use some wildcards in config, and request stream something like that: http://ip_mediamtx:8888/rtsp://CameraLogin:CameraPass@CameraIP:554/media/video1/index.m3u8
Or something else?

[asturl]

Is there anything preventing your own python application from using the MediaMTX API (over http) to dynamically create the paths at runtime and then opening these path's streams in whatever supported protocol you require?

[unkn0wnpp]

Hi, I'm going to use Python. I found an API that allows me to add streams dynamically. However, I'm having trouble with cameras that output an H.265 stream. Chrome on Linux and Chromium on Raspberry Pi don't support it, so I need to transcode it to h.264 using ffmpeg. But I can't even find the sample path in YAML with runOnDemand ffmpeg for testing one camera and get HLS in Chrome.
H264 streams without transcoding shows perfect like HLS streams.

I've tried a couple of variants, like this:

paths:
cam1:
runOnDemand: ffmpeg -rtsp_transport tcp -i rtsp://user:pass@10.15.4.18:554/stream -c:v h264_nvenc -preset fast -rc vbr -c:a aac -f rtsp rtsp://localhost:8554/cam1

[kalwinskidawid]

@unkn0wnpp I guess we have the same problem. There is an example in the documentation, but it doesn't work as I expected.
I also started a discussion #5044, but I didn't get any support...

@aler9 any suggestions?

[kalwinskidawid]

@unkn0wnpp Did you resolve the problem?

[aler9]

It's impossible to understand why the H265-toH264 transcoding fails if you do not provide any detail or log. If you still have problems, open a dedicated bug report.