UI: Unify output record paths across setting dialogs

It seems more intuitive if the recording paths for the Simple
Output, Advanced Default Output and Advanced FFmpeg Output are
linked together, so that the user does not have to manage three
paths if switching between the different options.

The UI elements are also connected so that a change to one
signals a change to the others with the corresponding config
setting.

These functions were not properly shifting the bits when calculating the
output.

linux capture: Fix issues with XComposite Window Capture

When a source window was not available, a red background was shown
instead. This was undesirable, and expected behavior would be for the
background to be transparent, enabling what exists behind the source
to be shown.

After source window closes, texture is still visible in preview until
the source window opens again.

These functions were mistakenly not marked as static.  They are not used
outside of their compiled object module files, therefore there's no
reason for them not to be static.

(This commit also modifies libobs-d3d11)

Boolean constant size should be 4

The default buffering time for audio was always 1 second before the
audio subsystem was changed, and it was always more than sufficient for
max audio buffering time

People who are blind cannot know what the button does due to lack of any
strings associated with the button.

Under certain circumstances, the timing_adjust variable would cause line
1161 to continually trigger over and over again.  The "loop detection"
code incorrectly made it so that any timestamp that was just simply
below the expected value would be seen as a jump.  After that, the
timing_adjust variable would be set for the frame again, and then the
audio would see it as a jump again after that, and those two things
would continue endlessly.  This would cause stuttering particularly with
certain devices (particularly elgato/lgp/hdpvr) where the audio/video
data are decoded and sent at varying/different/unpredictable times.

To fix this issue, it should not detect values below as jumps, but
instead should only do it for values that exceed the MAX_TS_VAR (maximum
timestamp variance) value.

Modify: EU-North (London) => EU-West (London)
Add: EU-North (Amsterdam)
Closes jp9000/obs-studio#508

Originally there was an issue using FLAC for audio in AVI files, AVI
files wouldn't play back with some players.  Because FLAC doesn't work,
and lossless should be lossless, instead just used uncompressed WAV
data for the lossless audio, which is always supported.

This reverts commit 6e203109.

FLAC doesn't work properly in AVI files, and MKV files don't work in
vegas.  So, sadly the only solution is to use lossless audio at a super
high bitrate for the time being.

(This commit also modifies the UI)

Closes jp9000/obs-studio#502

Closes jp9000/obs-studio#487

Apple wants to get people to move over to their own crypto APIs instead
of using OpenSSL, so disable the warning in the files where OpenSSL is
used for the time being.

A lot of people had the problem where they'd initialize video settings
with 0 width or height on their output resolution value.  This just
changes it so that the user always has a valid resolution so video
initialization doesn't just outright fail.

Originally an intentional design decision, right-clicking would also
perform selection, which is actually rather annoying and unnecessary.

It was mistakenly using ac3 at a high bitrate -- lossless should be
lossless, both video and audio.

Makes the log message a bit less confusing