Just saw your post. Not sure if you've solved this issue yet, but wanted to share a solution for anyone in the future reading this post. What we've experienced is that FB only generates a stream key when you go live.
That is NOT true. it depends..
I do NOT use a persistent key (for security reason). We use a FB Scheduled Event instead in FB's /Live/Producer, so that FB creates a consistent URL that non FB users can watch (without logging in, ex Roku). The new (non-persistent) stream key is available as soon as event is created (days/week+ in advance)
We found that to be limiting to get us prepped before going live. we use a third part app like switchboard or restream to be the intermediary proxy before going to FB. This way, it helps monitor the stream as it comes out from OBS or elsewhere (in our case we zoom to it) then going to facebook or youtube is as simple as clicking "Go Live". A much smoother transition. Hope it helps. Thanks.
SO, you have an option
- use (same) persistent stream key (FB or other)
or
- improve security and go non-persistent stream key. Even without Scheduling, if you go into FB's /Live/Producer and go to the Go Live Now area [note: area/page to setup, not actually truly Going Live] and select Streaming Software (vs locally attached camera) your next stream key will be available.
IF you want a new stream key for each video stream (a good security practice), of course you are going to have to retrieve that key and enter into whatever system is streaming to FB (be that OBS or a restream type service).
This is in no way limiting for our workflow, though is based on well-trained volunteers to run stream. We already monitor stream using FB's /live/producer, so I have no need for an alternate service for just monitoring stream (nor would I advise it for such a use case). Res-streaming makes sense when your upload doesn't have a solid connection, and you want a restreamer to prevent interruption; or you want single upload stream to go to multiple CDNs.
For our workflow,
- we start 1-2 hours before HoW livestream service (primarily to leave LOTS of time for any troubleshooting).
- As noted above, we use a Scheduled Event so all users connect/comment etc in one environment, and build community. Streaming to FB and YouTube at same time would be counter-productive for our situation (and I'd argue for most HoW).
- A very early step is to log into FB's /live/producer and get the new stream key, and enter that into OBS
- for years, we would test streaming (again 1.5+ hrs in advance) just to confirm OBS PC, camera, internet, etc all working. [However, recently the automated Go Live at scheduled time didn't work, so last week we didn't test stream well in advance, and auto start worked.. not sure if causal or just correlated.. tbd]
- we then go through Service Bulletin and other content, to make sure everything is ready, configured properly, test audio, etc. In our situation, due to volunteer who creates unique Service Bulletin per service, it is not uncommon to spend 30+ minutes cleaning up the Service Bulletin (PPTx in our case), updating OBS overlays when go camera full screen.
- leaving 30-45+ minutes of free time
- Schedule FB Video event requires streaming to start more than 10 minutes (was 15 at one time)
- we use FB's /live/producer to monitor technical aspect of stream, see and respond to comments as appropriate (ie act as Digital Usher), etc.
Once service is over, from the same /Live/Producer page, we manually end livestream (we turn off auto-end if stream interruption due to issues 2 years ago with Internet circuit), and then go check/adjust video thumbnail