- 14 6月, 2017 2 次提交
-
-
由 jp9000 提交于
With certain media files (wmv in particular), the very last frame will have a timestamp of AV_NOPTS_VALUE. This could cause the media to stick on that frame indefinitely. Instead, use the estimated next timestamp that was calculated in the previous frame.
-
由 jp9000 提交于
Media files that have a very low framerate or very long interval between frames would cause the media playback to stall indefinitely until the next frame is played. This adds a 200ms timeout to ensure that the media can be destroyed without being forced to wait indefinitely for the next frame.
-
- 12 6月, 2017 1 次提交
-
-
由 Richard Stanway 提交于
-
- 09 6月, 2017 2 次提交
- 05 6月, 2017 1 次提交
-
- 04 6月, 2017 1 次提交
-
-
由 jp9000 提交于
Certain functions such as avformat_open_input and av_read_frame can block, causing the program to someone wait very long periods of time when a network URL is used with the media source. The interrupt_callback member variable in AVFormatContext allows safely canceling IO operations when trying to shut down or stop the media-playback interface.
-
- 30 5月, 2017 9 次提交
-
-
由 Jim 提交于
Suppress -Wimplicit-fallthrough in GCC 7
-
由 jp9000 提交于
-
由 jp9000 提交于
(Note: This commit also modifies deps/media-playback) Allows buffering network-based media sources where supported. Default is two megabytes of buffering.
-
由 jp9000 提交于
Currently, when media-playback is used with a network address, video has to wait for the first keyframe before it starts decoding. This is probably not wise because the first packet of video may contain additional header information, and because audio is forced to wait and buffer while waiting for a keyframe, potentially causing a lot of audio to get backed up unnecessarily which could inadvertently cause sync or audio playback issues. So, instead of waiting for a keyframe before decoding starts, decode right away, and make it wait for a keyframe before calling the video callback instead.
-
由 jp9000 提交于
-
由 jp9000 提交于
Limits OpenProcess flags to only the flags that are necessary to prevent any further issues with anti-cheat hooks in the future.
-
由 Shaolin 提交于
Signed-off-by: NShaolin <admshao@gmail.com>
-
由 Jim 提交于
UI: Look for plugins in ~/Library/Application Support/obs-studio/plug…
-
由 Colin Edwards 提交于
-
- 29 5月, 2017 4 次提交
-
-
由 jp9000 提交于
-
由 jp9000 提交于
-
由 jp9000 提交于
-
由 jp9000 提交于
When using the full installer, there'll be a section where you can choose what to install -- one section is a tree view with a "plugins" section, and in that section there's "Browser plugin" and "Realsense plugin". Instead of superfluously saying "plugin" for each of those, replace with "source" instead -- so browser source and realsense source. Also somewhat helps prevent the user from getting confused and thinking we're installing a browser or something.
-
- 27 5月, 2017 1 次提交
-
-
由 Jim 提交于
rtmp-services: Rename Beam to Mixer
-
- 26 5月, 2017 1 次提交
-
-
由 Jim 提交于
librtmp: Fix build error with ENODATA on FreeBSD
-
- 25 5月, 2017 2 次提交
-
-
由 derrod 提交于
-
由 Ryan Foster 提交于
When building on FreeBSD before this patch, it would produce the error "error: use of undeclared identifier 'ENODATA'". This fixes that.
-
- 22 5月, 2017 2 次提交
- 21 5月, 2017 14 次提交
-
-
由 jp9000 提交于
-
由 jp9000 提交于
When custom server is used, it would still use the "common" RTMP service to cap its bitrate. So if Twitch was selected and you changed over to custom RTMP server, it would still cap to Twitch's bitrate limits even though you're not using Twitch anymore.
-
由 jp9000 提交于
There's no need to reset vertex buffers like this anymore. This would unintentionally cause certain things (such as the freetype text source on windows) to stop rendering properly.
-
由 Jim 提交于
UI: Fix creation of crash log with non-english paths
-
由 mntone 提交于
-
由 Jim 提交于
enc-amf: Version 2.1.5
-
由 Michael Fabian Dirks 提交于
This has the 32-bit crash workaround as AMD has not yet fixed the AMF runtime logging crash.
-
由 jp9000 提交于
-
由 jp9000 提交于
When an output fails to connect and it's already been prematurely stopped, the event to mark the output as stopped would not be signaled, causing obs_output_destroy to lock up indefinitely while waiting for the event to be signaled.
-
由 jp9000 提交于
Prevents the output from hard-locking on itself when the stop call would trigger the callback and then try to lock again. Probably could be solved with a recursive mutex, but at that point it's not really necessary.
-
由 jp9000 提交于
Rather than have the back-end try to determine whether the output can or cannot stop, allow the stop callback to continue in the plugin either way and let the plugin itself make that determination. This fixes a bug where the back-end wouldn't have data active while connecting, therefore the stop callback wouldn't be called, and once connected it wouldn't know that it was supposed to stop. In other words trying to call obs_output_stop on an output that was in a state of connecting would do nothing and the output would never stop.
-
由 Gol-D-Ace 提交于
-
由 jp9000 提交于
The radio buttons had been changed so "Streaming" would be selected by default, but it only sets the wizard's "type" to streaming if the user actually clicks the radio button themselves manually, so it would stay set to "Invalid" by mistake, causing settings to not be applied.