Question / Help Upgrade PC and now stream quality is worse.

[ilmank]

Hello, i upgraded to a better procesor and Motherboard.
Now when i try to stream a get a lot a pixels when i move.
This is an example of my stream with new specs:
https://clips.twitch.tv/SpineyAuspiciousSaladWholeWheat
This is an example of my stream with previous specs:
https://www.twitch.tv/videos/120561746

You can see that the quality is so much better with the old PC than the new PC.
What can i do to improve the quality.
My new processor and Motherboard are like x5 times better that old ones, so it shuld be streaming with equal/better quality not worse.
I tried thousunds of different configs but still pixels a lot when i move.

This is my config:
http://i.imgur.com/VaMdYB0.png
http://i.imgur.com/8dQuNSu.png
http://i.imgur.com/8bf5Y2A.png
http://i.imgur.com/srel5sZ.png
http://i.imgur.com/j9NMo20.png

LOG FILE:

19:52:37.486: Settings changed (outputs)
19:52:37.486: ------------------------------------------------
19:53:34.764: ---------------------------------
19:53:34.789: [x264 encoder: 'simple_h264_stream'] preset: veryfast
19:53:34.789: [x264 encoder: 'simple_h264_stream'] settings:
19:53:34.789:     rate_control: CBR
19:53:34.789:     bitrate:      1400
19:53:34.789:     buffer size:  1400
19:53:34.789:     crf:          0
19:53:34.789:     fps_num:      30
19:53:34.789:     fps_den:      1
19:53:34.789:     width:        1920
19:53:34.789:     height:       1080
19:53:34.789:     keyint:       60
19:53:34.789:     vfr:          off
19:53:34.789:
19:53:34.793: [x264 encoder: 'simple_h264_stream'] custom settings: scenecut=0
19:53:34.801: [Media Foundation AAC: 'simple_aac']: encoder created
19:53:34.801:     bitrate: 160
19:53:34.801:     channels: 2
19:53:34.801:     sample rate: 44100
19:53:34.801:     bits-per-sample: 16
19:53:34.801:
19:53:34.832: [rtmp stream: 'simple_stream'] Connecting to RTMP URL rtmp://live-eze.twitch.tv/app...
19:53:34.954: [rtmp stream: 'simple_stream'] Interface: Realtek PCIe GBE Family Controller (ethernet, 1000 mbps)
19:53:37.131: [rtmp stream: 'simple_stream'] Connection to rtmp://live-eze.twitch.tv/app successful
19:53:37.134: ==== Streaming Start ===============================================
19:54:29.524: [rtmp stream: 'simple_stream'] User stopped the stream
19:54:29.524: Output 'simple_stream': stopping
19:54:29.524: Output 'simple_stream': Total encoded frames: 4294925605
19:54:29.525: Output 'simple_stream': Total drawn frames: 1642
19:54:29.528: ==== Streaming Stop ================================================

Another Log File:

00:30:04.920: OBS 19.0.3 (64bit, windows)
00:30:04.920: ---------------------------------
00:30:04.921: ---------------------------------
00:30:04.921: audio settings reset:
00:30:04.921:     samples per sec: 44100
00:30:04.921:     speakers:        2
00:30:04.922: ---------------------------------
00:30:04.922: Initializing D3D11...
00:30:04.922: Available Video Adapters:
00:30:04.923:     Adapter 1: NVIDIA GeForce GTX 750 Ti
00:30:04.923:       Dedicated VRAM: 2115698688
00:30:04.923:       Shared VRAM:    4270133248
00:30:04.923:       output 1: pos={0, 0}, size={1920, 1080}, attached=true
00:30:04.925: Loading up D3D11 on adapter NVIDIA GeForce GTX 750 Ti (0)
00:30:04.962: D3D11 loaded successfully, feature level used: 45056
00:30:05.698: ---------------------------------
00:30:05.698: video settings reset:
00:30:05.698:     base resolution:   1920x1080
00:30:05.698:     output resolution: 1920x1080
00:30:05.698:     downscale filter:  Bicubic
00:30:05.698:     fps:               30/1
00:30:05.698:     format:            NV12
00:30:05.699: Audio monitoring device:
00:30:05.699:     name: Por defecto
00:30:05.699:     id: default
00:30:05.699: ---------------------------------
00:30:05.701: Required module function 'obs_module_load' in module '../../obs-plugins/64bit/chrome_elf.dll' not found, loading of module failed
00:30:05.703: [CoreAudio encoder]: CoreAudio AAC encoder not installed on the system or couldn't be loaded
00:30:05.704: [AMF] Encountered Exception during AMF initialization: Unable to load 'amfrt64.dll', error code 126.
00:30:05.704: Failed to initialize module 'enc-amf.dll'
00:30:05.715: Required module function 'obs_module_load' in module '../../obs-plugins/64bit/libcef.dll' not found, loading of module failed
00:30:05.715: Required module function 'obs_module_load' in module '../../obs-plugins/64bit/libEGL.dll' not found, loading of module failed
00:30:05.716: Required module function 'obs_module_load' in module '../../obs-plugins/64bit/libGLESv2.dll' not found, loading of module failed
00:30:05.716: Failed to load 'en-US' text for module: 'obs-browser.dll'
00:30:05.716: [browser_source: 'Version: 1.29.0']
00:30:05.720: NVENC supported
00:30:05.761: Couldn't find VLC installation, VLC video source disabled
00:30:05.764: No blackmagic support
00:30:05.800: ---------------------------------
00:30:05.800:   Loaded Modules:
00:30:05.800:     win-wasapi.dll
00:30:05.800:     win-mf.dll
00:30:05.800:     win-dshow.dll
00:30:05.800:     win-decklink.dll
00:30:05.800:     win-capture.dll
00:30:05.800:     vlc-video.dll
00:30:05.800:     text-freetype2.dll
00:30:05.800:     rtmp-services.dll
00:30:05.800:     obs-x264.dll
00:30:05.800:     obs-vst.dll
00:30:05.800:     obs-transitions.dll
00:30:05.800:     obs-text.dll
00:30:05.800:     obs-qsv11.dll
00:30:05.800:     obs-outputs.dll
00:30:05.800:     obs-filters.dll
00:30:05.800:     obs-ffmpeg.dll
00:30:05.800:     obs-browser.dll
00:30:05.800:     image-source.dll
00:30:05.800:     frontend-tools.dll
00:30:05.800:     enc-amf.dll
00:30:05.800:     coreaudio-encoder.dll
00:30:05.800: ==== Startup complete ===============================================
00:30:05.802: All scene data cleared
00:30:05.802: ------------------------------------------------
00:30:05.831: WASAPI: Device 'Altavoces (Realtek High Definition Audio)' initialized
00:30:06.096: Switched to scene 'Escena'
00:30:06.098: ------------------------------------------------
00:30:06.098: Loaded scenes:
00:30:06.098: - scene 'Escena':
00:30:06.098:     - source: 'fort' (image_source)
00:30:06.098:     - source: 'Monitor' (monitor_capture)
00:30:06.098:     - source: 'age' (window_capture)
00:30:06.098:     - source: 'AGEVENTANA' (window_capture)
00:30:06.098:     - source: 'H!Z!JUEGO' (game_capture)
00:30:06.098: ------------------------------------------------
00:30:06.230: adding 23 milliseconds of audio buffering, total audio buffering is now 23 milliseconds
00:30:28.550: User added source 'Chat' (browser_source) to scene 'Escena'
00:32:08.414: ---------------------------------
00:32:08.414: [x264 encoder: 'simple_h264_stream'] preset: veryfast
00:32:08.414: [x264 encoder: 'simple_h264_stream'] settings:
00:32:08.414:     rate_control: CBR
00:32:08.414:     bitrate:      1400
00:32:08.414:     buffer size:  1400
00:32:08.414:     crf:          0
00:32:08.414:     fps_num:      30
00:32:08.414:     fps_den:      1
00:32:08.414:     width:        1920
00:32:08.414:     height:       1080
00:32:08.414:     keyint:       60
00:32:08.414:     vfr:          off
00:32:08.414:
00:32:08.414: [x264 encoder: 'simple_h264_stream'] custom settings: scenecut=0
00:32:08.430: [Media Foundation AAC: 'simple_aac']: encoder created
00:32:08.430:     bitrate: 160
00:32:08.430:     channels: 2
00:32:08.430:     sample rate: 44100
00:32:08.430:     bits-per-sample: 16
00:32:08.430:
00:32:08.431: [rtmp stream: 'simple_stream'] Connecting to RTMP URL rtmp://live-eze.twitch.tv/app...
00:32:08.506: [rtmp stream: 'simple_stream'] Interface: Realtek PCIe GBE Family Controller (ethernet, 1000 mbps)
00:32:10.463: [rtmp stream: 'simple_stream'] Connection to rtmp://live-eze.twitch.tv/app successful
00:32:10.471: ==== Streaming Start ===============================================
00:35:37.831: WASAPI: Device 'Micrófono (Realtek High Definition Audio)' initialized
00:35:37.845: Settings changed (audio)
00:35:37.845: ------------------------------------------------
00:36:14.536: adding 23 milliseconds of audio buffering, total audio buffering is now 46 milliseconds
01:20:43.787: ---------------------------------
01:20:43.800: [x264 encoder: 'simple_h264_stream'] settings:
01:20:43.800:     rate_control: CBR
01:20:43.800:     bitrate:      1200
01:20:43.800:     buffer size:  1200
01:20:43.800:     crf:          0
01:20:43.800:     fps_num:      30
01:20:43.800:     fps_den:      1
01:20:43.800:     width:        1920
01:20:43.800:     height:       1080
01:20:43.800:     keyint:       60
01:20:43.800:     vfr:          off
01:20:43.800:
01:20:43.803: [x264 encoder: 'simple_h264_stream'] custom settings: scenecut=0
01:20:43.815: Settings changed (outputs)
01:20:43.815: ------------------------------------------------
01:23:01.659: ---------------------------------
01:23:01.702: [x264 encoder: 'simple_h264_stream'] settings:
01:23:01.702:     rate_control: CBR
01:23:01.702:     bitrate:      1400
01:23:01.702:     buffer size:  1400
01:23:01.702:     crf:          0
01:23:01.702:     fps_num:      30
01:23:01.702:     fps_den:      1
01:23:01.702:     width:        1920
01:23:01.702:     height:       1080
01:23:01.702:     keyint:       60
01:23:01.702:     vfr:          off
01:23:01.702:
01:23:01.799: [x264 encoder: 'simple_h264_stream'] custom settings: scenecut=0
01:23:01.813: Settings changed (outputs)
01:23:01.813: ------------------------------------------------
01:26:28.169: ---------------------------------
01:26:28.182: [x264 encoder: 'simple_h264_stream'] settings:
01:26:28.182:     rate_control: CBR
01:26:28.182:     bitrate:      1200
01:26:28.182:     buffer size:  1200
01:26:28.182:     crf:          0
01:26:28.182:     fps_num:      30
01:26:28.182:     fps_den:      1
01:26:28.182:     width:        1920
01:26:28.182:     height:       1080
01:26:28.182:     keyint:       60
01:26:28.182:     vfr:          off
01:26:28.182:
01:26:28.185: [x264 encoder: 'simple_h264_stream'] custom settings: scenecut=0
01:26:28.191: Settings changed (outputs)
01:26:28.191: ------------------------------------------------
03:05:07.301: [rtmp stream: 'simple_stream'] User stopped the stream
03:05:07.326: Output 'simple_stream': stopping
03:05:07.327: Output 'simple_stream': Total encoded frames: 271628
03:05:07.327: Output 'simple_stream': Total drawn frames: 275367
03:05:07.327: Output 'simple_stream': Number of lagged frames due to rendering lag/stalls: 4 (0.0%)
03:05:07.327: Output 'simple_stream': Number of dropped frames due to insufficient bandwidth/connection stalls: 15207 (5.6%)
03:05:07.328: [rtmp stream: 'simple_stream'] Freeing 1 remaining packets
03:05:07.331: ==== Streaming Stop ================================================

Any tips?

 

[SumDim]

Your missing the most important part man. What is your new CPU? LOL

 

[wallrik]

Your old stream is 1280x720, that's the difference. Your bitrate is too low to get any sort of good result from higher resolutions.

 

[ilmank]

Your old stream is 1280x720, that's the difference. Your bitrate is too low to get any sort of good result from higher resolutions.

I changed that. I now use 1280x720 and it's still the same. Tried a lot of resultuions and still the same.
I used to stream with 1280x720 and 1200 bitrate and the quality was so much better than now.

Your missing the most important part man. What is your new CPU? LOL

My new CPU is a Ryzen 5 1600. And my previous one was A10 5800k very bad one but still better resolution

 

[SumDim]

Go run a speedtest to get your current upload.

Tell us what it is.

You got a faster CPU now capable of pushing out more bits. If your upload speed is suitable, you need to increase the bitrate higher.

 

[ilmank]

Go run a speedtest to get your current upload.

Tell us what it is.

You got a faster CPU now capable of pushing out more bits. If your upload speed is suitable, you need to increase the bitrate higher.

But the thing is that i only changed my CPU, my internet is the same, i can stream with 1200 Bitrate, if i put more than 1400 i get packet loss.
I always streamged with 1200 with the previous PC and got better quality than now.

http://imgur.com/nqqdPfH

 

[SumDim]

Sorry, but you need to get a faster Internet upload service.

2Mbps is not fast enough to take advantage of your new Ryzen 1600. Buying a really fast computer doesn't matter when you are being limited by a slow Internet upload speed. It is like owning a Honda Civic and upgrading to a Lambourghini Aventador. Only that the highway speed limit is still 35mph.

Call up Cablevision Fibertel and get a better Internet package. In Argentina, Cablevision Fibertel has the 50Megas plan that has 50Mbps download/6Mbps upload. With 6Mbps upload, you should be able to do 720@30/60fps with your new Ryzen 1600.

 

[alpinlol]

Try 720p30 with medium preset and whatever Bitrate works for you best without having packet loss or other laggs ingame.

@SumDim low or high Bitrate doesnt really concern cpu usage

 

[SumDim]

@alpinlol Bitrate and CPU usage have nothing to do with one another.

You can have 100% CPU usage and be pumping out the agreed upon bitrate. You can also have 100% CPU usage and not pumping out the agreed upon bitrate. Bitrate is just a suggestion to the ingest server of what the client thinks it can upload. You can lie to the server and say "Hey, I'm going to send you 1 Gazillion kbps as the bitrate. When the server detects something isn't right, its tries its best to adapt and if can't, complain.

In the ops case, he's got 2Mbps upload which is 2000Kbps.

YouTube recommendation (https://support.google.com/youtube/answer/2853702?hl=en) says this:

720p 60fps.= 2,250 - 6,000 Kbps
720p = 1,500 - 4,000 Kbps
480p 500-2,000 Kbps

He's at the low end of 720p. If his upload link isn't good, and wavers 20%, now he's looking at even uglier lower end of 720p and its not going to look very good at all. 2Mbps is a very tough spot to be in.

Remember, he's always had a 2Mbps upload link. He just bought a brand new Ryzen 1600. I seriously doubt he wants to keep producing 480p/720p output with that machine.
He needs to get higher upload bandwidth at 6Mbps as I previous stated to move him up in the streaming world, not be held back at the same level.

 

[alpinlol]

@alpinlol Bitrate and CPU usage have nothing to do with one another.

You can have 100% CPU usage and be pumping out the agreed upon bitrate. You can also have 100% CPU usage and not pumping out the agreed upon bitrate. Bitrate is just a suggestion to the ingest server of what the client thinks it can upload. You can lie to the server and say "Hey, I'm going to send you 1 Gazillion kbps as the bitrate. When the server detects something isn't right, its tries its best to adapt and if can't, complain.

In the ops case, he's got 2Mbps upload which is 2000Kbps.

YouTube recommendation (https://support.google.com/youtube/answer/2853702?hl=en) says this:

720p 60fps.= 2,250 - 6,000 Kbps
720p = 1,500 - 4,000 Kbps
480p 500-2,000 Kbps

He's at the low end of 720p. If his upload link isn't good, and wavers 20%, now he's looking at even uglier lower end of 720p and its not going to look very good at all. 2Mbps is a very tough spot to be in.

Remember, he's always had a 2Mbps upload link. He just bought a brand new Ryzen 1600. I seriously doubt he wants to keep producing 480p/720p output with that machine.
He needs to get higher upload bandwidth at 6Mbps as I previous stated to move him up in the streaming world, not be held back at the same level.

Go run a speedtest to get your current upload.

Tell us what it is.

You got a faster CPU now capable of pushing out more bits. If your upload speed is suitable, you need to increase the bitrate higher.

You dont read properly what I said, also I was just correcting your false information.

Counteract a certain amount of Quality/Bitrate with a slower Preset than veryfast to achieve a better picture quality due to his limited resources which literally opened up after he upgraded. He will still only produce 720p livestreams no matter what with that kind of upload and even if he would upgrade his upstream he wouldnt really be able to properly stream 1080p due to bad ingest servers for unpartnered streamers and constant buffering issues leading into decreased Bitrate once again.

Yes Twitch finally, after years, "updated" their ingest capacities but are still running the same awful system of routing everything over sfo for non partners yo *yeay* we get up to 6mbit up to their ingest and *yeay* it still buffers for the majority of unknown streamers that arent partners if they ever hit 3500 or higher in a lot of cases with even lower Bitrates.

 

[Osiris]

@alpinlol It's no longer the case that non-partners get "routed" over San Francisco. Just watched someone with 0 viewers who was not a partner or an affiliate, stream came from servers in Amsterdam (I live in the Netherlands).

@alpinlol Bitrate and CPU usage have nothing to do with one another.

You can have 100% CPU usage and be pumping out the agreed upon bitrate. You can also have 100% CPU usage and not pumping out the agreed upon bitrate. Bitrate is just a suggestion to the ingest server of what the client thinks it can upload. You can lie to the server and say "Hey, I'm going to send you 1 Gazillion kbps as the bitrate. When the server detects something isn't right, its tries its best to adapt and if can't, complain.

Bitrate is not a suggestion to the ingest server, it is what the client is sending to the server (assuming CBR).

 

[SumDim]

Osiris, we are talking about two different things.

I'm talking about the bitrate I set with OBS Studio in the Output settings. You are talking about the actual bitrate measurement as the stream is live.

For example, I can tell YouTube via OBS Studio to cram a gazillion bitrate (a wrong number bitrate that is not possible given my upload speed) in a live stream. I am suggesting a contract between myself and YouTube to deliver that bitrate. YouTube expects that bitrate for the live session.

So I press the Start Streaming button. We handshake based on that number. YouTube opens the connection perfectly fine believing I am going to deliver that bitrate even though I'm lying and fully know I can't. The stream goes live. Then, moments into the stream, I'm told by YouTube, I'm under delivering data.

The bitrate number I give in OBS is just a suggestion, a wrong one in this case. The bitrate I give and the actual bitrate throughput is rarely ever going to be the same. There is "slack" or variance involved. I believe for YouTube, its 10-20% based on my tests and watching how they leave the green light, yellow light, and red light on in the stream video manager console. Everything appears as real time adaptative within their guidelines on a handshake.

 

[SumDim]

Ilmank, I wanted to turn the discussion to you so you understand what's being said here. Unfortunately, the respondents here are not helping you solve your problem. I am the only one giving you help. The discussion has gone from your question, and instead to me, with people trying to correct what they feel are "false statements". I'm very sorry for this but I have to respond to their concerns.

The fact of the matter is, you have slow Internet upload speed. 2Mbps is not good enough to do really outstanding live streams. You need to go to Cablevision and upgrade your plan. That will solve your problem and expectations to do great things going forward..

 

[ilmank]

Ilmank, I wanted to turn the discussion to you so you understand what's being said here. Unfortunately, the respondents here are not helping you solve your problem. I am the only one giving you help. The discussion has gone from your question, and instead to me, with people trying to correct what they feel are "false statements". I'm very sorry for this but I have to respond to their concerns.

The fact of the matter is, you have slow Internet upload speed. 2Mbps is not good enough to do really outstanding live streams. You need to go to Cablevision and upgrade your plan. That will solve your problem and expectations to do great things going forward..

Yes, but i only changed my Computer specs. My internet is the same i allways had. I was able to stream with better Quality with the previous PC and same internet. And now with this new PC can't get to stream to at least the same quality that i was able to stream before i had this new proccesor.
I tougth that upgrading my computer would be better or at least the same. But no, i can't stream at the same quality as i was streaming before.
I know that i have low upload speed. I shuld consider upgrading soon, saddly here in Argentina is very expensive to have good internet.

Thanks

 

[Osiris]

You can stream at the same quality you always had, just keep all the settings the same.
Like what has been said before, you can try increasing the x264 cpu preset to slower sounding ones to get some better encoding, but that's about all you can do.

@SumDim There is no handshaking about the bitrate, it's just about what the connection can handle or not.

 

[SumDim]

 

[Osiris]

Not sure how that has anything to do with handshaking, there is no handshaking about the bitrate in the RTMP protocol.
That part refers to the fact that you don't have to set a max. sustainable bitrate like you had to for YT events.

 

[SumDim]

By handshaking I mean "passing a value" and agreeing upon contract to that number. Not the RTMP handshake of sending 3 packets.

Given this "passing a bitrate value and both sides contracting to it" then why in the hell YouTube complains when given two outside boundary tests of an extreme bitrate value at the high end and an extreme bitrate value at the low end. Values that ***we suggest*** in OBS Studio.

YouTube Stream health is shown in its own HTML management console, not back to OBS Studio. Both server and client keep chugging along regardless.

Again, according to YouTube it ignores bitrate:
"you do not need to set a bitrate"

But is that necessarily true.

Test #1: High Bitrate Well Above Normal
-----------------------------------------------------------------
Set rate control to CBR, bitrate to 1000000 (a big number) and keyframe to 2 seconds.
Then connect a live stream to YouTube.
The stream health is red lit. YouTube complains back and says video output is too low.

Test #2: Low Bitrate Well Below Normal
----------------------------------------------------------------
Set rate control to CBR, bitrate to 100 (a very low number) and keyframe to 2 seconds.
Then connect a live stream to YouTube.
Notice that the preview screen looks very odd. The stream health is green lit. A few minutes into it, stream health goes yellow and complains that the video output is low and says that I need to increase it.

Test #3: "Just right" Bitrate Within "Guidelines"
---------------------------------------------------------------------
Set rate control to CBR, bitrate to a proper bitrate that is within the upload speed less 20% and keyframe to 2 seconds
Then connect a live stream to YouTube
Works. Just works.

So there are three test cases above with three different results.

If YouTube doesn't give a crap about bitrate, then why does it complain in the extreme cases when it isn't getting what it wants.

When things aren't working, both OBS Studio and YouTube continue to communicate.It continues until you tell OBS Studio to disconnect. YouTube defines what is "proper video output" and senses what is "low". There must be measurement going on YouTube end's and consideration with the agreed upon bitrate to fit within a "quality guideline" to meet expectation of both parties. YouTube wouldn't be complaining about low output it if there were no consideration of the bitrate setting.