Journalist Tool

Kineticist

  • HDashboard
  • IItems
  • ↓Ingest
  • SSources
  • KBeats
  • BBriefs
  • RIntel
  • QSearch
  • NName Review
  • +Health

v0.1.0

← Back to items

SSS Ep 4: Presenting OBS (Open Broadcaster Software) for Pinball Streaming

Mystery Pinball Theater 3000·video·1h 2m·analyzed·Oct 23, 2019
View original
Export .md

Analysis

claude-haiku-4-5-20251001 · $0.033

TL;DR

Technical deep-dive on OBS configuration best practices for pinball streaming with focus on multi-camera setups and CPU optimization.

Summary

Mystery Pinball Theater 3000 hosts an in-depth technical tutorial on configuring Open Broadcaster Software (OBS) for pinball streaming. The hosts discuss OBS architecture (scenes, sources, transitions), camera configuration challenges specific to pinball (tracking a physical ball across multiple cameras), CPU resource optimization for resource-constrained streaming setups, and practical workarounds for common hardware issues like USB controller bandwidth limits and camera detection problems.

Key Claims

  • Standard gaming streaming recommendations are not well-suited for pinball streaming due to the need to track a physical ball across multiple cameras (typically 3: playfield, player, LCD/DMD)

    high confidence · Host discussing how gaming-focused OBS guides default to 30 FPS or 60 FPS with single camera, whereas pinball requires different optimization

  • Display capture in OBS does not work with NVIDIA-only chipsets; must use Intel chipset or configure NVIDIA to use Intel for OBS

    high confidence · Host states this took ~1 hour of research to solve; workaround involves telling NVIDIA to use Intel chipset for OBS specifically

  • Logitech webcams and other USB cameras often require frame rate adjustments (e.g., switching between 29.95 FPS and 30 FPS) to resolve jittery video, even after auto-detection

    high confidence · Both hosts report independent experiences with this issue; Manu mentions even Logitech cameras need manual tweaking after detection

  • USB controller bandwidth is a hard constraint for pinball streamers with resource-limited laptops; exceeding capacity causes black screens or glitching

    high confidence · Host describes needing to reduce a 4th camera resolution from 720p to ~320x260 to stay within USB bandwidth limits

  • Studio mode in OBS can cause significant CPU overhead and frame dropping on resource-constrained systems, making it impractical for multi-camera pinball streaming

    high confidence · Host reports personal experience: studio mode caused CPU spikes and frame drops despite having all other settings optimized

  • Video format selection (YUV vs MJPEG) impacts ball tracking visibility and motion artifacts in pinball camera feeds

    medium confidence · Host states personal observation that YUV2 format improved ball tracking visibility compared to MJPEG or 'any' auto mode, though notes this may be device/environment specific

  • Downscaling from 1080p input to smaller canvas sizes adds CPU overhead; resolution should be set at source if resources are constrained

    medium confidence · Host discusses trade-off between native 1080p input with algorithmic downscaling (better image quality if CPU permits) vs. setting lower resolution at source

Notable Quotes

  • “all of the recommendations out there are for gamers who have one camera... it's not really geared towards pinball and tracking a physical ball while managing two other cameras or potentially even three other cameras.”

    Host (Unknown name)@ 1:59 — Identifies the core problem that pinball streaming requires different OBS optimization than standard gaming streaming

  • “I have everything dialed in to the point where one small adjustment and I start dropping frames.”

    Host (Unknown name)@ 9:34 — Illustrates how resource-constrained pinball streaming setups operate at the edge of hardware capability

  • “every time I go into OBS, I try and find one new setting to change and just change a little bit and see if it improves performance.”

    Manu@ 22:29 — Demonstrates iterative optimization approach; reflects how trial-and-error tuning is necessary for pinball streaming

  • “There's no way to tell in their software which one you're actually looking at because they're all represented by little images at the bottom on the sideways scroll screen.”

    Host (Unknown name)@ 23:23 — Highlights poor user experience with Logitech configuration software; explains why OBS's Configure Video button is a workaround

  • “if you're resource constrained, do it. Drop it, and then my opinion. It's not worth... You're outputting at 1080p.”

    Host (Unknown name)@ 30:09 — Clear recommendation: resource-constrained pinball streamers should downscale at source, not rely on OBS downscaling

  • “I had to drop that down to, I think it's like 320 by 260 or something like that... I just had hit the cap on USB data.”

Entities

Mystery Pinball Theater 3000organizationManupersonPinsomniacpersonPenn StadiumpersonMatt ScottpersonCameron Silver BallproductWolfmanpersonCNKpersonSuejackperson

Signals

  • ?

    content_signal: Mystery Pinball Theater 3000 producing long-form technical education content on OBS for pinball streaming; includes post-production cleanup and YouTube distribution as playlist format

    high · Host states Manu 'fixes it and then post' to YouTube; Penn Stadium requests podcast format; show mentions plans to edit and post content

  • ?

    technology_signal: Pinball streaming community standardizing on OBS with specific optimizations for multi-camera pinball setups; iterative tuning approaches across 75+ streams to handle CPU/USB constraints

    high · Host reports 75-80 streams of optimization; Manu confirms similar troubleshooting patterns; discussion of resource allocation specific to pinball's unique requirements

  • ?

    product_concern: Widespread issues with USB webcam detection/frame rate in OBS; Logitech cameras require manual frame rate adjustment even after auto-detection; Sony a6400 has color space issues

    high · Both hosts independently report frame rate adjustment fixes (29.95 vs 30 FPS); host mentions Sony a6400 always has red issues; Logitech detection unreliable across multiple models

  • ?

    technology_signal: Host discovered display capture in OBS non-functional with NVIDIA-only chipsets; required ~1 hour research to identify and implement Intel chipset workaround

    high · Host states 'took about an hour of research to finally get through the process'; explains NVIDIA workaround by configuring GPU to use Intel for OBS specifically

  • ?

    operational_signal: Pinball streamers must optimize for USB bandwidth constraints (hard limit ~4 cameras at reasonable resolution); recommend downscaling at source over OBS algorithmic downscaling for resource-constrained setups

Transcript

youtube_groq_whisper · $0.187

0:00
Tonight we're talking about OBS configuration for pinball streaming and I'm taking the lead on this one. I have spent a good amount of time changing up settings and I'm gesticulating but you can't see them because I don't do stuff up here I guess I do it down this level and my camera doesn't catch it we'll let that go so I've gone through a bunch of different iterations of streaming and my stream sucking in terms of quality and like alright I won't use that setting again We all have.
0:54
And I'm going to try, instead of very fast on my H.264 encoder, I'm going to try it with, I don't know, moderate. Let's go crazy. Let's see what happens. And suddenly my CPUs start spiking every once in a while, especially when the lights start flashing on a pinball machine. I'm at like 60 or 70% CPU usage and you can see not just my stream dropping frames but OBS actually starting to hiccup and have problems at that point. So I have played around with a bunch of those settings. I've done a decent amount of research online to figure out what those settings should be at least by default. And I've found and Manu and maybe other people have found something similar that all of the recommendations out there are for gamers who have one camera, who there might not even be good justification for moving above 30 frames per second on their streams. That's kind of like a, whoa, you're a great streamer, you go to 60. And it's not really geared towards pinball and tracking a physical ball while managing two other cameras or potentially even three other cameras. Right. Okay, cool. I'm ready to learn some stuff, man, because hopefully you have like a dummies guide for OBS going on right now maybe a little bit. Okay, and Pinsomniac says, same. I don't have a dummies guide, but I did throw together a PowerPoint presentation. So we've got 19 slides to try and make it through here. And because the last time we did this and I had the stream in a way where when we were looking at stuff, you couldn't see us. We changed it around. So here we go. Let's see if this works and how much our faces actually cover stuff up. So now you can still see us while we're going through and I'm walking through the PowerPoint presentation. Y'all see how impressive my man Don't Panic Flip is? This is an OBS. I'm already like, what? Sorry, I won't interrupt anymore. No, no, please. Continue interrupting. Throw questions. Throw stuff at, like, George. That doesn't make any sense. What are you talking about there? I've never seen a PowerPoint Twitch stream. I know. Thank you, Suejack. And as you can see, this is the scenes down here to the left. We have sources, and we'll go through and describe each of these. The audio, scene transitions, also called stingers, and finally your settings and the ability to start and stop your stream over here to the right. So let's move on to coming up with terminology. What's a scene? So a scene is a collection of sources, or I like to think of them as widgets, used to present the stream to your viewers. And each scene has those sources, which are images, media, camera, cameras, audio. It's just a collection of those. And this is kind of a quick little zoom in of what the scenes look like and then what those individual sources look like.

  • Animated media overlays and borders in OBS streams can cause stuttering and frame drops due to CPU intensity

    high confidence · Host reports stuttering in early Cameron Silver Ball streams where everything (borders, backgrounds, light effects) was animated simultaneously

  • VLC playlist plugins for OBS can be used to capture IP cameras, avoiding USB bandwidth constraints

    medium confidence · Pinsomniac viewer comment; host confirms unfamiliar with this but acknowledges it as useful option for cheap IP cameras

  • The host has optimized OBS settings across 75-80 streams to achieve a balance between CPU load, video card offload, and stream quality on their specific laptop

    high confidence · Host states: 'after 75 or 80 streams, I've gotten to a point where... I know exactly what every setting needs to be'

    • Host (Unknown name)@ 27:07 — Concrete example of hitting USB controller limits; demonstrates extreme compression necessary on tight hardware

  • “glitching... which means, which is almost 100% of the time, not enough power. They're not getting enough power.”

    Manu@ 26:35 — Manu's diagnosis of power-related USB glitching; adds practical troubleshooting insight

  • “Manu fixes it and then post and outputs it... as I haven't seen an actual podcast, but I have seen YouTube videos.”

    Host (Unknown name)@ 32:42 — Reveals that Mystery Pinball Theater 3000 edits and posts cleaned-up video/audio to YouTube; mentions Manu's role in post-production

    • Open Broadcaster Software (OBS)product
    NVIDIAcompany
    Intelcompany
    Logitechcompany
    Sony a6400product
    Handycam 405product
    Freegal Watchproduct
    YouTubeorganization
    Second Stringproduct
    TriCasterproduct
    VLCproduct
    Photoshopproduct
    Heroes of the Stormproduct
    Magicproduct
    Twitchorganization

    high · Host dropped 4th camera to 320x260 resolution to fit USB bandwidth; explains trade-offs between source-side vs. OBS-side downscaling; states 1080p native input not worth CPU cost for 40% of screen real estate

  • ?

    design_innovation: Pinball streaming community developing specialized OBS configurations (multiple scenes, specific source ordering) tailored to 3-camera pinball setup (playfield, player, LCD/DMD) that differs from standard gaming streaming

    high · Host emphasizes standard gaming guides inadequate for pinball ball tracking; explains primary scene, close-up scene, intro/break scene structure for pinball; mentions IP camera plugins as alternative to USB

  • ?

    product_concern: Animated media overlays in OBS streams cause stuttering and frame drops; early Cameron Silver Ball streams exhibited consistent stuttering when multiple animated elements looped simultaneously

    high · Host states 'everything was animated all the time' and 'the stream would stutter every once and then a while'; attributes to simultaneous animation loops; notes this is addressable in post-production

  • ?

    content_signal: Lack of pinball-specific OBS documentation and optimization guides; mystery theater hosts filling gap with custom PowerPoint presentation (19 slides) and podcast/YouTube content distribution

    high · Host notes 'recommendations out there are for gamers'; states 'I didn't want to miss' explaining OBS fundamentals; Penn Stadium requests podcast format to reach streamers and aspiring streamers

  • ?

    technology_signal: Pinball streamers on resource-constrained laptops using NVIDIA and Intel chipsets; offloading OBS processing to older video cards to reduce CPU load while maintaining stream quality

    medium · Host states goal to 'offload as much as possible to my older video card' and 'still maintain decent quality'; mentions forcing NVIDIA to use Intel for display capture; CPU spikes 60-70% even with optimization

  • ?

    operational_signal: Pinball streamers use iterative one-setting-at-a-time adjustment approach to diagnose and resolve OBS issues; examples include frame rate tweaking, camera re-selection, and source deactivation/reactivation

    high · Manu states 'every time I go into OBS, I try and find one new setting to change'; host describes 'stepping it down one of its settings each time'; multiple examples of toggling/re-selecting sources to wake cameras up

  • ?

    business_signal: Manu operates full-time video/audio production operation; cleans up and posts Mystery Pinball Theater 3000 streams to YouTube as playlists; separate YouTube channel for professional editing work

    high · Host states 'that's like his full-time job is to do video and audio stuff'; Manu 'fixes it and then post'; host references Manu's own YouTube channel; streams appear as 'playlist on Mystery Pinball Theater 3000 on YouTube'

    • 4:07
    And then we'll dive in once again into greater detail later. I just want to make sure that we're all on the same page with regards to vocab and at least a brief understanding of how OBS functions. So next up is a scene collection. You don't always want to display just the same scene. And in fact, in just this stream right here, we've switched between several different scenes to show off a different view based on like contextually with what we're doing. So and sometimes if we're chatting and we're chatting with people who are also chatting, I might want to display the chat window. And we have a scene specifically for kind of a close in larger view of us, Manu, and then the chat window over to the right. or, and this is another scene I have, which is the ability to see the full screen PDF that I have right now and still see our faces as we're moving through each slide of that slide deck. And that's just one example of two different scenes. And when you have multiple scenes together, that is a scene collection. and let's see, I kind of stepped off of the actual chat stuff there, but where are we?
    5:26
    This scene collection, great. And the other cool thing about having different scene collections is you might have your pinball stream and then you might stream Magic the Gathering or something else along those lines. So it's good to be able to reference those. And you can see here, I have one for coding, one for Heroes of the Storm, one for Magic, one for Pinball, and one for the streamcast that show up in the drop-down menu.
    5:50
    And when you have a scene collection, you typically break them down, at least for me and the investigation I've done. You have a scene for your intro, which is kind of waiting for the stream to start and people to get the message and show up. You have another one, which is maybe a close-up view. I think of it as chatting. You have your primary scene, which is the one where if you're gaming, it's just going to be a big one of your game for pinball and us. It's going to be the play field, the smaller image of us and the smaller image of the LCD and DMD. And maybe you have another one after that. Finally, you have some sort of a break scene. So imagine you run out of beer and you've got to go run someplace else. You typically have a scene just to let people know that you are going to be right back. sometimes and I need to invest some time into building this I would go a technical a technical one right like oh we're experiencing difficulties we need to figure this out and finally an ending scene would be would be another one now you can have many other scenes in fact I have two other scenes here I have my screen and Manu's screen so if Manu wanted to show something I can flip so that way what he's displaying goes into full screen. But that's just another example of why you have different scene collections and how you have scenes that are meant to do specific things in each scene collection. Wolfman says he needs a beer transition scene, which I think is a great idea. I do think that's a great idea. A big old thing of beer goes... Okay. I you know who we need to get on that would be Scott from Penn Stadium he would be amazing at putting something like that together so what's that I hit a new scene and the Pensomniac brings me another beer or beet Beets Battlestar Galactica and sources you can pull so sources are the things that you fill your scenes up with here is me clicking the plus sign and giving you access to all the different types. And each one of these has its own configuration screen. We're going to get into cameras and media types. Everything else is pretty straightforward. Those are the two that do have some customization that's worth learning a few little tweaks to.
    8:19
    Moving on. This didn't have a name, honestly, that I could find, but in Photoshop and other things, I've always called it the canvas or the thing that you're working on or drawing or building on. So at least for this conversation, unless you have a better name for it, Manu, I'm just going to call it the Canvas.
    8:39
    Canvas is fine. Technically, in OBS, it's considered either the program or the preview screen. Or the preview screen. Okay, I like that. I'll go with preview. So yours is going to be called either the Canvas, which I really love, because they both have a Canvas. Yeah. and depending on whether you're doing studio mode in OBS or you're just doing basic mode. Basic mode, you have a preview. In studio mode, you have a preview and a program. Ah, right. Okay, cool. That's because we Twitch stream the Freegal Watch, and I used to use a TriCaster, so I want to find all that. That's really interesting because I have heard you say things that let me know that you were using the studio mode, and I have never been able to get the studio mode to work well because I feel like it kills my CPU running in studio. I don't have excess cycles, I should say. I have everything dialed in to the point where one small adjustment and I start dropping frames.
    9:42
    And I was using studio mode for a while because it's amazing. It allows you to see what you're actually presenting to the audience, but then still have the ability to work on things on a different screen. And the problem with that is that, at least on the computer I'm currently using, it just can't handle it. And also stream at the same quality I normally stream at, which is frustrating. But, okay, cool. So we have the preview screen, and this is just where you have the ability to drag and drop and move stuff around, throw things onto the screen. This represents ultimately what your viewers are going to see.
    10:20
    Moving on. Scene transitions. You know, that cool graphic that plays when a streamer switches between scenes. That in OBS is referred to as a transition, and the graphic itself, if you're going to perform a search and try to find some of these, are referred to as stingers. Each scene in OBS can have its own unique stinger with different unique settings. It doesn't always have to be the same, or you can, by default, set everything to use one transition slash stinger. And they can have audio associated with them. You can silence that audio. I really like them. I think they're a great way to quite literally transition between scenes. I like your glitch transition, a stinger. That's pretty cool. I do like that too. Yeah.
    11:07
    Okay, and you have a settings area. This is going to be the next major component we'll tackle. So we're going to hit a couple of the individual source types and go through configuration on some of those. And then we're going to spend a good amount of time in settings talking about different settings and variations that at least I've gone through. And Manu, I'm willing to bet that you also have plenty that you've learned in having to deal with OBS and messing specifically with the output and I'm guessing video settings.
    11:40
    But this is where you specify the details of how you want your stream streamed, which could be resolution, how it's converted, upscaling, downscaling. and this is also where you can specify default settings. And I didn't want to miss that because it's really easy to forget that you actually set your default microphone and default like desktop computer audio. You set that in settings as well rather than trying to manually bring in a microphone, which was problematic for me the one time I forgot about the default microphone settings.
    12:10
    Okay, cool. So this is part two, which would be source configuration. and I wanted to take a little time to jump into common source types and how best to configure those. For pinball, the biggest, I would say the costliest or the weirdest ones that require the most configuration in pinball are going to be cameras. You have typically three of them, the play field, the player, and the LCD or DMD.
    12:38
    And I guess it's just the cameras is what I have identified here. Media, I think, is going to be the other type, which I end up jumping into.
    12:48
    Everything else with images, and actually I even say media is pretty straightforward, but there actually is a decent amount of configuration in there that required a little bit of learning in order to do well. But images, audio files for the most part, even though mine tend to crackle all of a sudden on this stream only, there's no reason for that. The majority of those are also pretty straightforward. I will throw out that you have the ability to pull in a display, a game, or a window capture. Window allows you to pull in like an app, like I'm running a PDF right now. So this is a window capture. And remember that OBS does not work well with Microsoft products on a window capture. Two, you have game capture. So that one's actually done really well by OBS. I think that's where they focused a lot of their effort, which was either windowed or full screen games. It does a really good job of identifying those and allowing you to be able to capture those in your display. Had no issues with that. And the third one doesn't work at all, which is your display capture, if you're using an NVIDIA chipset for your graphics card. So this is interesting. I figured, and this took about an hour of research to finally get through the process. But if you want to try and capture a display, and by display, I mean if you've got like three or four screens on your setup, and you want whatever shows up on the second screen to actually be on your stream, anything. If you drag something over into it, you want that to be displayed. That's called the display capture. And it doesn't work if you are not using an Intel chipset. Now, cool part about that is that in most laptops that have a really cool NVIDIA video card, you also typically have a board and an Intel chipset running on your board that is like a native component of your CPU board itself. So you can tell NVIDIA for specific applications, namely OBS, to use Intel over NVIDIA, and suddenly you can start doing display capture. I just went through that last week, and that was very interesting. I've got to say to go over that. But I digress.
    15:11
    And Pinsomniac says, on this too, there's a plug-in for VLC playlists. that's best to use for IP cameras and most cheap cameras. Okay, cool. So there's a plug-in for OBS that allows you to connect with IP cameras.
    15:29
    Wow, that's amazing. I didn't know that. Yeah I haven had to work with IP cameras yet Yeah Okay great picture of me while I was at Urban Air from just my webcam Don use the built webcams on your computers
    15:45
    So this is a video capture device is the type, and this is for capturing webcams or connected webcams or cameras, however you want to get that in there. Ultimately, it comes through as a USB device. And you first select the device in the dropdown, which you can see in that nice little graphic there. And it should automatically go through and set everything else to either the defaults or to something that it auto detects. A really good one would be resolution. If the incoming image is 1080p, it's going to typically set it to 1080p.
    16:21
    Or if you end up getting red on any of those, which happens all the time with the Handycam 405 for me, and not all the time, but every single time with my Sony a6400, you have to go in and manually adjust some of those because it doesn't auto-detect it nicely. Manu, have you ever run into any of those issues when trying to connect with a camera? It's funny you mention that because, yeah, just before the show, maybe two streams ago for me, I realized that even the Logitech webcams, even though they are detected on my system this sounds similar to your issue even on my system even though they're detected they may not be detected at the right frame rate until you just change something something yep right it's weird it's so weird like i just noticed this i i took my uh one of my cameras it was a little jittery and i was you know you do the wave of the hand in front of it to see how smooth it is and it wasn't quite smooth i switched it from 30 frames per second to 29.95 frames per second and it looked good okay all right cool i'll use 29.9 the next time it was at 29.9 and it didn't look good when i booted up i switched it to 30 and it looked good so for some reason if you're using webcams and george exactly the same thing with the sony camera i'll get red and sometimes i'll have to kind of wake them up with the settings. If you're using a Logitech web camera and your screen looks a little jittery and you know it's supposed to be fine, just change one of the, either the frame rate.
    18:02
    I had luck when I changed, just changed the frame rate and all of a sudden the camera snapped into a better, a better state than it was before. So I need to try doing that because when, when, when, when it doesn't work for me, I just select a different camera from the dropdown list and then go back and re-choose the other camera. Right, or you can say activate, deactivate. Yeah. Something to wake the camera up. Yeah, it's so odd. It's really great to hear that I'm not the only one that has to do something to trigger the OBS source to start working and do something. I was really concerned for a while that I was just that problematic person. I feel like that always has crap go wrong on their stuff, but they have all these six or seven workarounds. Oh, no, wait a second. I've got it. don't freak out we just have to flip this switch three times and do a little jig uh great now now it'll work exactly um so kind of lost my where was i so resolution here is important oh uh going back to pinsomniac i don't see rendering errors when that happens by the way uh i often don't see anything like not even a black screen uh well off like uh i'll give you a perfect example this camera wasn't connecting for some reason. There was nothing, no issues, no red. It just, it wasn't even on the display. So it was like the little box that represents where this camera should be was gone. And I could turn the visible on or off, and there was no box that showed up on the screen. I could click on the source, which is normally a nice hack. If you want to find where something is, you click on it in the sources, and it'll show up with a red box around it up on the canvas or the preview screen. And that wasn't happening. So I had to choose a different camera, bring it back to that camera before it showed up exactly like it was supposed to.
    20:04
    And frames per second should default to whatever you have your stream set to, which we haven't gone over yet, but we will. or match output FPS, but sometimes you don't want this. And I'm going to give a really good example. I run the stream at 60 frames per second, just like Manu suggested in episode three of Second String.
    20:27
    But I don't run my 920 Logitech at 60 frames per second for two reasons. One, I don't need to waste the bandwidth, and two, I don't have the 60 FPS version of that, I have the 30. And when it comes to USB controllers, I think physical controllers on my laptop, I think I only have two, and I'm constantly hitting the edge of what those can support. So anything I can do to bring down the amount of data traversing and hitting those two different USB controllers is really helpful. So even if I had a device that could perform at 60 FPS, I wouldn't do it. And I would downgrade it to 30 frames per second. Agreed. Specifically on this. The video format can also impact performance and how it looks. So not just like CPU performance, but if I leave my, and this works with the 405 as well, if I leave it set to any, I feel like, and this isn't measured in any way other than I was looking at it, and I feel like I could see the ball better. But if I left it at any, I saw more tearing or more issues with trying to track the ball than if I specify yuk2. I think it is yuk2. And I don't know if that is device or laptop specific or environment specific or CPU specific, but I would play around with those different formats to see what's best. Generally, as far as I know, that's device specific. Okay. It depends on what the native kind of... It's either YUK or MJPEG.
    22:11
    And yeah, so just like George says, just play with either one and see what gives you the best. Don't just go any and be like, we're done.
    22:20
    Or do it and then run a stream with that and then go in and try and play with the settings. I feel like every time I go into OBS, I try and find one new setting to change and just change a little bit and see if it improves performance. And after 75 or 80 streams, I've gotten to a point where, at least on this laptop, I know exactly what every setting needs to be in order to not overload my CPU, offload as much as possible to my older video card, and still maintain decent quality.
    22:56
    So there's video format. And also notice that you have access to the Configure Video button from the Properties menu. You can see it even here just below deactivate. That is awesome. Real time saver, especially if you've used Logitech's configuration screens for all their devices. There was a while there where I had two 920s and a 922 or whatever the 60 FPS version is. And there's no way to tell in their software which one you're actually looking at because they're all represented by little images at the bottom on the sideways scroll screen. That's all awful. But you can't name them or do anything unique to each one of those through their interface. So you just kind of have to guess which one it is. And it changes every time you unplug and plug something back in. So I think it has something to do with USB priority as to where they are in that list. It doesn't put like the 922 is higher than the 920. Anyway, the configure video button is a great hack because it knows specifically which properties menu to bring up through the, I don't think it's a native Logitech window. but it's interesting because my Logitech has a different set of settings available to configure it, as opposed to, let's say, my A6400 will bring up a much more slimmed-down set of settings. All I can really do is mess with saturation.
    24:29
    Okay, cool. So that is video capture. Moving on. There's a lot of text on this screen. Oh, my God, run away! Yeah, there's a lot going on here. But on the positive side, this is, I feel like, where a lot of the good stuff from this stream is going to be. Pinball and cameras. And what's funny is we've probably chatted about all of this so far.
    24:56
    But I'm just going to start at the top. Assuming you didn't build your computer specifically for streaming, which means you don't have an endless supply of HDMI receivers or inputs, and you don't have six different USB controllers and you're not running the i9 with 16 megabytes of cache and 32 gigs of RAM and multiple rated solid-state drives. Assume that you do have some resource issues that you're going to run against because it's a pinball laptop and you've bought pinball machines, which is obviously where you spent your money, instead of on a laptop. up. Penn Stadium, welcome to the stream. You got referenced a little bit earlier, actually.
    25:43
    And so what can you do? You can reduce the amount of data traversing each USB controller by reducing the resolution of each camera. So imagine, and this we were just talking about, times where your USB cameras, if you have some number of controllers on your laptop, and they can only accept a certain amount of data going across them before devices just stop working. And what you typically see is like a black screen in OBS, where a camera should be, and you should see actual imagery coming through. At least for me, it shows up as black when I've exceeded what my USB controller can handle.
    26:24
    And I'm not sure if you've seen anything similar like that, Manu. I've seen glitching. Glitching, okay, where things start to drop in and out? Right, which means, which is almost 100% of the time, not enough power. They're not getting enough power. And they're getting little spikes of power that they need, and they glitch. And that's that. Okay.
    26:47
    So displaying nothing. You've seen power issues with them glitching. So a really good time where that impacted the stream was in trying to bring in the fourth camera for me in order to get the tilt bob. I had to drop that down from, I think it defaulted to 720. I had to drop that down to, I think it's like 320 by 260 or something like that. Oh, my gosh. Yeah, before the image actually started showing up consistently without any issue.
    27:22
    And I think that was the first time where I dropped it down to something really small, confirmed that I could get the image up, then I put it back to 720, and then stepped it down one of its settings each time until it finally showed up. And that was quite literally at that point, I just had hit the cap on USB data.
    27:45
    And Pinsomniac says, just a consideration, IP cameras don't use USB, but they have a latency. Okay? Right.
    27:53
    Yeah. And this next one is actually a really good question. Do you really need to output 1080p from your device if the entire stream is outputting at 1080p and your play field, let's just shoot with the play field, only represents about 40% of the real estate on your stream? So what that says is your camera is giving you 1080. And does that make sense, right? To put that on your stream when you're already condensing 1080 down to something much smaller. You're essentially downscaling.
    28:28
    And somebody, CNK, what's up, man? Somebody has to do that downscaling. That's the thing about computers and streaming is it doesn't just happen. There's CPU cycles. that have to go through to convert a 1080p and make it this big?
    28:47
    And what's cool is, A, that's a great question. Thank you for asking that. I feel like the answer is yes and no. And Manu, feel free to jump in here if you have any other thoughts. But if you have the resources, so imagine I said, I'm going to make the assumption that you're not the person who has that amazing computer with the RAID solid-state hard drives and the 32 gigs of RAM. But if you are that person who has maybe one of the new 2070 NVIDIA cards, and you have the ability to push a lot of your processing onto the GPU, and you've got a decent i7 with 32 gigs of RAM, if you've got a laptop which in the past couple of months would have been around that $2,000 range, It might be worth outputting at 1080p natively from the device and allowing your computer to downscale that as opposed to letting the device statically set it and output it at a smaller resolution and putting it into the stream. Because there's a chance you could still get a better image using algorithmic downscaling instead of natively just saying, nope, here's the pixels. There's nothing else going on.
    30:03
    So that would be, I think, a time when you want to output from the device at 1080p. Otherwise, if you're resource constrained, do it. Drop it, in my opinion. It's not worth... You're outputting at 1080p. Your stream, the canvas or the preview screen is set to 1080, likely if you were going to output at 1080. And there's no way you're going to get your stream and all those pixels on your 1080 output play field to actually show up. It's going to get downscaled somewhere. Yeah.
    30:38
    And just for giggles, I threw in here a picture of two recent streams I've done where we were outputting at 720 in one and 1080 on the other. Now, these are different streams. In a perfect world, I would do two side-by-side comparisons of the exact same pen with the exact same equipment at the exact same time and give you, like, this is what it looks like at 1080 and this is what it looks like at 720. I think I blocking the 1080 designation Here I move Well played Well played But the one on the right is 1080 and of course we're blocking it, but that's not going to be an easy move. You know, I'm not messing with the stream. That's fine. Take our word for it. The 1080 looks better, but does it look that much better? Does it look like 20% increased CPU resources better? I don't know. You're going to have to feel that one out.
    31:42
    But that's the pinball cameras. Moving on. How much time we got? Wow. We've been going for a little over 40 minutes. Time is flying. Penn Stadium says, I hope you guys rip this audio as a podcast, as I think a lot of those wanting to stream or streaming would appreciate this. Can you please tell him what happens when we're done? yes uh pin stadium uh manu and i just found this out but that's like his full-time job is to do video and audio stuff all the time so uh manu has his own uh youtube channel and he cleans this up he uh what's what's what's the what's the phrase you're gonna clean it up in post or do it in post yeah fix it in post we'll fix it in post never never say that which i love now that i know that's an option and Manu hates it every time I mention it.
    32:37
    There's no we involved in this at all, but Manu fixes it in post and outputs it, I think, as I haven't seen an actual podcast, but I have seen YouTube videos. Are you also outputting this to some sort of an audio-only format? That would be great. We do use a lot of video references, but that would be great. It shows up as a playlist on Mystery Pinball Theater 3000 on YouTube if you're looking for it. There you go. And yes, he is Fancy Pants.
    33:06
    I'm so fancy. Okay, so media. This is the other type. For me, at least on my streams, I have collections of media source types and camera source types. And when I say media, I mean, honestly, media can mean anything. But specifically in this, I'm referencing MP4 or WebM files. and there's a few other format types that we can use but some sort of a looping video uh that that actually does something to to simulate some sort of an effect on the screen so these are all fun animated borders and containers we put around i really should read what i spent the time to to write because obviously i thought about it at some point instead of just winging it and looking at the camera over here. But these files can be ridiculously CPU intensive to run. I'm going to give a great example. The first two streams of silver, sorry, second string silver ball that we did, you'll notice that everything is animated. There was this cool light effect that was either coming from the bottom going up or the side going over in the background. The containers around Manu and myself were completely animated and looked amazing and just everything was animated all the time and you'll also notice in those streams unless Manu cleaned it up at some point because you can fix things in post that the stream would stutter every once in a while and I think that was consistent with all of the images looping at one time like at the exact same number of seconds and it killed you would see a stutter on the stream and that actually moved between computers. I switched to the same computer I stream pinball on and even there we were seeing the stutter on some sort of an interesting timer. And you can see the CPU spike. Like right now, while we're streaming at 30 frames per second at 1080p, I've got a Zoom meeting running which I'm using to pull MPT3K into this stream. I've got my own camera and we're pulling in the PDF, I'm at 4.8% on CPU. So huge, absolutely huge difference there, as opposed to like the 40 to 50%, which then you start to see stutters. And not that you would see dropped frames actually show up in OBS. I feel like those dropped frames only show up when it has to do with networking issues. You can actually see in OBS when you're looking at your own OBS view or the preview screen, you'll see that start to stutter, and that's the kind of stuff that your audience can see as well.
    35:56
    I was led to believe outside of using your GPU, which I see you have in there, I was led to believe that using WebM as a
    36:11
    animation container, so to speak, as opposed to MP4 would be a lighter choice and an easier container for OBS to handle. Now, I've heard exactly the same thing, but it could be that you literally told me that. Yeah, I think it was me.
    36:28
    So that's what I've been looking for is WebM as opposed to MP4. But you don't always get that. No, and I make them myself. Pentomniac says, yeah, WebM is better. I make them myself because I have Adobe and I use Media Encoder, but I'm sure there's a ton of free downloadable applications you can get that will convert your MP4s to WebM. And specifically, if you just show a video and it's done and you're not going to refer to it again, don't bother with that WebM. It'll load it, it'll play it, and it'll be done. But if it's a looping and intensive video that continues, then do WebM. So all of my transitions and everything on my stream is basically WebM.
    37:16
    And so I don't know. Your mileage may vary, but I'm just telling everyone that that's because MP3 is all-knowing. Also, Pinsomniac ended that with a question mark. He just wanted clarification. We're saying WebM is better optimized for streaming over MP4?
    37:37
    That's the general consensus. Also, I got that from EposVox on YouTube. If you haven't seen him, he has an amazing OBS, like a five-hour OBS tutorial. I'll leave a link in the description on the YouTube page where they do talk about what an OBS-friendly codec is to use for looping animations and such. and that that's the same guy you sent me a link to right i went through and watched about four or five of those videos amazing the only issue is that they're like two to three years old now and yeah he's put out a couple of videos since then to kind of do updates i think his most recent one was the end of 2018 um so i feel like he's due to go through and and rerun through all of those but still so helpful uh the the few videos that that i went through were were very very helpful here I just threw his name in the chat research EposVox yeah and you hit another item here actually when you were talking earlier about use an mp4 and just load it and run it once and be done there's actually settings in here that you have to make sure are checked if you don't want that file gunking up RAM and potentially slowing down OBS especially if the mp4 is a large file So I have some really cool background images I had purchased off of Envato something, Envato Elements, about a year ago. Not realizing that when I put them in OBS, I had four different files, each about 200 to 300 megabytes. And I had them as the background to four different scenes.
    39:27
    And my stream, once I started streaming, came to a crashing halt. It was so bad. So I downloaded a converter, which is another thing you referenced, where I was able to convert MP4 and adjust the quality. I can go lower and lower quality and output it as a much smaller file. Now, unfortunately, WebM isn't one of the output file types, but I think I'm going to look for that now.
    39:54
    WebM is an open source thing. And if you have Adobe Suite, you have to get a plug-in for Premiere to use it. It doesn't come out of the box. So you've got to do a little work to get WebM, but once you get it, generally speaking, it should be better. That's worth with an E instead of an O, just to be hip and cool.
    40:16
    But specifically in that case, you want to make sure... That was hip and cool? Yes. Sorry. No, no, that was good. So you want to make sure you uncheck loop. You want to make sure that you uncheck restart playback. Oh, you actually might want to check restart playback when the source becomes active, meaning that once you flip to that scene, do you want it to start from the beginning? And that's probably a good idea if it's a one-time use. If it's looping, it really shouldn't matter.
    40:45
    Using hardware decoding when available. That one you've got to feel out. I have found that certain file types are not processed nicely by my GPU. and I'm to the point now where I want to start putting additional strain on the CPU as opposed to my GPU. But then again, I have a much older GPU on this machine. So this is the 960M, I think, on my Razer laptop. And I'm two major, major, major revisions behind. That's, you know, you got the 1080 series and now they've got the 2080 RTX series.
    41:19
    And the other thing you'd want to do, and this is actually, I think I have something on this. If you have a solid-state hard drive or less than 16 gigabytes of RAM, you should check both restart playback and close file when inactive to reduce the footprint on RAM. That means your solid-state hard drive is going to be very quick to be able to pull that file back in, and don't cloud up your RAM with that file. So allow it to close when you move to a different scene, so that way OBS can reuse different resources and clean up some of the garbage that accrues as you move between scenes. If you don't have a solid-state hard drive and you have more RAM, like let's say you have 32, maybe you just want to load those files up and leave them in RAM so that way they load nice and quick when you start switching scenes. If you don't have solid-state and you don't have a lot of RAM, I don't have a fix for you. It sounds like you're really going to struggle to play those kinds of files. You don't have a stream.
    42:22
    Also, the really irritating one that says, lastly, make sure that show nothing when playback ends is unchecked. I haven't come across a situation yet, and obviously a situation must exist for a checkbox like that to exist, but I feel... I've got one. You do, okay. I feel like it's when I create a video sequence and I want it on a stream. Like, I used to do walkthroughs. So think of it like straight down the middle style, flying walkthroughs with a camera. I had one of those for all of my pins for a while. And when it was done, I didn't want it to disappear and just show the background.
    43:01
    I actually wanted it to stay on there until I switch scenes or to loop and go back through. But I feel like that is checked by default.
    43:10
    And I don't know if I can change that in OBS, but that's just one that I always have to uncheck, I feel like.
    43:16
    I use it once. Okay. I use it when I run my credits at the end. When the music finishes, the screen goes black.
    43:27
    That's all it does. Oh, okay. I like that. That's the show nothing. It merely means kind of show black video. Right. Also, 64K of RAM is plenty for everyone. It's plenty. No one will ever need more than 64K.
    43:44
    Okay, cool. So we're there. That's media. cool stream setup and configuration we've got two minutes to make it through this i think we're gonna i think we're just gonna fly right through it because this obviously isn't the most difficult stuff uh but the real question will they find treasure at oak island i am unfamiliar with that reference you want to can we get serious again okay jumping back in uh we're going to assume you're streaming to Twitch, even though Mixer, Caffeine, YouTube, and many others are all very popular, and that you've taken second-strings advice from Episode 3 and are streaming pinball at either 1080 at 60 frames per second or 720 at 60 frames per second. Because anything less than 60 frames per second is... MPT3K got it. I can't remain serious. I have to understand what this is referencing.
    44:42
    I don't know. It's just ridiculous. When they find treasure at Oak Island. I don't get it. It's just funny. Okay.
    44:51
    And Pinsomniac, yes, you can just download RAM. Yes, that's the way that goes. Okay, a lot of text. This is tackling what I think in simple mode, and we briefly talk about advanced. The settings here that will be most impactful on streaming. And I'm going to try and fly through this, but your bitrate is your target KBPS. And this is if you're in simple mode, your stream is automatically going to try and output at a quality consistent with the bitrate you have selected. Potentially, the single most impactful change you can make on your stream is going to be your bitrate followed very closely by the encoder. But we'll get there. I really quickly want to say, bit rates, if you're trying to stream at 1080 by 60, shoot for 4500 or better. And if you're streaming at 720, maybe 3000 or better. If you're on location, it's okay to drop below that. Realize that your stream is going to look like crap. But everybody understands if you're on location, there are no locations that have good internet. We just deal with it.
    46:02
    Neil, welcome to the stream and the curse of Oak Island on the History Channel. that didn't get me any closer unfortunately um the other good one and this is awesome to hear this uh you don't want to exceed 80 of your available upload so um if you run an upload test and you're right around that 10 megabyte per second 10 megabit per second upload rate don't go over eight uh and in general that just to do the math but twitch also unless you're a partner and are on their beta program for 4K streaming, you can't exceed 6,000 kbps. Ooh, 4K streaming on Twitch, huh? Yeah, everyone's getting there. Eventually Okay cool That is bit rates Manu did you have anything about bit rates Anything else you wanted to say No that spot on man Okay great The encoder, another very important setting, and this is the one that I ruined several streams with this because I couldn't tell how badly my computer was performing at the time because I didn't know where to look. But your encoder, you can, once again, if you're in simple mode and you're set to software, I think, you can, I should look at the text. Once again, I wrote the text. I should look to see what I wrote so I can say that. The default is x264 and your encoder preset, which that's what I was doing. I'm skipping down to the bottom. Sorry. Encoder presets, software x264. This one is going to rely on your CPU. If you have an NVIDIA graphics card that is good enough, capable enough to offload some of the processing to, you can go ahead and choose NVENC. N-V-E-N-C. I'm not going to try to pronounce that. And this will offload the encoding process to your GPU, which is great.
    47:57
    Or, I'm going to throw this out there because this was a huge performance increase for me. with the newest version of OBS. They released a new encoder,
    48:08
    which is called NVIDIA NVENC H.264 parentheses new close parentheses. But you can't get to it through... Thank you for laughing. But you can't get to it through the simple menu. You've got to step up your game and go to advanced in order to get access to that dropdown. So you switch over to advanced. That opens up a whole new window of configuration. Also, if you configure everything in simple and then switch to advanced, it's going to reset your bitrate back down to like 2000 or something. Really, really awful. So just make sure to double check all of your settings when you switch over to advanced. And choose, if you have an NVIDIA video card, that new H.264 encoder. It does drastically reduce the overall CPU cycles used without sacrificing a noticeable level of quality. It really was a big improvement for me.
    49:02
    Pinsomniac says, I still haven't figured out my NVENC encoder. Somehow get render frames dropped. That is really interesting, because if I remember correctly, you have the 1060 NVIDIA card. You have a much better video card than I have. So yeah, I think we're going to have to figure that one out. I'm due to go visit Pinsomniac at some point soon.
    49:26
    Next up, encoder presets. You'll see in the image that I have the encoder preset set to ultra-fast. There is ultra-fast, fast, ultra-sort of fast, moderate. I'm making stuff up. But there's like eight or nine different settings in here that set a whole bunch of different values based on just that adjective of whatever that word means. And in my mind, just play around with it. I have, and that is a setting that you can change live as opposed to some of the other settings you can't. And you'll see your stream change drastically. And typically what I see in terms of change is a lot of people view streams on their phones. And if you're on your phone, honestly, not a lot of this is going to impact you. I'm saying that now remembering of course that like the new iPhone 11 and the newest Galaxy Notes have monster screens that are probably better than 1080p style resolution and my eyesight sucks. Okay you're holding up exactly what I'm talking about it's a big screen so the bigger our devices are getting especially with like the folds coming out it's going to impact even mobile devices as much as it does desktop so I'll just stick with desktop for now. When I'm on my desktop and I am running at the ultra-fast encoder, and I've got kind of low-quality settings and max performance, meaning don't tax my CPU, or try to limit how much you tax my CPU, when I go to a full-screen view of that stream, you'll see, I swear, it's like individual pixels. It's not that the stream gets grainy, but that you really can't make out fine details. You won't be able to read things on the play field, or you might even struggle to differentiate between things that are similarly colored on the play field. And that's the kind of quality that changes drastically with the encoder preset that you choose in this dropdown. But realize, anytime you change that, you are drastically going to change the CPU and GPU performance as well.
    51:35
    That is the settings output. I think between that and the camera stuff, those were the two biggies. Manu, did you have anything you wanted to add about this screen? No, thank you for the explanation about the fast, very fast, whatever. Cool. More sort of moderately fast. Yeah.
    51:54
    Okay, cool. Settings, video. This one's actually pretty straightforward, but still very impactful. Your can... Oh, hey, it called it the canvas.
    52:04
    I feel better now. Yeah. But that was complete luck. By the way, I just decided to call it the canvas. No, it wasn't luck. You knew you saw Canvas somewhere.
    52:13
    Okay, well, yeah. So the Canvas resolution is set at 1920 by 1080, and your output resolution you can change. But guess what? Downscaling isn't free. So you might be thinking to yourself, gosh, the Internet here sucks. I'm going to downscale this to 720, but not thinking about the fact that you've got everything dialed in to work just right with your stream at 1080 and 1080. And when you drop it down to 720, your CPU goes up, even though you're no longer bogged down by internet. And by dropping your frame rate, by dropping your output resolution, you are going to decrease ultimately the quality of your stream and the amount of bits being pushed out, which is great then if you are on location and the internet sucks. But realize you're adding additional CPU cycles onto the stream because it has to convert 1080 down to 720.
    53:12
    So what did I actually write in here? We want either 720 or 1080. Remember that downscaling is an additional effort on your computer. And if your system is struggling, oh, and if your system is struggling and you find yourself outputting at 720 often, consider actually dropping your canvas down to 720. So that way you don't have to do any downscaling. It sounds like pinball streaming is hard. Why is everything about pinball hard? Everything about pinball is hard. Everything.
    53:43
    Scott, you know, I'm curious. Scott, was it easy to build the lights that you work on? Would you have called that easy? Because there's even a third person who has done something with pinball. And I feel like there's no way in hell Scott's going to say, oh, yeah, pin stadium lights were easy. um let's see i've not messed with the downscale filter it looks scary that's the best thing i can say about it which is fastest but blurry if uh if scaling um if you're gonna stream pinball i i can't stress this enough and and manu stressed it a lot during episode three please stream at 60 frames per second uh 30 frames per second looks awful there was a beautiful video that uh mpt3k put up, and I feel like you maybe even linked at some point into it, that actually it was amazing. By the way, I have referenced that multiple times, Manu, to other people to show the difference in what the stream looks like between 60 and 30 frames per second. And if you're going to stream, please stream at 60 on the playfield. It's just, it's night and day difference. And remember that this screen is not modifiable in stream. So once you decide beforehand to output at 720, you can't, oops, I meant 1080 or vice versa, or drop yourself from 60 to 30 without stopping the stream, editing those values and restarting it, which is going to create a different video, and you may potentially lose viewers. That's never happened to me, ever.
    55:18
    Okay, cool. We're coming up on an hour here, and we're almost done. So if you've seen mine or Manu's, although, Manu, you build all of your own content. That's amazing. I'm just not that skilled. So if you see this and you want the easy way out, let's say, to content, and you want some cool animated screens, and you want to throw some boxes around some stuff, where can you get those? Or animated backgrounds? or if you want some of the fun alerts and events as to what's actually happening on stream, well, there's three places that I go to for all of that content, Nerd or Die, Streamlabs, and Envato. And Envato is the last one that's really just, like, that was easy for me. It wasn't so much so that there aren't other opportunities out there, but we'll get to that. So Nerd or Die is a great site for overlays, sounds and alert notifications. Anything that has to do with the look and feel of your stream, they have a couple of free options. Their paid options are amazing. I've gone through, I think, three major versions or three major overhauls on what the look and feel of the stream is. This stream in particular is one of the overlays, complete overlay solutions that they offer.
    56:44
    I like this one. This one's great. I do, too. It kind of reminds me of the goblins from World of Warcraft, the Ratchet Town. This is the theme that should be associated with Ratchet Town.
    56:59
    So that's where I shop for overlays if I want to change the look and feel. It is. Dirty Toes, hey, welcome to the stream. And, yeah, it's a mad scientist, which I thought was very fitting for second string.
    57:13
    Widgets. So that's just Streamlabs. Like, there's other stuff out there that maybe does some cool things, but I feel like nobody out there does what Streamlabs does all in one location, giving you access to everything for no cost at all. So if you want chat windows, events, alerts, tip jars, viewer count, and, like, 20 other completely free components added to your stream that integrates completely with Twitch and with Streamlabs, it's great. And that's how you build browser-specific sources in your scenes, which are a collection of scenes that lead to scene collections. And that's just referencing all the stuff we were talking about earlier on with the vocab words.
    58:02
    They also offer paid-for services that allow some really interesting integrations. So, like, if you want to allow listeners to choose the music that you're listening to, or minigames to earn bits, and they offer a bunch more after that as well. So a little bit more on the audience participation and integration side. Cool.
    58:24
    And then finally... Oh, that's right. This was a video. I was going to play the video at the end. But animated backgrounds... Can I do it?
    58:38
    Okay, go ahead. No. they're the audiophiles uh animated backgrounds just really cool stuff uh i go to envato for that there's probably a hundred different websites out there that are filled with just as cool of stuff um envato uh what i did with that was um uh i bought a uh access like an all access pass for 30 bucks or something like that for a month and uh and downloaded just a ton of stuff during that month and then canceled it for month two so i only paid 30 bucks and and i got i was something probably like 30 or 40 different videos and uh and a couple of different audio files i may have to do that it's pretty cool it is pretty cool so that was uh envato uh elements thank you yeah that's it anyway that is the whole shebang wow so yeah that was we're only 15 minutes over i apologize for keeping you uh manu i feel like i could have gone through that 19 slides a lot faster well there's a lot we gotta say that there's a there's a lot to this game we covered the hardware we're trying to cover the software and you did a great job right there um i think what we'll do is uh we'll between uh don't panic flip and myself we'll gather up all the links that we talked about in the stream and uh the sources and i will add them to the description on the playlist that this goes up on so this will live on don't panic flips site for a little while and it'll live on the YouTube site for Mystery Pinball Theater forever so that if you have friends who need to know some of the resources and stuff. And the playlist view as well, right? I mean, think about it rather than the videos just dropping off on Twitch. Your YouTube station has a playlist where you can literally see everything in chronological order. Episode 1, 2, 3. So you can just kind of walk through the whole series if you're interested. Yeah.
    60:54
    Cool. Good job. Thank you. And back at you. This was fun. Awesome. Yeah. We could take a couple of questions. If there's no questions, then we could just say, thanks for watching, and we will see you guys on the next one.
    61:12
    Dice, I'm sorry, man. We are just ending. And MillsGameDev as well, thank you very much for hanging out. And it is God stuff. I thought it was God stuff.
    61:24
    That wasn't a typo. No, not at all. Yeah, sorry, Dice. Missed it. But this one was a little bit different. So this was second string. This is a little streamcast that MPT3K and I have been doing about once a month where we focus on a different topic associated with kind of how to stream pinball. So if you're interested in the hardware, the software, the process, MPT3K's YouTube, which he can link to, has a playlist where you can kind of go back and watch all of those individual learning episodes.
    61:59
    Cool. Doesn't look like we have any other questions, so I will say everybody have a wonderful night. Enjoy what's left of your Sunday and lots of coffee Monday morning. You guys take it easy.
    62:11
    Cheers. Oh, yeah, good call. Cheers. I'm out of wine. Thanks for watching!