Stream looks blurry/grainy, can't stream multiplayer games like CSGO

D

doncynose

New Member
Hello,
My streams look blurry/grainy. When i stream x264 with CBR on 600kbps then i can stream multiplayer games buut my stream looks like shit even on 480p. If i go above 600kbps (sometimes that's too much) i get 300ms on games. Please help because i'm lost. I have watched countless youtube videos but none of them have helped.

PC specs.
Nvidia GeForce GTX 1060 3gb
Intel Core i7-6700K 4.00GHz
16gb RAM


Thank you. Doncynose

My internet:

ping.PNG

P.S It becomes more grainy when i move.
 
1. Having the YUV Color range set to "Full" will cause playback issues in certain browsers and on various video platforms. Shadows, highlights and color will look off. In OBS, go to "Settings -> Advanced" and set "YUV Color Range" back to "Partial".
2. Update your Windows 10 per https://obsproject.com/blog/five-simple-tips-for-new-streamers
3. Run OBS as Admin
4. Your log contains no recording or streaming session. Results of this log analysis are limited. Please post a link to a clean log file.
To make a clean log file, please follow these steps:

1) Restart OBS.
2) Start your stream/recording for about 30 seconds. Make sure you replicate any issues as best you can, which means having any games/apps open and captured, etc.
3) Stop your stream/recording.
4) Select Help > Log Files > Upload Current Log File. Send that link via this troubleshooting tool or whichever support chat you are using.

Your monitor has a refresh rate of 71 Hz. Make sure your games are not are set to run at a higher FPS than 71.
 
qhobbes said:
1. Having the YUV Color range set to "Full" will cause playback issues in certain browsers and on various video platforms. Shadows, highlights and color will look off. In OBS, go to "Settings -> Advanced" and set "YUV Color Range" back to "Partial".
2. Update your Windows 10 per https://obsproject.com/blog/five-simple-tips-for-new-streamers
3. Run OBS as Admin
4. Your log contains no recording or streaming session. Results of this log analysis are limited. Please post a link to a clean log file.
To make a clean log file, please follow these steps:

1) Restart OBS.
2) Start your stream/recording for about 30 seconds. Make sure you replicate any issues as best you can, which means having any games/apps open and captured, etc.
3) Stop your stream/recording.
4) Select Help > Log Files > Upload Current Log File. Send that link via this troubleshooting tool or whichever support chat you are using.

Your monitor has a refresh rate of 71 Hz. Make sure your games are not are set to run at a higher FPS than 71.
Click to expand...

It actually looked a bit better, here is the log, hopefully I got it right.
log: https://obsproject.com/logs/VJ9mOJiqVekNtvoM
 
1. A slower x264 preset than 'veryfast' is in use. It is recommended to leave this value on veryfast, as there are significant diminishing returns to setting it lower.
2. Try using NVENC as your encoder instead. Preset: Quality Profile: High , Look-ahead and Psycho Visual Tuning unchecked.
 
qhobbes said:
1. A slower x264 preset than 'veryfast' is in use. It is recommended to leave this value on veryfast, as there are significant diminishing returns to setting it lower.
2. Try using NVENC as your encoder instead. Preset: Quality Profile: High , Look-ahead and Psycho Visual Tuning unchecked.
Click to expand...

I tried both of those options. Don't know if its my bitrate or something. Thank you for your help tho
 
qhobbes said:
Try bumping your bitrate to at least 1200 kbps for 480p 30fps streaming. Restream's guide recommends 400 to 1,200 kbps for Twitch and 500 to 2,000 kbps for YouTube.
Click to expand...

Well i tried bumping it up to 1200 kbps, but the game went from 50 ping to 400 ping. I don't get it. When i installed OBS it auto recommended me to stream on 6000 kbps but same issue 400 ping. Maybe it's my ethernet cable or maybe my ISP?
 
It means you will be connecting to a different server for your RTMP upload, which potentially will behave differently with your game traffic.

If this method also causes the same issue, then the problem lies with either your router or your ISP.
 
You must log in or register to reply here.
Back
Top