- 13 5月, 2014 4 次提交
- 12 5月, 2014 7 次提交
-
-
由 Jim 提交于
Added a version to the X11 GL context request
-
由 Thomas McGrew 提交于
This enables the application to start on Intel graphics under Mesa 10.2
-
由 jp9000 提交于
The 'how many scenes is this source in' reference counter used in the basic UI was not being decremented.
-
由 Palana 提交于
-
由 Palana 提交于
With the previous locking strategy some display captures would sometimes not process multiple frames in a row if multiple display captures were active
-
由 Palana 提交于
-
由 Palana 提交于
-
- 11 5月, 2014 1 次提交
-
-
由 jp9000 提交于
Add a 'source selection' dialog to replace the 'enter a name' dialog. This new dialog allows you to make new instances of pre-existing sources so that you can add a pre-existing source to a different scene, or in to the same scene more than once. Also started implementing locale. Comtemplating switching to JSON-based locale later, so we can add things like descriptions/disambiguation, and so we can use jansson's built-in hash table when doing the string lookup.
-
- 10 5月, 2014 5 次提交
- 09 5月, 2014 2 次提交
- 08 5月, 2014 10 次提交
- 06 5月, 2014 2 次提交
- 05 5月, 2014 3 次提交
-
-
由 jp9000 提交于
-
由 jp9000 提交于
First, if the private data of the source fails to be created, then do not destroy the source. If the source is destroyed, all the user's data associated with that source is lost, which could end up being a potential problem. Instead, let it linger as a 'dead' source until the user chooses to fix the problem (though this should never really happen, the source module functions should be programmed to handle this scenario) Secondly, rename new_frame_ready to ready_async_frame, and fix a potential memory leak with it.
-
由 Palana 提交于
obs_source_output_video can cause cached frames to be freed twice if called with a partially destroyed source, among other undesirable effects; freeing the source private data right after the destroy signal has been processed ensures proper behavior
-
- 04 5月, 2014 4 次提交
-
-
由 jp9000 提交于
-
由 jp9000 提交于
- Add volume control These volume controls are basically nothing more than sliders. They look terrible and hopefully will be as temporary as they are terrible. - Allow saving of specific non-user sources via obs_load_source and obs_save_source functions. - Save data of desktop/mic audio sources (sync data, volume data, etc), and load the data on startup. - Make it so that a scene is created by default if first time using the application. On certain operating systems where supported, a default capture will be created. Desktop capture on mac, particularly. Not sure what to do about windows because monitor capture on windows 7 is completely terrible and is bad to start users off with.
-
由 jp9000 提交于
These are guidelines, not necessarily a rulebook.
-
由 paibox 提交于
Make sure the D3D11 scissorrect settings actually get applied.
-
- 03 5月, 2014 2 次提交
-
-
由 jp9000 提交于
I had forgotten how constants worked when compiled; constants are uploaded as constant registers. When constants are used with shaders, multiple constants are often packed in to a single register when possible to reduce constant register count. For example, one 'float' constant and one 'float3' constant will be packed in to a single register (c0.x for constant 1, c0.yzw for constant 2), but two 'float' constants and one 'float3' constant must inhabit two registers (c0.xy for constant 1, c1.xyz for constant 2), so it must start on a new register boundry (every 16 bytes). I had first instinctively thought it was just a simple case of alignment like it is on the CPU, but then I realized that it didn't sound right, so I went back and did some more tests and then ultimately remembered how constants actually are uploaded.
-
由 jp9000 提交于
-