So I'm going to take everything you said and reply to it...
- "Keep your encoder at x264" - Unless you have a reason not to, which would be good to explain. Quick Sync and NVENCare both supported just fine on Twitch and are good fallback solutions when a CPU can't keep up with the work load of running a game and encoding with x264 at the same time. Also perfectly acceptable when recording locally where you aren't being limited by bitrate.
First off I said I believe you can't use the other settings, which I know at one time you could not. Might have been a long time ago but still... The video is for a high end pc and it is to show my settings to try and help people. With a high end pc I don't see why you wouldn't use x264. The video is for twitch so local recording is not what I'm even talking about.
- Despite the name CBR still allows for bitrate fluctuations. It's called a "leaky bucket" model where individual frames can still be different sizes.
I understand how that works, but with that one it's not going to jump up 1000... or at least it has not for me.
- Your explanation of CBR padding and custom buffer sizes (vbv-bufsize) are completely wrong.
I don't see how this is wrong... it goes up with the demand...
- Your explanation of bitrate/buffering is off but I'm glad you touched on it at least, it's frequently overlooked.
I pretty much said the higher the bit rate the harder it is for people to view. Which is correct.
- "Always stream at 720p, there's no need to stream at 1080p" - this depends on a lot of factors including CPU, available bandwidth, and source material. It does not appreciably affect a viewer's ability to watch -- you're thinking of bitrate. If you're associating higher stream resolutions with the higher bitrates typically required to make them look good then sure, and that would be a good thing to talk about. Explanations of when different output resolutions are appropriate would be much better.
First off I said I always stream at 720. I then explained the reason is because most people won't full screen you so they can see the chat. I'm telling people I do that because it uses less cpu. Also if you stream in 1080 p it's going to require you to use a higher bitrate.
- "If you're sponsored with Twitch stream at the highest settings you possibly can" - Just because viewers have access to transcoded versions of your video doesn't mean you should encourage streamers to make Source quality unwatchable for most. You can of course, but it's not something I'd actively recommend to people.
You got me there...
- Your explanation of 30 FPS vs 60 FPS seems to be almost completely wrong, except where you mention the increased CPU load. I feel like there's missing information here that led you to your conclusions but it's hard to tell.
Well I had a serious lag issue with Destiny at 30 fps, I posted here and NO ONE knew how to resolve my issue. Someone even told me to buy a new graphics card to fix it. Nothing was working. So I switched it to 60 fps and all of my issues went away.
- "Always disable Aero" I threw myself in front of a bus with this one, your explanation is backwards. There are very very few times you should disable Aero, primarily when you need to use monitor capture on Windows 7 (should be a last resort) or are stuck window capturing an unsupported video capture device like an HD-PVR, Without Aero window capture performance is super terrible, plus the target window won't be captured if another window is placed on top of it. Game capture should be unaffected at least.
I said," I always have disable aero, I honestly don't know what it does". Then I said something along the lines of window capturing being the main issue. Then I said I have unchecked it and it doesn't change a lot for me. Keep in mind I'm only showing my settings, if I don't know what something does I let the viewer know.
- Poor explanation of how the "Default" desktop audio option in OBS works, how the default device is selected, when recording from the default device is actually required, etc. (Hint: It's only needed for programs that can't choose an output device, like a web browser. Not Skype.)
I keep mine on default because it catches everything I need... I don't see how that was an issue.
- No explanation for forcing a mic to mono other than "I always do it".
"I always force mine to mono" is what I said... Like I said earlier the video is for my settings... Most people know what mono means.
- Scene Buffering Time's default value is 700ms and should be left there for the vast majority of streamers. 400 is an old default, too low, and causes audio issues for some people, particularly those with USB capture devices or mics.
I don't have a USB capture card or usb mic... 400ms works great for me.
- Actively advising users to tamper with the x264 preset without sufficiently explaining how it works and what's involved.
I don't have the time to fully explain it. I told them the slower the harder on your cpu, and to change it you have issues. Again, this is for a high end computer. Should be able to change it with a high end cpu.
- Disabling "Use CFR" and "Custom Params" because you don't know how they work, despite one being checked by default. (Hint: crf values don't work with CBR encoding, you'll primarily be using a crf=x param for a local recording with VBR instead.) "Use CFR" should always be checked unless you know for sure that you want a variable frame rate video. "Custom Params" should only be checked if you need to customize an encoding setting that isn't controlled elsewhere.
I told them I don't know how they work. At least I'm not acting like I do.
- "Automatic Low Latency" mode is not enabled by default and should not be enabled unless a support staff member suggests it or you know what you're doing and have a good reason for turning it on. It controls the effects of the "Minimize network impact" option under Broadcast Settings which also shouldn't be enabled by default.
It works fine for me.
- Almost no explanation of monitor vs. window vs. game capture, when to use them, what affects them, what they support, etc. A really large number of issues arise from users not knowing which source type is appropriate.
I was running out of time so I went over that shortly. I only use my avermedia since I use a dual pc setup so if I went into detail I would probably only show how to set up that.
- Remember that video capture devices include webcams, not just capture cards.
Webcams are very easy to setup.
I appreciate the fact that you are trying to educate me and I have learned something about the two things I said I didn't know. I feel like you skimmed through the video and didn't really catch the whole message.
