Question / Help More threads for multiple window captures?

A

ajay836018

New Member
Hey, I use obs to stream a show. In the show I capture a zoom call and duplicate the source in window captures so each guest can be in their own overlay. I also run a camera from my pc to the zoom and then use my iPhone as a my obs cam. I am using a fx 4100 and a rx 470 8gb GPU, I am getting a fx 8350 tomorrow. I am not gaming and only doing 720p no downscaling. But my iPhone cam stake a blow and gets laggy as soon as I start streaming. It’s fine before hand. Will the Fox 8350 do better since it has more threads? Will it be able to handle everything I am trying to run?
 
WizardCM

WizardCM

Forum Moderator
Community Helper
Are you using the iPhone as a camera over WiFi? Sounds like you're saturating your network bandwidth on your computer. Make sure you're on Ethernet, and make sure your network is gigabit.
 
A

ajay836018

New Member
WizardCM said:
Are you using the iPhone as a camera over WiFi? Sounds like you're saturating your network bandwidth on your computer. Make sure you're on Ethernet, and make sure your network is gigabit.
Click to expand...

i am using the iphone cam through the plug in and it is directly connected to my pc. it is not using any bandwidth to my knowledge. how do i check to see if i have a gb of bandwidth? i know i run 100mbs and have an upload speed of 10mbs..
 
Narcogen

Narcogen

Active Member
Without a logfile from a session as you describe it is difficult to see where the performance bottleneck is, and therefore not possible to tell if a CPU upgrade would address it.
 
Narcogen

Narcogen

Active Member
21:53:10.586: adding 23 milliseconds of audio buffering, total audio buffering is now 69 milliseconds (source: iOS Camera 2)
21:53:34.815: adding 23 milliseconds of audio buffering, total audio buffering is now 92 milliseconds (source: iOS Camera 2)
21:53:42.777: adding 23 milliseconds of audio buffering, total audio buffering is now 139 milliseconds (source: iOS Camera 2)
21:53:53.427: adding 23 milliseconds of audio buffering, total audio buffering is now 185 milliseconds (source: iOS Camera 2)
21:53:57.827: adding 23 milliseconds of audio buffering, total audio buffering is now 208 milliseconds (source: iOS Camera 2)
22:21:17.100: adding 23 milliseconds of audio buffering, total audio buffering is now 232 milliseconds (source: iOS Camera 2)
22:21:25.406: adding 23 milliseconds of audio buffering, total audio buffering is now 255 milliseconds (source: iOS Camera 2)
22:38:24.843: adding 46 milliseconds of audio buffering, total audio buffering is now 301 milliseconds (source: iOS Camera 2)
22:38:26.347: adding 23 milliseconds of audio buffering, total audio buffering is now 325 milliseconds (source: iOS Camera 2)
22:41:45.369: adding 23 milliseconds of audio buffering, total audio buffering is now 348 milliseconds (source: iOS Camera 2)
22:41:56.220: adding 46 milliseconds of audio buffering, total audio buffering is now 394 milliseconds (source: iOS Camera 2)
22:49:34.175: adding 23 milliseconds of audio buffering, total audio buffering is now 417 milliseconds (source: iOS Camera 2)
22:49:37.335: adding 23 milliseconds of audio buffering, total audio buffering is now 441 milliseconds (source: iOS Camera 2)

Either your CPU or your USB bus controller is being overloaded during broadcast. This is manifested in increasing audio buffering from the iOS Camera source.
 
A

ajay836018

New Member
If it is the bus controller what does that mean? Also the iPhone cam works fine until I hit start stream. So my thought is it must be the cpu.. I am receiving the fx 8350 today. It has got to be better than the fox 4100 I have right now. So fingers crossed it will be able to handle the whole load.
 
Narcogen

Narcogen

Active Member
If it is the bus controller then it means you have too many USB devices connected to ports that are all running through the same controller chip.
 
You must log in or register to reply here.
Top