davethejackal
Member
I've already chatted to Jim about one of these, but here's a full list. The idea is to allow a user to run OBS on their gaming PC and then encode using an external encoder, and broadcast the encoded data via a second PC, even if it's just a laptop. Even with my i7 4790k I'd use this for games like Cities Skylines when cities get big (200k+ citizens).
1. We need to be able to send the full audio mix to the capture device, which could be done using OBS's monitoring function, however, at the moment you can't monitor sound from desktop audio. This needs to be fixed anyway, since most of the time you want to monitor audio to see how you've mixed say your mic vs desktop audio, so without the desktop audio, it's more or less useless.
2. Add an "auto project". Thus, each time you start OBS, in preview mode or whatever, it'd project the image of it's video mix (inc overlays etc) to the capture card, which windows sees as a monitor. I know, this might mean you do it inadvertently some of the time, but that is a non-problem. What is a problem is if you have to restart OBS for some reason, you get flustered and for some reason forget to enable the projector feature and only after 5 minutes does a viewer comment that they can't see your gameplay.
3. Instead of selecting a number to identify the monitor as the destination for a projector, select from a list of named monitors. So, for example, my monitor list might read "unnamed PnP monitor" and "AVERMEDIA GAMER LIVE". If I select "AVERMEDIA GAMER LIVE" it will default to that, even if initially it was Display 1 and the other Display 0 and later, when add a monitor and it becomes Display 1 and I reconnect my Gamer Live, and it switches to being Display 2 (or whatever) OBS still sends output to the capture card and not the new monitor.
OBS should also warn me if, at any point, it cannot project to the selected monitor.
1. We need to be able to send the full audio mix to the capture device, which could be done using OBS's monitoring function, however, at the moment you can't monitor sound from desktop audio. This needs to be fixed anyway, since most of the time you want to monitor audio to see how you've mixed say your mic vs desktop audio, so without the desktop audio, it's more or less useless.
2. Add an "auto project". Thus, each time you start OBS, in preview mode or whatever, it'd project the image of it's video mix (inc overlays etc) to the capture card, which windows sees as a monitor. I know, this might mean you do it inadvertently some of the time, but that is a non-problem. What is a problem is if you have to restart OBS for some reason, you get flustered and for some reason forget to enable the projector feature and only after 5 minutes does a viewer comment that they can't see your gameplay.
3. Instead of selecting a number to identify the monitor as the destination for a projector, select from a list of named monitors. So, for example, my monitor list might read "unnamed PnP monitor" and "AVERMEDIA GAMER LIVE". If I select "AVERMEDIA GAMER LIVE" it will default to that, even if initially it was Display 1 and the other Display 0 and later, when add a monitor and it becomes Display 1 and I reconnect my Gamer Live, and it switches to being Display 2 (or whatever) OBS still sends output to the capture card and not the new monitor.
OBS should also warn me if, at any point, it cannot project to the selected monitor.
Last edited: