Clears source video when the media stream ends.

A null frame send to the frame callback signals
the end of media being played.  Null frames are not
sent for looped media

This is in preparation of an API change that will send null
frames to signal the end of the media being played.

Silly code that pre-incremented a value while also assigning
it to the same value.

Skip decode refresh scheduling if the abort flag is
set when the timer fails to start.  This avoids extraneous
refresh scheduling when tearing down the decoders.

When compiling under mingw it was using the w32-pthreads
instead of the shared mingw pthread library.

Since sws_getCachedContext possibly logs a message every
time it is used (depending on the input), use our own caching
logic to minimize log spam.

Using LOG_ERROR here isn't really necessary, it just means that there's
no blackmagic support.

Fix a bug where when a source first starts up its async cache, it
unintentionally resets its cache, which means that the first few frames
would be lost.

The name 'Monitor' is a bit inconsistent with what it's called by the
operating system.

If the settings are reset to defaults or if the settings are just bad,
the video would get stuck on the last frame that was displayed, which
feels a bit awkward.  Best to make it stop video output entirely rather
than get stuck on the last video frame.

Having devices not active by default may cause confusion for some users.

When hitting the Cancel button, cleanup code needs to go through the
reject() callback as well.

Ensures that ->deleteLater events are put in to the event queue before
the destructor is called.

Sometimes events with rogue source references are in the event queue
when the program is shutting down.  This can cause the program to
reference freed data.  Processing those remaining events before shutting
down solves the issue.

This prevents the save timer from unexpectedly going off during the
middle of the save process.

When an item is selected but not focused, it would be too similar to the
non-selected color.

Only store the last restored (non-maximized and non-minimized) window
position and size on exit.

Certain devices (particularly certain mixers and soundflower 64ch) would
have an arbitrary number of channels, and wouldn't really be mappable to
a specific speaker layout supported by libobs.

So to fix this issue, if the channel count is above 8, force the data to
stereo to ensure playback can still occur, rather than cause it to just
fail.

Prevents issues on specific locales, especially where decimal points are
represented by commas rather than periods.

This is just in case a filter is applied to a scene, filters will turn
off the blending so it's necessary to set the blending.

This optionally specifies that the int/float value should be displayed
with a slider rather than and up/down control.  UIs are not necessarily
required to implement it, it's meant to be more of a hint.

This fixes an issue primarily with filter rendering: when capturing
windows and displays, their alpha channel is almost always 0, causing
the image to be completely invisible unintentionally.  The original fix
for this for many sources was just to turn off the blending, which would
be fine if you're not rendering any filters, but filters will render to
render targets first, and that lack of alpha will end up carrying over
in to the final image.

This doesn't apply to any mac captures because mac actually seems to set
the alpha channel to 1.

This returns a common effect useful for rendering an image with the
alpha channel overridden to 1.0.

If negative was specified it would not parse the negative sign and thus
would not interpret that number as negative, and would cause
shader/effect parsing to simply fail on the file.

This is particularly important for the filter pipeline in order to
ensure that when the last filter is reached that the original blend
state is properly reset.

The linux window and monitor captures draw in a custom way, therefore
they must be marked as types of sources that do custom rendering.

Switching between shaders often can cause a performance hit, so cache
effects so that they persist until the graphics subsystem is destroyed.

If a render target was switched from one to another and then back
consecutively, the texture would not get reattached at the last point
due to the fact that the cur_render_target variable of the FBO storage
structure would already be set to that texture, and then it would never
get reattached because it thought it was already using that render
target.

So to fix this, any time a render target legitimately changes from one
to another, it sets the cur_render_target and cur_zstencil_buffer
variables of the FBO structure to null.

I encountered a scenario where effects might reference shader parameters
that may not potentially exist, this isn't particularly a bad thing that
needs to return failure.  It just needs to gracefully ignore it.

When render targets are used, they output to the render target inverted
due to the way that opengl works.  This fixes that issue by inverting
the projection matrix so that it renders the image upside down and
inverting the front face from counterclockwise to clockwise.

Texture units were not being properly associated with the shader uniform
variables.

obs_leave_graphics() may not be properly called if this returns null for
whatever reason.