Skip to content

Add custom title to stream page #1957

Closed

Description

@chrissv

I access my webcam streams through the direct URL for streams.html
When I do, the browser title is always "go2rtc - Stream"

Is there any way to specify in the config file for a camera an alternate title? I'd like to distinguish each camera with its own title

Thanks for a great utility!

Activity

  1. changed the title [-]Custom title?[/-] [+]Add custom title to stream page[/+] on Nov 26, 2025
  2. added this to the master milestone on Nov 26, 2025
  3. AlexxIT commented on Nov 26, 2025

    @AlexxIT
    Owner

    Currently, a stream doesn't have a name. It only has an ID, which also serves as a name. I added this ID to the page title.

  4. lulol commented on Dec 17, 2025

    @lulol

    @AlexxIT could the stream metadata title also be set to that stream ID?

    Using go2rtc v1.9.13 from Docker solves the stream page title issue present in v1.9.12.

    My issue is similar, but with the stream metadata title.

    mpv OSD and window legend shows all streams named as "go2rtc/1.9.13" since that is the metadata title it gets from the go2rtc streams.

    $ mpv --ontop --geometry=320x240-0+0 rtsp://<go2rtc_ip>:8554/camh264
     (+) Video --vid=1 (h264 320x240 5.000fps)
    File tags:
     Title: go2rtc/1.9.13
    Cannot load libcuda.so.1
    Using hardware decoding (vaapi).
    VO: [gpu] 320x240 vaapi[nv12]
    

    Using ffmpeg I can easily change the stream metadata title.

    $ ffmpeg -hide_banner -i rtsp://<go2rtc_ip>:8554/camh264 -rtsp_transport tcp -f rtsp -metadata title="Shack" rtsp://localhost:8554/fabada
    [rtsp @ 0x5598ff96a540] method SETUP failed: 461 Unsupported transport
    Input #0, rtsp, from 'rtsp://<go2rtc_ip>:8554/camh264':
      Metadata:
        title           : go2rtc/1.9.13
      Duration: N/A, start: 1.200000, bitrate: N/A
      Stream #0:0: Video: h264 (High), yuvj420p(pc, bt470bg/unknown/unknown, progressive), 320x240 [SAR 1:1 DAR 4:3], 5 fps, 5 tbr, 90k tbn, 10 tbc
    Stream mapping:
      Stream #0:0 -> #0:0 (h264 (native) -> mpeg4 (native))
    Press [q] to stop, [?] for help
    [swscaler @ 0x5598ffb03740] deprecated pixel format used, make sure you did set range correctly
    Output #0, rtsp, to 'rtsp://localhost:8554/fabada':
      Metadata:
        title           : Shack
        encoder         : Lavf58.76.100
      Stream #0:0: Video: mpeg4, yuv420p(tv, bt470bg/unknown/unknown, progressive), 320x240 [SAR 1:1 DAR 4:3], q=2-31, 200 kb/s, 5 fps, 90k tbn
        Metadata:
          encoder         : Lavc58.134.100 mpeg4
        Side data:
          cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: N/A
    

    So I tried to add a custom ffmpeg source to set the stream metadata title based on the json probe source info, without luck.

    ~/go2rtc/go2rtc.yaml
    
    streams:
      cam:
        - http://<cam_ip>/cam.mjpg
    
      camh264: exec:ffmpeg -hide_banner -v error -fflags nobuffer -flags low_delay -r 5 -i http://<cam_ip>/cam.mjpg -c:v libx264 -g 50 -profile:v high -level:v 4.1 -preset:v superfast -tune:v zerolatency -pix_fmt:v yuv420p -an -user_agent ffmpeg/go2rtc -rtsp_transport tcp -f rtsp -metadata title="Shack" {output}
    
      camh264a: ffmpeg:http://<cam_ip>/cam.mjpg#video=h264
    

    The resulting stream metadata title is always is set back to go2rtc/1.9.13.

  5. AlexxIT commented on Dec 17, 2025

    @AlexxIT
    Owner

    @lulol it's better to create separate issue, because your not about webui, but about rtsp

  6. AlexxIT commented on Dec 18, 2025

    @AlexxIT
    Owner
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions