F5F Stay Refreshed Software Operating Systems OBS Help!

OBS Help!

OBS Help!

Pages (2): Previous 1 2
L
LorrenK
Senior Member
703
08-05-2023, 07:22 PM
#11
Lanczos filter influences image quality by reducing blur and enhancing sharpness in digital images.
L
LorrenK
08-05-2023, 07:22 PM #11

Lanczos filter influences image quality by reducing blur and enhancing sharpness in digital images.

X
73
08-05-2023, 07:22 PM
#12
It doesn't seem to matter which filter you choose. Your performance remains unaffected.
X
XxAnormalKidxX
08-05-2023, 07:22 PM #12

It doesn't seem to matter which filter you choose. Your performance remains unaffected.

S
Super_Wreqz
Junior Member
4
08-05-2023, 07:22 PM
#13
When not partnered, keep bitrate under 2500-2600 to ensure smooth viewing on Twitch. Adjust your encoding settings to match 720p at 60fps using an i7 processor—it performs adequately for streaming. Aim for a bitrate around 2500 or higher for optimal quality. Use Constant Bit Rate (CBR) and add padding if needed. The downscale filters affect sharpness; bilinear may blur slightly but works well with lower bitrates, while bicubic offers sharper results but can cause artifacts at high bitrates. Lanczos provides the sharpest output but requires more bandwidth. Performance varies by game—some titles like Hearthstone handle bilinear better, whereas CoD might benefit from bilinear for clarity. If you need detailed OBS guidance, I can provide it, though it would require payment for my expertise.
S
Super_Wreqz
08-05-2023, 07:22 PM #13

When not partnered, keep bitrate under 2500-2600 to ensure smooth viewing on Twitch. Adjust your encoding settings to match 720p at 60fps using an i7 processor—it performs adequately for streaming. Aim for a bitrate around 2500 or higher for optimal quality. Use Constant Bit Rate (CBR) and add padding if needed. The downscale filters affect sharpness; bilinear may blur slightly but works well with lower bitrates, while bicubic offers sharper results but can cause artifacts at high bitrates. Lanczos provides the sharpest output but requires more bandwidth. Performance varies by game—some titles like Hearthstone handle bilinear better, whereas CoD might benefit from bilinear for clarity. If you need detailed OBS guidance, I can provide it, though it would require payment for my expertise.

F
finandchaz101
Junior Member
19
08-05-2023, 07:22 PM
#14
I achieve crisp 720p clarity with these configurations: x264 encoder (QuickSync recommended for single monitor), CBR, Quality 8, bitrate between 2700-3200 kbps (reduce if you lose frames), buffer matching bitrate, audio in AAC 160kbps. The video is scaled down, uses a bilinear filter, and runs at 30 fps. In advanced settings I turned on multithreading, chose a profile above normal, and ran x264 extremely quickly.
F
finandchaz101
08-05-2023, 07:22 PM #14

I achieve crisp 720p clarity with these configurations: x264 encoder (QuickSync recommended for single monitor), CBR, Quality 8, bitrate between 2700-3200 kbps (reduce if you lose frames), buffer matching bitrate, audio in AAC 160kbps. The video is scaled down, uses a bilinear filter, and runs at 30 fps. In advanced settings I turned on multithreading, chose a profile above normal, and ran x264 extremely quickly.

R
Rami_Silber
Junior Member
42
08-05-2023, 07:22 PM
#15
I’m not sure what the other person was considering when they replied, but your configuration is more than sufficient for 1080p60. Keep in mind that higher quality—like better resolution, frame rate, or bitrate—demands a more powerful setup from the viewer’s side. Some individuals may struggle to watch 1080p60 streams, particularly if the bit rate is high. I believe 720p60 would likely be your optimal choice right now, even though your rig can support more. If you haven’t done it yet, try downloading JTVPing and identify the area with the lowest (greenest) numbers for you. Then adjust the OBS connection to that location. Bit rate and buffer size should remain consistent. It works for me, but differences appear only when values don’t match. The actual speed should fall between 2500 and 3500 kbps. 3500 offers better visual quality but needs faster download speeds, while 2500 works with lower bandwidth. A 12mbps connection can handle both well. I wouldn’t exceed 3500 unless you’re a collaborator. For encoding, x264 is the top choice. Quick sync is handy for weaker CPUs, but unnecessary if you have a 4670k or better. The profile should be fast or even faster. If your CPU seems capable, you might lower the setting slightly for marginally better results. Regarding final adjustments, I share my own settings (same upload speed, but less powerful components) and suggest a few tweaks. Encoder: x264. Use CBR, enable padding, and custom buffer size are confirmed. Maximum bitrate and buffer size: 2750 kbps each. Audio: default is set, but network impact minimization is enabled—though I’m unsure if it’s necessary. I save streams locally, though you decide. I usually start at 1080p, downscale to 720p with Lanczos for viewers who can’t handle full resolution. Multithreaded optimizations are verified. Process priority is set to normal; if CPU usage hits ~90-100%, consider raising the class. My CPU is very fast. Sometimes I opt for the “faster” preset, but it causes excessive usage during intense gaming sessions. Testing lower settings can improve quality while reducing load. Turn on “Use CFR” if it’s off. Here’s a sample configuration I use: bitrate 2750 kbps, resolution 1080p, downscaled to 720p with Lanczos for accessibility. Quality drops at 2500, but 3500 gives better clarity—though it demands higher speeds. Save files locally if you prefer; the choice is yours. I’ve checked CPU usage and multithreading, so feel free to adjust accordingly.
R
Rami_Silber
08-05-2023, 07:22 PM #15

I’m not sure what the other person was considering when they replied, but your configuration is more than sufficient for 1080p60. Keep in mind that higher quality—like better resolution, frame rate, or bitrate—demands a more powerful setup from the viewer’s side. Some individuals may struggle to watch 1080p60 streams, particularly if the bit rate is high. I believe 720p60 would likely be your optimal choice right now, even though your rig can support more. If you haven’t done it yet, try downloading JTVPing and identify the area with the lowest (greenest) numbers for you. Then adjust the OBS connection to that location. Bit rate and buffer size should remain consistent. It works for me, but differences appear only when values don’t match. The actual speed should fall between 2500 and 3500 kbps. 3500 offers better visual quality but needs faster download speeds, while 2500 works with lower bandwidth. A 12mbps connection can handle both well. I wouldn’t exceed 3500 unless you’re a collaborator. For encoding, x264 is the top choice. Quick sync is handy for weaker CPUs, but unnecessary if you have a 4670k or better. The profile should be fast or even faster. If your CPU seems capable, you might lower the setting slightly for marginally better results. Regarding final adjustments, I share my own settings (same upload speed, but less powerful components) and suggest a few tweaks. Encoder: x264. Use CBR, enable padding, and custom buffer size are confirmed. Maximum bitrate and buffer size: 2750 kbps each. Audio: default is set, but network impact minimization is enabled—though I’m unsure if it’s necessary. I save streams locally, though you decide. I usually start at 1080p, downscale to 720p with Lanczos for viewers who can’t handle full resolution. Multithreaded optimizations are verified. Process priority is set to normal; if CPU usage hits ~90-100%, consider raising the class. My CPU is very fast. Sometimes I opt for the “faster” preset, but it causes excessive usage during intense gaming sessions. Testing lower settings can improve quality while reducing load. Turn on “Use CFR” if it’s off. Here’s a sample configuration I use: bitrate 2750 kbps, resolution 1080p, downscaled to 720p with Lanczos for accessibility. Quality drops at 2500, but 3500 gives better clarity—though it demands higher speeds. Save files locally if you prefer; the choice is yours. I’ve checked CPU usage and multithreading, so feel free to adjust accordingly.

Pages (2): Previous 1 2