Aaron Turner

Tried doing this with tee muxing, but didn't work with node fluent ffmpeg. Thus, there is logic for this in the form of "stream_outputs" in the config.json.

Honestly, if you know how to set up the nginx way, that is definitely going to be the best / fastest. But I think keeping the project JS only, and...

@vjasieg I didn't have that support in mind, but we can keep this issue open in case someone wants to pick it up :smile:

@dropitlikecross Definitely feel free to give it a try if you would like! :smile:

Agreed with @AndreasWebdev Streamlabs (as I understand), would require a browser. But this gets me thinking, with pupeteer, maybe that's something we can do? 🤔 But that would bump the...

@ALegitCookie Thanks for the workaround! @AndreasWebdev I think I saw something in the past about piping a chrome window through FFMPEG. But maybe I had a dream about it 😂

@AndreasWebdev > dreaming of ffmpeg? must've been a nightmare.. HAHAHAHA 😂 Probably was 😂 > in any ways, no thoughts on either option for splitting right now, it depends on...

So I talked to a colleague of mine on this issue for an upgrade path if/when we get the time to experiment with pupeteer. But we came to the agreement...

@AndreasWebdev Yeah, definitely. I think we can direct users (like for example, if a pi can't handle running puppeteer and ffmpeg), we can direct them to 1.0. Which could still...

Was thinking about this today and found this: “How to use headless chrome to screencast audio and video to an RTMP endpoint” by Sebastian Pereyro https://link.medium.com/qGCVJKJ8XW It's totally possible, and...