- 15 7月, 2017 2 次提交
-
-
由 jp9000 提交于
Allows the ability to override bframes (useful for specific protocols)
-
由 jp9000 提交于
Allows the ability to change the output type in case one service requires a different output type. NOTE: This should be considered a temporarily yet simple solution to a specific problem: support for RTMP-like outputs. This will allows seamless integration of supporting different RTMP-like output types within the same service. This should probably be replaced with a more ideal solution later, such as implementing a completely different service type instead, when time permits.
-
- 14 7月, 2017 1 次提交
-
-
由 jp9000 提交于
(This commit also modifies obs-outputs)
-
- 13 7月, 2017 1 次提交
-
-
由 Richard Stanway 提交于
-
- 08 7月, 2017 1 次提交
-
-
由 Gol-D-Ace 提交于
-
- 05 7月, 2017 1 次提交
-
-
由 jp9000 提交于
-
- 03 7月, 2017 4 次提交
-
-
由 Cephas Reis 提交于
Closes jp9000/obs-studio#945
-
由 VodBox 提交于
Deprecates "Theme" global config value and uses "CurrentTheme" instead to ensure backward compatibility with older versions of OBS, which will fail to load if you have a theme that isn't available. (Jim Edit: Putting this back because I misunderstood the purpose of jp9000/obs-studio#936)
-
由 jp9000 提交于
-
由 VodBox 提交于
Closes jp9000/obs-studio#936
-
- 02 7月, 2017 9 次提交
-
-
由 jp9000 提交于
Closes jp9000/obs-studio#738
-
由 cg2121 提交于
-
由 jp9000 提交于
-
由 Jim 提交于
UI: Add new theme, update theme capabilities
-
由 Richard Stanway 提交于
-
由 Jim 提交于
obs-qsv11: change re-enter lock implementation
-
由 Jim 提交于
obs-text: Fix file reader occasionally not updating
-
由 Jim 提交于
libobs: Fix an int underflow in log_frame_info
-
由 Jim 提交于
plugins: Clear warnings about -Wincompatible-pointer-types
-
- 01 7月, 2017 1 次提交
-
-
由 Joseph El-Khouri 提交于
Adds the ability to zoom into the preview when fixed scaling mode is enabled. (Edit by Jim: Also now saves zoom and scroll position) Closes jp9000/obs-studio#917
-
- 30 6月, 2017 2 次提交
- 29 6月, 2017 4 次提交
- 28 6月, 2017 10 次提交
-
-
由 Jim 提交于
.editorconfig: Add file to speed up editor configuration
-
由 Shaolin 提交于
Closes jp9000/obs-studio#937
-
由 adocilesloth 提交于
Closes jp9000/obs-studio#948
-
由 jp9000 提交于
If size is 0 after popping data from the front or back, set the start/end points to 0 as well to ensure that any subsequent buffer pushes start from the beginning of the buffer rather than the middle of the buffer. Reduces potential unnecessary operations in that case. Additionally, this fixes a bug with circulebuf_pop_back where if start position was 0, and all the data was popped off the buffer (equal to the capacity), the end position would be equal to the original size. As an example to replicate the bug, push 5, pop 5, then push 10. The start/end points will be invalid. Closes jp9000/obs-studio#954
-
由 Jim 提交于
UI: Add functions and events for Studio Mode into the Frontend API
-
由 Jim 提交于
CI: Download deps if they are outdated
-
由 notmark 提交于
Removed LAX server, added new NYC server for Vaughn Live & Breakers.TV Closes jp9000/obs-studio#933
-
由 mntone 提交于
Add Japanese shortcut keys, non-convert (無変換) and convert (変換) and disable IME for OBSHotkeyEdit. Closes jp9000/obs-studio#930
-
由 cg2121 提交于
Adds a lock checkbox to allow the user to lock a specific scene item. Closes jp9000/obs-studio#949
-
由 jp9000 提交于
-
- 27 6月, 2017 4 次提交
-
-
由 Skid-Inc 提交于
-
由 Skid-Inc 提交于
Delayed reading the text file till the update after the timestamp changes, this should fix a minor issue where if the file updates twice in one second, only the first change it displayed.
-
由 cg2121 提交于
This adds a "Defaults" button in the source and filter properties, which will clear and reset all settings. Closes jp9000/obs-studio#875
-
由 jp9000 提交于
If a source is created with settings, default values would not be set on data items that already had values set. The check here was supposed to be a not equal rather than an equal because you're not supposed to be able to set a default value of one type on an item that already exists but is of a different type. This bug would make it so that if a particular setting was removed, there would be no default value to fall back on, and it would always be 0 or NULL for all values. It's likely this bug wasn't encountered until now because before now there had been no reason to clear or remove settings on most things.
-