- 25 2月, 2015 7 次提交
-
-
由 Jim 提交于
linux-v4l2: Add support for dv timings
-
由 fryshorts 提交于
Use the dv timing selected in the source properties to configure the device instead of resolution/framerate.
-
由 fryshorts 提交于
Add a helper function to set the dv timing for the input.
-
由 fryshorts 提交于
Show the dv timing property when the selected input supports it.
-
由 fryshorts 提交于
Add the dv timing property and hide it by default.
-
由 fryshorts 提交于
Add a helper function to enumerate dv timings supported by the selected input and add them to a property.
-
由 fryshorts 提交于
Add a helper function to get a dv timing by index for the input.
-
- 24 2月, 2015 10 次提交
-
-
由 Jim 提交于
View Log menu entry in Help -> Log Files menu
-
由 Caleb Anderson 提交于
Since the file being logged to changes with each run, opening a log file is a tad more involved than desirable when it's necessary to view the log each time OBS is run. This new menu entry shortcuts opening the file from the file system manually.
-
由 Jim 提交于
linux-v4l2: Add support for video standards
-
由 fryshorts 提交于
Use the video standard selected in the source properties to configure the device instead of resolution/framerate.
-
由 fryshorts 提交于
Add a helper function to get/set the video standard for the input.
-
由 fryshorts 提交于
Use the capabilities for the selected input to decide which properties are enumerated and displayed.
-
由 fryshorts 提交于
Add the video standard property and hide it by default.
-
由 fryshorts 提交于
Add a helper function to enumerate video standards supported by the selected input and add them to a property.
-
由 fryshorts 提交于
Add a helper function to get the capabilities of a specific or the currently selected input of the device.
-
由 fryshorts 提交于
Remove the constraint for device inputs to be of the type "CAMERA". This was added under the false assumption that inputs of the type "TUNER" are only used for control purposes.
-
- 21 2月, 2015 3 次提交
- 18 2月, 2015 4 次提交
-
-
由 jp9000 提交于
This was caused to do the new RTMP code that added support for multiple streams; the stream index needs to be reset on RTMP_Close otherwise it will keep using the wrong stream information.
-
由 jp9000 提交于
-
由 Jim 提交于
UI: Fix rounding issues for advanced audio
-
由 fryshorts 提交于
Remove the close_float check for values that are set through the advanced UI. If the difference of the integer was 1 this would sometimes cause the input to be ignored. Add rounding to values that are set through the signal system, since casting alone will act like floor, which is not desirable in this case.
-
- 17 2月, 2015 4 次提交
-
-
由 Palana 提交于
Previously having a source multiple times in a single scene would cause the recursion check to trigger. Example scenes.json: { "current_scene": "Scene", "sources": [ { "flags": 0, "id": "scene", "mixers": 0, "name": "Scene", "settings": { "items": [ { "align": 5, "bounds": { "x": 0.0, "y": 0.0 }, "bounds_align": 0, "bounds_type": 0, "name": "Text (FreeType 2)", "pos": { "x": 0.0, "y": 0.0 }, "rot": 0.0, "scale": { "x": 1.0, "y": 1.0 }, "visible": true }, { "align": 5, "bounds": { "x": 0.0, "y": 0.0 }, "bounds_align": 0, "bounds_type": 0, "name": "Text (FreeType 2)", "pos": { "x": 0.0, "y": 98.0 }, "rot": 0.0, "scale": { "x": 1.0, "y": 1.0 }, "visible": true } ] }, "sync": 0, "volume": 1.0 }, { "flags": 0, "id": "text_ft2_source", "mixers": 0, "name": "Text (FreeType 2)", "settings": {}, "sync": 0, "volume": 1.0 } ] }
-
由 Palana 提交于
Previously a NULL item would cause a crash when reading transform info. The crash can be reproduced by e.g. editing scenes.json so that two scenes contain each other. Example scenes.json: { "current_scene": "Scene", "sources": [ { "flags": 0, "id": "scene", "mixers": 0, "name": "Scene", "settings": { "items": [ { "align": 5, "bounds": { "x": 1440.0, "y": 900.0 }, "bounds_align": 0, "bounds_type": 2, "name": "Scene 2", "pos": { "x": 0.0, "y": 0.0 }, "rot": 0.0, "scale": { "x": 1.0, "y": 1.0 }, "visible": true } ] }, "sync": 0, "volume": 1.0 }, { "flags": 0, "id": "scene", "mixers": 0, "name": "Scene 2", "settings": { "items": [ { "align": 5, "bounds": { "x": 1.0, "y": 1.0 }, "bounds_align": 0, "bounds_type": 0, "name": "Scene", "pos": { "x": 854.0, "y": -520.0 }, "rot": 0.0, "scale": { "x": 1.75, "y": 1.7562724351882935 }, "visible": true } ] }, "sync": 0, "volume": 1.0 } ] }
-
由 HomeWorld 提交于
Display "No properties available" text in the property view if there are no properties available. Closes Pull Request #377
-
由 Kevin Tardif 提交于
Since we rely on the dynamic linker to find the library for us via dlopen(), we need to have DL_OPENGL be .so.N, not the full library filename, as ldconfig doesn't cache the full filename Use of TARGET_SONAME_FILE requires the library to be marked as SHARED, not MODULE This closes pull request #370
-
- 16 2月, 2015 2 次提交
- 15 2月, 2015 9 次提交
-
-
由 Jim 提交于
Fix typo in README
-
由 kc5nra 提交于
-
由 jp9000 提交于
Do not update the avermedia encoders if they are already active, they weren't designed to be updated in real time, so it will cause encoding to break.
-
由 Socapex 提交于
If the jsonData string is null, then there's nothing that should be written. Closes pull request #366 from Socapex/debugcrash
-
由 jp9000 提交于
-
由 Jim 提交于
win-dshow: Reorder CapsMatch for gcc
-
由 Martell Malone 提交于
-
由 Jim 提交于
UI: Small fixes to advanced audio settings
-
由 jp9000 提交于
I had this issue where IDXGISwapChain::ResizeBuffers would fail in the hooks, causing games to crash when they resized their backbuffers because ResizeBuffers would return an 'invalid call' HRESULT value. In the ResizeBuffers documentation it says that it will only happen if a backbuffer currently has any outstanding references, but there's no way this would happen unless ResizeBuffers internally calls Present or vise versa. After ResizeBuffers has been called, the very first call to Present will somehow seemingly invalidate and/or destroy the current backbuffer. It's very strange, but that seems to be what's going on, at least for the game I was testing. So if you are performing a post-overlay capture, then you must ignore the capture on the very first call to Present. It's Microsoft's code so you can't really know what's going on, you just have to work around these strange issues seemingly in the dark.
-
- 14 2月, 2015 1 次提交
-
-
由 jp9000 提交于
Although STDMETHODCALLTYPE is technically WINAPI (__stdcall), it's best not to make any assumptions.
-