multi-service-rtmp-broadcaster
multi-service-rtmp-broadcaster copied to clipboard
michaelkamprath
Adding title and description (and other metadata) on the JSON file
Hi, I know that multiple endpoints (fb/youtube/twitch) etc is supported, but is there a way to include the other metadata in the JSON file? Or do I have to manually go to these services and set it up there?
Unfortunately, the JSON standard does not define any ability to create comments in the JSON itself. However, you can certainly put key/value pair element in any JSON dictionary where the key is unused by multi-service-rtmp-broadcaster, and use that for meta data and documentation.
Where did you want the meta data to be made available?
I stumbled upon your project looking for an alternative to mobcrush which I had been using for years to stream to twitch, youtube and facebook. I previously used the https://github.com/jprjr/multistreamer on a docker container til the complications on non https apps in fb made me abandon it.
Metadata might not be the best word but my need is more of setting the title, description, content type, game name for the streams. I was just trying to figure out a way to do it in one place vs manually setting each on all these services one at a time before streaming.
Upon checking it might be a little complex than passing the stream keys to a live URL as (from what I checked) your code is doing. Multistreamer had to employ the use of app keys to be able to modify those title/description/game metadatas. https://youtu.be/HdDDtBOLme4?t=1621
Seems like API calls would need prior authorization like whats discussed in:
- https://developers.google.com/youtube/v3/live/docs/liveBroadcasts
- https://dev.twitch.tv/docs/api/reference#modify-channel-information
- https://developers.facebook.com/docs/live-video-api/guides/streaming/
Oh, I see what you are trying to do. Sorry, I totally misunderstood.
As currently written, multi-service-rtmp-broadcaster only manages the pushing of the stream. It does no interaction with the platform API's to manage the attributes or meta-data of the stream on that platform. Another entity must do that.
As currently written,
multi-service-rtmp-broadcasteronly manages the pushing of the stream.
And that is a great choice, to leave my +1
