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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding channel without active source #422

Closed
szergej01 opened this issue Oct 3, 2022 · 8 comments
Closed

Adding channel without active source #422

szergej01 opened this issue Oct 3, 2022 · 8 comments
Assignees

Comments

@szergej01
Copy link

szergej01 commented Oct 3, 2022

Hi,

Is it possible to make channels without active source for future streaming? If not, it will be a good future update for us! 馃挴

image

@noho501
Copy link

noho501 commented Oct 3, 2022

Agree

@saschafoerster
Copy link

I had the same issue. Now I need to open OBS, copy the RTMP-address, start streaming, and only then I can proceed to create new destinations. Would be great if I can create a channel and destinations without needing to start OBS, as in our situation this are two different tasks done by different people.

@ioppermann
Copy link
Member

From the wizard you can change to the "Advanced Setup". There you'll have the possibility to create a virtual source in order to create the channel. Whenever the actual source is ready you can change from the virtual source to the RTMP source.

@ioppermann ioppermann self-assigned this Oct 3, 2022
@saschafoerster
Copy link

Of course this is a workaround in the best meaning of the word. It is work and it is "around". And a painful one. I had to make 9 more clicks and decide which of the (irrelevant) options are the right one by creating a virtual stream, just for the simple task of creating a RTMP stream, which is a clear and easy option at the start, which I can't complete, when I don't send anything. I wish there was just a little warning (hey, there is no signal yet, would you still like to continue, yes), done. :)

@svenerbeck
Copy link
Member

Added it as a feature Request #345

If someone here has pressure on the function, he may contact us. There are certainly ways to speed up the development!

Thank you for your understanding.

Cheerio
Sven

@FilipStadler
Copy link

It would be very nice to have chanals that are not/never shown in the player site list because it can be virtual source or other input streams that can stream to the visible included playersite list.

  • like an option if input included in the player site list or not.

Non visible input streams can be used to push the stream for a visible chanal and it would allow to add sources that mainly are to allow publishing. A workaroud solution is maybe to run two restreamers where one is only for the secret chanals without a player Playersite active (it can be turned to non active) but selection if a chanal/stream is included in the playersite list would be the same :) I am a really not a programmer so it better I just share ideas and not make some bad ugly code with alot of bugs but I really like the design on the restreamer webgui.

@jstabenow
Copy link
Member

It would be very nice to have chanals that are not/never shown in the player site list because it can be virtual source or other input streams that can stream to the visible included playersite list.

  • like an option if input included in the player site list or not.

Non visible input streams can be used to push the stream for a visible chanal and it would allow to add sources that mainly are to allow publishing. A workaroud solution is maybe to run two restreamers where one is only for the secret chanals without a player Playersite active (it can be turned to non active) but selection if a chanal/stream is included in the playersite list would be the same :) I am a really not a programmer so it better I just share ideas and not make some bad ugly code with alot of bugs but I really like the design on the restreamer webgui.

Good idea @FilipStadler! Let's put it on the roadmap 馃憤

@svenerbeck
Copy link
Member

Hello @szergej01

We are closing your ticket #422.

This may be due to the following reasons:

  • Problem/inquiry has been solved
  • Ticket remained unanswered by you for a more extended period
  • Problem was explained and handled in another ticket

You can reopen this ticket at any time!

Please only open related tickets once! Always answer/ask in the original ticket with the same issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants