Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple outgoing RTMP connections: 1) How to define? 2) Invalid YAML in documentation example, but accepted by Majestic. #194

Open
iGraveD opened this issue Sep 8, 2024 · 0 comments
Labels
low priority Not considered without funding rtmp

Comments

@iGraveD
Copy link

iGraveD commented Sep 8, 2024

How to define multiple outgoing RTMP connections?
E. g.

outgoing:
  enabled: true
  naluSize: 1200
  server:
    - rtmp://a.rtmp.youtube.com/live2/key1
    - rtmp://a.rtmp.youtube.com/live2/key2

or, even better:

outgoing:
  - enabled: true
    naluSize: 1200
    server: rtmp://a.rtmp.youtube.com/live2/key1
  - enabled: true
    naluSize: 1200
    server: rtmp://a.rtmp.youtube.com/live2/key2

These theoretical examples do not work, video is being sent to the 1st server only.

Documentation contains INVALID YAML in the corresponding section:

outgoing:
  enabled: true
  server: udp://192.168.1.10:5600
  naluSize: 1200
  - udp://IP-1:port
  - udp://IP-2:port
  - unix:/tmp/rtpstream.sock
  - rtmps://dc4-1.rtmp.t.me/s/mykey

You can check it with any YAML validator.

But Majestic successfully parses it. However, video is only sent to the 1st RTMP server, again.

@flyrouter flyrouter added low priority Not considered without funding rtmp labels Sep 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low priority Not considered without funding rtmp
Projects
None yet
Development

No branches or pull requests

2 participants