You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm actually trying to provide a chat overlay for OBS Studio, it actually use Matterbridge API as message provider.
Matterbridge can also unify different chat solution as one for the overlay enabling a nice double-stream chat overlay.
The issue is that only PeerTube require to change the room in the config for each live on the same channel. And restarting Matterbridge if someone else is using the solution is not a good idea.
Using permanent live which unfortunately use live slot even if not streaming, so it's not a solution.
Describe the solution you'd like
So I thought, what about creating a room related to the channel and make channel's live able to use it when needed.
It will add an option when creating a video to use a room related to the channel rather than the video.
So any live from the same channel with this option enabled will provide the same room.
It could also enable the possibility to recover the room, if a crash happen on a non-permanent live.
Note: There is no need to keep the room alive all the time.
Describe alternatives you've considered
Like I said changing the config manually on the server each time is not convenient and worse if someone is already streaming and using the solution.
Additional context
I tried to implement it myself but I'm beginner at JS/TS but I don't think I'd be able to make it.
If you want I can push my draft of the attempt in my repo.
The text was updated successfully, but these errors were encountered:
The fact that you add it to your roadmap is enough. When I ask for a feature, I wait for something like "yes, I will implement it in a future version" or a "no, this feature is not worth it more explanation", not a release date
Is your feature request related to a problem? Please describe.
I'm actually trying to provide a chat overlay for OBS Studio, it actually use Matterbridge API as message provider.
Matterbridge can also unify different chat solution as one for the overlay enabling a nice double-stream chat overlay.
The issue is that only PeerTube require to change the room in the config for each live on the same channel. And restarting Matterbridge if someone else is using the solution is not a good idea.
Using permanent live which unfortunately use live slot even if not streaming, so it's not a solution.
Describe the solution you'd like
So I thought, what about creating a room related to the channel and make channel's live able to use it when needed.
It will add an option when creating a video to use a room related to the channel rather than the video.
So any live from the same channel with this option enabled will provide the same room.
It could also enable the possibility to recover the room, if a crash happen on a non-permanent live.
Note: There is no need to keep the room alive all the time.
Describe alternatives you've considered
Like I said changing the config manually on the server each time is not convenient and worse if someone is already streaming and using the solution.
Additional context
I tried to implement it myself but I'm beginner at JS/TS but I don't think I'd be able to make it.
If you want I can push my draft of the attempt in my repo.
The text was updated successfully, but these errors were encountered: