![]() Life is Strange is much better-looking as there's less full-screen motion and the game is more stylized with cartoony graphics, that are a lot easier to compress.The AMD Radeon RX 6700 XT arrives at an awkward time for next-gen graphics card buyers. The game needs more bits-per-pixel, and to avoid having your viewers buffer, you can't bump the bitrate. This is the sucky part of working within realistic limitations though. Not too much of a problem as many viewers don't fullscreen, just leaving the video popped-in, and may not even notice. Not much you can really do about that one aside from downscale to while casting Witcher it'll devote more bitrate per pixel, and alleviate at least some of the blur. DayZ does the same kind of thing with its grass and the like, and it munches it too. it's a TON of full screen high-variance movement with lots of ground clutter and detail. Yeah, Witcher 3 is going to be pretty hard on the encoder if you're constantly moving and spinning the camera like that. You're also duplicating a lot of frames in that testing log for some reason (anything over 1% should be looked at). on Medium should be eating quite a bit more CPU. ![]() That's actually a disturbingly low load number. Have to exit OBS and reopen it to close out the log file from your most recent cast. But start with Veryfast and go one step down at a time, testing each for at least 20-30 minutes, watching your CPU temperatures and throttling to make sure you're not overworking it.Ĭlick to expand.That looks like a testing log, it's only 8 minutes long, with around 3 of testing. ![]() The slower the preset, the better the compression that's used, and the better your stream will look at a given bitrate. With your CPU you can probably drop to Faster or Fast when streaming at 720p, depending on the game you're playing (BF4, ArmA II/III are all badly coded and will eat CPU, and DayZ is notoriously hard on encoders). They all offer very poor encoding quality, and will look *significantly* worse than x264 Veryfast. If you're using VCE, NVENC or QSV, stop it. If people can't watch your stream, why stream at all, after all? Go over this (even to 2500) and you'll have more and more people buffering. Do it from the Help menu, and post the link it gives you here.Ģ000kbps is the recommended maximum for non-partners, based on user metrics released by Twitch a while back. ![]() Seriously, we need it to be able to point out issues and see what's happening on the back end. I'd probably go with Bicubic (but test all of them!) as you're going with a power-of-two downscale essentially each 4 pixels become 1 pixel in the downscaled frame, which bicubic tends to work well with, and I believe can provide more clarity on text (one of the big problems with downscaling maintaining readability). The rescale methods (Bicubic/Lanczos) are more a matter of personal preference, and won't realistically cause a performance hit on any modern GPU. If you're set to 1080p and squash the source, then downscale that using the dropdown, you'll be taking twice the quality loss hit the in-preview squash-style downscale is a lower quality scaling method, and is individually per-source, so you'll get more artifacts and blur.ĭownscaling through the dropdown only will do a full-frame rescale post-compositing, which will help to maintain more relative image fidelity (think of it like a full-frame antialiasing). If you're unable to do that, set the base resolution to 1280x720 and resize the source in the preview. Set your OBS resolution to 2560x1440 if possible, capture native-size, and use the downscale dropdown for resizing to 720p before it gets sent out.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |