Question / Help Error 10060, First time issues.

S

SpriteArt

New Member
Hi.
So, recently I've been having a lot of trouble with OBS disconnecting, dropping frames, and now has begun to give me the error 10060. Using the log scanner, I got two error notifications:
-Bad Bitrate/Resolution/FPS
-Connection Stalls Detected (This is where the main problem is.)
This has only shown up in the past week, even though I've been streaming to Picarto.tv for quite some time, now. My stream will be up from anywhere between 20 minutes to 2 hours before going down from this. I'm at wit's end with this, and it keeps ruining my streams.

OS: Windows 7 Home Premium 64-bit (Since the OBS log file doesn't show the operating system.)

Log file:
Code: 
21:10:16: Open Broadcaster Software v0.657b - 64bit (　^ω^)
21:10:16: -------------------------------
21:10:16: CPU Name: Intel(R) Pentium(R) CPU G3258 @ 3.20GHz
21:10:16: CPU Speed: 3200MHz
21:10:16: Physical Memory:  8140MB Total, 4099MB Free
21:10:16: stepping id: 3, model 60, family 6, type 0, extmodel 1, extfamily 0, HTT 1, logical cores 2, total cores 2
21:10:16: monitor 1: pos={0, 0}, size={1440, 900}
21:10:16: monitor 2: pos={1440, 132}, size={1360, 768}
21:10:16: Windows Version: 6.1 Build 7601 (revision 23418)
21:10:16: Aero is Enabled
21:10:16: -------------------------------
21:10:16: OBS Modules:
21:10:16: Base Address     Module
21:10:16: 000000003FDD0000 OBS.exe
21:10:16: 00000000E38F0000 OBSApi.dll
21:10:16: 00000000F2F00000 DShowPlugin.dll
21:10:16: 00000000F2EC0000 GraphicsCapture.dll
21:10:16: 00000000F2E90000 NoiseGate.dll
21:10:16: 00000000E9660000 PSVPlugin.dll
21:10:16: 00000000E9630000 scenesw.dll
21:10:16: ------------------------------------------
21:10:16: Adapter 1
21:10:16:   Video Adapter: NVIDIA GeForce GTX 750
21:10:16:   Video Adapter Dedicated Video Memory: 2070609920
21:10:16:   Video Adapter Shared System Memory: 2147807232
21:10:16:   Video Adapter Output 1: pos={0, 0}, size={1440, 900}, attached=true
21:10:16:   Video Adapter Output 2: pos={1440, 132}, size={1360, 768}, attached=true
21:10:16: =====Stream Start: 2016-06-28, 21:10:16===============================================
21:10:16:   Multithreaded optimizations: On
21:10:16:   Base resolution: 1440x900
21:10:16:   Output resolution: 1440x900
21:10:16: ------------------------------------------
21:10:16: Loading up D3D10 on NVIDIA GeForce GTX 750 (Adapter 1)...
21:10:16: ------------------------------------------
21:10:16: Audio Format: 48000 Hz
21:10:16: ------------------------------------------
21:10:16: Audio Channels: 2 Ch
21:10:16: Playback device Default
21:10:16: ------------------------------------------
21:10:16: Using desktop audio input: Headset Earphone (3- Microsoft LifeChat LX-3000)
21:10:16: Global Audio time adjust: 0
21:10:16: ------------------------------------------
21:10:16: Using auxilary audio input: Headset Microphone (3- Microsoft LifeChat LX-3000)
21:10:16: Mic time offset: 0
21:10:16: ------------------------------------------
21:10:16: Audio Encoding: AAC
21:10:16:     bitrate: 128
21:10:17: Using bitmap image
21:10:17: Using Window Capture
21:10:17: Using Window Capture
21:10:17: Using bitmap image
21:10:17: Scene buffering time set to 700
21:10:17: ------------------------------------------
21:10:17: Video Encoding: x264
21:10:17:     fps: 30
21:10:17:     width: 1440, height: 900
21:10:17:     preset: veryfast
21:10:17:     profile: high
21:10:17:     keyint: 250
21:10:17:     CBR: yes
21:10:17:     CFR: yes
21:10:17:     max bitrate: 600
21:10:17:     buffer size: 600
21:10:17: ------------------------------------------
21:10:18:   Interface: Killer e2200 Gigabit Ethernet Controller (ethernet, 1000 mbps)
21:10:18: Completed handshake with rtmp://live.us.picarto.tv/golive in 187 ms.
21:10:19: SO_SNDBUF was at 8192
21:10:19: SO_SNDBUF is now 65536
21:26:06: Audio timestamp for device 'Headset Microphone (3- Microsoft LifeChat LX-3000)' was behind target timestamp by 80
21:32:10: RTMPPublisher::SocketLoop: Stalled for 1584 ms to write 117464 bytes (buffer: 0 / 131072), unstable connection?
21:32:27: RTMPPublisher::SocketLoop: Stalled for 1548 ms to write 114351 bytes (buffer: 0 / 131072), unstable connection?
21:32:30: RTMPPublisher::SocketLoop: Stalled for 2743 ms to write 131029 bytes (buffer: 0 / 131072), unstable connection?
21:32:32: RTMPPublisher::SocketLoop: Stalled for 2789 ms to write 128372 bytes (buffer: 0 / 131072), unstable connection?
21:32:35: RTMPPublisher::SocketLoop: Stalled for 3065 ms to write 130772 bytes (buffer: 0 / 131072), unstable connection?
21:32:38: RTMPPublisher::SocketLoop: Stalled for 2399 ms to write 130882 bytes (buffer: 0 / 131072), unstable connection?
21:32:41: RTMPPublisher::SocketLoop: Stalled for 2842 ms to write 131020 bytes (buffer: 0 / 131072), unstable connection?
21:32:44: RTMPPublisher::SocketLoop: Stalled for 3014 ms to write 129759 bytes (buffer: 0 / 131072), unstable connection?
21:32:47: RTMPPublisher::SocketLoop: Stalled for 2978 ms to write 130701 bytes (buffer: 0 / 131072), unstable connection?
21:32:49: RTMPPublisher::SocketLoop: Stalled for 2756 ms to write 130786 bytes (buffer: 0 / 131072), unstable connection?
21:32:52: RTMPPublisher::SocketLoop: Stalled for 2855 ms to write 130192 bytes (buffer: 0 / 131072), unstable connection?
21:32:58: RTMPPublisher::SocketLoop: Stalled for 5319 ms to write 130964 bytes (buffer: 0 / 131072), unstable connection?
21:33:01: RTMPPublisher::SocketLoop: Stalled for 3018 ms to write 130822 bytes (buffer: 0 / 131072), unstable connection?
21:33:03: RTMPPublisher::SocketLoop: Stalled for 2941 ms to write 128116 bytes (buffer: 0 / 131072), unstable connection?
21:33:06: RTMPPublisher::SocketLoop: Stalled for 2803 ms to write 130221 bytes (buffer: 0 / 131072), unstable connection?
21:33:09: RTMPPublisher::SocketLoop: Stalled for 2824 ms to write 129268 bytes (buffer: 0 / 131072), unstable connection?
21:33:14: RTMPPublisher::SocketLoop: Stalled for 5264 ms to write 129501 bytes (buffer: 0 / 131072), unstable connection?
21:33:20: RTMPPublisher::SocketLoop: Stalled for 5316 ms to write 129026 bytes (buffer: 0 / 131072), unstable connection?
21:34:21: FlushBufferedVideo: Flushing 9 packets over 267 ms
21:34:22: Total frames encoded: 43325, total frames duplicated: 439 (1.01%)
21:34:22: Number of frames skipped due to encoder lag: 102 (0.24%)
21:34:22: Total frames rendered: 43162, number of late frames: 79 (0.18%) (it's okay for some frames to be late)
21:34:22:
21:34:22: Profiler time results:
21:34:22:
21:34:22: ==============================================================
21:34:22: video thread frame - [100%] [avg time: 2.871 ms] [children: 83.7%] [unaccounted: 16.3%]
21:34:22: | scene->Preprocess - [75.8%] [avg time: 2.177 ms]
21:34:22: | GPU download and conversion - [7.87%] [avg time: 0.226 ms] [children: 6.76%] [unaccounted: 1.11%]
21:34:22: | | flush - [5.33%] [avg time: 0.153 ms]
21:34:22: | | CopyResource - [1.39%] [avg time: 0.04 ms]
21:34:22: | | conversion to 4:2:0 - [0.0348%] [avg time: 0.001 ms]
21:34:22: Convert444Thread - [100%] [avg time: 1.1 ms] [children: 99.5%] [unaccounted: 0.455%]
21:34:22: | Convert444toNV12 - [99.5%] [avg time: 1.095 ms]
21:34:22: encoder thread frame - [100%] [avg time: 1.861 ms] [children: 2.31%] [unaccounted: 97.7%]
21:34:22: | sending stuff out - [2.31%] [avg time: 0.043 ms]
21:34:22: ==============================================================
21:34:22:
21:34:22:
21:34:22: Profiler CPU results:
21:34:22:
21:34:22: ==============================================================
21:34:22: video thread frame - [cpu time: avg 0.408 ms, total 17628.1 ms] [avg calls per frame: 1]
21:34:22: | scene->Preprocess - [cpu time: avg 0.048 ms, total 2090.42 ms] [avg calls per frame: 1]
21:34:22: | GPU download and conversion - [cpu time: avg 0.045 ms, total 1950.02 ms] [avg calls per frame: 1]
21:34:22: | | flush - [cpu time: avg 0.031 ms, total 1357.21 ms] [avg calls per frame: 1]
21:34:22: | | CopyResource - [cpu time: avg 0.005 ms, total 218.401 ms] [avg calls per frame: 1]
21:34:22: | | conversion to 4:2:0 - [cpu time: avg 0 ms, total 15.6 ms] [avg calls per frame: 1]
21:34:22: Convert444Thread - [cpu time: avg 1.016 ms, total 43851.9 ms] [avg calls per frame: 1]
21:34:22: | Convert444toNV12 - [cpu time: avg 1.014 ms, total 43773.9 ms] [avg calls per frame: 1]
21:34:22: encoder thread frame - [cpu time: avg 1.027 ms, total 44522.7 ms] [avg calls per frame: 1]
21:34:22: | sending stuff out - [cpu time: avg 0.002 ms, total 93.6 ms] [avg calls per frame: 1]
21:34:22: ==============================================================
21:34:22:
21:34:22: =====Stream End: 2016-06-28, 21:34:22=================================================
21:34:22: ~RTMPPublisher: Packet flush completed in 133 ms
21:34:38: =====Stream End: 2016-06-28, 21:34:38=================================================
21:34:40: Terminating 0x1a14
21:34:40: Terminating 0x1e5c
 
bilehazard

bilehazard

Member
Looks like something is up with Picarto.tv or a routing issue to their service, i'd do a ping test a couple times to see if the connection is stable or not
 
S

SpriteArt

New Member
bilehazard said:
Looks like something is up with Picarto.tv or a routing issue to their service, i'd do a ping test a couple times to see if the connection is stable or not
Click to expand...
I just did. CMD comes back with:
Code: 
C:\Users\xxxxxx>ping www.picarto.tv

Pinging www.picarto.tv [104.20.70.13] with 32 bytes of data:
Reply from 104.20.70.13: bytes=32 time=38ms TTL=56
Reply from 104.20.70.13: bytes=32 time=42ms TTL=56
Reply from 104.20.70.13: bytes=32 time=36ms TTL=56
Reply from 104.20.70.13: bytes=32 time=35ms TTL=56

Ping statistics for 104.20.70.13:
     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 42ms, Average = 37ms
Looks like my connection is stable.
 
bilehazard

bilehazard

Member
Do more then a few passes, could show stable on one pass but some others. also do a tracert as well to see how the traffic is being routed. Make sure nothing else is consuming your bandwidth, including anyone connected to your network
 
Steve Macintosh

Steve Macintosh

Member
Looks like either picarto.tv or your connection.
Anyway, you probably want to test with a larger sample size. And pinging the RTMP-server instead of the web server.

Code: 
ping -n 100 live.us.picarto.tv

If you keep having issues, check if there are other available nodes on picarto or test another streaming service just to rule out that it's on your side.
 
S

SpriteArt

New Member
bilehazard said:
Do more then a few passes, could show stable on one pass but some others. also do a tracert as well to see how the traffic is being routed. Make sure nothing else is consuming your bandwidth, including anyone connected to your network
Click to expand...
I ran seven ping tests, all were within the 34-43ms range.
I seem to be getting stuck at my ISP's place. Running TraceRoute to 104.20.70.13 yielded this:
Code: 
C:\Users\xxxxxxx>tracert 104.20.70.13

Tracing route to 104.20.70.13 over a maximum of 30 hops
1     2ms     <1ms hitronhub.home [192.168.0.1] (obviously the modem.)
2     12ms     28ms     9ms [redacted ip]
3     21ms     19ms     19ms [redacted ip]
4     20ms      19ms     19ms [redacted ip]
5     29ms     29ms     39ms van58-9-229-254.dynamic.rogerstelecom.net [redacted ip]
6     43ms     39ms     39ms van58-9-229-229.dyanmic.rogerstelecom.net [redacted ip]
7     36ms     78ms     39ms van58-9-230-10.dynamic.rogerstelecom.net [redacted ip]
8     *     *     *     Request timed out.
9     41ms     36ms     39ms 104.20.70.13
Trace complete.

On the note of someone else taking up bandwidth, no one in the house uses anything bandwidth heavy, aside from me. I've streamed while my mother upstairs was DJing on an internet radio station with no problems before. No one uses Netflix, no consoles are hooked up or online to take additional bandwidth.
 
S

SpriteArt

New Member
Steve Macintosh said:
Looks like either picarto.tv or your connection.
Anyway, you probably want to test with a larger sample size. And pinging the RTMP-server instead of the web server.

Code: 
ping -n 100 live.us.picarto.tv

If you keep having issues, check if there are other available nodes on picarto or test another streaming service just to rule out that it's on your side.
Click to expand...

Ran this test. No packets lost, min of 54, max of 90, average of 60.
 
You must log in or register to reply here.
Top