- #Beep test recording code
- #Beep test recording windows 7
- #Beep test recording download
- #Beep test recording windows
With these changes, I was able to get SRBeep to properly play start/stop sounds reliably no matter how short the interval in between starting and stopping. So either boost::thread must have some way of detecting the potentially fatal error and has some workaround to avoid it, or std::thread is purposefully causing a crash when it detects the memory leaks as some kind of ham-handed debugging. Hence why OBS Studio log reports "2 output(s) were remaining" and 2 extra memory leaks either way.
#Beep test recording code
I don't know what they are in particular, but my guess would be that, as coded and with my modifications, they are both either leaving open thread handles on module unload or the reference count is getting messed up when the code is exited with the threads left in a joinable state. So in theory boost::thread and std::thread would be the same, but I know many of the boost libraries and in particular boost::thread have some minor differences with the std libraries. But as you probably know, boost is basically intended to bring older C++ standards up to date, or at least more up to date, with C++11 and future standards.
#Beep test recording windows
I must apologize now because I am fairly new to Windows API, C++, and coding in general, so I really don't know much and may be wrong about any number of things. And worse because even though the Window closes, the OBS Studio process keeps running in the background until ended through Task Manager. It's different because the crash notification appears to be from OBS Studio itself and not the bog standard Windows crash message box. Boost was built using the included bootstrap batch file as per the documentation.įunny enough, that changed you proposed was the first thing I tried before changing to boost, and it gives a different, worse crash. Then it's as simple as adding the boost root dir to "Additional Include Libraries" and stage\lib in the boost root dir to "Additional Library Directories. Just to confirm in case you want to test for yourself, the only other code change is altering #include to #include. So now I am leaving std::atomic but changing std::thread to boost::thread everywhere it appears. Still, with my fix, the log is still noting "2 output(s) were remaining" and 2 extra memory leaks as with the original code, so it would seem like using boost::thread is just 'covering up' or something. So it is definitely the std::thread objects. Then went and only changed std::thread to boost::thread, leaving std::atomic, and the crash is fixed again. Just tested switching only std::atomic to boost::atomic and it gets the original crash. Any idea what is causing the crash? I'll give you the information from Event Viewer from one of the 32-bit crashes in case it can provide any clues.įaulting application name: obs32.exe, version: 0.0.0.0, time stamp: 0x57a87607įaulting module name: MSVCR120.dll, version: 5.1, time stamp: 0x524f7ce6įaulting application start time: 0x01d216e9c896f53cįaulting application path: C:\Program Files (x86)\obs-studio\bin\32bit\obs32.exeįaulting module path: C:\Windows\system32\MSVCR120.dll
#Beep test recording download
I tried to download the source code and recompile it myself, but couldn't get it working (probably because I'm using Visual Studio 2008). I've tried repairing my VC++ 2013 redistributables. Removing SRBeep DLLs makes the crashes go away.
#Beep test recording windows 7
Maybe one of these will suit you and both OBS Studio 32-bit and 64-bit on Windows 7 圆4, SRBeep seems to be working as intended but I get an application crash with EventID 1000 upon every exit. There are guides about for using virtual audio cables, I'm sure. Use a virtual audio cable to channel audio to OBS and have your programs play through that (as well as your desktop obviously) but do not have OBS's audio going through the virtual audio cable. You accept that this will happen and remove the beep. From what I've read, some people are lazy when it comes to editing so this may cut out some of this out. Change the beep to some bad ass intro music and have it as an intro.
![beep test recording beep test recording](http://ecx.images-amazon.com/images/I/61GsXGr4xPL.png)
![beep test recording beep test recording](https://members.itkd.co.nz/reference/documents/technical/images/beep-test-scoring.png)
You accept this will happen and embrace it. If this is a problem, off the top of my head there are two options: The second beep works similarly but once the stream/recording goes from active to inactive so isn't captured. As a result, the first 'beep' happens just after the stream/recording goes from being inactive (or not happening) to active (happening) so it can only occur once the stream/recording is running and so is recorded. So the only way (I've found) to do this is to monitor if a stream/recording is active. As I suspect this will come up a lot, I shall attempt to address the first 'beep' being recorded.Īt the time of writing, as far as I'm aware, there is no way to get if the stream/recording button has been pressed via OBS's API.