Pretty new to OBS, but my searches haven't yielded all of the results that I'm looking to accomplish. I've been back through the forum a bit, but so far, I haven't found everything that I need. So, bear with me, but I'm trying to sort through a couple of issues that I think ASS can help me solve.
My basic setup is that I have 3 scenes (maybe in the same collection - definitely in the same profile - for now). I'd like to live stream all three to YouTube, simultaneously, on a schedule (say, every night from 7-9p). Where are the gotchas that I need to avoid in order to make this happen? I'll also preface this all that I'm sitting at work and my OBS instance is at the (non-work-related) facility, so I don't have it in front of me and I'm doing some of this from memory. So, in my newbie-ness, I may have some of the details/terminology wrong.
- I tried setting up a schedule last night, and when I did it while I was standing there, it worked. I started it, it ran for 3 minutes, and then stopped. So, I set it up to run from 7-9 and walked away. When I returned after 9p, there was a message about needing to create a broadcast. Unfortunately, I didn't get a screenshot of the exact message, but in the end, nothing had happened. What am I missing with the broadcast setup that will allow it to work with ASS in an unattended manner that doesn't require the broadcast to be created each and every time?
- Is it possible, through the macro somewhere, to change the name of the video that is created on YouTube? Ideally, I'd like to include the scene name and date in the title, but I don't see a macro action for altering the broadcast at all, which I'd expect I'd need to do. Is that possible?
- I found a post a few weeks ago about using the multi, profile and collection launch parameters, and I should be able to use scene as well now that I found the full list (for the reference of others - https://obsproject.com/kb/launch-parameters). Anything else that I should be considering to get multiple instances doing something at the same time? Luckily, they're all on the same schedule, so I can use the same macros for each instance.
- If I wanted a different schedule (say, on Monday, skip "scene 3"), could I use the "Scene" condition to stop that one from running?
Anything else that I should be considering? Other issues that you've run into in similar situations? I'm trying to make this as set-it-and-forget-it as possible, so any advice going forward would be appreciated.
Thanks!
If they're simultaneous with different content, then they probably need to be in different instances of OBS. And to keep those instances from running over each other, they need different settings. So that's probably a different profile even, not just a different scene collection.
Adv. SS settings are entirely in the scene collection, so if you want the same thing across all of them, you'll have to either duplicate your work, or set up the first collection and then duplicate that. Or you could export/import Adv. SS settings, since there's a button for that too.
Then there's the problem of using the same source in multiple instances. If you never do that, you're fine. If you do, then you may or may not might run into a problem. Historically, for performance reasons, pretty much every operating system restricted media access to one app at a time. The first app to request something, got it, and everything else would either be denied, or get something that is easy for the OS to create, like solid black, silence, etc. Some systems have removed that restriction now, others have not.
If yours hasn't, then you might use one of several plugins that are designed to send things between instances of OBS. You start the master first, which grabs all the sources, and then the master sends them to the slave(s). But only do that if you actually have to.
For the timing, you could have each instance independent with its own macro that looks for the same time. Or you could have a master/slave arrangement, where the master has the timing macro that not only starts itself but also sends a WebSocket message to the slave(s).
For the stream itself, and the error message, that's probably because of the way you set up the stream. I use a persistent stream key on YouTube. OBS is not logged into my account; it only has that key. Start throwing data at it, and it starts the stream. Stop throwing data at it, and it eventually times out. Start again, and it starts a new stream. Other methods might be "one and done", so that your short test worked, but then the long test didn't have anywhere to go because you already did the one and then it was done.
Play around and see if you can have OBS logged in, and still have the behavior that I have. If OBS is logged in, then Adv. SS can change some attributes of the stream itself...as long as YT decides to keep that API. They used to have a better one, then they killed it to get rid of spambots, and now it's back in a different, more limited form. The future is not guaranteed.
