Okay I'll start this post off by saying that I registered to hopefully get this bug (if it is considered as such) fixed, but I'd like to also say that the OBSproject is simply fantastic and I really like where this, and the community, is going.
...Down to the problem. My OBS (no matter if it's the stable or beta versions) cannot stream when I tell it to fetch for a text file with song details from a network computer. By cannot stream, I mean that as soon as I turn on the stream, I will see the text file's contents being displayed, but everything will freeze up and 5 seconds later OBS will crash. I will include the OBSCrashLog in a spoiler below. Here's the .dmp (dump) file: https://www.dropbox.com/s/r2unakirpz9qo ... 6-26_2.dmp
If you need an alternate mirror ask away.
Now onto why you should even go about fixing this "bug" (I'm using quotes because I have not heard of anyone on the forums displaying their song through networking). A long time ago (perhaps more than a year and a half) I was using Xsplit (mind you at the time I did not know about OBS, and it was also in its less primal beta stages, to the point where it was compared to the weak FFsplit), and streamed using a dual-PC setup. Using networking, I would send the metadata of a song to Xsplit with NowPlayingSimple (foobar plugin). It was an easy way to display the song playing by pointing the stream PC to the gaming PC's text output (e.g. //Gaming-PC/NowPlayingShare/NowPlaying.txt).
About two weeks ago I tried the same thing with OBS, only to find that it would crash everytime I loaded up the network text, and if I loaded up locally updated text, it would run fine (the networked text didn't even have to update, it just crashed OBS upon loading). I took the network text off, and the stream ran fine again. I really want this feature, but could understand if it's a minor bug that would be worked out eventually someday in the future where all the other minor bugs are already worked out. Why is it a feature to me? Well, I don't listen to music on the streaming PC and need to send the metadata text over to it. I have no doubt in my mind that if the networked text was working, I'd be able to display the currently playing song and its playback time and remaining length. Thanks for hearing me out, I really appreciate it!
...Down to the problem. My OBS (no matter if it's the stable or beta versions) cannot stream when I tell it to fetch for a text file with song details from a network computer. By cannot stream, I mean that as soon as I turn on the stream, I will see the text file's contents being displayed, but everything will freeze up and 5 seconds later OBS will crash. I will include the OBSCrashLog in a spoiler below. Here's the .dmp (dump) file: https://www.dropbox.com/s/r2unakirpz9qo ... 6-26_2.dmp
If you need an alternate mirror ask away.
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 'f:\users\ichigo.stream-pc\desktop\64bit\obsapi.dll' module.
**** UNHANDLED EXCEPTION: c0000005
Fault address: 000007FCC18FAB0C (f:\users\ichigo.stream-pc\desktop\64bit\obsapi.dll)
OBS version: Open Broadcaster Software v0.52.07b aquaman build
Windows version: 6.2 (Build 9200)
Crashing thread stack trace:
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
000000000831F620 000007FCC18FAB0C 0000000000000000 000000000099F300 000000000831F729 0000000000000001 obsapi.dll!FastAlloc::_Allocate+0x17c
000000000831F670 000007FCC18EEDCB 00000000022E6000 000000000099F300 00000000022E4000 0000000002242800 obsapi.dll!List<float>::SetSize+0x6b
000000000831F6A0 000007FCC18ED04E 0000000000000000 0000000000000000 000000000831F729 0000000002242800 obsapi.dll!AudioSegment::AudioSegment+0x4e
000000000831F6D0 000007FCC18EE76F 00000000000001B9 0000000000000000 00000000000050F7 00000000085E0000 obsapi.dll!AudioSource::QueryAudio+0x101f
000000000831F790 000007F64635C895 0000000000000000 0000000000000000 000000000831F8C0 0000000000000001 obs.exe!OBS::QueryNewAudio+0x35
000000000831F7C0 000007F64635CC35 0000000000000001 0000000000000372 00000000000050F7 0000000000000F81 obs.exe!OBS::MainAudioLoop+0x245
000000000831F950 000007F64635C591 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs.exe!OBS::MainAudioThread+0x11
000000000831F980 000007FCCE4A1832 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x7fcce4a1832
000000000831F9B0 000007FCD030D609 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7fcd030d609
A minidump was saved to F:\Users\Ichigo.Stream-PC\AppData\Roaming\OBS\crashDumps\OBSCrashDump2013-06-26_2.dmp.
Please include this file when posting a crash report.
List of loaded modules:
Base Address Module
000007F646330000-000007F646484000 F:\Users\Ichigo.Stream-PC\Desktop\64bit\OBS.exe
000007FCD02B0000-000007FCD0470000 F:\Windows\SYSTEM32\ntdll.dll
000007FCCE4A0000-000007FCCE5D6000 F:\Windows\system32\KERNEL32.DLL
000007FCCD5B0000-000007FCCD6A3000 F:\Windows\system32\KERNELBASE.dll
000007FCC9EA0000-000007FCC9EA9000 F:\Windows\SYSTEM32\AVRT.dll
000007FCCB6E0000-000007FCCB701000 F:\Windows\SYSTEM32\dwmapi.dll
000007FCCB0E0000-000007FCCB154000 F:\Windows\SYSTEM32\dxgi.dll
000007FCCB1C0000-000007FCCB1F4000 F:\Windows\SYSTEM32\d3d10_1.dll
000007FCC51E0000-000007FCC525F000 F:\Windows\SYSTEM32\d3dx10_43.dll
000007FCD0250000-000007FCD02A8000 F:\Windows\system32\WS2_32.dll
000007FCC8BF0000-000007FCC8C1A000 F:\Windows\SYSTEM32\IPHLPAPI.DLL
000007FCC3DA0000-000007FCC3DC0000 F:\Windows\SYSTEM32\WINMM.dll
000007FCC18E0000-000007FCC1AFD000 F:\Users\Ichigo.Stream-PC\Desktop\64bit\OBSApi.dll
000007FCCEF70000-000007FCD0250000 F:\Windows\system32\SHELL32.dll
Now onto why you should even go about fixing this "bug" (I'm using quotes because I have not heard of anyone on the forums displaying their song through networking). A long time ago (perhaps more than a year and a half) I was using Xsplit (mind you at the time I did not know about OBS, and it was also in its less primal beta stages, to the point where it was compared to the weak FFsplit), and streamed using a dual-PC setup. Using networking, I would send the metadata of a song to Xsplit with NowPlayingSimple (foobar plugin). It was an easy way to display the song playing by pointing the stream PC to the gaming PC's text output (e.g. //Gaming-PC/NowPlayingShare/NowPlaying.txt).
About two weeks ago I tried the same thing with OBS, only to find that it would crash everytime I loaded up the network text, and if I loaded up locally updated text, it would run fine (the networked text didn't even have to update, it just crashed OBS upon loading). I took the network text off, and the stream ran fine again. I really want this feature, but could understand if it's a minor bug that would be worked out eventually someday in the future where all the other minor bugs are already worked out. Why is it a feature to me? Well, I don't listen to music on the streaming PC and need to send the metadata text over to it. I have no doubt in my mind that if the networked text was working, I'd be able to display the currently playing song and its playback time and remaining length. Thanks for hearing me out, I really appreciate it!