Caused us no end of pain. Users clicked it so much that it made us all
snap. Now, if a user really, REALLY wants to use it, they'll have to
manually set the ini file variable in their profile ini, under [Audio],
InputDevicesForDesktopSound=1
- Add an option in game capture to use SetWindowsHookEx instead of
CreateRemoteThread to inject the library.
- Add logging of what process game capture is trying to capture.
- Rename "audio time offset" where it was used to "audio sync offset"
- Adde logging for audio sync offsets
- Update version to 0.62b test 1
Original change in 1c8df6329ac6e3b8d28c68ee7001cc12a1dd935d modified the unused
second parameter for BM_SETCHECK instead of sending BST_CHECKED as first
parameter
The log file menu will now only contain log files that have at least logged
the system stats since too many people uploaded useless logs, unfortunately
This should alleviate the impact of enabling "Use Input devices ..." in
the advanced config
Also add a log message to signify that "Use Input devices ..." is enabled
The entire mono situation is my fault. I did test it and it seemed
like it was working at first when I got the pull request so I said "hey
okay looks good." Unfortunately I was mistaken, so I'm fixing the code
myself.
AAC was taking in stereo audio and was not calculating the timestamps
correctly. Internally OBS still gets data in the form of stereo, so
because this is OBS1 I'm just going to put in this workaround code that
downmixes stereo to mono in to the AAC encoder buffer.
This should eliminate all problems users had with corrupted shader cache files
API users who need non-blocking compilation of shaders are encouraged to use the
new async API
This includes "optimizations" for almost all publish warnings; the aspect ratio
warning is not fixed because trying to fix that has wider repercussions for
scene/source layout/positioning and potentially even required bitrate
A possible future "optimization" to fix the aspect ratio warning would be to
compute a number of possible choices based on the current downscale setting with
a target output resolution of 480p/540p/720p/etc. and let the user select one of
the resulting base resolutions
Displaying both the defaults and the optimize button requires (currently
unnecessary) tweaking of the settings dialog, so they are mutually exclusive for
now
