howto:obs

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
howto:obs [2020/12/23 00:44] – [Profile and Scene Collection] derpeterhowto:obs [2026/07/26 22:17] (current) – external edit 127.0.0.1
Line 1: Line 1:
-OBS Studio+OBS Studio
  
 Open Broadcaster Software (OBS) is a free and open-source cross-platform streaming and recording program built with Qt and maintained by the OBS Project. As of 2016, the software is now referred to as OBS Studio.[6] There are versions of OBS Studio available for Microsoft Windows, macOS, and Linux distributions. [ from https://en.wikipedia.org/wiki/Open_Broadcaster_Software ] Open Broadcaster Software (OBS) is a free and open-source cross-platform streaming and recording program built with Qt and maintained by the OBS Project. As of 2016, the software is now referred to as OBS Studio.[6] There are versions of OBS Studio available for Microsoft Windows, macOS, and Linux distributions. [ from https://en.wikipedia.org/wiki/Open_Broadcaster_Software ]
Line 5: Line 5:
 Related projects are: [[OBS Ninja]], … etc. Related projects are: [[OBS Ninja]], … etc.
  
-== Profile and Scene Collection+## Profile and Scene Collection
  
 Before you make any further setting, import the Profile and Scene collection from the [[events:rc3:artwork | Artwork]] page.   Before you make any further setting, import the Profile and Scene collection from the [[events:rc3:artwork | Artwork]] page.  
Line 11: Line 11:
 Even when using OBS with local cameras or other ingest paths this is a good start for you. Even when using OBS with local cameras or other ingest paths this is a good start for you.
  
-If you produce content for the main track (curated content), you can follow the guidelines on the Artwork page.+If you produce content for the main track (curated content), you could consider to follow the guidelines on the Artwork page.
  
-== Settings+## Settings
  
     * Stream     * Stream
Line 44: Line 44:
       * Output (Scaled) Resolution: 1920x1080       * Output (Scaled) Resolution: 1920x1080
       * Integer FPS Value: 25       * Integer FPS Value: 25
-{{ :howto:streaming.png?400|}}{{ :howto:recording.png?400 |}} 
  
-=== advanced recording for fuse-ts +{{:howto:streaming.png?400|}}{{:howto:recording.png?400 |}} 
-While the recording settings above will provide video files which can edited with e.g. shotcut or kdenlive, the following setting will provide 180 second mpeg ts snippets that can be used with [[projects:fuse-ts]] in combination with the tracker. HERE BE DRAGONS: While this seems to save solution we have not extensively tested it. Please test before the event starts!+ 
 +It has been reported that on Windows a Max Bitrate of 0 is not working. The best solution would be to replace windows with Linux, you could probably also just write 5000 in the field. 
 + 
 +### advanced recording for fuse-ts 
 +While the recording settings above will provide video files which can be edited with e.g. shotcut or kdenlive, the following setting will provide 180 second mpeg ts snippets that can be used with [[projects:fuse-ts]] in combination with the tracker.   
 +HERE BE DRAGONS: While this seems to be a save solutionwe have not extensively tested it. Please test before the event starts! 
 + 
 +{{:howto:schnipsel.png?600|}}   
  
-{{ :howto:schnipsel.png?600 |}} 
 The custom muxer line should look like The custom muxer line should look like
 <code> <code>
Line 56: Line 62:
 Where 'track1' needs to be replaced with the room name in your schedule. Where 'track1' needs to be replaced with the room name in your schedule.
 This will produce the 180s snippets and an m3u8 playlist. So if everything fails in terms of fuse you should still be able to just drop all the files into a video editing tool or ffmpeg This will produce the 180s snippets and an m3u8 playlist. So if everything fails in terms of fuse you should still be able to just drop all the files into a video editing tool or ffmpeg
-== HowTo's+ 
 +The tracker worker will do the mounting for you if everything works. You can try the mount yourself with 
 +<code> 
 +fuse-ts p="track1-" c="/home/user/obs/recoding-test/" st="2020-12-23_17-44-51-110787" numfiles=10 totalframes=4300 -oallow_other,use_ino "/video//fuse/rc3/track1/2342" 
 +</code> 
 + 
 +## HowTo's
  
   * [[events:rc3:speakers-prep:obs-template|How to import templates / starter pack]]   * [[events:rc3:speakers-prep:obs-template|How to import templates / starter pack]]
Line 64: Line 76:
   * [[howto:iphone-camera-obs]]   * [[howto:iphone-camera-obs]]
  
-== Usage at VOC+## Usage at VOC
  
 Our on-premise video productions typically use [[:voctomix]] or voc2mix, but started using OBS for the remote conferences in 2020 (DiVOCs, SOTM 2020, etc.) for speakers and in our "cloud" due to its flexibility. The first usecase is described at [[:distributed-conference#open_broadcast_software_obs|distributed conference]], the second at [[events:sotm2020#mixer_manual]] and https://github.com/voc/cm/compare/mixer-obs. Our on-premise video productions typically use [[:voctomix]] or voc2mix, but started using OBS for the remote conferences in 2020 (DiVOCs, SOTM 2020, etc.) for speakers and in our "cloud" due to its flexibility. The first usecase is described at [[:distributed-conference#open_broadcast_software_obs|distributed conference]], the second at [[events:sotm2020#mixer_manual]] and https://github.com/voc/cm/compare/mixer-obs.
  
-== Usage during rC3+## Usage during rC3
  
 For rC3 everything is different: We (VOC and the decentralised studios/channels) use several different video mixing solutions, both in software and maybe even in hardware. See [[events:rc3:production]] to get an overview: Speakers used OBS Studio to prerecord talks (provided with a [[events:rc3:speakers-prep:obs-template|template]]); studios use OBS Studio for playout or live video production, channels use OBS Studio as broadcast distribution switcher. A basic template for this second use-case can be found on [[events:rc3:artwork]]. For rC3 everything is different: We (VOC and the decentralised studios/channels) use several different video mixing solutions, both in software and maybe even in hardware. See [[events:rc3:production]] to get an overview: Speakers used OBS Studio to prerecord talks (provided with a [[events:rc3:speakers-prep:obs-template|template]]); studios use OBS Studio for playout or live video production, channels use OBS Studio as broadcast distribution switcher. A basic template for this second use-case can be found on [[events:rc3:artwork]].
  
 +## Tools and Tricks
 +
 +
 +### Adjusting audio levels for sources not on air
 +
 +If you want to check audio levels for sources that are not currently live, there is a small trick to get OBS to show them: simply pull the transition slider one pixel to the right. This will add the audio meters, but you won't see and hear the new sources yet.
 +### Better Integration of Jitsi into OBS Studio
 +
 +  * https://github.com/oe1rfc/jitsi2obs
 +  * https://git.theater.digital/ATD/jitsi-stream-client
 +
 +
 +### Lower Thirds as animated HTML for the main channels
 +
 +https://franconian.net/bauchbinde/?intro=1&theme=main&headline=advi%20sein%20talk&speaker=advi
 +
 +https://github.com/fl0rp/bauchbinde
 +
 +
 +### Lower Thirds as animated HTML for the assembly channels
  
 +https://franconian.net/bauchbinde/?intro=1&headline=test&speaker=test
  • howto/obs.1608684244.txt.gz
  • Last modified: 2020/12/23 00:44
  • by derpeter