- 05 10月, 2015 10 次提交
-
-
由 jp9000 提交于
-
由 jp9000 提交于
Reloading symbols after each plugin is causing the load times to increase a fair bit on some computers, so do it after all plugins are loaded instead.
-
由 jp9000 提交于
Used to get the version of a dynamic link library on windows.
-
由 jp9000 提交于
-
由 jp9000 提交于
Fixes a bug where config_save could not save the file due to the fact that it did not store the path of the file as it was supposed to.
-
由 jp9000 提交于
-
由 jp9000 提交于
Intended as a means of expressing an error occurred (-1) when performing a seek or getting a position.
-
由 jp9000 提交于
On the first call to update the symbol paths, pass the path string to the SymInitializeW function first if it hasn't been called yet. If it has been called, then defer to SymSetSearchPathW and then SymRefreshModuleList. This is meant to reduce a needless extra call to the latter two functions on the first use of the function.
-
由 jp9000 提交于
-
由 jp9000 提交于
Microphones and other input devices can often have bad or erroneous timestamps. Although we handle bad timestamps much better in obs-studio, there are still lingering issues that can crop up from time to time with device QPC timestamps that leads to mic data not playing back properly. It's best if it be off by default rather than on, which will now cause it to use system timestamps for input devices by default. This changes it to the same handling as OBS1 for this case.
-
- 29 9月, 2015 2 次提交
- 24 9月, 2015 1 次提交
-
-
由 Palana 提交于
RemoveScene would always remove the currently selected item from the scenes list, even if that item didn't reference the actual scene being removed; finding the proper item via its OBSRef fixes this issue. How to reproduce the original issue: Create two scenes "a" and "b", set a hotkey for switching to scene "a", select scene "b" and press the remove scene button, then while the confirmation dialog is up press the hotkey while the UI is out of focus. The active scene should have switched to "a", while the dialog still displays "b" as its target; now confirm the removal of "b". Note how "a" was removed from the scenes list instead. Reported at https://obsproject.com/mantis/view.php?id=333
-
- 23 9月, 2015 9 次提交
-
-
由 jp9000 提交于
This reverts commit 35b2ce56. There is far too much potential for issues to occur if the first-time start creates a display capture by default on linux and windows. Display capture on windows laptops will not be guaranteed to capture properly, leaving the user with a blank screen. Display capture on linux downloads its image off the graphics processor, so it's quite inefficient to have on by default.
-
由 jp9000 提交于
-
由 jp9000 提交于
Adds LGP Lite capture support
-
由 Jim 提交于
Latest translations from CrowdIn
-
由 dodgepong 提交于
-
由 jp9000 提交于
It is not necessary to reset the capture when cx or cy is at 0 because 0 means the application is minimized.
-
由 jp9000 提交于
The new 'offset' value was not being passed back to the caller, which caused the caller to continue to use the old value and thus would cause an invalid hook and crash.
-
由 jp9000 提交于
The call to CoInitializeEx in the win-mf module caused some sort of conflict with the decklink module, causing the decklink module to crash on exit. Instead, let libobs handle COM initialization.
-
由 jp9000 提交于
Due to the fact that certain modules may need COM on startup, initialize COM by default in libobs.
-
- 22 9月, 2015 7 次提交
-
-
由 jp9000 提交于
If the GL capture part of the game capture hook fails to initialized for whatever reason, it will go in to an infinite reacquire loop. If it fails to initialize shared texture capture, try shared memory capture instead.
-
由 jp9000 提交于
-
由 jp9000 提交于
22.05khz audio really doesn't make sense to have available, and causes issues with encoders (primarily CoreAudio)
-
由 jp9000 提交于
Use SymSetSearchPath to include plugin directories in pdb search paths. This is important for generating proper crash data and crash logs on windows.
-
由 jp9000 提交于
-
由 jp9000 提交于
When an encoder has been removed (such as CoreAudio) and the audio bitrates currently configured no longer are available to the current audio encoders anymore, it would cause GetAACEncoderForBitrate to return false with no encoder available. To fix the issue, instead just choose the closest bitrate relative to the current bitrate (rounded up).
-
由 jp9000 提交于
Fixes warning: warning C4244: 'initializing' : conversion from 'int64_t' to 'int', possible loss of data
-
- 21 9月, 2015 3 次提交
-
-
由 jp9000 提交于
-
由 jp9000 提交于
Using gzdopen will not work properly if the C standard library used to get the descriptor is not the same library as the one that was compiled with zlib. When this is the case, it causes zlib to fail to write a file, and would report a C standard library error. Use gzopen and gzopen_w instead to ensure that the file is opened and closed by zlib itself, ensuring that zlib and the libobs do not have to share the C standard library between each other.
-
由 jp9000 提交于
-
- 20 9月, 2015 6 次提交
-
-
由 jp9000 提交于
After some more testing, utvideo not only gives better encoding performance, but also better compression and better decoding performance. It's pretty much superior all around over huffyuv.
-
由 jp9000 提交于
So certain high-profile individuals were complaining that it was difficult to configure recording settings for quality in OBS. So, I decided to add a very easy-to-use auto-configuration for high quality encoding -- including lossless encoding. This feature will automatically configure ideal recording settings based upon a specified quality level. Recording quality presets added to simple output: - Same as stream: Copies the encoded streaming data with no extra usage hit. - High quality: uses a higher CRF value (starting at 23) if using x264. - Indistinguishable quality: uses a low CRF value (starting at 16) if using x264. - Lossless will spawn an FFmpeg output that uses huffyuv encoding. If a user tries to select lossless, they will be warned both via a dialog prompt and a warning message in the settings window to ensure they understand that it requires tremendous amounts of free space. It will always use the AVI file format. Extra Notes: - When High/Indistinguishable quality is set, it will allow you to select the recording encoder. Currently, it just allows you to select x264 (at either veryfast or ultrafast). Later on, it'll be useful to be able to set up pre-configured presets for hardware encoders once more are implemented and tested. - I decided to allow the use of x264 at both veryfast or ultrafast presets. The reasoning is two-fold: 1.) ultrafast is perfectly viable even for near indistinguishable quality as long as it has the appropriate CRF value. It's nice if you want to record but would like to or need to reduce the impact of encoding on the CPU. It will automatically compensate for the preset at the cost of larger file size. 2.) It was suggested to just always use ultrafast, but ultrafast requires 2-4x as much disk space for the same CRF (most likely due to x264 compensating for the preset). Providing veryfast is important if you really want to reduce file size and/or reduce blocking at lower quality levels. - When a recording preset is used, a secondary audio encoder is also spawned at 192 bitrate to ensure high quality audio. I chose 192 because that's the limit of the media foundation aac encoder on windows, which I want to make sure is used if available due to its high performance. - The CRF calculation is based upon resolution, quality, and whether it's set to ultrafast. First, quality sets the base CRF, 23 for "good" quality, 16 for "very high" quality. If set to ultrafast, it'll subtract 2 points from the CRF value to help compensate. Lower resolutions will also lower the CRF value to help improve higher details with a smaller pixel ratio.
-
由 jp9000 提交于
-
由 jp9000 提交于
Seems that most decoders that don't read the h264 header tend to expect 601 instead of 709.
-
由 jp9000 提交于
For game capture, if a game is running at for example 800 FPS and limit capture framerate is off, it would try to capture all 800 of those frames, dramatically reducing performance more than what would ever be necessary. When limit capture framerate is off, instead of capturing all frames, capture frames at an interval of twice the OBS FPS, identical to how OBS1 works by default. This should greatly increase performance under that circumstance.
-
由 jp9000 提交于
Use the actual parameter from the x264 params for CRF, and also make sure to specify that CRF is meant to be 0 if CBR is enabled.
-
- 19 9月, 2015 2 次提交