0.54.09 network test build

Status
Not open for further replies.

Jim

Jim
Developer
WARNING: This thread is an archived discussion of an old test build. Download the most recent version of OBS which incorporates these changes and more from https://obsproject.com/download

Testing out some network updates, also trying to test various fixes for certain GL capture bugs that are present currently.

Please let us know how things are working in terms of network; also please check to see how much of the end of your stream gets cut off, as this is something we're currently trying to fix.

download: http://sourceforge.net/projects/obsproj ... p/download

Changes:
  • 09 - fixed a potential mic sync issue
  • 09 - reverted opengl capture cold to more stable (blow slower) code until it's ready for more testing again
  • 09 - other random tweaks and fixes
  • 08 - moved keyframe interval to advanced and made auto default
  • 08 - fixed incorrect drawing of monitor capture on rotated monitors
  • 07 - made a workaround/fix for game capture for when it would capture a 1x1 pixel or a smaller size than intended from games that don't properly use the swap chain
  • 07 - fixed a few more game capture bugs (hopefully in particular related to iRacing and the weird CPU increase)
  • 07 - added RTMP auth support
  • 07 - fixed a few other minor bugs
  • 06 - fixed a crash with the new network code at the end of the stream
  • 06 - added some minor game capture fixes in relation to the weird bugs people have been seeing
  • 06 - got rid of some unnecessary debug log messages
  • 05 - got rid of that horrible cutoff at the end of streaming/recording, it was really annoying (r1ch)
  • 05 - fixed some bugs with game capture causing weird glitches and lag to certain games (like iRacing) (jim)
  • 05 - reverted GL code to a previous build
  • 04 - Fixed a crash on shutdown (r1ch)
  • 04 - Further network code improvements (r1ch)
  • 04 - Fixed another crash (r1ch)
  • 04 - Corrected some typos in german locale (GolDAce)
  • 04 - Fixed a hotkey crash that could happen sometimes (r1ch)
  • Made it so that remaining video/audio data is sent over the network when stopping a capture (r1ch)
  • Testing a refactor of the network code (r1ch)
  • Improved network code to prevent certain network issues (r1ch)
  • Added some more network logging (r1ch)
  • Testing a GL game capture fix after a certain (annoying) bug was introduced in 0.542b that caused some OpenGL games not to operate properly
 

Gol D. Ace

Member
Re: 0.54.03 network test build

I click Stop Streaming then the UI freezes for short and then I get reconnecting.
Loosing less then 2 secs.

Twitch
 

Boildown

Active Member
Re: 0.54.03 network test build

Works perfectly for me after one 2.5 hour stream with local capture.
 

Joe33345

Member
Re: 0.54.03 network test build

Gol D. Ace said:
I click Stop Streaming then the UI freezes for short and then I get reconnecting.
Loosing less then 2 secs.

Twitch
I have a similar problem. When you end the broadcast OBS locks up for a few seconds then proceeds to reconnect to start up again.
 

paibox

heros in an halfshel
Re: 0.54.03 network test build

That's weird. It should lock up for a second or two (depending on the size of your buffer), but it shouldn't attempt to reconnect again. Are you guys using FLV or MP4 for the local recording? (If you are recording to a file as well, that is.)
 

R1CH

Forum Admin
Developer
Re: 0.54.03 network test build

Will look into the reconnecting issue. I was worried this might happen, it seems Twitch may disconnect if you exceed the server-side frame buffer?
 

Floatingthru

Community Helper
Re: 0.54.03 network test build

"18:36:38: RTMPPublisher::SocketLoop: Aborting due to FD_CLOSE, error 0"

Yeah, that's what happens when you click stop streaming. OBS stops responding for a bit then the reconnect pop up shows up. Even if you only stream for 2 seconds this still happens. Also the dreaded "18:37:44: Memory Leaks Were Detected." appears again. Going to do more real testing in a bit to see if I can reproduce it. Good news that is only at most 1 second was missing from the time I clicked stop streaming in the VOD.

http://pastebin.com/m0kHFwsW

http://www.twitch.tv/floatingthru/b/433948505
 

Boildown

Active Member
Re: 0.54.03 network test build

I've streamed twice now with this beta version where OBS crashed. Both times were with a 900 second delay. Both times it finished streaming the delayed stream successfully. Where it went wrong is after the 900 seconds, it seemed to start streaming again, instead of just ending and going back to a normal non-streaming state. Only the file it output was corrupt, and Twitch didn't recognize any data it sent for this erroneous second stream. When I aborted this, OBS crashed with the following (this is the second time it happened, just tonight):

Code:
OBS has encountered an unhandled exception and has terminated. If you are able to
reproduce this crash, please submit this crash report on the forums at
http://www.obsproject.com/ - include the contents of this crash log and the
minidump .dmp file (if available) as well as your regular OBS log files and
a description of what you were doing at the time of the crash.

This crash appears to have occured in the 'd:\ark\obs\currenttest\obs.exe' module.

**** UNHANDLED EXCEPTION: c0000005
Fault address: 000000013F2035E9 (d:\ark\obs\currenttest\obs.exe)
OBS version: Open Broadcaster Software v0.54.03 network test
Windows version: 6.1 (Build 7601) Service Pack 1
CPU: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz

Crashing thread stack trace:
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
00000000001EF200 000000013F2035E9 0000000000000000 0000000001CCAE00 000000000039CAE0 0000000000000005 obs.exe!RTMPPublisher::FlushDataBuffer+0x19
00000000001EF230 000000013F201D11 0000000000000000 0000000001CCAE00 0000000000000001 0000000000001389 obs.exe!RTMPPublisher::~RTMPPublisher+0xd1
00000000001EF2A0 000000013F1E0FB4 0000000000000001 00000000775A9AA6 00000000001EF318 0000000200000030 obs.exe!DelayedPublisher::`scalar deleting destructor'+0x14
00000000001EF2D0 000000013F1FC4BC 0000000000001389 00000000001EF450 0000000000000111 0000000000000000 obs.exe!OBS::Stop+0x10c
00000000001EF350 000000013F21A13E 0000000000000070 FFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFF 00000000775A9B43 obs.exe!OBS::OBSProc+0xa8e
00000000001EF4E0 00000000775A9BD1 00000000007E5800 000000013F2196B0 00000000FFFFFED1 0000000000010374 user32.dll!0x775a9bd1
00000000001EF5A0 00000000775A6AA8 0000000000010358 0000000000000111 0000000000001389 000007FEFC5E0A29 user32.dll!0x775a6aa8
00000000001EF630 00000000775A6BAD 0000000000437820 0000000000000001 0000000000000000 0000000000000000 user32.dll!0x775a6bad
00000000001EF680 000007FEFC5E0BBF 0000000000010374 0000000000000001 0000000000437820 000007FEFE462421 comctl32.dll!0x7fefc5e0bbf
00000000001EF6C0 000007FEFC5E47FE 000000000000FF00 0000000000030000 0000000000000202 0000000000000000 comctl32.dll!0x7fefc5e47fe
00000000001EF780 00000000775A9BD1 00000000001EFA40 000007FEFC5E3B20 00000000007E5800 00000000007E8C20 user32.dll!0x775a9bd1
00000000001EF840 00000000775A98DA 0000000000000000 0000000000000000 000007FEFC5E3B20 0000000000000001 user32.dll!0x775a98da
00000000001EF8C0 00000000775A67C2 00000000000103B7 00000000000103B7 000007FEFE462164 0000000000425A20 user32.dll!0x775a67c2
00000000001EF950 000000013F1F0B49 0000000000000000 0000000000000000 000000013F1D0000 0000000000000000 obs.exe!WinMain+0x8b9
00000000001EFE80 000000013F263600 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs.exe!strstr+0x1ac
00000000001EFF30 00000000776A652D 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x776a652d
00000000001EFF60 00000000777DC521 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x777dc521

A minidump was saved to C:\Users\default\AppData\Roaming\OBS\crashDumps\OBSCrashDump2013-07-23_1.dmp.
Please include this file when posting a crash report.

List of loaded modules:
Base Address                      Module
This is pretty low-priority to me because both the stream and the file saved to the hard drive are both correct.

I didn't see the part about minidump and normal log before, let me dig that up...

Minidump and logs: https://anonfiles.com/file/e5aa2140e7cc ... 89acb4fb4d

Regular OBS log:

Code:
19:17:28: Open Broadcaster Software v0.54.03 network test - 64bit ( ^ω^)
19:17:28: -------------------------------
19:17:28: CPU Name: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
19:17:28: CPU Speed: 3400MHz
19:17:28: Physical Memory:  12255MB Total, 10978MB Free
19:17:28: stepping id: 7, model 10, family 6, type 0, extmodel 1, extfamily 0, HTT 1, logical cores 8, total cores 4
19:17:28: monitor 1: pos={0, 0}, size={1680, 1050}
19:17:28: Windows Version: 6.1 Build 7601 S
19:17:28: Aero is Disabled
19:17:28: -------------------------------
19:17:28: OBS Modules:
19:17:28: Base Address     Module
19:17:28: 000000003F1D0000 OBS.exe
19:17:28: 00000000F4790000 OBSApi.dll
19:17:28: 00000000F45D0000 DShowPlugin.dll
19:17:28: 00000000F45A0000 GraphicsCapture.dll
19:17:28: 00000000F4580000 NoiseGate.dll
19:17:28: 00000000F4560000 PSVPlugin.dll
19:17:28: ------------------------------------------
19:17:28: Adapter 1
19:17:28:   Video Adapter: NVIDIA GeForce GTX 560 Ti  
19:17:28:   Video Adapter Dedicated Video Memory: 1025966080
19:17:28:   Video Adapter Shared System Memory: 3220779008
19:17:28: =====Stream Start: 2013-07-22, 19:17:28===============================================
19:17:28:   Multithreaded optimizations: On
19:17:28:   Base resolution: 1920x1080
19:17:28:   Output resolution: 1280x720
19:17:28: ------------------------------------------
19:17:28: Loading up D3D10...
19:17:29: Playback device Default
19:17:29: ------------------------------------------
19:17:29: Using desktop audio input: Speakers (Creative SB X-Fi)
19:17:29: ------------------------------------------
19:17:29: Using auxilary audio input: Microphone (3- USB Audio Device)
19:17:29: ------------------------------------------
19:17:29: Audio Encoding: AAC
19:17:29:     bitrate: 160
19:17:29: ------------------------------------------
19:17:29:     device: AVerMedia HD Capture C985 Bus 4,
19:17:29:     device id \\?\pci#ven_1af2&dev_a001&subsys_a0011af2&rev_00#4&1d7623a1&0&00e2#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{957bd672-7934-4b55-b81a-3e22b14c679a},
19:17:29:     chosen type: YV12, usingFourCC: true, res: 1920x1080 - 1920x1080, frameIntervals: 333333-666666, fourCC: 'YV12'
19:17:29:     audio device: Disable,
19:17:29:     audio device id Disabled,
19:17:29: 
19:17:29: Using directshow input
19:17:29: Using custom x264 settings: "opencl=true threads=8 rc_lookahead=60"
19:17:29: ------------------------------------------
19:17:29: Video Encoding: x264
19:17:29:     fps: 30
19:17:29:     width: 1280, height: 720
19:17:29:     preset: medium
19:17:29:     CBR: yes
19:17:29:     CFR: yes
19:17:29:     max bitrate: 3000
19:17:29: ------------------------------------------
19:32:33: Using RTMP service: Twitch / Justin.tv
19:32:33:   Server selection: rtmp://live-iad.justin.tv/app
19:32:33:   Interface: Intel(R) 82579V Gigabit Network Connection (ethernet, 1000 mbps)
19:32:34: SO_SNDBUF was at 8192
19:32:34: SO_SNDBUF is now 65536
19:33:38: RTMPPublisher::BufferedSend: Increasing socket send buffer to ISB 131072
19:33:58: Total frames rendered: 29650, number of frames that lagged: 9 (0.03%) (it's okay for some frames to lag)
19:33:58: Total duplicated frames: 4 (0.01%)
19:34:05: RTMPPublisher::SocketLoop: Aborting due to FD_CLOSE, error 0
19:34:06: Number of times waited to send: 4, Waited for a total of 16388 bytes
19:34:06: Number of b-frames dropped: 5 (0.2%), Number of p-frames dropped: 0 (0%), Total 5 (0.2%)
19:34:06: =====Stream End: 2013-07-22, 19:34:06=================================================
19:34:32: =====Stream Start: 2013-07-22, 19:34:32===============================================
19:34:32:   Multithreaded optimizations: On
19:34:32:   Base resolution: 1920x1080
19:34:32:   Output resolution: 1280x720
19:34:32: ------------------------------------------
19:34:32: Loading up D3D10...
19:34:32: Playback device Default
19:34:32: ------------------------------------------
19:34:32: Using desktop audio input: Speakers (Creative SB X-Fi)
19:34:32: ------------------------------------------
19:34:32: Using auxilary audio input: Microphone (3- USB Audio Device)
19:34:32: ------------------------------------------
19:34:32: Audio Encoding: AAC
19:34:32:     bitrate: 160
19:34:32: ------------------------------------------
19:34:32:     device: AVerMedia HD Capture C985 Bus 4,
19:34:32:     device id \\?\pci#ven_1af2&dev_a001&subsys_a0011af2&rev_00#4&1d7623a1&0&00e2#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{957bd672-7934-4b55-b81a-3e22b14c679a},
19:34:32:     chosen type: YV12, usingFourCC: true, res: 1920x1080 - 1920x1080, frameIntervals: 333333-666666, fourCC: 'YV12'
19:34:32:     audio device: Disable,
19:34:32:     audio device id Disabled,
19:34:32: 
19:34:32: Using directshow input
19:34:32: Using custom x264 settings: "opencl=true threads=8"
19:34:32: ------------------------------------------
19:34:32: Video Encoding: x264
19:34:32:     fps: 30
19:34:32:     width: 1280, height: 720
19:34:32:     preset: medium
19:34:32:     CBR: yes
19:34:32:     CFR: yes
19:34:32:     max bitrate: 3000
19:34:32: ------------------------------------------
19:49:35: Using RTMP service: Twitch / Justin.tv
19:49:35:   Server selection: rtmp://live-iad.justin.tv/app
19:49:35:   Interface: Intel(R) 82579V Gigabit Network Connection (ethernet, 1000 mbps)
19:49:36: SO_SNDBUF was at 8192
19:49:36: SO_SNDBUF is now 65536
20:29:40: RTMPPublisher::BufferedSend: Increasing socket send buffer to ISB 262144
23:46:23: Total frames rendered: 453332, number of frames that lagged: 39 (0.01%) (it's okay for some frames to lag)
23:46:23: Total duplicated frames: 8 (0.00%)
00:01:30: RTMPPublisher::SocketLoop: Aborting due to FD_CLOSE, error 0
00:01:31: Number of times waited to send: 6, Waited for a total of 24596 bytes
00:01:31: Number of b-frames dropped: 30 (0.0066%), Number of p-frames dropped: 52 (0.011%), Total 82 (0.018%)
00:01:48: =====Stream End: 2013-07-23, 00:01:48=================================================
00:01:58: =====Stream Start: 2013-07-23, 00:01:58===============================================
00:01:58:   Multithreaded optimizations: On
00:01:58:   Base resolution: 1920x1080
00:01:58:   Output resolution: 1280x720
00:01:58: ------------------------------------------
00:01:58: Loading up D3D10...
00:01:58: Playback device Default
00:01:58: ------------------------------------------
00:01:58: Using desktop audio input: Speakers (Creative SB X-Fi)
00:01:58: ------------------------------------------
00:01:58: Using auxilary audio input: Microphone (3- USB Audio Device)
00:01:58: ------------------------------------------
00:01:58: Audio Encoding: AAC
00:01:58:     bitrate: 160
00:01:58: ------------------------------------------
00:01:58:     device: AVerMedia HD Capture C985 Bus 4,
00:01:58:     device id \\?\pci#ven_1af2&dev_a001&subsys_a0011af2&rev_00#4&1d7623a1&0&00e2#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{957bd672-7934-4b55-b81a-3e22b14c679a},
00:01:58:     chosen type: YV12, usingFourCC: true, res: 1920x1080 - 1920x1080, frameIntervals: 333333-666666, fourCC: 'YV12'
00:01:58:     audio device: Disable,
00:01:58:     audio device id Disabled,
00:01:58: 
00:01:58: Using directshow input
00:01:58: Using custom x264 settings: "opencl=true threads=8"
00:01:58: ------------------------------------------
00:01:58: Video Encoding: x264
00:01:58:     fps: 30
00:01:58:     width: 1280, height: 720
00:01:58:     preset: medium
00:01:58:     CBR: yes
00:01:58:     CFR: yes
00:01:58:     max bitrate: 3000
00:01:58: ------------------------------------------
00:02:23: Total frames rendered: 744, number of frames that lagged: 0 (0.00%) (it's okay for some frames to lag)
00:02:23: Total duplicated frames: 0 (0.00%)
 

Jim

Jim
Developer
Re: 0.54.04 network test build

Updated the build with a fair amount of fixes for the new code (0.54.04), particularly crash fixes
 

WayZHC

Member
Re: 0.54.04 network test build

Btw there is the auto-update checking for current stable versions (like 0.542). So why wouldn't you add option (like checkbox) in OBS general settings (or advanced) to also check for test builds with the auto-update? In the OBS root folder in program files (x86) it would place the test build files in a "test version" folder.
 

Joe33345

Member
Re: 0.54.04 network test build

My reconnect issue was fixed as well but the issue I have now is a long 15 to 20 second pause when I hit stop streaming.
 

paibox

heros in an halfshel
Re: 0.54.04 network test build

The pause you're experiencing is the encoder buffer waiting to run out, so that nothing will get cut off at the end of the stream/recording. There's really no way to make it not "pause", since you have to wait for the encoder to finish everything up.
 

Boildown

Active Member
Re: 0.54.04 network test build

Did a 3.5 hour stream with 900 second delay using the 0.54.04 version and the stream ended properly, no early aborts, no mysterious reconnection attempts, no crashes.
 

R1CH

Forum Admin
Developer
Re: 0.54.04 network test build

Joe33345 said:
My reconnect issue was fixed as well but the issue I have now is a long 15 to 20 second pause when I hit stop streaming.
Are you using a stream delay? I'm also getting fairly long pauses with a delay, will look into it.
 

Joe33345

Member
Re: 0.54.04 network test build

R1CH said:
Joe33345 said:
My reconnect issue was fixed as well but the issue I have now is a long 15 to 20 second pause when I hit stop streaming.
Are you using a stream delay? I'm also getting fairly long pauses with a delay, will look into it.
Nah, no Stream Delay. Just regular settings. :-)
 

Kharay

Member
Re: 0.54.04 network test build

I'm getting the same, although very randomly and quite short but it does indeed seem to lag a bit both when starting and when stopping a stream. At least for me. Again, this is intermittently and for me is a delay/stutter of maybe 0.5 - 1.5 seconds but it definitely is there. And no stream delay specified here either.

What's also new to me is that particularly in the first 30 - 60 seconds of the stream it tends to drop frames where it didn't drop those before. Afterwards the stream will be perfectly fine but sometimes it does drop frames at the start.

Edit: Regarding this 'Stop Streaming' stutter/delay, just now the interval was a bit longer than it had been before. Something in the order of 4 seconds or so. And I noticed something unusual in the log file afterwards: RTMPPublisher::SocketLoop: Aborting due to FD_CLOSE during shutdown, buffered data lost, error 0. As opposed to the usual: RTMPPublisher::SocketLoop: Graceful loop exit.
 
Status
Not open for further replies.
Top