jp9000
/
obs-studio
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
obs-studio/UI/forms/OBSBasicSettings.ui

8063 lines
343 KiB
Plaintext
Raw Permalink Normal View History

Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
<?xml version="1.0" encoding="UTF-8"?>
<ui version="4.0">
<class>OBSBasicSettings</class>
<widget class="QDialog" name="OBSBasicSettings">
<property name="geometry">
<rect>
<x>0</x>
<y>0</y>
UI: Add "Bind to IP" setting to advanced settings
2016-07-29 08:30:54 -07:00
<width>981</width>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<height>730</height>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</rect>
</property>
Add (temporary terrible) volume controls - 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.
2014-05-03 22:54:38 -07:00
<property name="sizePolicy">
UI: Fix settings window minimum width/height This fixes the issue presented in: https://obsproject.com/mantis/view.php?id=885 Minimum size is changed to 700x512. I arrived at this number from testing the minimum sizes that I felt the settings UI was still perfectly usable and readable. Any smaller, and things became difficult to see and adjust. As a note, this does increase the minum width of the settings window, as the previous minimum allowed you to cut off objects and render the window too small to be usable.
2017-07-27 19:02:39 -07:00
<sizepolicy hsizetype="Expanding" vsizetype="Expanding">
Add (temporary terrible) volume controls - 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.
2014-05-03 22:54:38 -07:00
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
UI: Fix settings window minimum width/height This fixes the issue presented in: https://obsproject.com/mantis/view.php?id=885 Minimum size is changed to 700x512. I arrived at this number from testing the minimum sizes that I felt the settings UI was still perfectly usable and readable. Any smaller, and things became difficult to see and adjust. As a note, this does increase the minum width of the settings window, as the previous minimum allowed you to cut off objects and render the window too small to be usable.
2017-07-27 19:02:39 -07:00
<property name="minimumSize">
<size>
<width>700</width>
<height>512</height>
</size>
</property>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
<property name="windowTitle">
Add text for missing window titles
2014-07-13 13:09:56 -07:00
<string>Settings</string>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
UI: Show sizing grip in dialogs where resizing is useful Some windows, like the main window and Interact, already do this.
2022-08-30 01:36:04 -07:00
<property name="sizeGripEnabled">
<bool>true</bool>
</property>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
<layout class="QVBoxLayout" name="verticalLayout">
<item>
<layout class="QHBoxLayout" name="horizontalLayout">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<property name="spacing">
<number>0</number>
</property>
UI: Display aspect ratios in video settings
2020-01-08 22:03:22 -08:00
<item>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
<widget class="QListWidget" name="listWidget">
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Expanding">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="maximumSize">
<size>
UI: Increase maximum size of settings' sidebar Some languages such as Spanish or Brazilian Portuguese have longer words that make the sidebar scroll. Unfortunately Qt reports a rather large minimum size for the sidebar, so simply removing the maximum size is not an option. Increase maximum width of the sidebar to 180px.
2022-04-17 15:56:12 -07:00
<width>180</width>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
<height>16777215</height>
</size>
</property>
<property name="iconSize">
<size>
UI: Set sidebar icon size to 16px Symbolic icons, such as the ones used in the sidebar of the settings dialog, are usually made to work best at 16x16.
2022-04-17 15:53:58 -07:00
<width>16</width>
<height>16</height>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</size>
</property>
UI: Adjust list style of settings sidebar Add padding between items and border; increase inner padding a bit; make list items rounded; add spacing between list items.
2022-07-30 20:12:09 -07:00
<property name="spacing">
<number>1</number>
</property>
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<property name="currentRow">
<number>0</number>
</property>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
<item>
<property name="text">
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
<string>Basic.Settings.General</string>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
<property name="icon">
<iconset resource="obs.qrc">
UI: Redo settings icons
2018-12-14 05:42:05 -08:00
<normaloff>:/settings/images/settings/general.svg</normaloff>:/settings/images/settings/general.svg</iconset>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
</item>
<item>
<property name="text">
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
<string>Basic.Settings.Stream</string>
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
</property>
<property name="icon">
<iconset resource="obs.qrc">
UI: Redo settings icons
2018-12-14 05:42:05 -08:00
<normaloff>:/settings/images/settings/stream.svg</normaloff>:/settings/images/settings/stream.svg</iconset>
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
</property>
</item>
<item>
<property name="text">
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
<string>Basic.Settings.Output</string>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
<property name="icon">
<iconset resource="obs.qrc">
UI: Redo settings icons
2018-12-14 05:42:05 -08:00
<normaloff>:/settings/images/settings/output.svg</normaloff>:/settings/images/settings/output.svg</iconset>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
</item>
<item>
<property name="text">
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
<string>Basic.Settings.Audio</string>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
<property name="icon">
<iconset resource="obs.qrc">
UI: Redo settings icons
2018-12-14 05:42:05 -08:00
<normaloff>:/settings/images/settings/audio.svg</normaloff>:/settings/images/settings/audio.svg</iconset>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
</item>
<item>
<property name="text">
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
<string>Basic.Settings.Video</string>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
<property name="icon">
<iconset resource="obs.qrc">
UI: Redo settings icons
2018-12-14 05:42:05 -08:00
<normaloff>:/settings/images/settings/video.svg</normaloff>:/settings/images/settings/video.svg</iconset>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
</item>
UI: Add hotkeys page in settings dialog
2014-11-01 13:50:36 -07:00
<item>
<property name="text">
<string>Basic.Settings.Hotkeys</string>
</property>
<property name="icon">
<iconset resource="obs.qrc">
UI: Redo settings icons
2018-12-14 05:42:05 -08:00
<normaloff>:/settings/images/settings/hotkeys.svg</normaloff>:/settings/images/settings/hotkeys.svg</iconset>
UI: Add hotkeys page in settings dialog
2014-11-01 13:50:36 -07:00
</property>
</item>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
<item>
<property name="text">
<string>Basic.Settings.Accessibility</string>
</property>
<property name="icon">
<iconset resource="obs.qrc">
<normaloff>:/settings/images/settings/accessibility.svg</normaloff>:/settings/images/settings/accessibility.svg</iconset>
</property>
</item>
UI: Add 'Advanced' settings section Currently, this allows the setting of values such as: - Audio buffering time - Color format (still somewhat unsupported) - YUV color space (if a YUV format) = YUV color range (if a YUV format) More color formats will be added in the future, such as RGB and YUV 4:2:2 formats.
2015-02-11 12:55:06 -08:00
<item>
<property name="text">
<string>Basic.Settings.Advanced</string>
</property>
<property name="icon">
<iconset resource="obs.qrc">
UI: Redo settings icons
2018-12-14 05:42:05 -08:00
<normaloff>:/settings/images/settings/advanced.svg</normaloff>:/settings/images/settings/advanced.svg</iconset>
UI: Add 'Advanced' settings section Currently, this allows the setting of values such as: - Audio buffering time - Color format (still somewhat unsupported) - YUV color space (if a YUV format) = YUV color range (if a YUV format) More color formats will be added in the future, such as RGB and YUV 4:2:2 formats.
2015-02-11 12:55:06 -08:00
</property>
</item>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</widget>
</item>
<item>
<widget class="QStackedWidget" name="settingsPages">
<property name="currentIndex">
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
<number>0</number>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
<widget class="QWidget" name="generalPage">
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<layout class="QVBoxLayout" name="verticalLayout_18">
<property name="leftMargin">
<number>0</number>
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
</property>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<property name="topMargin">
<number>0</number>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QScrollArea" name="scrollArea_2">
UI: Hide border for General Settings container This makes the screen consistent with Advanced and Audio
2019-02-02 19:47:25 -08:00
<property name="frameShape">
UI, obs-plugins: Add spinbox suffixes where necessary
2019-07-18 00:38:50 -07:00
<enum>QFrame::NoFrame</enum>
UI: Hide border for General Settings container This makes the screen consistent with Advanced and Audio
2019-02-02 19:47:25 -08:00
</property>
<property name="frameShadow">
<enum>QFrame::Plain</enum>
</property>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<property name="widgetResizable">
UI: Add snap options to general settings section Allows the user to disable snapping all together or control the snap threshold.
2016-04-06 18:03:29 -07:00
<bool>true</bool>
</property>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<widget class="QWidget" name="scrollAreaWidgetContents_2">
<property name="geometry">
<rect>
<x>0</x>
UI: Redo settings icons
2018-12-14 05:42:05 -08:00
<y>0</y>
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<width>767</width>
<height>1326</height>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
</rect>
UI: Add snap options to general settings section Allows the user to disable snapping all together or control the snap threshold.
2016-04-06 18:03:29 -07:00
</property>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<layout class="QVBoxLayout" name="verticalLayout_19">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>9</number>
</property>
UI: Clean up Settings form markup This continues work from #5133 to correct UI file markup and save correctly in Qt Creator Defining alignment as an attribute in the <item> tag seems to be old behaviour that current versions of Qt Creator do not respect and will clobber these entries on save. The correct approach is to have alignment as a property element in the widget. As well, QWidgets that contain property definitions as well as a layout child item do not properly show up in the Qt Creator hierarchy. These properties are still invisibly applied but the QWidgets are not shown in Qt Creator and will get removed from the file after saving.
2021-08-16 22:41:57 -07:00
<item>
<widget class="QFrame" name="widget_2">
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<layout class="QVBoxLayout" name="verticalLayout_20">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<property name="leftMargin">
<number>9</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<item>
<widget class="QGroupBox" name="groupBox_15">
<property name="title">
<string>Basic.Settings.General</string>
</property>
<layout class="QFormLayout" name="formLayout_32">
UI: Fix some settings layouts on non-windows systems Form layouts should laways have the setting "all non-fixed fields grow" to make it look consistent across operating systems.
2017-02-25 06:31:06 -08:00
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
UI: Add front-end auto-updater
2017-02-20 04:46:29 -08:00
<property name="topMargin">
<number>2</number>
</property>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<item row="0" column="0">
<widget class="QLabel" name="label">
<property name="text">
<string>Basic.Settings.General.Language</string>
</property>
<property name="buddy">
<cstring>language</cstring>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QComboBox" name="language"/>
</item>
<item row="1" column="0">
<widget class="QLabel" name="label_42">
<property name="text">
<string>Basic.Settings.General.Theme</string>
</property>
<property name="buddy">
<cstring>theme</cstring>
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QComboBox" name="theme"/>
</item>
UI: Add front-end auto-updater
2017-02-20 04:46:29 -08:00
<item row="2" column="0">
<spacer name="horizontalSpacer_3">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeType">
<enum>QSizePolicy::Fixed</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
<height>5</height>
</size>
</property>
</spacer>
</item>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<item row="2" column="1">
<widget class="QCheckBox" name="enableAutoUpdates">
<property name="text">
<string>Basic.Settings.General.EnableAutoUpdates</string>
</property>
<property name="checked">
<bool>true</bool>
</property>
</widget>
</item>
<item row="3" column="1">
<widget class="QCheckBox" name="openStatsOnStartup">
<property name="text">
<string>Basic.Settings.General.OpenStatsOnStartup</string>
UI: Add option to hide OBS windows on Windows This uses the SetWindowDisplayAffinity API to hide windows from capture applications (including OBS). This is not perfect - internal windows such as context menus, combo box dropdowns, etc will still be displayed. Even with these limitations, it should help people with single monitors capture content with less interference from the OBS window. This implementation is for Windows only but the code is generic enough that adding other platforms should be straightforward.
2020-06-26 17:31:08 -07:00
</property>
</widget>
</item>
<item row="4" column="1">
<widget class="QCheckBox" name="hideOBSFromCapture">
UI: Better Hide OBS Window description, add first time dialog & tooltip
2022-01-22 17:27:18 -08:00
<property name="toolTip">
<string>Basic.Settings.General.HideOBSWindowsFromCapture.Tooltip</string>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
</property>
UI: Fixup minor Qt Creator inconsistencies Qt Creator automatically adjusts these files when opened. Rather than contributors having to manually undo these changes, just apply them directly into the repository.
2022-03-19 16:32:07 -07:00
<property name="text">
<string>Basic.Settings.General.HideOBSWindowsFromCapture</string>
</property>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
</widget>
</item>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
</layout>
</widget>
</item>
<item>
<widget class="QGroupBox" name="groupBox_16">
<property name="title">
<string>Basic.Settings.Output</string>
</property>
<layout class="QFormLayout" name="formLayout_2">
UI: Fix some settings layouts on non-windows systems Form layouts should laways have the setting "all non-fixed fields grow" to make it look consistent across operating systems.
2017-02-25 06:31:06 -08:00
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
UI: Add front-end auto-updater
2017-02-20 04:46:29 -08:00
<property name="topMargin">
<number>2</number>
</property>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<item row="0" column="0">
<spacer name="horizontalSpacer_5">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
UI: Make sure size-specific spacers are fixed Fixes the general settings pane on mac
2017-02-24 14:11:23 -08:00
<property name="sizeType">
<enum>QSizePolicy::Fixed</enum>
</property>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
UI: Add front-end auto-updater
2017-02-20 04:46:29 -08:00
<height>5</height>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
</size>
</property>
</spacer>
</item>
<item row="0" column="1">
<widget class="QCheckBox" name="warnBeforeStreamStart">
<property name="text">
<string>Basic.Settings.General.WarnBeforeStartingStream</string>
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QCheckBox" name="warnBeforeStreamStop">
<property name="text">
<string>Basic.Settings.General.WarnBeforeStoppingStream</string>
</property>
</widget>
</item>
<item row="2" column="1">
UI: Add option to warn on stop recording OBS has an option to warn before stopping a stream, but it doesn't have a similar warning for recording. This can result in a recording being unintentionally stopped. Add an option to warn when the "Stop Recording" button is pressed. Note: While OBS also has an option to warn on stream start, this patch purposefully does not add similar warn on recording start option. This is because accidentally starting to record isn't risky in the same way that accidentally starting to stream is.
2019-06-17 07:14:14 -07:00
<widget class="QCheckBox" name="warnBeforeRecordStop">
<property name="text">
<string>Basic.Settings.General.WarnBeforeStoppingRecord</string>
</property>
</widget>
</item>
<item row="3" column="1">
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<widget class="QCheckBox" name="recordWhenStreaming">
<property name="text">
<string>Basic.Settings.General.RecordWhenStreaming</string>
</property>
</widget>
</item>
UI: Add option to warn on stop recording OBS has an option to warn before stopping a stream, but it doesn't have a similar warning for recording. This can result in a recording being unintentionally stopped. Add an option to warn when the "Stop Recording" button is pressed. Note: While OBS also has an option to warn on stream start, this patch purposefully does not add similar warn on recording start option. This is because accidentally starting to record isn't risky in the same way that accidentally starting to stream is.
2019-06-17 07:14:14 -07:00
<item row="4" column="1">
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<widget class="QCheckBox" name="keepRecordStreamStops">
<property name="enabled">
<bool>false</bool>
</property>
<property name="text">
<string>Basic.Settings.General.KeepRecordingWhenStreamStops</string>
</property>
</widget>
</item>
UI: Add option to warn on stop recording OBS has an option to warn before stopping a stream, but it doesn't have a similar warning for recording. This can result in a recording being unintentionally stopped. Add an option to warn when the "Stop Recording" button is pressed. Note: While OBS also has an option to warn on stream start, this patch purposefully does not add similar warn on recording start option. This is because accidentally starting to record isn't risky in the same way that accidentally starting to stream is.
2019-06-17 07:14:14 -07:00
<item row="5" column="1">
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<widget class="QCheckBox" name="replayWhileStreaming">
<property name="text">
<string>Basic.Settings.General.ReplayBufferWhileStreaming</string>
</property>
</widget>
</item>
UI: Add option to warn on stop recording OBS has an option to warn before stopping a stream, but it doesn't have a similar warning for recording. This can result in a recording being unintentionally stopped. Add an option to warn when the "Stop Recording" button is pressed. Note: While OBS also has an option to warn on stream start, this patch purposefully does not add similar warn on recording start option. This is because accidentally starting to record isn't risky in the same way that accidentally starting to stream is.
2019-06-17 07:14:14 -07:00
<item row="6" column="1">
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<widget class="QCheckBox" name="keepReplayStreamStops">
<property name="enabled">
<bool>false</bool>
</property>
<property name="text">
<string>Basic.Settings.General.KeepReplayBufferStreamStops</string>
</property>
</widget>
</item>
</layout>
</widget>
</item>
<item>
<widget class="QGroupBox" name="groupBox_10">
<property name="enabled">
<bool>true</bool>
</property>
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Maximum">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="title">
<string>Basic.Settings.General.Snapping</string>
</property>
<property name="flat">
<bool>false</bool>
</property>
<layout class="QFormLayout" name="formLayout_21">
UI: Fix some settings layouts on non-windows systems Form layouts should laways have the setting "all non-fixed fields grow" to make it look consistent across operating systems.
2017-02-25 06:31:06 -08:00
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="topMargin">
<number>2</number>
</property>
<item row="0" column="1">
<widget class="QCheckBox" name="snappingEnabled">
<property name="text">
<string>Enable</string>
</property>
<property name="checked">
<bool>true</bool>
</property>
</widget>
</item>
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
<item row="2" column="1">
<widget class="QCheckBox" name="screenSnapping">
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<property name="text">
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
<string>Basic.Settings.General.ScreenSnapping</string>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
</property>
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
<property name="checked">
<bool>true</bool>
</property>
</widget>
</item>
<item row="4" column="1">
<widget class="QCheckBox" name="centerSnapping">
<property name="text">
<string>Basic.Settings.General.CenterSnapping</string>
</property>
<property name="checked">
<bool>true</bool>
</property>
</widget>
</item>
<item row="3" column="1">
<widget class="QCheckBox" name="sourceSnapping">
<property name="text">
<string>Basic.Settings.General.SourceSnapping</string>
</property>
<property name="checked">
<bool>true</bool>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QDoubleSpinBox" name="snapDistance">
<property name="decimals">
<number>1</number>
</property>
<property name="singleStep">
<double>0.500000000000000</double>
</property>
<property name="value">
<double>10.000000000000000</double>
</property>
</widget>
</item>
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
<item row="1" column="0">
<widget class="QLabel" name="label_9">
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<property name="text">
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
<string>Basic.Settings.General.SnapDistance</string>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
</property>
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
<property name="buddy">
<cstring>snapDistance</cstring>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
</property>
</widget>
</item>
<item row="3" column="0">
<spacer name="horizontalSpacer_4">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeType">
<enum>QSizePolicy::Fixed</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
<height>5</height>
</size>
</property>
</spacer>
</item>
</layout>
</widget>
</item>
<item>
<widget class="QGroupBox" name="groupBox_14">
<property name="title">
<string>Basic.Settings.General.Projectors</string>
</property>
<layout class="QFormLayout" name="formLayout_28">
UI: Fix some settings layouts on non-windows systems Form layouts should laways have the setting "all non-fixed fields grow" to make it look consistent across operating systems.
2017-02-25 06:31:06 -08:00
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<property name="topMargin">
<number>2</number>
</property>
<item row="0" column="1">
<widget class="QCheckBox" name="hideProjectorCursor">
<property name="text">
<string>Basic.Settings.General.HideProjectorCursor</string>
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QCheckBox" name="projectorAlwaysOnTop">
<property name="text">
<string>Basic.Settings.General.ProjectorAlwaysOnTop</string>
</property>
</widget>
</item>
<item row="2" column="1">
<widget class="QCheckBox" name="saveProjectors">
<property name="text">
<string>Basic.Settings.General.SaveProjectors</string>
</property>
</widget>
</item>
UI: Add option for only one fullscreen projector per screen This option is added for users who want to have only one projector on a screen and want to save gpu resources.
2021-08-05 23:42:29 -07:00
<item row="3" column="1">
<widget class="QCheckBox" name="closeProjectors">
<property name="text">
<string>Basic.Settings.General.CloseExistingProjectors</string>
</property>
</widget>
</item>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<item row="1" column="0">
<spacer name="horizontalSpacer">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeType">
<enum>QSizePolicy::Fixed</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
<height>5</height>
</size>
</property>
</spacer>
</item>
</layout>
</widget>
</item>
<item>
<widget class="QGroupBox" name="groupBox_13">
<property name="title">
<string>Basic.Settings.General.SysTray</string>
</property>
<layout class="QFormLayout" name="formLayout_29">
UI: Fix some settings layouts on non-windows systems Form layouts should laways have the setting "all non-fixed fields grow" to make it look consistent across operating systems.
2017-02-25 06:31:06 -08:00
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<property name="topMargin">
<number>2</number>
</property>
<item row="0" column="1">
<widget class="QCheckBox" name="systemTrayEnabled">
<property name="text">
UI: Use correct string for systemTrayEnabled
2017-02-28 20:20:05 -08:00
<string>Enable</string>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QCheckBox" name="systemTrayWhenStarted">
<property name="enabled">
<bool>false</bool>
</property>
<property name="text">
<string>Basic.Settings.General.SysTrayWhenStarted</string>
</property>
</widget>
</item>
<item row="2" column="1">
<widget class="QCheckBox" name="systemTrayAlways">
<property name="enabled">
<bool>false</bool>
</property>
<property name="text">
<string>Basic.Settings.General.SystemTrayHideMinimize</string>
</property>
</widget>
</item>
<item row="1" column="0">
<spacer name="horizontalSpacer_2">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeType">
<enum>QSizePolicy::Fixed</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
<height>5</height>
</size>
</property>
</spacer>
</item>
</layout>
</widget>
</item>
UI: Add scene item canvas overflow to preview
2019-01-14 17:58:20 -08:00
<item>
<widget class="QGroupBox" name="groupBox_18">
<property name="title">
<string>StudioMode.Preview</string>
</property>
<layout class="QFormLayout" name="formLayout_35">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="topMargin">
<number>2</number>
</property>
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
<item row="1" column="1">
<widget class="QCheckBox" name="overflowAlwaysVisible">
<property name="text">
<string>Basic.Settings.General.OverflowAlwaysVisible</string>
</property>
</widget>
</item>
UI: Add scene item canvas overflow to preview
2019-01-14 17:58:20 -08:00
<item row="0" column="0">
<spacer name="horizontalSpacer_25">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
<height>5</height>
</size>
</property>
</spacer>
</item>
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
<item row="2" column="1">
<widget class="QCheckBox" name="overflowSelectionHide">
UI: Add scene item canvas overflow to preview
2019-01-14 17:58:20 -08:00
<property name="text">
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
<string>Basic.Settings.General.OverflowSelectionHidden</string>
UI: Various screen reader fixes This commit fixes various issues with screen readers in the main OBS interface. These were tested using NVDA on Windows 10 1903. Checkboxes or buttons which toggle, when receiving an activate signal from the screen reader would visually update, but not perform any action. This is because they're listening only for clicks. They should all now be listening for toggles instead. The screen reader would navigate through the UI in the order that elements are defined in the .ui XML, and not by their row positions. The XML has been reordered so that things should be defined in their row order. Audio track selection now says Track 1, 2, etc, rather than just the number. Various checkboxes that just say "Enable" now have accessible text that says what the enable is for (since it says "checkbox", the fact it's an enable should hopefully be clear). Type in the recording tab of output now has accessible text which says "Recording Type". All the right side buttons in hotkeys now have tooltips, and by extension, accessible text. Currently it does not yet say what hotkey the action is in relation to, but that would require more locales.
2019-09-03 13:58:53 -07:00
</property>
</widget>
</item>
UI: Add option to draw safe areas in preview
2021-08-19 21:56:49 -07:00
<item row="3" column="1">
<widget class="QCheckBox" name="previewSafeAreas">
<property name="text">
<string>Basic.Settings.General.Multiview.DrawSafeAreas</string>
</property>
</widget>
</item>
UI: Show spacing helpers in preview This shows distance between sides of preview and edges of sources. This will allow users to more easily align sources. Co-authored-by: Palakis <contact@slepin.fr>
2021-11-01 00:16:56 -07:00
<item row="4" column="1">
<widget class="QCheckBox" name="previewSpacingHelpers">
<property name="text">
<string>Basic.Settings.General.SpacingHelpers</string>
</property>
</widget>
</item>
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
<item row="0" column="1">
<widget class="QCheckBox" name="overflowHide">
UI: Various screen reader fixes This commit fixes various issues with screen readers in the main OBS interface. These were tested using NVDA on Windows 10 1903. Checkboxes or buttons which toggle, when receiving an activate signal from the screen reader would visually update, but not perform any action. This is because they're listening only for clicks. They should all now be listening for toggles instead. The screen reader would navigate through the UI in the order that elements are defined in the .ui XML, and not by their row positions. The XML has been reordered so that things should be defined in their row order. Audio track selection now says Track 1, 2, etc, rather than just the number. Various checkboxes that just say "Enable" now have accessible text that says what the enable is for (since it says "checkbox", the fact it's an enable should hopefully be clear). Type in the recording tab of output now has accessible text which says "Recording Type". All the right side buttons in hotkeys now have tooltips, and by extension, accessible text. Currently it does not yet say what hotkey the action is in relation to, but that would require more locales.
2019-09-03 13:58:53 -07:00
<property name="text">
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
<string>Basic.Settings.General.OverflowHidden</string>
UI: Add scene item canvas overflow to preview
2019-01-14 17:58:20 -08:00
</property>
UI: Add advanced scene collection importer This replaces the previous Open File dialog for importing collections with a window for importing many collections at once, based on the remux window, along with support for importing from OBS Classic, XSplit Broadcaster and from Streamlabs' fork. This also translates sources between OSes that Studio supports.
2020-02-01 23:44:07 -08:00
</widget>
</item>
</layout>
</widget>
</item>
<item>
<widget class="QGroupBox" name="groupBox_19">
<property name="title">
<string>Basic.Settings.General.Importers</string>
</property>
<layout class="QFormLayout" name="formLayout_36">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="topMargin">
<number>2</number>
</property>
<item row="0" column="0">
<spacer name="horizontalSpacer_26">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
<height>5</height>
</size>
</property>
</spacer>
</item>
<item row="0" column="1">
<widget class="QCheckBox" name="automaticSearch">
<property name="text">
<string>Basic.Settings.General.AutomaticCollectionSearch</string>
</property>
UI: Add scene item canvas overflow to preview
2019-01-14 17:58:20 -08:00
</widget>
</item>
</layout>
</widget>
</item>
UI: Add transition on double-click studio mode option This adds the ability to switch to a scene by double-clicking it when in studio mode. (Edit by Jim: In case this change is undesired by the user, this has been changed to be an option in general settings; disabled by default) Closes jp9000/obs-studio#1029
2017-09-21 13:37:01 -07:00
<item>
<widget class="QGroupBox" name="groupBox_11">
<property name="title">
<string>Basic.TogglePreviewProgramMode</string>
</property>
<layout class="QFormLayout" name="formLayout_31">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
UI: Add Multiview Layout Options
2017-12-13 13:42:19 -08:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
UI: Add transition on double-click studio mode option This adds the ability to switch to a scene by double-clicking it when in studio mode. (Edit by Jim: In case this change is undesired by the user, this has been changed to be an option in general settings; disabled by default) Closes jp9000/obs-studio#1029
2017-09-21 13:37:01 -07:00
<property name="topMargin">
<number>2</number>
</property>
<item row="0" column="1">
<widget class="QCheckBox" name="doubleClickSwitch">
<property name="text">
<string>Basic.Settings.General.SwitchOnDoubleClick</string>
</property>
</widget>
</item>
<item row="0" column="0">
<spacer name="horizontalSpacer_6">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
<height>5</height>
</size>
</property>
</spacer>
</item>
UI: Add Studio Mode layout option for portrait mode displays This commit adds a checkbox to general setting to allow users to enable a vertically oriented layout for studio mode. This commit addresses mantis issue 827: https://obsproject.com/mantis/view.php?id=827 Closes jp9000/obs-studio#1072
2017-11-08 20:44:22 -08:00
<item row="1" column="1">
<widget class="QCheckBox" name="studioPortraitLayout">
<property name="text">
<string>Basic.Settings.General.StudioPortraitLayout</string>
</property>
</widget>
</item>
UI: Add preview/program labels in studio mode
2019-02-28 13:29:41 -08:00
<item row="2" column="1">
<widget class="QCheckBox" name="prevProgLabelToggle">
<property name="text">
<string>Basic.Settings.General.TogglePreviewProgramLabels</string>
</property>
<property name="checked">
<bool>true</bool>
</property>
</widget>
</item>
UI: Move multiview settings to its own groupbox
2018-03-16 12:20:18 -07:00
</layout>
</widget>
</item>
<item>
<widget class="QGroupBox" name="groupBoxMultiview">
<property name="title">
<string>Basic.Settings.General.Multiview</string>
</property>
<layout class="QFormLayout" name="formLayoutMultiview">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="topMargin">
<number>2</number>
</property>
<item row="0" column="0">
<spacer name="horizontalSpacerMultiview">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeType">
<enum>QSizePolicy::Fixed</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
<height>5</height>
</size>
</property>
</spacer>
</item>
UI: Add option to toggle multiview mouse switching
2018-03-16 14:55:56 -07:00
<item row="0" column="1">
<widget class="QCheckBox" name="multiviewMouseSwitch">
<property name="text">
<string>Basic.Settings.General.Multiview.MouseSwitch</string>
</property>
<property name="checked">
<bool>true</bool>
</property>
</widget>
</item>
UI: Move multiview settings to its own groupbox
2018-03-16 12:20:18 -07:00
<item row="1" column="1">
UI: Add option to toggle multiview scene names
2018-03-16 19:00:32 -07:00
<widget class="QCheckBox" name="multiviewDrawNames">
<property name="text">
<string>Basic.Settings.General.Multiview.DrawSourceNames</string>
</property>
<property name="checked">
<bool>true</bool>
</property>
</widget>
</item>
<item row="2" column="1">
UI: Add option to toggle multiview draw safe area
2018-03-18 19:02:27 -07:00
<widget class="QCheckBox" name="multiviewDrawAreas">
<property name="text">
<string>Basic.Settings.General.Multiview.DrawSafeAreas</string>
</property>
<property name="checked">
<bool>true</bool>
</property>
</widget>
</item>
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
<item row="3" column="1">
<widget class="QComboBox" name="multiviewLayout"/>
</item>
UI: Add option to toggle multiview draw safe area
2018-03-18 19:02:27 -07:00
<item row="3" column="0">
UI: Add Multiview Layout Options
2017-12-13 13:42:19 -08:00
<widget class="QLabel" name="label_64">
<property name="text">
<string>Basic.Settings.General.MultiviewLayout</string>
</property>
<property name="buddy">
<cstring>multiviewLayout</cstring>
</property>
</widget>
</item>
UI: Add transition on double-click studio mode option This adds the ability to switch to a scene by double-clicking it when in studio mode. (Edit by Jim: In case this change is undesired by the user, this has been changed to be an option in general settings; disabled by default) Closes jp9000/obs-studio#1029
2017-09-21 13:37:01 -07:00
</layout>
</widget>
</item>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
</layout>
</widget>
</item>
</layout>
</widget>
UI: Add auto-start replay buf. opt. when stream starts Closes jp9000/obs-studio#748
2017-01-04 13:11:52 -08:00
</widget>
</item>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</layout>
</widget>
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
<widget class="QWidget" name="streamPage">
<layout class="QVBoxLayout" name="verticalLayout_5">
<property name="leftMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
<property name="topMargin">
<number>0</number>
Add preliminary streaming code for testing - Add some temporary streaming code using FFmpeg. FFmpeg itself is not very ideal for streaming; lack of direct control of the sockets and no framedrop handling means that FFmpeg is definitely not something you want to use without wrapper code. I'd prefer writing my own network framework in this particular case just because you give away so much control of the network interface. Wasted an entire day trying to go through FFmpeg issues. There's just no way FFmpeg should be used for real streaming (at least without being patched or submitting some sort of patch, but I'm sort of feeling "meh" on that idea) I had to end up writing multiple threads just to handle both connecting and writing, because av_interleaved_write_frame blocks every call, stalling the main encoder thread, and thus also stalling draw signals. - Add some temporary user interface for streaming settings. This is just temporary for the time being. It's in the outputs section of the basic-mode settings - Make it so that dynamic arrays do not free all their data when the size just happens to be reduced to 0. This prevents constant reallocation when an array keeps going from 1 item to 0 items. Also, it was bad to become dependent upon that functionality. You must now always explicitly call "free" on it to ensure the data is free, and that's how it should be. Implicit functionality can lead to confusion and maintainability issues.
2014-03-10 13:10:35 -07:00
</property>
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
UI: Clean up Settings form markup This continues work from #5133 to correct UI file markup and save correctly in Qt Creator Defining alignment as an attribute in the <item> tag seems to be old behaviour that current versions of Qt Creator do not respect and will clobber these entries on save. The correct approach is to have alignment as a property element in the widget. As well, QWidgets that contain property definitions as well as a layout child item do not properly show up in the Qt Creator hierarchy. These properties are still invisibly applied but the QWidgets are not shown in Qt Creator and will get removed from the file after saving.
2021-08-16 22:41:57 -07:00
<widget class="QFrame" name="widget_5">
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
<property name="sizePolicy">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<sizepolicy hsizetype="Preferred" vsizetype="Maximum">
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
Add preliminary streaming code for testing - Add some temporary streaming code using FFmpeg. FFmpeg itself is not very ideal for streaming; lack of direct control of the sockets and no framedrop handling means that FFmpeg is definitely not something you want to use without wrapper code. I'd prefer writing my own network framework in this particular case just because you give away so much control of the network interface. Wasted an entire day trying to go through FFmpeg issues. There's just no way FFmpeg should be used for real streaming (at least without being patched or submitting some sort of patch, but I'm sort of feeling "meh" on that idea) I had to end up writing multiple threads just to handle both connecting and writing, because av_interleaved_write_frame blocks every call, stalling the main encoder thread, and thus also stalling draw signals. - Add some temporary user interface for streaming settings. This is just temporary for the time being. It's in the outputs section of the basic-mode settings - Make it so that dynamic arrays do not free all their data when the size just happens to be reduced to 0. This prevents constant reallocation when an array keeps going from 1 item to 0 items. Also, it was bad to become dependent upon that functionality. You must now always explicitly call "free" on it to ensure the data is free, and that's how it should be. Implicit functionality can lead to confusion and maintainability issues.
2014-03-10 13:10:35 -07:00
</property>
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<layout class="QFormLayout" name="topStreamLayout">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
</property>
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
</property>
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item row="2" column="0">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<widget class="QLabel" name="serviceLabel">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<property name="text">
<string>Basic.AutoConfig.StreamPage.Service</string>
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
</property>
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<property name="buddy">
<cstring>service</cstring>
</property>
</widget>
</item>
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<item row="2" column="1">
UI: Clean up Settings form markup This continues work from #5133 to correct UI file markup and save correctly in Qt Creator Defining alignment as an attribute in the <item> tag seems to be old behaviour that current versions of Qt Creator do not respect and will clobber these entries on save. The correct approach is to have alignment as a property element in the widget. As well, QWidgets that contain property definitions as well as a layout child item do not properly show up in the Qt Creator hierarchy. These properties are still invisibly applied but the QWidgets are not shown in Qt Creator and will get removed from the file after saving.
2021-08-16 22:41:57 -07:00
<widget class="QFrame" name="serviceWidget">
UI: Add support for "More Info" link from service (Jim) Allows the ability to get a link from the service's settings about a specific service selection the user chooses and display it as a "More Info" button that the user can click to find out more information about that particular service.
2020-10-12 21:20:12 -07:00
<layout class="QHBoxLayout" name="serviceWidgetLayout" stretch="0,0">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QComboBox" name="service">
<property name="maxVisibleItems">
<number>20</number>
</property>
</widget>
</item>
<item>
<widget class="UrlPushButton" name="moreInfoButton">
<property name="sizePolicy">
<sizepolicy hsizetype="Maximum" vsizetype="Fixed">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string>Basic.AutoConfig.StreamPage.MoreInfo</string>
</property>
</widget>
</item>
</layout>
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
</widget>
</item>
</layout>
</widget>
</item>
<item>
<widget class="QStackedWidget" name="streamStackWidget">
<property name="sizePolicy">
<sizepolicy hsizetype="Expanding" vsizetype="Expanding">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="currentIndex">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>0</number>
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
</property>
UI: Add auth. support to settings/autoconfig Adds the ability to connect/login to an account via the settings and auto-configuration dialogs. Checks registered Auth objects, and if the Auth object matches the currently selected service in the settings window or auto-configuration dialog, will display "connect account" buttons for the user to be able to click (which are optional, they can still use stream keys if they'd prefer).
2019-02-06 22:37:36 -08:00
<widget class="QWidget" name="loginPage">
<layout class="QFormLayout" name="loginPageLayout">
<item row="0" column="0">
<spacer name="horizontalSpacer_20">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeType">
<enum>QSizePolicy::Fixed</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
<height>19</height>
</size>
</property>
</spacer>
</item>
<item row="0" column="1">
<layout class="QHBoxLayout" name="horizontalLayout_16">
<item>
<widget class="QPushButton" name="connectAccount">
<property name="text">
<string>Basic.AutoConfig.StreamPage.ConnectAccount</string>
</property>
</widget>
</item>
<item>
<spacer name="horizontalSpacer_21">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>40</width>
<height>10</height>
</size>
</property>
</spacer>
</item>
</layout>
</item>
<item row="1" column="0">
<spacer name="horizontalSpacer_22">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeType">
<enum>QSizePolicy::Fixed</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
<height>19</height>
</size>
</property>
</spacer>
</item>
<item row="1" column="1">
<layout class="QHBoxLayout" name="horizontalLayout_17">
<item>
<widget class="QPushButton" name="useStreamKey">
<property name="text">
<string>Basic.AutoConfig.StreamPage.UseStreamKey</string>
</property>
</widget>
</item>
<item>
<spacer name="horizontalSpacer_23">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>40</width>
<height>20</height>
</size>
</property>
</spacer>
</item>
</layout>
</item>
</layout>
</widget>
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<widget class="QWidget" name="streamKeyPage">
<layout class="QFormLayout" name="streamkeyPageLayout">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<item row="0" column="0">
<widget class="QLabel" name="serverLabel">
<property name="text">
<string>Basic.AutoConfig.StreamPage.Server</string>
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
</property>
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
</widget>
</item>
<item row="0" column="1">
<widget class="QStackedWidget" name="serverStackedWidget">
UI: Don't stretch server field in Qt 5.14
2020-04-04 18:50:53 -07:00
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Maximum">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<property name="currentIndex">
UI: Upgrade stream link hotlink to a button Most of the top streaming services now have a link in the stream key label. Upgrading this button to a button clarifies the assistance for the important step of setting up a stream. Creates a new type of button for URL opening simply which also automatically updates the tootip to the current URL. Includes addition of Twitter/Periscope URL to make this feature more complete.
2019-10-24 21:05:43 -07:00
<number>1</number>
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
</property>
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<widget class="QWidget" name="servicePage">
<layout class="QHBoxLayout" name="horizontalLayout_21">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QComboBox" name="server"/>
</item>
</layout>
</widget>
<widget class="QWidget" name="customPage">
<layout class="QHBoxLayout" name="horizontalLayout_22">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QLineEdit" name="customServer"/>
</item>
</layout>
</widget>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="streamKeyLabel">
<property name="text">
<string>Basic.AutoConfig.StreamPage.StreamKey</string>
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
</property>
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<property name="openExternalLinks">
<bool>true</bool>
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
</property>
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<property name="buddy">
<cstring>key</cstring>
</property>
</widget>
</item>
<item row="1" column="1">
UI: Clean up Settings form markup This continues work from #5133 to correct UI file markup and save correctly in Qt Creator Defining alignment as an attribute in the <item> tag seems to be old behaviour that current versions of Qt Creator do not respect and will clobber these entries on save. The correct approach is to have alignment as a property element in the widget. As well, QWidgets that contain property definitions as well as a layout child item do not properly show up in the Qt Creator hierarchy. These properties are still invisibly applied but the QWidgets are not shown in Qt Creator and will get removed from the file after saving.
2021-08-16 22:41:57 -07:00
<widget class="QFrame" name="streamKeyWidget">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<layout class="QHBoxLayout" name="horizontalLayout_11">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QLineEdit" name="key">
<property name="inputMask">
<string notr="true"/>
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
</property>
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<property name="text">
<string notr="true"/>
</property>
<property name="echoMode">
<enum>QLineEdit::Password</enum>
</property>
</widget>
</item>
<item>
<widget class="QPushButton" name="show">
<property name="text">
<string>Show</string>
</property>
</widget>
</item>
UI: Upgrade stream link hotlink to a button Most of the top streaming services now have a link in the stream key label. Upgrading this button to a button clarifies the assistance for the important step of setting up a stream. Creates a new type of button for URL opening simply which also automatically updates the tootip to the current URL. Includes addition of Twitter/Periscope URL to make this feature more complete.
2019-10-24 21:05:43 -07:00
<item>
UI: Add setting for Twitch chat add-ons choice Both BTTV and FFZ are fairly popular however they do occasionally interfere. To give users the option to chose whichever one they like most we add a new setting that allows BTTV, FFZ, both, or neither. Defaults to "None" for new users. Existing users will be migrated to "Both" as that's the previous behavior.
2019-10-09 18:29:09 -07:00
<widget class="UrlPushButton" name="getStreamKeyButton">
<property name="toolTip">
<string/>
</property>
<property name="toolTipDuration">
<number>-4</number>
</property>
<property name="text">
<string>Basic.AutoConfig.StreamPage.GetStreamKey</string>
</property>
</widget>
</item>
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
</layout>
</widget>
</item>
UI: Upgrade stream link hotlink to a button Most of the top streaming services now have a link in the stream key label. Upgrading this button to a button clarifies the assistance for the important step of setting up a stream. Creates a new type of button for URL opening simply which also automatically updates the tootip to the current URL. Includes addition of Twitter/Periscope URL to make this feature more complete.
2019-10-24 21:05:43 -07:00
<item row="3" column="0">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<spacer name="horizontalSpacer_18">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
<height>8</height>
</size>
</property>
</spacer>
</item>
UI: Add YouTube integration
2021-06-27 15:30:00 -07:00
<item row="4" column="1">
<layout class="QHBoxLayout" name="horizontalLayout_23">
<property name="spacing">
<number>8</number>
</property>
<property name="leftMargin">
<number>7</number>
</property>
<property name="rightMargin">
<number>7</number>
</property>
UI: Add auth. support to settings/autoconfig Adds the ability to connect/login to an account via the settings and auto-configuration dialogs. Checks registered Auth objects, and if the Auth object matches the currently selected service in the settings window or auto-configuration dialog, will display "connect account" buttons for the user to be able to click (which are optional, they can still use stream keys if they'd prefer).
2019-02-06 22:37:36 -08:00
<item>
UI: Add YouTube integration
2021-06-27 15:30:00 -07:00
<widget class="QLabel" name="connectedAccountText">
<property name="styleSheet">
<string notr="true">font-weight: bold</string>
</property>
UI: Add auth. support to settings/autoconfig Adds the ability to connect/login to an account via the settings and auto-configuration dialogs. Checks registered Auth objects, and if the Auth object matches the currently selected service in the settings window or auto-configuration dialog, will display "connect account" buttons for the user to be able to click (which are optional, they can still use stream keys if they'd prefer).
2019-02-06 22:37:36 -08:00
<property name="text">
UI: Add YouTube integration
2021-06-27 15:30:00 -07:00
<string>Auth.LoadingChannel.Title</string>
UI: Add auth. support to settings/autoconfig Adds the ability to connect/login to an account via the settings and auto-configuration dialogs. Checks registered Auth objects, and if the Auth object matches the currently selected service in the settings window or auto-configuration dialog, will display "connect account" buttons for the user to be able to click (which are optional, they can still use stream keys if they'd prefer).
2019-02-06 22:37:36 -08:00
</property>
</widget>
</item>
<item>
<widget class="QPushButton" name="disconnectAccount">
<property name="text">
<string>Basic.AutoConfig.StreamPage.DisconnectAccount</string>
</property>
</widget>
</item>
<item>
<spacer name="horizontalSpacer_24">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>40</width>
<height>20</height>
</size>
</property>
</spacer>
</item>
</layout>
</item>
UI: Add YouTube integration
2021-06-27 15:30:00 -07:00
<item row="6" column="1">
UI: Upgrade stream link hotlink to a button Most of the top streaming services now have a link in the stream key label. Upgrading this button to a button clarifies the assistance for the important step of setting up a stream. Creates a new type of button for URL opening simply which also automatically updates the tootip to the current URL. Includes addition of Twitter/Periscope URL to make this feature more complete.
2019-10-24 21:05:43 -07:00
<widget class="QCheckBox" name="bandwidthTestEnable">
UI: Add back auth for custom RTMP servers This was a feature that was available when you chose custom RTMP server; it was not considered when making the new version. Note: it looks unslightly, but it works for now.
2019-02-14 23:09:43 -08:00
<property name="text">
UI: Upgrade stream link hotlink to a button Most of the top streaming services now have a link in the stream key label. Upgrading this button to a button clarifies the assistance for the important step of setting up a stream. Creates a new type of button for URL opening simply which also automatically updates the tootip to the current URL. Includes addition of Twitter/Periscope URL to make this feature more complete.
2019-10-24 21:05:43 -07:00
<string>Basic.Settings.Stream.BandwidthTestMode</string>
UI: Add back auth for custom RTMP servers This was a feature that was available when you chose custom RTMP server; it was not considered when making the new version. Note: it looks unslightly, but it works for now.
2019-02-14 23:09:43 -08:00
</property>
</widget>
</item>
UI: Add YouTube integration
2021-06-27 15:30:00 -07:00
<item row="7" column="1">
UI: Upgrade stream link hotlink to a button Most of the top streaming services now have a link in the stream key label. Upgrading this button to a button clarifies the assistance for the important step of setting up a stream. Creates a new type of button for URL opening simply which also automatically updates the tootip to the current URL. Includes addition of Twitter/Periscope URL to make this feature more complete.
2019-10-24 21:05:43 -07:00
<widget class="QCheckBox" name="useAuth">
<property name="text">
<string>Basic.Settings.Stream.Custom.UseAuthentication</string>
</property>
</widget>
UI: Add back auth for custom RTMP servers This was a feature that was available when you chose custom RTMP server; it was not considered when making the new version. Note: it looks unslightly, but it works for now.
2019-02-14 23:09:43 -08:00
</item>
UI: Add YouTube integration
2021-06-27 15:30:00 -07:00
<item row="9" column="0">
UI: Add back auth for custom RTMP servers This was a feature that was available when you chose custom RTMP server; it was not considered when making the new version. Note: it looks unslightly, but it works for now.
2019-02-14 23:09:43 -08:00
<widget class="QLabel" name="authUsernameLabel">
<property name="text">
<string>Basic.Settings.Stream.Custom.Username</string>
</property>
<property name="buddy">
<cstring>authUsername</cstring>
</property>
</widget>
</item>
UI: Add YouTube integration
2021-06-27 15:30:00 -07:00
<item row="9" column="1">
UI: Upgrade stream link hotlink to a button Most of the top streaming services now have a link in the stream key label. Upgrading this button to a button clarifies the assistance for the important step of setting up a stream. Creates a new type of button for URL opening simply which also automatically updates the tootip to the current URL. Includes addition of Twitter/Periscope URL to make this feature more complete.
2019-10-24 21:05:43 -07:00
<widget class="QLineEdit" name="authUsername"/>
</item>
UI: Add YouTube integration
2021-06-27 15:30:00 -07:00
<item row="10" column="0">
UI: Add back auth for custom RTMP servers This was a feature that was available when you chose custom RTMP server; it was not considered when making the new version. Note: it looks unslightly, but it works for now.
2019-02-14 23:09:43 -08:00
<widget class="QLabel" name="authPwLabel">
<property name="text">
<string>Basic.Settings.Stream.Custom.Password</string>
</property>
<property name="buddy">
<cstring>authPw</cstring>
</property>
</widget>
</item>
UI: Add YouTube integration
2021-06-27 15:30:00 -07:00
<item row="10" column="1">
UI: Clean up Settings form markup This continues work from #5133 to correct UI file markup and save correctly in Qt Creator Defining alignment as an attribute in the <item> tag seems to be old behaviour that current versions of Qt Creator do not respect and will clobber these entries on save. The correct approach is to have alignment as a property element in the widget. As well, QWidgets that contain property definitions as well as a layout child item do not properly show up in the Qt Creator hierarchy. These properties are still invisibly applied but the QWidgets are not shown in Qt Creator and will get removed from the file after saving.
2021-08-16 22:41:57 -07:00
<widget class="QFrame" name="authPwWidget">
UI: Add back auth for custom RTMP servers This was a feature that was available when you chose custom RTMP server; it was not considered when making the new version. Note: it looks unslightly, but it works for now.
2019-02-14 23:09:43 -08:00
<layout class="QHBoxLayout" name="horizontalLayout_25">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QLineEdit" name="authPw">
<property name="echoMode">
<enum>QLineEdit::Password</enum>
</property>
</widget>
</item>
<item>
<widget class="QPushButton" name="authPwShow">
<property name="text">
<string>Show</string>
</property>
</widget>
</item>
</layout>
</widget>
</item>
UI: Add YouTube integration
2021-06-27 15:30:00 -07:00
<item row="8" column="1">
UI: Add setting for Twitch chat add-ons choice Both BTTV and FFZ are fairly popular however they do occasionally interfere. To give users the option to chose whichever one they like most we add a new setting that allows BTTV, FFZ, both, or neither. Defaults to "None" for new users. Existing users will be migrated to "Both" as that's the previous behavior.
2019-10-09 18:29:09 -07:00
<widget class="QComboBox" name="twitchAddonDropdown"/>
</item>
UI: Add YouTube integration
2021-06-27 15:30:00 -07:00
<item row="8" column="0">
UI: Add setting for Twitch chat add-ons choice Both BTTV and FFZ are fairly popular however they do occasionally interfere. To give users the option to chose whichever one they like most we add a new setting that allows BTTV, FFZ, both, or neither. Defaults to "None" for new users. Existing users will be migrated to "Both" as that's the previous behavior.
2019-10-09 18:29:09 -07:00
<widget class="QLabel" name="twitchAddonLabel">
<property name="text">
<string>Basic.Settings.Stream.TTVAddon</string>
</property>
<property name="buddy">
<cstring>twitchAddonDropdown</cstring>
</property>
</widget>
</item>
UI: Add YouTube integration
2021-06-27 15:30:00 -07:00
<item row="11" column="1">
UI: Move "enforce" setting to "ignore" stream section Moves the "Enforce streaming service bitrate" option from simple output mode to the stream section, renames it to "Ignore streaming service setting recommendations" (inverting it). When trying to check it, it will now also display a message box warning the user that it's generally a not-so-good idea. Also displays recommended settings for the service.
2020-11-11 09:48:39 -08:00
<widget class="QCheckBox" name="ignoreRecommended">
<property name="text">
<string>Basic.Settings.Stream.IgnoreRecommended</string>
</property>
</widget>
</item>
UI: Add YouTube integration
2021-06-27 15:30:00 -07:00
<item row="12" column="1">
UI: Move "enforce" setting to "ignore" stream section Moves the "Enforce streaming service bitrate" option from simple output mode to the stream section, renames it to "Ignore streaming service setting recommendations" (inverting it). When trying to check it, it will now also display a message box warning the user that it's generally a not-so-good idea. Also displays recommended settings for the service.
2020-11-11 09:48:39 -08:00
<widget class="QLabel" name="enforceSettingsLabel">
<property name="text">
<string notr="true"/>
</property>
UI: Add required links when using YouTube These links are required by Google to be shown on any API client when using Google/YouTube API.
2021-08-20 06:24:00 -07:00
<property name="textFormat">
<enum>Qt::RichText</enum>
</property>
<property name="openExternalLinks">
<bool>true</bool>
</property>
UI: Move "enforce" setting to "ignore" stream section Moves the "Enforce streaming service bitrate" option from simple output mode to the stream section, renames it to "Ignore streaming service setting recommendations" (inverting it). When trying to check it, it will now also display a message box warning the user that it's generally a not-so-good idea. Also displays recommended settings for the service.
2020-11-11 09:48:39 -08:00
</widget>
</item>
UI: Add YouTube integration
2021-06-27 15:30:00 -07:00
<item row="5" column="1">
<layout class="QHBoxLayout" name="horizontalLayout_28">
<item>
<widget class="QPushButton" name="useStreamKeyAdv">
<property name="text">
<string>Basic.AutoConfig.StreamPage.UseStreamKeyAdvanced</string>
</property>
</widget>
</item>
<item>
<spacer name="horizontalSpacer_28">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>40</width>
<height>20</height>
</size>
</property>
</spacer>
</item>
</layout>
</item>
<item row="4" column="0">
<widget class="QLabel" name="connectedAccountLabel">
<property name="text">
<string>Basic.AutoConfig.StreamPage.ConnectedAccount</string>
</property>
</widget>
</item>
<item row="3" column="1">
<layout class="QHBoxLayout" name="horizontalLayout_15">
<item>
<widget class="QPushButton" name="connectAccount2">
<property name="cursor">
UI: Fixup minor Qt Creator inconsistencies Qt Creator automatically adjusts these files when opened. Rather than contributors having to manually undo these changes, just apply them directly into the repository.
2022-03-19 16:32:07 -07:00
<cursorShape>PointingHandCursor</cursorShape>
UI: Add YouTube integration
2021-06-27 15:30:00 -07:00
</property>
<property name="text">
<string>Basic.AutoConfig.StreamPage.ConnectAccount</string>
</property>
</widget>
</item>
<item>
<spacer name="horizontalSpacer_19">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>40</width>
<height>20</height>
</size>
</property>
</spacer>
</item>
</layout>
</item>
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
</layout>
</widget>
Add preliminary streaming code for testing - Add some temporary streaming code using FFmpeg. FFmpeg itself is not very ideal for streaming; lack of direct control of the sockets and no framedrop handling means that FFmpeg is definitely not something you want to use without wrapper code. I'd prefer writing my own network framework in this particular case just because you give away so much control of the network interface. Wasted an entire day trying to go through FFmpeg issues. There's just no way FFmpeg should be used for real streaming (at least without being patched or submitting some sort of patch, but I'm sort of feeling "meh" on that idea) I had to end up writing multiple threads just to handle both connecting and writing, because av_interleaved_write_frame blocks every call, stalling the main encoder thread, and thus also stalling draw signals. - Add some temporary user interface for streaming settings. This is just temporary for the time being. It's in the outputs section of the basic-mode settings - Make it so that dynamic arrays do not free all their data when the size just happens to be reduced to 0. This prevents constant reallocation when an array keeps going from 1 item to 0 items. Also, it was bad to become dependent upon that functionality. You must now always explicitly call "free" on it to ensure the data is free, and that's how it should be. Implicit functionality can lead to confusion and maintainability issues.
2014-03-10 13:10:35 -07:00
</widget>
</item>
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
</layout>
</widget>
<widget class="QWidget" name="outputPage">
<layout class="QVBoxLayout" name="verticalLayout_2">
<property name="leftMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
UI: Fix settings window minimum width/height This fixes the issue presented in: https://obsproject.com/mantis/view.php?id=885 Minimum size is changed to 700x512. I arrived at this number from testing the minimum sizes that I felt the settings UI was still perfectly usable and readable. Any smaller, and things became difficult to see and adjust. As a note, this does increase the minum width of the settings window, as the previous minimum allowed you to cut off objects and render the window too small to be usable.
2017-07-27 19:02:39 -07:00
<item>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<widget class="QFrame" name="frame">
<layout class="QVBoxLayout" name="verticalLayout_6">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item>
<widget class="QFrame" name="widget">
<property name="sizePolicy">
<sizepolicy hsizetype="Expanding" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<layout class="QFormLayout" name="formLayout_5">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
UI: Add recording presets to simple output 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.
2015-09-18 22:29:36 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="leftMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>0</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="topMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>0</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="bottomMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>0</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<item row="0" column="0">
<widget class="QLabel" name="outputModeLabel">
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
<property name="text">
<string>Basic.Settings.Output.Mode</string>
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="buddy">
<cstring>outputMode</cstring>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QComboBox" name="outputMode">
<property name="enabled">
<bool>true</bool>
</property>
<property name="sizePolicy">
<sizepolicy hsizetype="Expanding" vsizetype="Fixed">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="currentIndex">
<number>0</number>
</property>
<item>
<property name="text">
<string>Basic.Settings.Output.Mode.Simple</string>
UI: Add recording presets to simple output 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.
2015-09-18 22:29:36 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</item>
<item>
UI: Add recording presets to simple output 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.
2015-09-18 22:29:36 -07:00
<property name="text">
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<string>Basic.Settings.Output.Mode.Adv</string>
UI: Add recording presets to simple output 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.
2015-09-18 22:29:36 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</item>
</widget>
</item>
</layout>
</widget>
</item>
<item>
<widget class="QStackedWidget" name="outputModePages">
<property name="currentIndex">
<number>0</number>
</property>
<widget class="QWidget" name="easyOutputsPage">
<layout class="QVBoxLayout" name="verticalLayout_3">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>0</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QScrollArea" name="simpleOutScroll">
<property name="frameShape">
<enum>QFrame::NoFrame</enum>
UI: Add recording presets to simple output 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.
2015-09-18 22:29:36 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="frameShadow">
<enum>QFrame::Plain</enum>
UI: Add label/control buddy pairs for main windows
2016-02-21 11:19:26 -08:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="widgetResizable">
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<bool>true</bool>
UI: Add recording presets to simple output 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.
2015-09-18 22:29:36 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<widget class="QWidget" name="scrollAreaWidgetContents_3">
<property name="geometry">
<rect>
<x>0</x>
<y>0</y>
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<width>772</width>
<height>651</height>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</rect>
UI: Add recording presets to simple output 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.
2015-09-18 22:29:36 -07:00
</property>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<property name="sizePolicy">
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<layout class="QVBoxLayout" name="verticalLayout_52">
<property name="leftMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>0</number>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="topMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>0</number>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="bottomMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>0</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<item>
<widget class="QGroupBox" name="simpleStreamingGroupBox">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Maximum">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="title">
<string>Basic.Settings.Output.Adv.Streaming</string>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<layout class="QFormLayout" name="simpleStreamingLayout">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="leftMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="topMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>2</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="bottomMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item row="0" column="0">
<widget class="QLabel" name="label_19">
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
<property name="text">
<string>Basic.Settings.Output.VideoBitrate</string>
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="buddy">
<cstring>simpleOutputVBitrate</cstring>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QSpinBox" name="simpleOutputVBitrate">
<property name="minimum">
<number>200</number>
</property>
<property name="maximum">
<number>1000000</number>
</property>
<property name="value">
<number>2000</number>
</property>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="label_20">
<property name="text">
<string>Basic.Settings.Output.AudioBitrate</string>
</property>
<property name="buddy">
<cstring>simpleOutputABitrate</cstring>
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QComboBox" name="simpleOutputABitrate">
<property name="currentIndex">
<number>8</number>
</property>
<item>
<property name="text">
<string>32</string>
</property>
</item>
<item>
<property name="text">
<string>48</string>
</property>
</item>
<item>
<property name="text">
<string>64</string>
</property>
</item>
<item>
<property name="text">
<string>80</string>
</property>
</item>
<item>
<property name="text">
<string>96</string>
</property>
</item>
<item>
<property name="text">
<string>112</string>
</property>
</item>
<item>
<property name="text">
<string>128</string>
</property>
</item>
<item>
<property name="text">
<string>160</string>
</property>
</item>
<item>
<property name="text">
<string>192</string>
</property>
</item>
<item>
<property name="text">
<string>256</string>
</property>
</item>
<item>
<property name="text">
<string>320</string>
</property>
</item>
</widget>
</item>
<item row="2" column="0">
<widget class="QLabel" name="simpleOutStrEncoderLabel">
<property name="text">
<string>Basic.Settings.Output.Encoder</string>
</property>
<property name="buddy">
<cstring>simpleOutRecEncoder</cstring>
</property>
</widget>
</item>
<item row="2" column="1">
<widget class="QComboBox" name="simpleOutStrEncoder"/>
</item>
<item row="3" column="0">
<widget class="QLabel" name="simpleOutPresetLabel">
<property name="enabled">
<bool>true</bool>
</property>
<property name="text">
<string>Basic.Settings.Output.EncoderPreset</string>
</property>
<property name="buddy">
<cstring>simpleOutPreset</cstring>
</property>
</widget>
</item>
<item row="3" column="1">
<widget class="QComboBox" name="simpleOutPreset"/>
</item>
<item row="4" column="1">
<widget class="QCheckBox" name="simpleOutAdvanced">
<property name="text">
<string>Basic.Settings.Output.Advanced</string>
</property>
<property name="checked">
<bool>true</bool>
</property>
</widget>
</item>
<item row="5" column="0">
<widget class="QLabel" name="label_23">
<property name="text">
<string>Basic.Settings.Output.CustomEncoderSettings</string>
</property>
<property name="buddy">
<cstring>simpleOutCustom</cstring>
</property>
</widget>
</item>
<item row="5" column="1">
<widget class="QLineEdit" name="simpleOutCustom"/>
</item>
</layout>
</widget>
</item>
<item>
<widget class="QGroupBox" name="simpleRecordingGroupBox">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Maximum">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="title">
<string>Basic.Settings.Output.Adv.Recording</string>
</property>
<layout class="QFormLayout" name="formLayout_6">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="leftMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="topMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>2</number>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="bottomMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<item row="0" column="0">
<widget class="QLabel" name="label_18">
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
<property name="text">
<string>Basic.Settings.Output.Simple.SavePath</string>
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="buddy">
<cstring>simpleOutputPath</cstring>
</property>
</widget>
</item>
<item row="0" column="1">
<layout class="QHBoxLayout" name="horizontalLayout_5">
<item>
<widget class="QLineEdit" name="simpleOutputPath">
<property name="enabled">
<bool>true</bool>
</property>
</widget>
</item>
<item>
<widget class="QPushButton" name="simpleOutputBrowse">
<property name="enabled">
<bool>true</bool>
</property>
<property name="text">
<string>Browse</string>
</property>
</widget>
</item>
</layout>
</item>
<item row="1" column="1">
<widget class="QCheckBox" name="simpleNoSpace">
<property name="text">
<string>Basic.Settings.Output.NoSpaceFileName</string>
</property>
<property name="checked">
<bool>true</bool>
</property>
</widget>
</item>
<item row="2" column="0">
<widget class="QLabel" name="label_26">
<property name="text">
<string>Basic.Settings.Output.Simple.RecordingQuality</string>
</property>
<property name="buddy">
<cstring>simpleOutRecQuality</cstring>
</property>
</widget>
</item>
<item row="2" column="1">
<widget class="QComboBox" name="simpleOutRecQuality"/>
</item>
<item row="3" column="0">
<widget class="QLabel" name="simpleOutRecFormatLabel">
<property name="text">
<string>Basic.Settings.Output.Format</string>
</property>
<property name="buddy">
<cstring>simpleOutRecFormat</cstring>
</property>
</widget>
</item>
<item row="3" column="1">
<widget class="QComboBox" name="simpleOutRecFormat">
<item>
<property name="text">
<string notr="true">flv</string>
</property>
</item>
<item>
<property name="text">
<string notr="true">mp4</string>
</property>
</item>
<item>
<property name="text">
<string notr="true">mov</string>
</property>
</item>
<item>
<property name="text">
<string notr="true">mkv</string>
</property>
</item>
<item>
<property name="text">
<string notr="true">ts</string>
</property>
</item>
<item>
<property name="text">
<string notr="true">m3u8</string>
</property>
</item>
</widget>
</item>
<item row="4" column="0">
<widget class="QLabel" name="simpleOutRecEncoderLabel">
<property name="text">
<string>Basic.Settings.Output.Encoder</string>
</property>
<property name="buddy">
<cstring>simpleOutRecEncoder</cstring>
</property>
</widget>
</item>
<item row="4" column="1">
<widget class="QComboBox" name="simpleOutRecEncoder"/>
</item>
<item row="5" column="0">
<widget class="QLabel" name="label_420">
<property name="text">
<string>Basic.Settings.Output.CustomMuxerSettings</string>
</property>
<property name="buddy">
<cstring>simpleOutMuxCustom</cstring>
</property>
</widget>
</item>
<item row="5" column="1">
<widget class="QLineEdit" name="simpleOutMuxCustom"/>
</item>
<item row="6" column="1">
<widget class="QCheckBox" name="simpleReplayBuf">
<property name="text">
<string>Basic.Settings.Output.UseReplayBuffer</string>
</property>
<property name="checked">
<bool>true</bool>
</property>
</widget>
</item>
</layout>
UI: Move Simple Mode audio bitrate above encoder
2022-06-25 10:16:14 -07:00
</widget>
</item>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item>
<widget class="QGroupBox" name="replayBufferGroupBox">
<property name="title">
<string>ReplayBuffer</string>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<layout class="QFormLayout" name="formLayout_24">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="leftMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="topMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>2</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="bottomMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<item row="0" column="0">
<widget class="QLabel" name="label_35">
<property name="text">
<string>Basic.Settings.Output.ReplayBuffer.SecondsMax</string>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QSpinBox" name="simpleRBSecMax">
<property name="suffix">
<string notr="true"> sec</string>
</property>
<property name="minimum">
<number>5</number>
</property>
<property name="maximum">
<number>21600</number>
</property>
<property name="value">
<number>15</number>
</property>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="simpleRBMegsMaxLabel">
<property name="text">
<string>Basic.Settings.Output.ReplayBuffer.MegabytesMax</string>
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QSpinBox" name="simpleRBMegsMax">
<property name="suffix">
<string notr="true"> MB</string>
</property>
<property name="minimum">
<number>20</number>
</property>
<property name="maximum">
<number>8192</number>
</property>
<property name="value">
<number>512</number>
</property>
</widget>
</item>
<item row="2" column="1">
<widget class="QLabel" name="simpleRBEstimate">
<property name="text">
<string notr="true"/>
</property>
</widget>
</item>
</layout>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</widget>
</item>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item>
<layout class="QVBoxLayout" name="simpleOutInfoLayout">
<property name="leftMargin">
<number>10</number>
UI: Move Simple Mode encoder preset out of Advanced
2022-06-25 10:24:04 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="topMargin">
<number>10</number>
UI: Move Simple Mode encoder preset out of Advanced
2022-06-25 10:24:04 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
<number>10</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="bottomMargin">
<number>10</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</layout>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</item>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item>
<widget class="QFrame" name="simpleOutputContainer">
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<property name="minimumSize">
<size>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<width>0</width>
<height>20</height>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</size>
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<layout class="QVBoxLayout" name="verticalLayout_4">
<property name="leftMargin">
<number>0</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="topMargin">
<number>0</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
<number>0</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="bottomMargin">
<number>0</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</layout>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</widget>
</item>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item>
<spacer name="verticalSpacer_2">
<property name="orientation">
<enum>Qt::Vertical</enum>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="sizeHint" stdset="0">
<size>
<width>20</width>
<height>10</height>
</size>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</spacer>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</item>
</layout>
</widget>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</widget>
</item>
</layout>
</widget>
<widget class="QWidget" name="advOutputsPage">
<layout class="QVBoxLayout" name="verticalLayout_8">
<property name="spacing">
<number>6</number>
</property>
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QTabWidget" name="advOutTabs">
<property name="currentIndex">
<number>0</number>
</property>
<property name="usesScrollButtons">
<bool>true</bool>
</property>
<widget class="QWidget" name="advOutputStreamTab">
<attribute name="title">
<string>Basic.Settings.Output.Adv.Streaming</string>
</attribute>
<layout class="QVBoxLayout" name="verticalLayout_12">
<property name="leftMargin">
<number>0</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="topMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>6</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>0</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QScrollArea" name="scrollArea_3">
<property name="frameShape">
<enum>QFrame::NoFrame</enum>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="frameShadow">
<enum>QFrame::Plain</enum>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="widgetResizable">
<bool>true</bool>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<widget class="QWidget" name="scrollAreaWidgetContents_5">
<property name="geometry">
<rect>
<x>0</x>
<y>0</y>
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<width>759</width>
<height>616</height>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</rect>
</property>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<layout class="QVBoxLayout" name="verticalLayout_14">
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<widget class="QGroupBox" name="advOutTopContainer">
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
<property name="sizePolicy">
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<sizepolicy hsizetype="Preferred" vsizetype="Fixed">
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="title">
<string>Basic.Settings.Output.Adv.Streaming.Settings</string>
</property>
UI: Add VOD track support in advanced output Adds a VOD track option (specific to Twitch) that allows a user to specify which audio track to use for their Twitch VODs, which uses a separate encoder to encode the track. This allows users the ability to choose what audio goes on their VOD, separately from the live stream.
2020-11-01 01:54:27 -08:00
<layout class="QFormLayout" name="advOutTopLayout">
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="leftMargin">
<number>8</number>
</property>
<property name="topMargin">
<number>2</number>
</property>
<property name="rightMargin">
<number>8</number>
</property>
<property name="bottomMargin">
<number>8</number>
</property>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<item row="1" column="0">
<widget class="QLabel" name="label_28">
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
<property name="text">
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<string>Basic.Settings.Output.Adv.AudioTrack</string>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
</widget>
</item>
UI: Allow file name generation without spaces This will probably go away once proper file name formatting is implemented (https://obsproject.com/mantis/view.php?id=361)
2015-11-27 03:14:18 -08:00
<item row="1" column="1">
UI: Clean up Settings form markup This continues work from #5133 to correct UI file markup and save correctly in Qt Creator Defining alignment as an attribute in the <item> tag seems to be old behaviour that current versions of Qt Creator do not respect and will clobber these entries on save. The correct approach is to have alignment as a property element in the widget. As well, QWidgets that contain property definitions as well as a layout child item do not properly show up in the Qt Creator hierarchy. These properties are still invisibly applied but the QWidgets are not shown in Qt Creator and will get removed from the file after saving.
2021-08-16 22:41:57 -07:00
<widget class="QFrame" name="widget_8">
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<property name="sizePolicy">
<sizepolicy hsizetype="Maximum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
UI: Add label/control buddy pairs for main windows
2016-02-21 11:19:26 -08:00
</property>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<layout class="QHBoxLayout" name="horizontalLayout_7">
<property name="leftMargin">
<number>0</number>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</property>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<property name="topMargin">
<number>0</number>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</property>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<property name="rightMargin">
<number>0</number>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<widget class="QRadioButton" name="advOutTrack1">
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
<property name="text">
<string notr="true">1</string>
</property>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<property name="checked">
<bool>true</bool>
</property>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</widget>
</item>
<item>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<widget class="QRadioButton" name="advOutTrack2">
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
<property name="text">
<string notr="true">2</string>
</property>
</widget>
</item>
<item>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<widget class="QRadioButton" name="advOutTrack3">
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
<property name="text">
<string notr="true">3</string>
</property>
</widget>
</item>
<item>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<widget class="QRadioButton" name="advOutTrack4">
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
<property name="text">
<string notr="true">4</string>
</property>
</widget>
</item>
UI: Increase maximum audio tracks to 6
2016-12-21 17:14:24 -08:00
<item>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<widget class="QRadioButton" name="advOutTrack5">
UI: Increase maximum audio tracks to 6
2016-12-21 17:14:24 -08:00
<property name="text">
<string notr="true">5</string>
</property>
</widget>
</item>
<item>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<widget class="QRadioButton" name="advOutTrack6">
UI: Increase maximum audio tracks to 6
2016-12-21 17:14:24 -08:00
<property name="text">
<string notr="true">6</string>
</property>
</widget>
</item>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</layout>
</widget>
</item>
UI: Remove redundant setting This setting, although technically different from the one in the streaming section of settings, is superseded by that setting. The setting can still be used via ini file if an actual custom rate control or keyframe interval is needed.
2020-12-02 01:09:37 -08:00
<item row="2" column="0">
<widget class="QLabel" name="advOutEncLabel">
<property name="text">
<string>Basic.Settings.Output.Encoder</string>
</property>
</widget>
</item>
<item row="2" column="1">
<widget class="QComboBox" name="advOutEncoder"/>
</item>
<item row="3" column="0">
<widget class="QCheckBox" name="advOutUseRescale">
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Expanding">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="layoutDirection">
<enum>Qt::RightToLeft</enum>
</property>
<property name="text">
<string>Basic.Settings.Output.Adv.Rescale</string>
</property>
</widget>
</item>
<item row="3" column="1">
<widget class="QComboBox" name="advOutRescale">
<property name="enabled">
<bool>false</bool>
</property>
<property name="editable">
<bool>true</bool>
</property>
</widget>
</item>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</layout>
</widget>
</item>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item>
<widget class="QGroupBox" name="advOutEncoderProps">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Fixed">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="title">
<string>Basic.Settings.Output.Adv.Encoder</string>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<layout class="QVBoxLayout" name="advOutEncoderLayout">
<property name="leftMargin">
<number>8</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="topMargin">
<number>2</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
<number>8</number>
</property>
<property name="bottomMargin">
<number>8</number>
</property>
</layout>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</widget>
</item>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item>
<spacer name="verticalSpacer_0">
<property name="orientation">
<enum>Qt::Vertical</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>20</width>
<height>40</height>
</size>
</property>
</spacer>
</item>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</layout>
</widget>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</widget>
</item>
</layout>
</widget>
<widget class="QWidget" name="advOutputRecordTab">
<attribute name="title">
<string>Basic.Settings.Output.Adv.Recording</string>
</attribute>
<layout class="QVBoxLayout" name="verticalLayout_11">
<property name="spacing">
<number>0</number>
</property>
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QFrame" name="advOutRecTypeContainer">
<layout class="QFormLayout" name="formLayout_9">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
UI: Allow generated filenames for FFmpeg output This changes the way the advanced output section's FFmpeg output settings work by allowing the user to select whether they want to output to a file or output to a URL, and makes it so file names are automatically generated like other recording outputs. If they choose to output to a file, it'll only require an output directory similarly to how other recording outputs work. They can select a directory to output to rather than being required to type in a full path and filename; the filename is automatically generated. The extension is also automatically retrieved from libff depending on the format selected. Otherwise if they have Output to URL selected, it'll show a simple edit box where they can type in the target URL.
2015-08-18 20:58:24 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="leftMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="topMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>6</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>0</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="bottomMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>6</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<item row="0" column="0">
<widget class="QLabel" name="label_31">
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="text">
<string>Basic.Settings.Output.Adv.Recording.Type</string>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
UI: Allow generated filenames for FFmpeg output This changes the way the advanced output section's FFmpeg output settings work by allowing the user to select whether they want to output to a file or output to a URL, and makes it so file names are automatically generated like other recording outputs. If they choose to output to a file, it'll only require an output directory similarly to how other recording outputs work. They can select a directory to output to rather than being required to type in a full path and filename; the filename is automatically generated. The extension is also automatically retrieved from libff depending on the format selected. Otherwise if they have Output to URL selected, it'll show a simple edit box where they can type in the target URL.
2015-08-18 20:58:24 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="buddy">
<cstring>advOutRecType</cstring>
UI: Allow generated filenames for FFmpeg output This changes the way the advanced output section's FFmpeg output settings work by allowing the user to select whether they want to output to a file or output to a URL, and makes it so file names are automatically generated like other recording outputs. If they choose to output to a file, it'll only require an output directory similarly to how other recording outputs work. They can select a directory to output to rather than being required to type in a full path and filename; the filename is automatically generated. The extension is also automatically retrieved from libff depending on the format selected. Otherwise if they have Output to URL selected, it'll show a simple edit box where they can type in the target URL.
2015-08-18 20:58:24 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</widget>
</item>
<item row="0" column="1">
<widget class="QComboBox" name="advOutRecType">
<item>
<property name="text">
<string>Basic.Settings.Output.Adv.Recording.Type.Standard</string>
</property>
</item>
UI: Add option to auto remux
2017-05-08 04:53:35 -07:00
<item>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="text">
<string>Basic.Settings.Output.Adv.Recording.Type.FFmpegOutput</string>
</property>
</item>
</widget>
</item>
</layout>
</widget>
</item>
<item>
<widget class="QStackedWidget" name="stackedWidget">
<property name="currentIndex">
<number>0</number>
</property>
<widget class="QWidget" name="advOutRecStandard">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Expanding">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<layout class="QVBoxLayout" name="verticalLayout_13" stretch="0">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>0</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QScrollArea" name="scrollArea_4">
<property name="sizePolicy">
<sizepolicy hsizetype="Expanding" vsizetype="Expanding">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="frameShape">
<enum>QFrame::NoFrame</enum>
</property>
<property name="frameShadow">
<enum>QFrame::Plain</enum>
</property>
<property name="lineWidth">
<number>0</number>
</property>
<property name="widgetResizable">
<bool>true</bool>
</property>
<property name="alignment">
<set>Qt::AlignLeading|Qt::AlignLeft|Qt::AlignTop</set>
</property>
<widget class="QWidget" name="scrollAreaWidgetContents_4">
<property name="geometry">
<rect>
<x>0</x>
<y>0</y>
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<width>759</width>
<height>587</height>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</rect>
</property>
UI: Add option to auto remux
2017-05-08 04:53:35 -07:00
<property name="sizePolicy">
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
UI: Add option to auto remux
2017-05-08 04:53:35 -07:00
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<layout class="QVBoxLayout" name="verticalLayout_21">
<property name="leftMargin">
<number>0</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Add option to auto remux
2017-05-08 04:53:35 -07:00
<property name="topMargin">
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<number>0</number>
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QGroupBox" name="advOutRecTopContainer">
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<property name="sizePolicy">
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<sizepolicy hsizetype="Preferred" vsizetype="Fixed">
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="title">
<string>Basic.Settings.Output.Adv.Recording.Settings</string>
UI: Add option to auto remux
2017-05-08 04:53:35 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<layout class="QFormLayout" name="formLayout_16">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
UI: Add option to auto remux
2017-05-08 04:53:35 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
UI: Add option to auto remux
2017-05-08 04:53:35 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="formAlignment">
<set>Qt::AlignLeading|Qt::AlignLeft|Qt::AlignTop</set>
UI: Add option to auto remux
2017-05-08 04:53:35 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="leftMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Add option to auto remux
2017-05-08 04:53:35 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="topMargin">
<number>2</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Add option to auto remux
2017-05-08 04:53:35 -07:00
</property>
<property name="bottomMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Add option to auto remux
2017-05-08 04:53:35 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item row="0" column="0">
<widget class="QLabel" name="label_32">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
<property name="text">
<string>Basic.Settings.Output.Simple.SavePath</string>
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
</widget>
</item>
<item row="0" column="1">
<layout class="QHBoxLayout" name="horizontalLayout_6">
<item>
<widget class="QLineEdit" name="advOutRecPath">
<property name="enabled">
<bool>true</bool>
</property>
<property name="sizePolicy">
<sizepolicy hsizetype="Expanding" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
</widget>
</item>
<item>
<widget class="QPushButton" name="advOutRecPathBrowse">
<property name="enabled">
<bool>true</bool>
</property>
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string>Browse</string>
</property>
</widget>
</item>
</layout>
</item>
<item row="1" column="0">
<spacer name="horizontalSpacer_27">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>40</width>
<height>20</height>
</size>
</property>
</spacer>
</item>
<item row="1" column="1">
<widget class="QCheckBox" name="advOutNoSpace">
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string>Basic.Settings.Output.NoSpaceFileName</string>
</property>
<property name="checked">
UI: Add option to auto remux
2017-05-08 04:53:35 -07:00
<bool>true</bool>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
</widget>
</item>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item row="2" column="0">
<widget class="QLabel" name="label_43">
<property name="text">
<string>Basic.Settings.Output.Format</string>
</property>
</widget>
</item>
<item row="2" column="1">
<widget class="QComboBox" name="advOutRecFormat">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<item>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
<property name="text">
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<string notr="true">flv</string>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</item>
<item>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
<property name="text">
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<string notr="true">mp4</string>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</item>
<item>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
<property name="text">
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<string notr="true">mov</string>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</item>
<item>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
<property name="text">
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<string notr="true">mkv</string>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</item>
<item>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
<property name="text">
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<string notr="true">ts</string>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</item>
<item>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
<property name="text">
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<string notr="true">m3u8</string>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</item>
</widget>
</item>
<item row="3" column="0">
<widget class="QLabel" name="label_29">
<property name="text">
<string>Basic.Settings.Output.Adv.AudioTrack</string>
</property>
</widget>
</item>
<item row="3" column="1">
<widget class="QStackedWidget" name="advRecTrackWidget">
<property name="sizePolicy">
<sizepolicy hsizetype="Maximum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="currentIndex">
<number>0</number>
</property>
<widget class="QWidget" name="recTracks">
<layout class="QHBoxLayout" name="horizontalLayout_9">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QCheckBox" name="advOutRecTrack1">
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string notr="true">1</string>
</property>
</widget>
</item>
<item>
<widget class="QCheckBox" name="advOutRecTrack2">
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string notr="true">2</string>
</property>
</widget>
</item>
<item>
<widget class="QCheckBox" name="advOutRecTrack3">
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string notr="true">3</string>
</property>
</widget>
</item>
<item>
<widget class="QCheckBox" name="advOutRecTrack4">
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string notr="true">4</string>
</property>
</widget>
</item>
<item>
<widget class="QCheckBox" name="advOutRecTrack5">
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string notr="true">5</string>
</property>
</widget>
</item>
<item>
<widget class="QCheckBox" name="advOutRecTrack6">
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string notr="true">6</string>
</property>
</widget>
</item>
</layout>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
</widget>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<widget class="QWidget" name="flvTracks">
<layout class="QHBoxLayout" name="horizontalLayout_8">
<property name="leftMargin">
<number>0</number>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="topMargin">
<number>0</number>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
<number>0</number>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="bottomMargin">
<number>0</number>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item>
<widget class="QRadioButton" name="flvTrack1">
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string>1</string>
</property>
</widget>
</item>
<item>
<widget class="QRadioButton" name="flvTrack2">
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string>2</string>
</property>
</widget>
</item>
<item>
<widget class="QRadioButton" name="flvTrack3">
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string>3</string>
</property>
</widget>
</item>
<item>
<widget class="QRadioButton" name="flvTrack4">
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string>4</string>
</property>
</widget>
</item>
<item>
<widget class="QRadioButton" name="flvTrack5">
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string>5</string>
</property>
</widget>
</item>
<item>
<widget class="QRadioButton" name="flvTrack6">
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string>6</string>
</property>
</widget>
</item>
</layout>
</widget>
</widget>
</item>
<item row="4" column="0">
<widget class="QLabel" name="advOutRecEncLabel">
<property name="text">
<string>Basic.Settings.Output.Encoder</string>
</property>
</widget>
</item>
<item row="4" column="1">
<widget class="QComboBox" name="advOutRecEncoder">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
</widget>
</item>
<item row="5" column="0">
<widget class="QCheckBox" name="advOutRecUseRescale">
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="layoutDirection">
<enum>Qt::RightToLeft</enum>
</property>
<property name="text">
<string>Basic.Settings.Output.Adv.Rescale</string>
</property>
</widget>
</item>
<item row="5" column="1">
<widget class="QFrame" name="advOutRecRescaleContainer">
<layout class="QHBoxLayout" name="horizontalLayout_4">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QComboBox" name="advOutRecRescale">
<property name="enabled">
<bool>false</bool>
</property>
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="editable">
<bool>true</bool>
</property>
</widget>
</item>
</layout>
</widget>
</item>
<item row="6" column="0">
<widget class="QLabel" name="label_9001">
<property name="text">
<string>Basic.Settings.Output.CustomMuxerSettings</string>
</property>
</widget>
</item>
<item row="6" column="1">
<widget class="QLineEdit" name="advOutMuxCustom">
<property name="sizePolicy">
<sizepolicy hsizetype="Expanding" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
</widget>
</item>
<item row="7" column="0">
<widget class="QCheckBox" name="advOutSplitFile">
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Expanding">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="layoutDirection">
<enum>Qt::RightToLeft</enum>
</property>
<property name="text">
<string>Basic.Settings.Output.EnableSplitFile</string>
</property>
</widget>
</item>
<item row="7" column="1">
<widget class="QComboBox" name="advOutSplitFileType">
<property name="enabled">
<bool>false</bool>
</property>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
<item>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="text">
<string>Basic.Settings.Output.SplitFile.TypeTime</string>
</property>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
</item>
<item>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="text">
<string>Basic.Settings.Output.SplitFile.TypeSize</string>
</property>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
</item>
UI: Add file splitting option "Only split manually"
2022-07-21 05:48:26 -07:00
<item>
<property name="text">
<string>Basic.Settings.Output.SplitFile.TypeManual</string>
</property>
</item>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</widget>
</item>
<item row="8" column="0">
<widget class="QLabel" name="advOutSplitFileTimeLabel">
<property name="text">
<string>Basic.Settings.Output.SplitFile.Time</string>
</property>
</widget>
</item>
<item row="8" column="1">
<widget class="QSpinBox" name="advOutSplitFileTime">
<property name="suffix">
<string> min</string>
</property>
<property name="minimum">
<number>1</number>
</property>
<property name="maximum">
UI: Increase maximum limit of automatic file splitting
2022-08-03 03:37:11 -07:00
<number>525600</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="value">
<number>15</number>
</property>
</widget>
</item>
<item row="9" column="0">
<widget class="QLabel" name="advOutSplitFileSizeLabel">
<property name="text">
<string>Basic.Settings.Output.SplitFile.Size</string>
</property>
</widget>
</item>
<item row="9" column="1">
<widget class="QSpinBox" name="advOutSplitFileSize">
<property name="suffix">
<string> MB</string>
</property>
<property name="minimum">
<number>20</number>
</property>
<property name="maximum">
UI: Increase maximum limit of automatic file splitting
2022-08-03 03:37:11 -07:00
<number>1073741824</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="value">
<number>2048</number>
</property>
</widget>
</item>
</layout>
</widget>
</item>
<item>
<widget class="QGroupBox" name="advOutRecEncoderProps">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Fixed">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="title">
<string>Basic.Settings.Output.Adv.Encoder</string>
</property>
<layout class="QVBoxLayout" name="verticalLayout_15">
<property name="leftMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="topMargin">
<number>2</number>
</property>
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="bottomMargin">
<number>8</number>
</property>
</layout>
UI: Use radio buttons for FLV track selection
2019-07-23 05:20:13 -07:00
</widget>
</item>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item>
<spacer name="verticalSpacer_3">
<property name="orientation">
<enum>Qt::Vertical</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>20</width>
<height>40</height>
</size>
</property>
</spacer>
</item>
UI: Add option to auto remux
2017-05-08 04:53:35 -07:00
</layout>
</widget>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</widget>
</item>
</layout>
</widget>
<widget class="QWidget" name="advOutRecFFmpegPage">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Expanding">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<layout class="QVBoxLayout" name="verticalLayout_26">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>0</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QScrollArea" name="scrollArea_5">
<property name="frameShape">
<enum>QFrame::NoFrame</enum>
</property>
<property name="frameShadow">
<enum>QFrame::Plain</enum>
</property>
<property name="lineWidth">
<number>0</number>
</property>
<property name="widgetResizable">
<bool>true</bool>
</property>
<widget class="QWidget" name="scrollAreaWidgetContents_8">
<property name="geometry">
<rect>
<x>0</x>
<y>0</y>
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<width>759</width>
<height>587</height>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</rect>
</property>
<layout class="QVBoxLayout" name="verticalLayout_27">
UI: Add option to auto remux
2017-05-08 04:53:35 -07:00
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Add option to auto remux
2017-05-08 04:53:35 -07:00
</property>
<property name="bottomMargin">
<number>0</number>
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item>
<widget class="QGroupBox" name="advOutRecFFmpeg">
<property name="title">
<string>Basic.Settings.Output.Adv.FFmpeg.Settings</string>
</property>
<layout class="QFormLayout" name="formLayout_7">
UI: Fix fields not growing in FFmpeg output settings Wasn't consistent with how it is with the rest of the user interface Fixes obsproject/obs-studio#7147
2022-08-22 14:39:49 -07:00
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="leftMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="topMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>2</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<property name="bottomMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<item row="0" column="0">
<widget class="QLabel" name="label_48">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Expanding">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
<property name="text">
<string>Basic.Settings.Output.Adv.FFmpeg.Type</string>
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QComboBox" name="advOutFFType">
<item>
<property name="text">
<string>Basic.Settings.Output.Adv.FFmpeg.Type.RecordToFile</string>
</property>
</item>
<item>
<property name="text">
<string>Basic.Settings.Output.Adv.FFmpeg.Type.URL</string>
</property>
</item>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="label_36">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Expanding">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
<property name="text">
<string>Basic.Settings.Output.Adv.FFmpeg.SavePathURL</string>
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QStackedWidget" name="stackedWidget_2">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Maximum">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="currentIndex">
UI: Fix ffmpeg path browse button not showing The ffmpeg path browse button would be hidden in the settings.
2022-08-07 01:28:14 -07:00
<number>0</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<widget class="QWidget" name="page_7">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Maximum">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<layout class="QHBoxLayout" name="horizontalLayout_27">
<property name="spacing">
<number>3</number>
</property>
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QLineEdit" name="advOutFFRecPath">
<property name="readOnly">
<bool>true</bool>
</property>
</widget>
</item>
<item>
<widget class="QPushButton" name="advOutFFPathBrowse">
<property name="text">
<string>Browse</string>
</property>
</widget>
</item>
</layout>
</widget>
<widget class="QWidget" name="page_8">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Maximum">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<layout class="QHBoxLayout" name="horizontalLayout_30">
<property name="spacing">
<number>0</number>
</property>
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QLineEdit" name="advOutFFURL">
<property name="enabled">
<bool>true</bool>
</property>
</widget>
</item>
</layout>
</widget>
</widget>
</item>
<item row="2" column="1">
<widget class="QCheckBox" name="advOutFFNoSpace">
<property name="text">
<string>Basic.Settings.Output.NoSpaceFileName</string>
</property>
<property name="checked">
<bool>true</bool>
</property>
</widget>
</item>
<item row="3" column="0">
<widget class="QLabel" name="label_16">
<property name="text">
<string>Basic.Settings.Output.Adv.FFmpeg.Format</string>
</property>
</widget>
</item>
<item row="3" column="1">
<widget class="QComboBox" name="advOutFFFormat"/>
</item>
<item row="4" column="0">
<widget class="QLabel" name="label_44">
<property name="text">
<string>Basic.Settings.Output.Adv.FFmpeg.FormatDesc</string>
</property>
</widget>
</item>
<item row="4" column="1">
<widget class="QLabel" name="advOutFFFormatDesc">
<property name="text">
<string/>
</property>
</widget>
</item>
<item row="5" column="0">
<widget class="QLabel" name="label_1337">
<property name="text">
<string>Basic.Settings.Output.Adv.FFmpeg.MuxerSettings</string>
</property>
</widget>
</item>
<item row="5" column="1">
<widget class="QLineEdit" name="advOutFFMCfg"/>
</item>
<item row="6" column="0">
<widget class="QLabel" name="label_40">
<property name="text">
<string>Basic.Settings.Output.VideoBitrate</string>
</property>
</widget>
</item>
<item row="6" column="1">
<widget class="QSpinBox" name="advOutFFVBitrate">
<property name="minimum">
<number>0</number>
</property>
<property name="maximum">
<number>1000000000</number>
</property>
<property name="value">
<number>2500</number>
</property>
</widget>
</item>
<item row="7" column="0">
<widget class="QLabel" name="label_63">
<property name="text">
<string>Basic.Settings.Output.Adv.FFmpeg.GOPSize</string>
</property>
</widget>
</item>
<item row="7" column="1">
<widget class="QSpinBox" name="advOutFFVGOPSize">
<property name="maximum">
<number>1000000000</number>
</property>
<property name="value">
<number>250</number>
</property>
</widget>
</item>
<item row="8" column="0">
<widget class="QCheckBox" name="advOutFFUseRescale">
<property name="sizePolicy">
<sizepolicy hsizetype="Minimum" vsizetype="Expanding">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="layoutDirection">
<enum>Qt::RightToLeft</enum>
</property>
<property name="text">
<string>Basic.Settings.Output.Adv.Rescale</string>
</property>
</widget>
</item>
<item row="8" column="1">
<widget class="QComboBox" name="advOutFFRescale">
<property name="enabled">
<bool>false</bool>
</property>
<property name="editable">
<bool>true</bool>
</property>
</widget>
</item>
<item row="9" column="1">
<widget class="QCheckBox" name="advOutFFIgnoreCompat">
<property name="text">
<string>Basic.Settings.Output.Adv.FFmpeg.IgnoreCodecCompat</string>
</property>
</widget>
</item>
<item row="10" column="0">
<widget class="QLabel" name="label_37">
<property name="text">
<string>Basic.Settings.Output.Adv.FFmpeg.VEncoder</string>
</property>
</widget>
</item>
<item row="10" column="1">
<widget class="QComboBox" name="advOutFFVEncoder"/>
</item>
<item row="11" column="0">
<widget class="QLabel" name="label_38">
<property name="text">
<string>Basic.Settings.Output.Adv.FFmpeg.VEncoderSettings</string>
</property>
</widget>
</item>
<item row="11" column="1">
<widget class="QLineEdit" name="advOutFFVCfg"/>
</item>
<item row="12" column="0">
<widget class="QLabel" name="label_41">
<property name="text">
<string>Basic.Settings.Output.AudioBitrate</string>
</property>
</widget>
</item>
<item row="12" column="1">
<widget class="QSpinBox" name="advOutFFABitrate">
<property name="minimum">
<number>32</number>
</property>
<property name="maximum">
<number>4096</number>
</property>
<property name="singleStep">
<number>16</number>
</property>
<property name="value">
<number>128</number>
</property>
</widget>
</item>
<item row="13" column="0">
<widget class="QLabel" name="label_47">
<property name="text">
<string>Basic.Settings.Output.Adv.AudioTrack</string>
</property>
</widget>
</item>
<item row="13" column="1">
<widget class="QFrame" name="widget_10">
<property name="sizePolicy">
<sizepolicy hsizetype="Maximum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<layout class="QHBoxLayout" name="horizontalLayout_26">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QCheckBox" name="advOutFFTrack1">
<property name="text">
<string notr="true">1</string>
</property>
<property name="checked">
<bool>true</bool>
</property>
</widget>
</item>
<item>
<widget class="QCheckBox" name="advOutFFTrack2">
<property name="text">
<string notr="true">2</string>
</property>
</widget>
</item>
<item>
<widget class="QCheckBox" name="advOutFFTrack3">
<property name="text">
<string notr="true">3</string>
</property>
</widget>
</item>
<item>
<widget class="QCheckBox" name="advOutFFTrack4">
<property name="text">
<string notr="true">4</string>
</property>
</widget>
</item>
<item>
<widget class="QCheckBox" name="advOutFFTrack5">
<property name="text">
<string notr="true">5</string>
</property>
</widget>
</item>
<item>
<widget class="QCheckBox" name="advOutFFTrack6">
<property name="text">
<string notr="true">6</string>
</property>
</widget>
</item>
</layout>
</widget>
</item>
<item row="14" column="0">
<widget class="QLabel" name="label_39">
<property name="text">
<string>Basic.Settings.Output.Adv.FFmpeg.AEncoder</string>
</property>
</widget>
</item>
<item row="14" column="1">
<widget class="QComboBox" name="advOutFFAEncoder"/>
</item>
<item row="15" column="0">
<widget class="QLabel" name="label_46">
<property name="text">
<string>Basic.Settings.Output.Adv.FFmpeg.AEncoderSettings</string>
</property>
</widget>
</item>
<item row="15" column="1">
<widget class="QLineEdit" name="advOutFFACfg"/>
</item>
</layout>
</widget>
</item>
<item>
<spacer name="verticalSpacer_6">
<property name="orientation">
<enum>Qt::Vertical</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>20</width>
<height>40</height>
</size>
</property>
</spacer>
</item>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</layout>
UI: Allow generated filenames for FFmpeg output This changes the way the advanced output section's FFmpeg output settings work by allowing the user to select whether they want to output to a file or output to a URL, and makes it so file names are automatically generated like other recording outputs. If they choose to output to a file, it'll only require an output directory similarly to how other recording outputs work. They can select a directory to output to rather than being required to type in a full path and filename; the filename is automatically generated. The extension is also automatically retrieved from libff depending on the format selected. Otherwise if they have Output to URL selected, it'll show a simple edit box where they can type in the target URL.
2015-08-18 20:58:24 -07:00
</widget>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</widget>
</item>
</layout>
</widget>
</widget>
</item>
</layout>
</widget>
<widget class="QWidget" name="advOutputAudioTracksTab">
<attribute name="title">
<string>Basic.Settings.Audio</string>
</attribute>
<layout class="QVBoxLayout" name="verticalLayout_9">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QFrame" name="widget_3">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<layout class="QVBoxLayout" name="verticalLayout_10">
<property name="leftMargin">
<number>0</number>
</property>
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<property name="topMargin">
<number>6</number>
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</property>
<item>
<widget class="QScrollArea" name="scrollArea_6">
<property name="frameShape">
<enum>QFrame::NoFrame</enum>
UI: Allow generated filenames for FFmpeg output This changes the way the advanced output section's FFmpeg output settings work by allowing the user to select whether they want to output to a file or output to a URL, and makes it so file names are automatically generated like other recording outputs. If they choose to output to a file, it'll only require an output directory similarly to how other recording outputs work. They can select a directory to output to rather than being required to type in a full path and filename; the filename is automatically generated. The extension is also automatically retrieved from libff depending on the format selected. Otherwise if they have Output to URL selected, it'll show a simple edit box where they can type in the target URL.
2015-08-18 20:58:24 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="frameShadow">
<enum>QFrame::Plain</enum>
UI: Allow generated filenames for FFmpeg output This changes the way the advanced output section's FFmpeg output settings work by allowing the user to select whether they want to output to a file or output to a URL, and makes it so file names are automatically generated like other recording outputs. If they choose to output to a file, it'll only require an output directory similarly to how other recording outputs work. They can select a directory to output to rather than being required to type in a full path and filename; the filename is automatically generated. The extension is also automatically retrieved from libff depending on the format selected. Otherwise if they have Output to URL selected, it'll show a simple edit box where they can type in the target URL.
2015-08-18 20:58:24 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="lineWidth">
UI: Allow generated filenames for FFmpeg output This changes the way the advanced output section's FFmpeg output settings work by allowing the user to select whether they want to output to a file or output to a URL, and makes it so file names are automatically generated like other recording outputs. If they choose to output to a file, it'll only require an output directory similarly to how other recording outputs work. They can select a directory to output to rather than being required to type in a full path and filename; the filename is automatically generated. The extension is also automatically retrieved from libff depending on the format selected. Otherwise if they have Output to URL selected, it'll show a simple edit box where they can type in the target URL.
2015-08-18 20:58:24 -07:00
<number>0</number>
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="widgetResizable">
<bool>true</bool>
</property>
<widget class="QWidget" name="scrollAreaWidgetContents_7">
<property name="geometry">
<rect>
<x>0</x>
<y>0</y>
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<width>759</width>
<height>616</height>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</rect>
</property>
<layout class="QVBoxLayout" name="verticalLayout_28">
<property name="spacing">
<number>6</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="leftMargin">
<number>0</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="topMargin">
<number>0</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Fix weird spacing in adv output FFmpeg recording
2020-12-07 19:15:16 -08:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="bottomMargin">
UI: Fix custom ffmpeg output file / URL entry The default value in the .ui file was out of sync so the signal to update the stacked widget was never sent. Fixes https://obsproject.com/mantis/view.php?id=1060
2017-11-08 06:29:30 -08:00
<number>0</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item>
<widget class="QGroupBox" name="groupBox">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="title">
<string>Basic.Settings.Output.Adv.Audio.Track1</string>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<layout class="QFormLayout" name="formLayout_10">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="leftMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="topMargin">
<number>2</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="bottomMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item row="0" column="1">
<widget class="QComboBox" name="advOutTrack1Bitrate">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="currentIndex">
<number>8</number>
</property>
<item>
<property name="text">
<string>32</string>
</property>
</item>
<item>
<property name="text">
<string>48</string>
</property>
</item>
<item>
<property name="text">
<string>64</string>
</property>
</item>
<item>
<property name="text">
<string>80</string>
</property>
</item>
<item>
<property name="text">
<string>96</string>
</property>
</item>
<item>
<property name="text">
<string>112</string>
</property>
</item>
<item>
<property name="text">
<string>128</string>
</property>
</item>
<item>
<property name="text">
<string>160</string>
</property>
</item>
<item>
<property name="text">
<string>192</string>
</property>
</item>
<item>
<property name="text">
<string>256</string>
</property>
</item>
<item>
<property name="text">
<string>320</string>
</property>
</item>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="label_55">
<property name="text">
<string>Name</string>
</property>
<property name="buddy">
<cstring>advOutTrack1Name</cstring>
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QLineEdit" name="advOutTrack1Name">
<property name="sizePolicy">
<sizepolicy hsizetype="Expanding" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
</widget>
</item>
<item row="0" column="0">
<widget class="QLabel" name="label_25">
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
<property name="text">
<string>Basic.Settings.Output.AudioBitrate</string>
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="buddy">
<cstring>advOutTrack1Bitrate</cstring>
</property>
</widget>
</item>
</layout>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</widget>
</item>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item>
<widget class="QGroupBox" name="groupBox_2">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="title">
<string>Basic.Settings.Output.Adv.Audio.Track2</string>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<layout class="QFormLayout" name="formLayout_11">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="leftMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="topMargin">
<number>2</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="bottomMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item row="0" column="0">
<widget class="QLabel" name="label_49">
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
<property name="text">
<string>Basic.Settings.Output.AudioBitrate</string>
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="buddy">
<cstring>advOutTrack2Bitrate</cstring>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QComboBox" name="advOutTrack2Bitrate">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="currentIndex">
<number>8</number>
</property>
<item>
<property name="text">
<string>32</string>
</property>
</item>
<item>
<property name="text">
<string>48</string>
</property>
</item>
<item>
<property name="text">
<string>64</string>
</property>
</item>
<item>
<property name="text">
<string>80</string>
</property>
</item>
<item>
<property name="text">
<string>96</string>
</property>
</item>
<item>
<property name="text">
<string>112</string>
</property>
</item>
<item>
<property name="text">
<string>128</string>
</property>
</item>
<item>
<property name="text">
<string>160</string>
</property>
</item>
<item>
<property name="text">
<string>192</string>
</property>
</item>
<item>
<property name="text">
<string>256</string>
</property>
</item>
<item>
<property name="text">
<string>320</string>
</property>
</item>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="label_50">
<property name="text">
<string>Name</string>
</property>
<property name="buddy">
<cstring>advOutTrack2Name</cstring>
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QLineEdit" name="advOutTrack2Name">
<property name="sizePolicy">
<sizepolicy hsizetype="Expanding" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
</widget>
</item>
</layout>
</widget>
</item>
<item>
<widget class="QGroupBox" name="groupBox_3">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="title">
<string>Basic.Settings.Output.Adv.Audio.Track3</string>
</property>
<layout class="QFormLayout" name="formLayout_12">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="leftMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="topMargin">
<number>2</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="bottomMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item row="0" column="0">
<widget class="QLabel" name="label_51">
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
<property name="text">
<string>Basic.Settings.Output.AudioBitrate</string>
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="buddy">
<cstring>advOutTrack3Bitrate</cstring>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QComboBox" name="advOutTrack3Bitrate">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="currentIndex">
<number>8</number>
</property>
<item>
<property name="text">
<string>32</string>
</property>
</item>
<item>
<property name="text">
<string>48</string>
</property>
</item>
<item>
<property name="text">
<string>64</string>
</property>
</item>
<item>
<property name="text">
<string>80</string>
</property>
</item>
<item>
<property name="text">
<string>96</string>
</property>
</item>
<item>
<property name="text">
<string>112</string>
</property>
</item>
<item>
<property name="text">
<string>128</string>
</property>
</item>
<item>
<property name="text">
<string>160</string>
</property>
</item>
<item>
<property name="text">
<string>192</string>
</property>
</item>
<item>
<property name="text">
<string>256</string>
</property>
</item>
<item>
<property name="text">
<string>320</string>
</property>
</item>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="label_52">
<property name="text">
<string>Name</string>
</property>
<property name="buddy">
<cstring>advOutTrack3Name</cstring>
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QLineEdit" name="advOutTrack3Name">
<property name="sizePolicy">
<sizepolicy hsizetype="Expanding" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
</widget>
</item>
</layout>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</widget>
</item>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item>
<widget class="QGroupBox" name="groupBox_4">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="title">
<string>Basic.Settings.Output.Adv.Audio.Track4</string>
</property>
<layout class="QFormLayout" name="formLayout_13">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="leftMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="topMargin">
<number>2</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="bottomMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item row="0" column="0">
<widget class="QLabel" name="label_53">
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
<property name="text">
<string>Basic.Settings.Output.AudioBitrate</string>
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="buddy">
<cstring>advOutTrack4Bitrate</cstring>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QComboBox" name="advOutTrack4Bitrate">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="currentIndex">
<number>8</number>
</property>
<item>
<property name="text">
<string>32</string>
</property>
</item>
<item>
<property name="text">
<string>48</string>
</property>
</item>
<item>
<property name="text">
<string>64</string>
</property>
</item>
<item>
<property name="text">
<string>80</string>
</property>
</item>
<item>
<property name="text">
<string>96</string>
</property>
</item>
<item>
<property name="text">
<string>112</string>
</property>
</item>
<item>
<property name="text">
<string>128</string>
</property>
</item>
<item>
<property name="text">
<string>160</string>
</property>
</item>
<item>
<property name="text">
<string>192</string>
</property>
</item>
<item>
<property name="text">
<string>256</string>
</property>
</item>
<item>
<property name="text">
<string>320</string>
</property>
</item>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="label_54">
<property name="text">
<string>Name</string>
</property>
<property name="buddy">
<cstring>advOutTrack4Name</cstring>
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QLineEdit" name="advOutTrack4Name">
<property name="sizePolicy">
<sizepolicy hsizetype="Expanding" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
</widget>
</item>
</layout>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</widget>
</item>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item>
<widget class="QGroupBox" name="groupBox_9">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="title">
<string>Basic.Settings.Output.Adv.Audio.Track5</string>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<layout class="QFormLayout" name="formLayout_25">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="leftMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="topMargin">
<number>2</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="bottomMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item row="0" column="0">
<widget class="QLabel" name="label_59">
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
<property name="text">
<string>Basic.Settings.Output.AudioBitrate</string>
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="buddy">
<cstring>advOutTrack5Bitrate</cstring>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QComboBox" name="advOutTrack5Bitrate">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="currentIndex">
<number>8</number>
</property>
<item>
<property name="text">
<string>32</string>
</property>
</item>
<item>
<property name="text">
<string>48</string>
</property>
</item>
<item>
<property name="text">
<string>64</string>
</property>
</item>
<item>
<property name="text">
<string>80</string>
</property>
</item>
<item>
<property name="text">
<string>96</string>
</property>
</item>
<item>
<property name="text">
<string>112</string>
</property>
</item>
<item>
<property name="text">
<string>128</string>
</property>
</item>
<item>
<property name="text">
<string>160</string>
</property>
</item>
<item>
<property name="text">
<string>192</string>
</property>
</item>
<item>
<property name="text">
<string>256</string>
</property>
</item>
<item>
<property name="text">
<string>320</string>
</property>
</item>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="label_60">
<property name="text">
<string>Name</string>
</property>
<property name="buddy">
<cstring>advOutTrack5Name</cstring>
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QLineEdit" name="advOutTrack5Name">
<property name="sizePolicy">
<sizepolicy hsizetype="Expanding" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
</widget>
</item>
</layout>
</widget>
</item>
<item>
<widget class="QGroupBox" name="groupBox_12">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="title">
<string>Basic.Settings.Output.Adv.Audio.Track6</string>
</property>
<layout class="QFormLayout" name="formLayout_26">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="leftMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="topMargin">
<number>2</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="bottomMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item row="0" column="0">
<widget class="QLabel" name="label_61">
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
<property name="text">
<string>Basic.Settings.Output.AudioBitrate</string>
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="buddy">
<cstring>advOutTrack6Bitrate</cstring>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QComboBox" name="advOutTrack6Bitrate">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="currentIndex">
<number>8</number>
</property>
<item>
<property name="text">
<string>32</string>
</property>
</item>
<item>
<property name="text">
<string>48</string>
</property>
</item>
<item>
<property name="text">
<string>64</string>
</property>
</item>
<item>
<property name="text">
<string>80</string>
</property>
</item>
<item>
<property name="text">
<string>96</string>
</property>
</item>
<item>
<property name="text">
<string>112</string>
</property>
</item>
<item>
<property name="text">
<string>128</string>
</property>
</item>
<item>
<property name="text">
<string>160</string>
</property>
</item>
<item>
<property name="text">
<string>192</string>
</property>
</item>
<item>
<property name="text">
<string>256</string>
</property>
</item>
<item>
<property name="text">
<string>320</string>
</property>
</item>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="label_62">
<property name="text">
<string>Name</string>
</property>
<property name="buddy">
<cstring>advOutTrack6Name</cstring>
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QLineEdit" name="advOutTrack6Name">
<property name="sizePolicy">
<sizepolicy hsizetype="Expanding" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
</widget>
</item>
</layout>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</widget>
</item>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item>
<spacer name="verticalSpacer_5">
<property name="orientation">
<enum>Qt::Vertical</enum>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="sizeType">
<enum>QSizePolicy::Expanding</enum>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="sizeHint" stdset="0">
<size>
<width>10</width>
<height>10</height>
</size>
</property>
</spacer>
UI: Enable Replay Buffer in Advanced Mode Replay buffer is currently only supported in simple mode. This change adds support to advanced mode and is, for the most part, a mirror of the addition of replay buffer to simple mode. Mantis-bug: https://obsproject.com/mantis/view.php?id=792 Closes jp9000/obs-studio#1019
2017-09-05 17:01:49 -07:00
</item>
</layout>
</widget>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</widget>
</item>
</layout>
</widget>
</item>
</layout>
</widget>
<widget class="QWidget" name="advOutputReplayTab">
<attribute name="title">
<string>ReplayBuffer</string>
</attribute>
<layout class="QVBoxLayout" name="verticalLayout_22">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QFrame" name="advOutputReplayFrame">
<property name="lineWidth">
<number>0</number>
</property>
<layout class="QVBoxLayout" name="verticalLayout_29">
<property name="leftMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="topMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>6</number>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>0</number>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="bottomMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>9</number>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item>
<widget class="QCheckBox" name="advReplayBuf">
<property name="text">
<string>Basic.Settings.Output.UseReplayBuffer</string>
</property>
</widget>
</item>
<item>
<widget class="QFrame" name="advReplayBufferFrame">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<layout class="QFormLayout" name="formLayout_30">
<property name="leftMargin">
<number>0</number>
UI: Increase maximum audio tracks to 6
2016-12-21 17:14:24 -08:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="topMargin">
<number>0</number>
UI: Increase maximum audio tracks to 6
2016-12-21 17:14:24 -08:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="rightMargin">
<number>0</number>
UI: Increase maximum audio tracks to 6
2016-12-21 17:14:24 -08:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<property name="bottomMargin">
<number>8</number>
UI: Increase maximum audio tracks to 6
2016-12-21 17:14:24 -08:00
</property>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<item row="0" column="0">
<widget class="QLabel" name="advRBSecMaxLabel">
<property name="text">
<string>Basic.Settings.Output.ReplayBuffer.SecondsMax</string>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QSpinBox" name="advRBSecMax">
<property name="suffix">
<string notr="true"> s</string>
</property>
<property name="minimum">
<number>5</number>
</property>
<property name="maximum">
<number>21600</number>
</property>
<property name="value">
<number>15</number>
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QSpinBox" name="advRBMegsMax">
<property name="suffix">
<string> MB</string>
</property>
<property name="minimum">
<number>20</number>
</property>
<property name="maximum">
<number>8192</number>
</property>
<property name="value">
<number>512</number>
</property>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="advRBMegsMaxLabel">
<property name="text">
<string>Basic.Settings.Output.ReplayBuffer.MegabytesMax</string>
</property>
</widget>
</item>
<item row="2" column="1">
<widget class="QLabel" name="advRBEstimate">
<property name="text">
<string notr="true"/>
</property>
</widget>
</item>
</layout>
</widget>
</item>
</layout>
</widget>
</item>
<item>
<spacer name="verticalSpacer">
<property name="orientation">
<enum>Qt::Vertical</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>20</width>
<height>20</height>
</size>
</property>
</spacer>
</item>
</layout>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</widget>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</widget>
</item>
</layout>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</widget>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
</widget>
</item>
</layout>
Add preliminary streaming code for testing - Add some temporary streaming code using FFmpeg. FFmpeg itself is not very ideal for streaming; lack of direct control of the sockets and no framedrop handling means that FFmpeg is definitely not something you want to use without wrapper code. I'd prefer writing my own network framework in this particular case just because you give away so much control of the network interface. Wasted an entire day trying to go through FFmpeg issues. There's just no way FFmpeg should be used for real streaming (at least without being patched or submitting some sort of patch, but I'm sort of feeling "meh" on that idea) I had to end up writing multiple threads just to handle both connecting and writing, because av_interleaved_write_frame blocks every call, stalling the main encoder thread, and thus also stalling draw signals. - Add some temporary user interface for streaming settings. This is just temporary for the time being. It's in the outputs section of the basic-mode settings - Make it so that dynamic arrays do not free all their data when the size just happens to be reduced to 0. This prevents constant reallocation when an array keeps going from 1 item to 0 items. Also, it was bad to become dependent upon that functionality. You must now always explicitly call "free" on it to ensure the data is free, and that's how it should be. Implicit functionality can lead to confusion and maintainability issues.
2014-03-10 13:10:35 -07:00
</widget>
</item>
</layout>
</widget>
<widget class="QWidget" name="audioPage">
UI: Refactor Audio Settings tab structure - Now uses a QVBoxLayout with a QScrollArea for the container - Uses QGroupBox for each section - Moved Monitoring and ducking settings out of the Advanced tab - Push-to hotkeys are no longer in a child scroll area - Renamed device labels for consistency
2019-02-02 03:09:47 -08:00
<layout class="QVBoxLayout" name="formLayout">
<property name="leftMargin">
<number>0</number>
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
</property>
UI: Refactor Audio Settings tab structure - Now uses a QVBoxLayout with a QScrollArea for the container - Uses QGroupBox for each section - Moved Monitoring and ducking settings out of the Advanced tab - Push-to hotkeys are no longer in a child scroll area - Renamed device labels for consistency
2019-02-02 03:09:47 -08:00
<property name="topMargin">
<number>0</number>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
UI: Refactor Audio Settings tab structure - Now uses a QVBoxLayout with a QScrollArea for the container - Uses QGroupBox for each section - Moved Monitoring and ducking settings out of the Advanced tab - Push-to hotkeys are no longer in a child scroll area - Renamed device labels for consistency
2019-02-02 03:09:47 -08:00
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QScrollArea" name="scrollArea_50">
<property name="frameShape">
UI, obs-plugins: Add spinbox suffixes where necessary
2019-07-18 00:38:50 -07:00
<enum>QFrame::NoFrame</enum>
UI: Add audio meter decay rate option The decay rate of the audio meters can now be selected in the audio settings. The values are: - "Fast" (OBS default, 40 dB / 1.7s) - "Medium" (Type I PPM, 20 dB / 1.7s) - "Slow" (Type II PPM, 24 dB / 2.8s) Closes jp9000/obs-studio#1143
2018-01-09 12:45:20 -08:00
</property>
UI: Refactor Audio Settings tab structure - Now uses a QVBoxLayout with a QScrollArea for the container - Uses QGroupBox for each section - Moved Monitoring and ducking settings out of the Advanced tab - Push-to hotkeys are no longer in a child scroll area - Renamed device labels for consistency
2019-02-02 03:09:47 -08:00
<property name="frameShadow">
<enum>QFrame::Plain</enum>
libobs, UI: Add true peak measurements Add a new algorithm to calculate the true-peak. It implements the Whittaker- Shannon interpolation from four samples to create 4 intermediate samples (5 x oversampling) inbetween the middle two samples. With 4 samples and 4 intermediate samples the algorithm can be implemented as a 4x4 vector-matrix cross product, which is ideal for SSE. I've also replaced the sample-peak algorithm using SSE as well to improve performance. Closes obsproject/obs-studio#1189
2018-01-19 13:57:36 -08:00
</property>
UI: Use theme for red message in audio settings
2018-08-16 13:15:43 -07:00
<property name="widgetResizable">
<bool>true</bool>
</property>
UI: Refactor Audio Settings tab structure - Now uses a QVBoxLayout with a QScrollArea for the container - Uses QGroupBox for each section - Moved Monitoring and ducking settings out of the Advanced tab - Push-to hotkeys are no longer in a child scroll area - Renamed device labels for consistency
2019-02-02 03:09:47 -08:00
<widget class="QWidget" name="scrollAreaWidgetContents_50">
UI: Use theme for red message in audio settings
2018-08-16 13:15:43 -07:00
<property name="geometry">
<rect>
<x>0</x>
<y>0</y>
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<width>781</width>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<height>640</height>
UI: Use theme for red message in audio settings
2018-08-16 13:15:43 -07:00
</rect>
</property>
UI: Refactor Audio Settings tab structure - Now uses a QVBoxLayout with a QScrollArea for the container - Uses QGroupBox for each section - Moved Monitoring and ducking settings out of the Advanced tab - Push-to hotkeys are no longer in a child scroll area - Renamed device labels for consistency
2019-02-02 03:09:47 -08:00
<layout class="QVBoxLayout" name="verticalLayout_50">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>9</number>
</property>
UI: Clean up Settings form markup This continues work from #5133 to correct UI file markup and save correctly in Qt Creator Defining alignment as an attribute in the <item> tag seems to be old behaviour that current versions of Qt Creator do not respect and will clobber these entries on save. The correct approach is to have alignment as a property element in the widget. As well, QWidgets that contain property definitions as well as a layout child item do not properly show up in the Qt Creator hierarchy. These properties are still invisibly applied but the QWidgets are not shown in Qt Creator and will get removed from the file after saving.
2021-08-16 22:41:57 -07:00
<item>
<widget class="QFrame" name="widget_50">
UI: Refactor Audio Settings tab structure - Now uses a QVBoxLayout with a QScrollArea for the container - Uses QGroupBox for each section - Moved Monitoring and ducking settings out of the Advanced tab - Push-to hotkeys are no longer in a child scroll area - Renamed device labels for consistency
2019-02-02 03:09:47 -08:00
<layout class="QVBoxLayout" name="verticalLayout_51">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<property name="leftMargin">
<number>9</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
UI: Refactor Audio Settings tab structure - Now uses a QVBoxLayout with a QScrollArea for the container - Uses QGroupBox for each section - Moved Monitoring and ducking settings out of the Advanced tab - Push-to hotkeys are no longer in a child scroll area - Renamed device labels for consistency
2019-02-02 03:09:47 -08:00
<item>
<widget class="QGroupBox" name="audioGeneralGroupBox">
<property name="title">
<string>Basic.Settings.General</string>
</property>
<layout class="QFormLayout" name="formLayout_52">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="topMargin">
<number>2</number>
</property>
<item row="0" column="0">
<widget class="QLabel" name="label_14">
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
<property name="text">
<string>Basic.Settings.Audio.SampleRate</string>
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="buddy">
<cstring>sampleRate</cstring>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QComboBox" name="sampleRate">
<property name="currentText">
UI: Display Sample Rate with proper formatting
2019-10-19 01:05:00 -07:00
<string notr="true">44.1 kHz</string>
UI: Refactor Audio Settings tab structure - Now uses a QVBoxLayout with a QScrollArea for the container - Uses QGroupBox for each section - Moved Monitoring and ducking settings out of the Advanced tab - Push-to hotkeys are no longer in a child scroll area - Renamed device labels for consistency
2019-02-02 03:09:47 -08:00
</property>
<property name="currentIndex">
<number>0</number>
</property>
<item>
<property name="text">
UI: Display Sample Rate with proper formatting
2019-10-19 01:05:00 -07:00
<string>44.1 kHz</string>
UI: Refactor Audio Settings tab structure - Now uses a QVBoxLayout with a QScrollArea for the container - Uses QGroupBox for each section - Moved Monitoring and ducking settings out of the Advanced tab - Push-to hotkeys are no longer in a child scroll area - Renamed device labels for consistency
2019-02-02 03:09:47 -08:00
</property>
</item>
<item>
<property name="text">
UI: Display Sample Rate with proper formatting
2019-10-19 01:05:00 -07:00
<string>48 kHz</string>
UI: Refactor Audio Settings tab structure - Now uses a QVBoxLayout with a QScrollArea for the container - Uses QGroupBox for each section - Moved Monitoring and ducking settings out of the Advanced tab - Push-to hotkeys are no longer in a child scroll area - Renamed device labels for consistency
2019-02-02 03:09:47 -08:00
</property>
</item>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="label_15">
<property name="text">
<string>Basic.Settings.Audio.Channels</string>
</property>
<property name="buddy">
<cstring>channelSetup</cstring>
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QComboBox" name="channelSetup">
<property name="currentText">
<string>Mono</string>
</property>
<property name="currentIndex">
<number>0</number>
</property>
<item>
<property name="text">
<string>Mono</string>
</property>
</item>
<item>
<property name="text">
<string>Stereo</string>
</property>
</item>
<item>
<property name="text">
<string>2.1</string>
</property>
</item>
<item>
<property name="text">
<string>4.0</string>
</property>
</item>
<item>
<property name="text">
<string>4.1</string>
</property>
</item>
<item>
<property name="text">
<string>5.1</string>
</property>
</item>
<item>
<property name="text">
<string>7.1</string>
</property>
</item>
</widget>
</item>
</layout>
</widget>
</item>
<item>
<widget class="QGroupBox" name="audioDevicesGroupBox">
<property name="title">
<string>Basic.Settings.Audio.Devices</string>
</property>
<layout class="QFormLayout" name="formLayout_53">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="topMargin">
<number>2</number>
</property>
<item row="0" column="0">
<widget class="QLabel" name="label_2">
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
<property name="text">
<string>Basic.Settings.Audio.DesktopDevice</string>
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="buddy">
<cstring>desktopAudioDevice1</cstring>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QComboBox" name="desktopAudioDevice1">
<property name="enabled">
<bool>true</bool>
</property>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="label_3">
<property name="text">
<string>Basic.Settings.Audio.DesktopDevice2</string>
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="buddy">
<cstring>desktopAudioDevice2</cstring>
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QComboBox" name="desktopAudioDevice2">
<property name="enabled">
<bool>true</bool>
</property>
</widget>
</item>
<item row="2" column="0">
<widget class="QLabel" name="label_4">
<property name="text">
<string>Basic.Settings.Audio.AuxDevice</string>
</property>
<property name="buddy">
<cstring>auxAudioDevice1</cstring>
</property>
</widget>
</item>
<item row="2" column="1">
<widget class="QComboBox" name="auxAudioDevice1">
<property name="enabled">
<bool>true</bool>
</property>
</widget>
</item>
<item row="3" column="0">
<widget class="QLabel" name="label_5">
<property name="text">
<string>Basic.Settings.Audio.AuxDevice2</string>
</property>
<property name="buddy">
<cstring>auxAudioDevice2</cstring>
</property>
</widget>
</item>
<item row="3" column="1">
<widget class="QComboBox" name="auxAudioDevice2">
<property name="enabled">
<bool>true</bool>
</property>
</widget>
</item>
<item row="4" column="0">
<widget class="QLabel" name="label_6">
<property name="text">
<string>Basic.Settings.Audio.AuxDevice3</string>
</property>
<property name="buddy">
<cstring>auxAudioDevice3</cstring>
</property>
</widget>
</item>
<item row="4" column="1">
<widget class="QComboBox" name="auxAudioDevice3">
<property name="enabled">
<bool>true</bool>
</property>
</widget>
</item>
<item row="5" column="1">
<widget class="QComboBox" name="auxAudioDevice4">
<property name="enabled">
<bool>true</bool>
</property>
</widget>
</item>
<item row="5" column="0">
<widget class="QLabel" name="label_67">
<property name="text">
<string>Basic.Settings.Audio.AuxDevice4</string>
</property>
<property name="buddy">
<cstring>auxAudioDevice4</cstring>
</property>
</widget>
</item>
</layout>
</widget>
</item>
<item>
<widget class="QGroupBox" name="audioMetersGroupBox">
<property name="title">
<string>Basic.Settings.Audio.Meters</string>
</property>
<layout class="QFormLayout" name="formLayout_54">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="topMargin">
<number>2</number>
</property>
<item row="0" column="0">
<widget class="QLabel" name="label_65">
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
<property name="text">
<string>Basic.Settings.Audio.MeterDecayRate</string>
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="buddy">
<cstring>meterDecayRate</cstring>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QComboBox" name="meterDecayRate">
<property name="currentText">
<string>Basic.Settings.Audio.MeterDecayRate.Fast</string>
</property>
<property name="currentIndex">
<number>0</number>
</property>
<item>
<property name="text">
<string>Basic.Settings.Audio.MeterDecayRate.Fast</string>
</property>
</item>
<item>
<property name="text">
<string>Basic.Settings.Audio.MeterDecayRate.Medium</string>
</property>
</item>
<item>
<property name="text">
<string>Basic.Settings.Audio.MeterDecayRate.Slow</string>
</property>
</item>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="label_66">
<property name="text">
<string>Basic.Settings.Audio.PeakMeterType</string>
</property>
<property name="buddy">
<cstring>peakMeterType</cstring>
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QComboBox" name="peakMeterType">
<property name="currentIndex">
<number>0</number>
</property>
<item>
<property name="text">
<string>Basic.Settings.Audio.PeakMeterType.SamplePeak</string>
</property>
</item>
<item>
<property name="text">
<string>Basic.Settings.Audio.PeakMeterType.TruePeak</string>
</property>
</item>
</widget>
</item>
</layout>
</widget>
</item>
<item>
<widget class="QGroupBox" name="audioAdvGroupBox">
<property name="title">
<string>Basic.Settings.Advanced</string>
</property>
<layout class="QFormLayout" name="formLayout_56">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="topMargin">
<number>2</number>
</property>
<item row="0" column="0">
<widget class="QLabel" name="monitoringDeviceLabel">
<property name="text">
<string>Basic.Settings.Advanced.Audio.MonitoringDevice</string>
</property>
<property name="buddy">
<cstring>monitoringDevice</cstring>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QComboBox" name="monitoringDevice"/>
</item>
UI: Fix crash if there is no monitoring available
2022-07-31 05:16:09 -07:00
<item row="1" column="1">
<widget class="QCheckBox" name="disableAudioDucking">
<property name="text">
<string>Basic.Settings.Advanced.Audio.DisableAudioDucking</string>
</property>
</widget>
</item>
<item row="2" column="0">
UI: Refactor Audio Settings tab structure - Now uses a QVBoxLayout with a QScrollArea for the container - Uses QGroupBox for each section - Moved Monitoring and ducking settings out of the Advanced tab - Push-to hotkeys are no longer in a child scroll area - Renamed device labels for consistency
2019-02-02 03:09:47 -08:00
<spacer name="horizontalSpacer_11">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
<height>20</height>
</size>
</property>
</spacer>
</item>
UI: Add low latency audio buffering mode to UI This feature is meant to reduce maximum audio buffering and turn off dynamic buffering mode. This allows the lowest possible consistent latency for audio buffering, which is useful for the decklink and NDI outputs which cannot rely on audio timestamps for synchronization. This can have a negative effect of making audio segments (partial or in full) cut out. So audio glitching or audio loss can occur if this is enabled.
2022-07-18 14:25:06 -07:00
<item row="2" column="1">
<widget class="QCheckBox" name="lowLatencyBuffering">
<property name="text">
<string>Basic.Settings.Audio.LowLatencyBufferingMode</string>
</property>
</widget>
</item>
UI: Refactor Audio Settings tab structure - Now uses a QVBoxLayout with a QScrollArea for the container - Uses QGroupBox for each section - Moved Monitoring and ducking settings out of the Advanced tab - Push-to hotkeys are no longer in a child scroll area - Renamed device labels for consistency
2019-02-02 03:09:47 -08:00
</layout>
</widget>
</item>
<item>
<widget class="QGroupBox" name="audioHotkeysGroupBox">
<property name="title">
<string>Basic.Settings.Hotkeys</string>
</property>
<layout class="QFormLayout" name="audioSourceLayout">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="topMargin">
<number>2</number>
</property>
</layout>
</widget>
</item>
UI: Fix vertical stretching in audio settings pane The fixes in #5143 caused the audio pane in settings to stretch out to fit the available space. Add a spacer so the pane only uses the space it needs.
2021-09-03 20:35:51 -07:00
<item>
<spacer name="verticalSpacer_4">
<property name="orientation">
<enum>Qt::Vertical</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>20</width>
<height>0</height>
</size>
</property>
</spacer>
</item>
UI: Refactor Audio Settings tab structure - Now uses a QVBoxLayout with a QScrollArea for the container - Uses QGroupBox for each section - Moved Monitoring and ducking settings out of the Advanced tab - Push-to hotkeys are no longer in a child scroll area - Renamed device labels for consistency
2019-02-02 03:09:47 -08:00
</layout>
</widget>
</item>
</layout>
UI: Use theme for red message in audio settings
2018-08-16 13:15:43 -07:00
</widget>
</widget>
</item>
UI, obs-plugins: Add spinbox suffixes where necessary
2019-07-18 00:38:50 -07:00
<item>
UI: Use theme for red message in audio settings
2018-08-16 13:15:43 -07:00
<widget class="QLabel" name="audioMsg">
libobs, UI: Add true peak measurements Add a new algorithm to calculate the true-peak. It implements the Whittaker- Shannon interpolation from four samples to create 4 intermediate samples (5 x oversampling) inbetween the middle two samples. With 4 samples and 4 intermediate samples the algorithm can be implemented as a 4x4 vector-matrix cross product, which is ideal for SSE. I've also replaced the sample-peak algorithm using SSE as well to improve performance. Closes obsproject/obs-studio#1189
2018-01-19 13:57:36 -08:00
<property name="text">
UI: Use theme for red message in audio settings
2018-08-16 13:15:43 -07:00
<string notr="true"/>
</property>
<property name="wordWrap">
<bool>true</bool>
</property>
<property name="themeID" stdset="0">
<string>error</string>
libobs, UI: Add true peak measurements Add a new algorithm to calculate the true-peak. It implements the Whittaker- Shannon interpolation from four samples to create 4 intermediate samples (5 x oversampling) inbetween the middle two samples. With 4 samples and 4 intermediate samples the algorithm can be implemented as a 4x4 vector-matrix cross product, which is ideal for SSE. I've also replaced the sample-peak algorithm using SSE as well to improve performance. Closes obsproject/obs-studio#1189
2018-01-19 13:57:36 -08:00
</property>
</widget>
</item>
UI, obs-plugins: Add spinbox suffixes where necessary
2019-07-18 00:38:50 -07:00
<item>
UI: Use theme for red message in audio settings
2018-08-16 13:15:43 -07:00
<widget class="QLabel" name="audioMsg_2">
<property name="text">
<string notr="true"/>
</property>
<property name="wordWrap">
<bool>true</bool>
</property>
<property name="themeID" stdset="0">
<string notr="true">warning</string>
</property>
</widget>
</item>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</layout>
</widget>
<widget class="QWidget" name="videoPage">
<layout class="QFormLayout" name="formLayout_3">
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<property name="leftMargin">
<number>9</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
<item row="0" column="0">
UI: Move Renderer/Adapter to advanced These really are advanced options that users shouldn't need to change normally, so moving them to advanced makes sense, and keeps them away from users who don't know what they're doing.
2016-01-25 05:55:01 -08:00
<widget class="QLabel" name="label_8">
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
<property name="minimumSize">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
<property name="text">
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
<string>Basic.Settings.Video.BaseResolution</string>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
UI: Fix a wrong label alignment in settings window
2016-01-30 09:00:23 -08:00
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
UI: Add label/control buddy pairs for main windows
2016-02-21 11:19:26 -08:00
<property name="buddy">
<cstring>baseResolution</cstring>
</property>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</widget>
</item>
UI: Move Renderer/Adapter to advanced These really are advanced options that users shouldn't need to change normally, so moving them to advanced makes sense, and keeps them away from users who don't know what they're doing.
2016-01-25 05:55:01 -08:00
<item row="0" column="1">
UI: Display aspect ratios in video settings
2020-01-08 22:03:22 -08:00
<layout class="QHBoxLayout" name="horizontalLayout_29">
<property name="spacing">
<number>6</number>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
UI: Display aspect ratios in video settings
2020-01-08 22:03:22 -08:00
<item>
<widget class="QComboBox" name="baseResolution">
<property name="sizePolicy">
<sizepolicy hsizetype="Expanding" vsizetype="Fixed">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="editable">
<bool>true</bool>
</property>
<property name="currentText">
<string notr="true"/>
</property>
<property name="duplicatesEnabled">
<bool>false</bool>
</property>
<property name="frame">
<bool>true</bool>
</property>
</widget>
</item>
<item>
<widget class="QLabel" name="baseAspect">
<property name="text">
<string>AspectRatio</string>
</property>
</widget>
</item>
</layout>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</item>
UI: Display aspect ratios in video settings
2020-01-08 22:03:22 -08:00
<item row="3" column="0">
UI: Add service res/fps limitation support to settings Allows services to limit and enforce resolution and framerate values the user can select in the UI if "ignore service recommendations" is not checked. If the "ignore service recommendations" option is not checked, the user will not be able to select or use a resolution and/or framerate in the user interface that the service does not support. If "ignore service recommendations" is checked, it will work as it normally would, allowing any value to be used as per normal. Fortunately, and hopefully for the foreseeable future, there is only one service that enforces resolutions and framerates.
2020-11-13 09:21:24 -08:00
<widget class="QLabel" name="outputResLabel">
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
<property name="text">
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
<string>Basic.Settings.Video.ScaledResolution</string>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
UI: Add label/control buddy pairs for main windows
2016-02-21 11:19:26 -08:00
<property name="buddy">
<cstring>outputResolution</cstring>
</property>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</widget>
</item>
UI: Display aspect ratios in video settings
2020-01-08 22:03:22 -08:00
<item row="5" column="0">
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
<widget class="QLabel" name="label_11">
<property name="text">
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
<string>Basic.Settings.Video.DownscaleFilter</string>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
UI: Add label/control buddy pairs for main windows
2016-02-21 11:19:26 -08:00
<property name="buddy">
<cstring>downscaleFilter</cstring>
</property>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</widget>
</item>
UI: Display aspect ratios in video settings
2020-01-08 22:03:22 -08:00
<item row="5" column="1">
UI: Move Renderer/Adapter to advanced These really are advanced options that users shouldn't need to change normally, so moving them to advanced makes sense, and keeps them away from users who don't know what they're doing.
2016-01-25 05:55:01 -08:00
<widget class="QComboBox" name="downscaleFilter">
<property name="enabled">
<bool>true</bool>
</property>
</widget>
</item>
UI: Display aspect ratios in video settings
2020-01-08 22:03:22 -08:00
<item row="6" column="0">
Fix/update forms for main and settings window - Had the wrong names set for the up/down widgets for sources/scenes - Updated the settings dialog and gave most of the widgets actual object names - Added code for the settings window. Settings window should now at least display.
2014-01-24 20:19:50 -08:00
<widget class="QComboBox" name="fpsType">
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
<property name="sizePolicy">
<sizepolicy hsizetype="Expanding" vsizetype="Fixed">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="currentText">
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
<string>Basic.Settings.Video.FPSCommon</string>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
<property name="sizeAdjustPolicy">
<enum>QComboBox::AdjustToContents</enum>
</property>
<item>
<property name="text">
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
<string>Basic.Settings.Video.FPSCommon</string>
Fix/update forms for main and settings window - Had the wrong names set for the up/down widgets for sources/scenes - Updated the settings dialog and gave most of the widgets actual object names - Added code for the settings window. Settings window should now at least display.
2014-01-24 20:19:50 -08:00
</property>
</item>
<item>
<property name="text">
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
<string>Basic.Settings.Video.FPSInteger</string>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
</item>
<item>
<property name="text">
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
<string>Basic.Settings.Video.FPSFraction</string>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
</item>
</widget>
</item>
UI: Display aspect ratios in video settings
2020-01-08 22:03:22 -08:00
<item row="6" column="1">
Finish the rest of the settings dialog code - Move over the last of the original settings dialog code to QT. It was actually a bit easier to write in the QT version. wxWidgets was definitely not ideal for that because the pages would fully create/destroy every time. - [Win32] Fix os_dlopen so that it only appends .dll if not present - [MacOS] Fix name dialog text edit widget issue (it would be better if we could just use the list widget for editing labels, will have to look in to that in the future) - Tweak the settings UI a bit more and make 30 FPS default - Add a macro to convert a QString to a UTF-8 const char * string - Rename build/plugins to build/obs-plugins - Remove the last of the wxWidgets code
2014-01-26 14:36:15 -08:00
<widget class="QStackedWidget" name="fpsTypes">
Fix/update forms for main and settings window - Had the wrong names set for the up/down widgets for sources/scenes - Updated the settings dialog and gave most of the widgets actual object names - Added code for the settings window. Settings window should now at least display.
2014-01-24 20:19:50 -08:00
<property name="currentIndex">
UI: Upgrade stream link hotlink to a button Most of the top streaming services now have a link in the stream key label. Upgrading this button to a button clarifies the assistance for the important step of setting up a stream. Creates a new type of button for URL opening simply which also automatically updates the tootip to the current URL. Includes addition of Twitter/Periscope URL to make this feature more complete.
2019-10-24 21:05:43 -07:00
<number>1</number>
Fix/update forms for main and settings window - Had the wrong names set for the up/down widgets for sources/scenes - Updated the settings dialog and gave most of the widgets actual object names - Added code for the settings window. Settings window should now at least display.
2014-01-24 20:19:50 -08:00
</property>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
<widget class="QWidget" name="page">
<layout class="QHBoxLayout" name="horizontalLayout_2">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item alignment="Qt::AlignTop">
Fix/update forms for main and settings window - Had the wrong names set for the up/down widgets for sources/scenes - Updated the settings dialog and gave most of the widgets actual object names - Added code for the settings window. Settings window should now at least display.
2014-01-24 20:19:50 -08:00
<widget class="QComboBox" name="fpsCommon">
<property name="currentText">
UI: Add 24 NTSC as a common FPS value
2017-02-06 14:55:14 -08:00
<string notr="true">10</string>
Fix/update forms for main and settings window - Had the wrong names set for the up/down widgets for sources/scenes - Updated the settings dialog and gave most of the widgets actual object names - Added code for the settings window. Settings window should now at least display.
2014-01-24 20:19:50 -08:00
</property>
Finish the rest of the settings dialog code - Move over the last of the original settings dialog code to QT. It was actually a bit easier to write in the QT version. wxWidgets was definitely not ideal for that because the pages would fully create/destroy every time. - [Win32] Fix os_dlopen so that it only appends .dll if not present - [MacOS] Fix name dialog text edit widget issue (it would be better if we could just use the list widget for editing labels, will have to look in to that in the future) - Tweak the settings UI a bit more and make 30 FPS default - Add a macro to convert a QString to a UTF-8 const char * string - Rename build/plugins to build/obs-plugins - Remove the last of the wxWidgets code
2014-01-26 14:36:15 -08:00
<property name="currentIndex">
UI: Add 24 NTSC as a common FPS value
2017-02-06 14:55:14 -08:00
<number>0</number>
Finish the rest of the settings dialog code - Move over the last of the original settings dialog code to QT. It was actually a bit easier to write in the QT version. wxWidgets was definitely not ideal for that because the pages would fully create/destroy every time. - [Win32] Fix os_dlopen so that it only appends .dll if not present - [MacOS] Fix name dialog text edit widget issue (it would be better if we could just use the list widget for editing labels, will have to look in to that in the future) - Tweak the settings UI a bit more and make 30 FPS default - Add a macro to convert a QString to a UTF-8 const char * string - Rename build/plugins to build/obs-plugins - Remove the last of the wxWidgets code
2014-01-26 14:36:15 -08:00
</property>
Fix/update forms for main and settings window - Had the wrong names set for the up/down widgets for sources/scenes - Updated the settings dialog and gave most of the widgets actual object names - Added code for the settings window. Settings window should now at least display.
2014-01-24 20:19:50 -08:00
<item>
<property name="text">
<string notr="true">10</string>
</property>
</item>
<item>
<property name="text">
<string notr="true">20</string>
</property>
</item>
UI: Add 24 NTSC as a common FPS value
2017-02-06 14:55:14 -08:00
<item>
<property name="text">
<string>24 NTSC</string>
</property>
</item>
UI: Add PAL 25 & 50 FPS as common FPS values
2019-03-09 23:31:08 -08:00
<item>
<property name="text">
<string>25 PAL</string>
</property>
</item>
Fix/update forms for main and settings window - Had the wrong names set for the up/down widgets for sources/scenes - Updated the settings dialog and gave most of the widgets actual object names - Added code for the settings window. Settings window should now at least display.
2014-01-24 20:19:50 -08:00
<item>
<property name="text">
<string notr="true">29.97</string>
</property>
</item>
<item>
<property name="text">
<string notr="true">30</string>
</property>
</item>
<item>
<property name="text">
<string notr="true">48</string>
</property>
</item>
UI: Add PAL 25 & 50 FPS as common FPS values
2019-03-09 23:31:08 -08:00
<item>
<property name="text">
<string>50 PAL</string>
</property>
</item>
Fix/update forms for main and settings window - Had the wrong names set for the up/down widgets for sources/scenes - Updated the settings dialog and gave most of the widgets actual object names - Added code for the settings window. Settings window should now at least display.
2014-01-24 20:19:50 -08:00
<item>
<property name="text">
<string notr="true">59.94</string>
</property>
</item>
<item>
<property name="text">
<string notr="true">60</string>
</property>
</item>
</widget>
</item>
</layout>
</widget>
<widget class="QWidget" name="page_3">
<layout class="QHBoxLayout" name="horizontalLayout_3">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item alignment="Qt::AlignTop">
<widget class="QSpinBox" name="fpsInteger">
<property name="minimum">
<number>1</number>
</property>
<property name="maximum">
<number>120</number>
</property>
<property name="value">
<number>30</number>
</property>
</widget>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</item>
</layout>
</widget>
<widget class="QWidget" name="page_2">
<layout class="QFormLayout" name="formLayout_4">
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
<property name="fieldGrowthPolicy">
<enum>QFormLayout::ExpandingFieldsGrow</enum>
</property>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item row="0" column="1">
Fix/update forms for main and settings window - Had the wrong names set for the up/down widgets for sources/scenes - Updated the settings dialog and gave most of the widgets actual object names - Added code for the settings window. Settings window should now at least display.
2014-01-24 20:19:50 -08:00
<widget class="QSpinBox" name="fpsNumerator">
<property name="minimum">
<number>1</number>
</property>
<property name="maximum">
<number>1000000</number>
</property>
<property name="value">
<number>30</number>
</property>
</widget>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</item>
<item row="1" column="1">
Fix/update forms for main and settings window - Had the wrong names set for the up/down widgets for sources/scenes - Updated the settings dialog and gave most of the widgets actual object names - Added code for the settings window. Settings window should now at least display.
2014-01-24 20:19:50 -08:00
<widget class="QSpinBox" name="fpsDenominator">
<property name="minimum">
<number>1</number>
</property>
<property name="maximum">
<number>1000000</number>
</property>
</widget>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</item>
<item row="0" column="0">
<widget class="QLabel" name="label_12">
<property name="text">
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
<string>Basic.Settings.Video.Numerator</string>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="label_13">
<property name="text">
Add 'source selection' dialog 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.
2014-05-10 18:47:48 -07:00
<string>Basic.Settings.Video.Denominator</string>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</property>
</widget>
</item>
</layout>
</widget>
</widget>
</item>
UI: Display aspect ratios in video settings
2020-01-08 22:03:22 -08:00
<item row="7" column="1">
Fix video reset and apply new video settings This allows the changing of bideo settings without having to completely reset all graphics data. Will recreate internal output/conversion buffers and such and reset the main preview.
2014-02-22 19:14:19 -08:00
<widget class="QLabel" name="videoMsg">
Finish the rest of the settings dialog code - Move over the last of the original settings dialog code to QT. It was actually a bit easier to write in the QT version. wxWidgets was definitely not ideal for that because the pages would fully create/destroy every time. - [Win32] Fix os_dlopen so that it only appends .dll if not present - [MacOS] Fix name dialog text edit widget issue (it would be better if we could just use the list widget for editing labels, will have to look in to that in the future) - Tweak the settings UI a bit more and make 30 FPS default - Add a macro to convert a QString to a UTF-8 const char * string - Rename build/plugins to build/obs-plugins - Remove the last of the wxWidgets code
2014-01-26 14:36:15 -08:00
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Expanding">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string notr="true"/>
</property>
Fix video reset and apply new video settings This allows the changing of bideo settings without having to completely reset all graphics data. Will recreate internal output/conversion buffers and such and reset the main preview.
2014-02-22 19:14:19 -08:00
<property name="wordWrap">
<bool>true</bool>
</property>
UI: Add 4th aux audio input device Closes obsproject/obs-studio#1343
2018-06-26 11:41:32 -07:00
<property name="themeID" stdset="0">
<string>error</string>
</property>
Finish the rest of the settings dialog code - Move over the last of the original settings dialog code to QT. It was actually a bit easier to write in the QT version. wxWidgets was definitely not ideal for that because the pages would fully create/destroy every time. - [Win32] Fix os_dlopen so that it only appends .dll if not present - [MacOS] Fix name dialog text edit widget issue (it would be better if we could just use the list widget for editing labels, will have to look in to that in the future) - Tweak the settings UI a bit more and make 30 FPS default - Add a macro to convert a QString to a UTF-8 const char * string - Rename build/plugins to build/obs-plugins - Remove the last of the wxWidgets code
2014-01-26 14:36:15 -08:00
</widget>
</item>
UI: Display aspect ratios in video settings
2020-01-08 22:03:22 -08:00
<item row="3" column="1">
UI: Add service res/fps limitation support to settings Allows services to limit and enforce resolution and framerate values the user can select in the UI if "ignore service recommendations" is not checked. If the "ignore service recommendations" option is not checked, the user will not be able to select or use a resolution and/or framerate in the user interface that the service does not support. If "ignore service recommendations" is checked, it will work as it normally would, allowing any value to be used as per normal. Fortunately, and hopefully for the foreseeable future, there is only one service that enforces resolutions and framerates.
2020-11-13 09:21:24 -08:00
<layout class="QHBoxLayout" name="outputResLayout">
UI: Display aspect ratios in video settings
2020-01-08 22:03:22 -08:00
<property name="spacing">
<number>6</number>
</property>
<item>
<widget class="QComboBox" name="outputResolution">
<property name="sizePolicy">
<sizepolicy hsizetype="Expanding" vsizetype="Fixed">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="editable">
<bool>true</bool>
</property>
<property name="currentText">
<string notr="true"/>
</property>
</widget>
</item>
<item>
<widget class="QLabel" name="scaledAspect">
<property name="text">
<string>AspectRatio</string>
</property>
</widget>
</item>
</layout>
</item>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</layout>
</widget>
UI: Don't recreate entire Hotkey Settings tab This replaces the programmatic generation of the hotkeys tab with XML. Also fixes a memory leak. Reuses concepts from LoadAudioSources().
2022-01-02 22:41:28 -08:00
<widget class="QWidget" name="hotkeyPage">
<layout class="QVBoxLayout" name="verticalLayout_25">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<property name="leftMargin">
<number>9</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
UI: Don't recreate entire Hotkey Settings tab This replaces the programmatic generation of the hotkeys tab with XML. Also fixes a memory leak. Reuses concepts from LoadAudioSources().
2022-01-02 22:41:28 -08:00
<item>
<layout class="QGridLayout" name="hotkeySearchLayout">
<item row="0" column="0">
<widget class="QLabel" name="hotkeySearchLabel">
<property name="text">
<string>Basic.Settings.Hotkeys.Filter</string>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QLineEdit" name="hotkeyFilterSearch"/>
</item>
<item row="0" column="2">
<widget class="QLabel" name="hotkeyFilterLabel">
<property name="text">
<string>Basic.Settings.Hotkeys.FilterByHotkey</string>
</property>
</widget>
</item>
<item row="0" column="3">
<widget class="OBSHotkeyEdit" name="hotkeyFilterInput"/>
</item>
<item row="0" column="4">
<widget class="QPushButton" name="hotkeyFilterReset">
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="sizePolicy">
<sizepolicy hsizetype="Maximum" vsizetype="Maximum">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
UI: Don't recreate entire Hotkey Settings tab This replaces the programmatic generation of the hotkeys tab with XML. Also fixes a memory leak. Reuses concepts from LoadAudioSources().
2022-01-02 22:41:28 -08:00
<property name="minimumSize">
<size>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<width>0</width>
<height>0</height>
UI: Don't recreate entire Hotkey Settings tab This replaces the programmatic generation of the hotkeys tab with XML. Also fixes a memory leak. Reuses concepts from LoadAudioSources().
2022-01-02 22:41:28 -08:00
</size>
</property>
<property name="maximumSize">
<size>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<width>16777215</width>
<height>16777215</height>
UI: Don't recreate entire Hotkey Settings tab This replaces the programmatic generation of the hotkeys tab with XML. Also fixes a memory leak. Reuses concepts from LoadAudioSources().
2022-01-02 22:41:28 -08:00
</size>
</property>
<property name="baseSize">
<size>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<width>0</width>
<height>0</height>
UI: Don't recreate entire Hotkey Settings tab This replaces the programmatic generation of the hotkeys tab with XML. Also fixes a memory leak. Reuses concepts from LoadAudioSources().
2022-01-02 22:41:28 -08:00
</size>
</property>
<property name="toolTip">
<string>Clear</string>
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="icon">
<iconset resource="obs.qrc">
<normaloff>:/res/images/revert.svg</normaloff>:/res/images/revert.svg</iconset>
</property>
<property name="iconSize">
<size>
<width>20</width>
<height>20</height>
</size>
</property>
UI: Don't recreate entire Hotkey Settings tab This replaces the programmatic generation of the hotkeys tab with XML. Also fixes a memory leak. Reuses concepts from LoadAudioSources().
2022-01-02 22:41:28 -08:00
<property name="flat">
UI: Add new theme Yami
2022-06-30 10:11:50 -07:00
<bool>false</bool>
UI: Don't recreate entire Hotkey Settings tab This replaces the programmatic generation of the hotkeys tab with XML. Also fixes a memory leak. Reuses concepts from LoadAudioSources().
2022-01-02 22:41:28 -08:00
</property>
<property name="themeID" stdset="0">
UI: Add new theme Yami
2022-06-30 10:11:50 -07:00
<string>revertIcon</string>
UI: Don't recreate entire Hotkey Settings tab This replaces the programmatic generation of the hotkeys tab with XML. Also fixes a memory leak. Reuses concepts from LoadAudioSources().
2022-01-02 22:41:28 -08:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="toolButton" stdset="0">
<bool>true</bool>
UI: Don't recreate entire Hotkey Settings tab This replaces the programmatic generation of the hotkeys tab with XML. Also fixes a memory leak. Reuses concepts from LoadAudioSources().
2022-01-02 22:41:28 -08:00
</property>
</widget>
</item>
</layout>
</item>
<item>
<widget class="QScrollArea" name="hotkeyScrollArea">
<property name="widgetResizable">
<bool>true</bool>
</property>
<widget class="QWidget" name="hotkeyScrollContents">
UI: Fixup minor Qt Creator inconsistencies Qt Creator automatically adjusts these files when opened. Rather than contributors having to manually undo these changes, just apply them directly into the repository.
2022-03-19 16:32:07 -07:00
<property name="geometry">
<rect>
<x>0</x>
<y>0</y>
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<width>761</width>
<height>644</height>
UI: Fixup minor Qt Creator inconsistencies Qt Creator automatically adjusts these files when opened. Rather than contributors having to manually undo these changes, just apply them directly into the repository.
2022-03-19 16:32:07 -07:00
</rect>
</property>
UI: Don't recreate entire Hotkey Settings tab This replaces the programmatic generation of the hotkeys tab with XML. Also fixes a memory leak. Reuses concepts from LoadAudioSources().
2022-01-02 22:41:28 -08:00
<layout class="QFormLayout" name="hotkeyFormLayout">
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="verticalSpacing">
<number>0</number>
</property>
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<property name="leftMargin">
<number>9</number>
</property>
<property name="topMargin">
<number>2</number>
</property>
<property name="rightMargin">
<number>9</number>
</property>
<property name="bottomMargin">
<number>9</number>
</property>
UI: Don't recreate entire Hotkey Settings tab This replaces the programmatic generation of the hotkeys tab with XML. Also fixes a memory leak. Reuses concepts from LoadAudioSources().
2022-01-02 22:41:28 -08:00
</layout>
</widget>
</widget>
</item>
</layout>
UI: Add hotkeys page in settings dialog
2014-11-01 13:50:36 -07:00
</widget>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
<widget class="QWidget" name="accessPage">
<layout class="QVBoxLayout" name="formLayout_41">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
UI: Deduplicate UI element names Prevent some warnings from AutoUIC.
2022-07-28 11:29:45 -07:00
<widget class="QScrollArea" name="scrollArea_7">
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
<property name="frameShape">
<enum>QFrame::NoFrame</enum>
</property>
<property name="frameShadow">
<enum>QFrame::Plain</enum>
</property>
<property name="widgetResizable">
<bool>true</bool>
</property>
<widget class="QWidget" name="accessPageContents">
<property name="geometry">
<rect>
<x>0</x>
<y>0</y>
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<width>799</width>
<height>666</height>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</rect>
</property>
<layout class="QVBoxLayout" name="verticalLayout_42">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
<item>
UI: Deduplicate UI element names Prevent some warnings from AutoUIC.
2022-07-28 11:29:45 -07:00
<layout class="QVBoxLayout" name="verticalLayout_7" stretch="0,0">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<property name="leftMargin">
<number>9</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
<item>
<widget class="QGroupBox" name="colorsGroupBox">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Maximum">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="title">
<string>Basic.Settings.Accessibility.ColorOverrides</string>
</property>
<property name="checkable">
<bool>true</bool>
</property>
<property name="checked">
<bool>false</bool>
</property>
UI: Deduplicate UI element names Prevent some warnings from AutoUIC.
2022-07-28 11:29:45 -07:00
<layout class="QFormLayout" name="formLayout_8">
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="topMargin">
<number>2</number>
</property>
<item row="0" column="0">
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<widget class="QLabel" name="colorPresetLabel">
<property name="text">
<string>Basic.Settings.Accessibility.ColorOverrides.Preset</string>
</property>
<property name="buddy">
<cstring>colorPreset</cstring>
</property>
</widget>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</item>
<item row="0" column="1">
<widget class="QComboBox" name="colorPreset">
<item>
<property name="text">
<string>Basic.Settings.Accessibility.ColorOverrides.Preset.Default</string>
</property>
</item>
<item>
<property name="text">
<string>Basic.Settings.Accessibility.ColorOverrides.Preset.ColorBlind1</string>
</property>
</item>
<item>
<property name="text">
<string>Basic.Settings.Accessibility.ColorOverrides.Preset.Custom</string>
</property>
</item>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="colorSelectLabel_1">
<property name="text">
<string>Basic.Settings.Accessibility.ColorOverrides.SelectRed</string>
</property>
<property name="buddy">
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<cstring>choose1</cstring>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
</widget>
</item>
<item row="1" column="1">
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<layout class="QHBoxLayout" name="colorSelectLayout_1">
<property name="leftMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="topMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="rightMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="bottomMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<item>
<widget class="QLabel" name="color1">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="minimumSize">
<size>
<width>80</width>
<height>0</height>
</size>
</property>
<property name="maximumSize">
<size>
<width>16777215</width>
<height>16777215</height>
</size>
</property>
<property name="text">
<string notr="true">color here</string>
</property>
<property name="alignment">
<set>Qt::AlignCenter</set>
</property>
</widget>
</item>
<item>
<widget class="QPushButton" name="choose1">
<property name="minimumSize">
<size>
<width>0</width>
<height>0</height>
</size>
</property>
<property name="maximumSize">
<size>
<width>16777215</width>
<height>16777215</height>
</size>
</property>
<property name="text">
<string>Basic.PropertiesWindow.SelectColor</string>
</property>
</widget>
</item>
<item>
<spacer name="colorSpacer_1">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>40</width>
<height>0</height>
</size>
</property>
</spacer>
</item>
</layout>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</item>
<item row="2" column="0">
<widget class="QLabel" name="colorSelectLabel_2">
<property name="text">
<string>Basic.Settings.Accessibility.ColorOverrides.SelectGreen</string>
</property>
<property name="buddy">
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<cstring>choose2</cstring>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
</widget>
</item>
<item row="2" column="1">
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<layout class="QHBoxLayout" name="colorSelectLayout_2">
<property name="leftMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="topMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="rightMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="bottomMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<item>
<widget class="QLabel" name="color2">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="minimumSize">
<size>
<width>80</width>
<height>0</height>
</size>
</property>
<property name="maximumSize">
<size>
<width>16777215</width>
<height>16777215</height>
</size>
</property>
<property name="text">
<string notr="true">color here</string>
</property>
<property name="alignment">
<set>Qt::AlignCenter</set>
</property>
</widget>
</item>
<item>
<widget class="QPushButton" name="choose2">
<property name="minimumSize">
<size>
<width>0</width>
<height>0</height>
</size>
</property>
<property name="maximumSize">
<size>
<width>16777215</width>
<height>16777215</height>
</size>
</property>
<property name="text">
<string>Basic.PropertiesWindow.SelectColor</string>
</property>
</widget>
</item>
<item>
<spacer name="colorSpacer_2">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>40</width>
<height>0</height>
</size>
</property>
</spacer>
</item>
</layout>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</item>
<item row="3" column="0">
<widget class="QLabel" name="colorSelectLabel_3">
<property name="text">
<string>Basic.Settings.Accessibility.ColorOverrides.SelectBlue</string>
</property>
<property name="buddy">
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<cstring>choose3</cstring>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
</widget>
</item>
<item row="3" column="1">
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<layout class="QHBoxLayout" name="colorSelectLayout_3">
<property name="leftMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="topMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="rightMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QLabel" name="color3">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="minimumSize">
<size>
<width>80</width>
<height>0</height>
</size>
</property>
<property name="maximumSize">
<size>
<width>16777215</width>
<height>16777215</height>
</size>
</property>
<property name="text">
<string notr="true">color here</string>
</property>
<property name="alignment">
<set>Qt::AlignCenter</set>
</property>
</widget>
</item>
<item>
<widget class="QPushButton" name="choose3">
<property name="minimumSize">
<size>
<width>0</width>
<height>0</height>
</size>
</property>
<property name="maximumSize">
<size>
<width>16777215</width>
<height>16777215</height>
</size>
</property>
<property name="text">
<string>Basic.PropertiesWindow.SelectColor</string>
</property>
</widget>
</item>
<item>
<spacer name="colorSpacer_3">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>40</width>
<height>0</height>
</size>
</property>
</spacer>
</item>
</layout>
</item>
<item row="4" column="0">
<widget class="QLabel" name="colorSelectLabel_4">
<property name="text">
<string>Basic.Settings.Accessibility.ColorOverrides.MixerGreen</string>
</property>
<property name="buddy">
<cstring>choose4</cstring>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
</widget>
</item>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<item row="4" column="1">
<layout class="QHBoxLayout" name="colorSelectLayout_4">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QLabel" name="color4">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="minimumSize">
<size>
<width>80</width>
<height>0</height>
</size>
</property>
<property name="maximumSize">
<size>
<width>16777215</width>
<height>16777215</height>
</size>
</property>
<property name="text">
<string notr="true">color here</string>
</property>
<property name="alignment">
<set>Qt::AlignCenter</set>
</property>
</widget>
</item>
<item>
<widget class="QPushButton" name="choose4">
<property name="minimumSize">
<size>
<width>0</width>
<height>0</height>
</size>
</property>
<property name="maximumSize">
<size>
<width>16777215</width>
<height>16777215</height>
</size>
</property>
<property name="text">
<string>Basic.PropertiesWindow.SelectColor</string>
</property>
</widget>
</item>
<item>
<spacer name="colorSpacer_4">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>40</width>
<height>0</height>
</size>
</property>
</spacer>
</item>
</layout>
</item>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
<item row="5" column="0">
<widget class="QLabel" name="colorSelectLabel_5">
<property name="text">
<string>Basic.Settings.Accessibility.ColorOverrides.MixerYellow</string>
</property>
<property name="buddy">
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<cstring>choose5</cstring>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
</widget>
</item>
<item row="5" column="1">
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<layout class="QHBoxLayout" name="colorSelectLayout_5">
<property name="leftMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="topMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="rightMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="bottomMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<item>
<widget class="QLabel" name="color5">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="minimumSize">
<size>
<width>80</width>
<height>0</height>
</size>
</property>
<property name="maximumSize">
<size>
<width>16777215</width>
<height>16777215</height>
</size>
</property>
<property name="text">
<string notr="true">color here</string>
</property>
<property name="alignment">
<set>Qt::AlignCenter</set>
</property>
</widget>
</item>
<item>
<widget class="QPushButton" name="choose5">
<property name="minimumSize">
<size>
<width>0</width>
<height>0</height>
</size>
</property>
<property name="maximumSize">
<size>
<width>16777215</width>
<height>16777215</height>
</size>
</property>
<property name="text">
<string>Basic.PropertiesWindow.SelectColor</string>
</property>
</widget>
</item>
<item>
<spacer name="colorSpacer_5">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>40</width>
<height>0</height>
</size>
</property>
</spacer>
</item>
</layout>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</item>
<item row="6" column="0">
<widget class="QLabel" name="colorSelectLabel_6">
<property name="text">
<string>Basic.Settings.Accessibility.ColorOverrides.MixerRed</string>
</property>
<property name="buddy">
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<cstring>choose6</cstring>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
</widget>
</item>
<item row="6" column="1">
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<layout class="QHBoxLayout" name="colorSelectLayout_6">
<property name="leftMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="topMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="rightMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="bottomMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<item>
<widget class="QLabel" name="color6">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="minimumSize">
<size>
<width>80</width>
<height>0</height>
</size>
</property>
<property name="maximumSize">
<size>
<width>16777215</width>
<height>16777215</height>
</size>
</property>
<property name="text">
<string notr="true">color here</string>
</property>
<property name="alignment">
<set>Qt::AlignCenter</set>
</property>
</widget>
</item>
<item>
<widget class="QPushButton" name="choose6">
<property name="minimumSize">
<size>
<width>0</width>
<height>0</height>
</size>
</property>
<property name="maximumSize">
<size>
<width>16777215</width>
<height>16777215</height>
</size>
</property>
<property name="text">
<string>Basic.PropertiesWindow.SelectColor</string>
</property>
</widget>
</item>
<item>
<spacer name="colorSpacer_6">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>40</width>
<height>0</height>
</size>
</property>
</spacer>
</item>
</layout>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</item>
<item row="7" column="0">
<widget class="QLabel" name="colorSelectLabel_7">
<property name="text">
<string>Basic.Settings.Accessibility.ColorOverrides.MixerGreenActive</string>
</property>
<property name="buddy">
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<cstring>choose7</cstring>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
</widget>
</item>
<item row="7" column="1">
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<layout class="QHBoxLayout" name="colorSelectLayout_7">
<property name="leftMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="topMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="rightMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="bottomMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<item>
<widget class="QLabel" name="color7">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="minimumSize">
<size>
<width>80</width>
<height>0</height>
</size>
</property>
<property name="maximumSize">
<size>
<width>16777215</width>
<height>16777215</height>
</size>
</property>
<property name="text">
<string notr="true">color here</string>
</property>
<property name="alignment">
<set>Qt::AlignCenter</set>
</property>
</widget>
</item>
<item>
<widget class="QPushButton" name="choose7">
<property name="minimumSize">
<size>
<width>0</width>
<height>0</height>
</size>
</property>
<property name="maximumSize">
<size>
<width>16777215</width>
<height>16777215</height>
</size>
</property>
<property name="text">
<string>Basic.PropertiesWindow.SelectColor</string>
</property>
</widget>
</item>
<item>
<spacer name="colorSpacer_7">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>40</width>
<height>0</height>
</size>
</property>
</spacer>
</item>
</layout>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</item>
<item row="8" column="0">
<widget class="QLabel" name="colorSelectLabel_8">
<property name="text">
<string>Basic.Settings.Accessibility.ColorOverrides.MixerYellowActive</string>
</property>
<property name="buddy">
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<cstring>choose8</cstring>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
</widget>
</item>
<item row="8" column="1">
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<layout class="QHBoxLayout" name="colorSelectLayout_8">
<property name="leftMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="topMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="rightMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="bottomMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<item>
<widget class="QLabel" name="color8">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="minimumSize">
<size>
<width>80</width>
<height>0</height>
</size>
</property>
<property name="maximumSize">
<size>
<width>16777215</width>
<height>16777215</height>
</size>
</property>
<property name="text">
<string notr="true">color here</string>
</property>
<property name="alignment">
<set>Qt::AlignCenter</set>
</property>
</widget>
</item>
<item>
<widget class="QPushButton" name="choose8">
<property name="minimumSize">
<size>
<width>0</width>
<height>0</height>
</size>
</property>
<property name="maximumSize">
<size>
<width>16777215</width>
<height>16777215</height>
</size>
</property>
<property name="text">
<string>Basic.PropertiesWindow.SelectColor</string>
</property>
</widget>
</item>
<item>
<spacer name="colorSpacer_8">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>40</width>
<height>0</height>
</size>
</property>
</spacer>
</item>
</layout>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</item>
<item row="9" column="0">
<widget class="QLabel" name="colorSelectLabel_9">
<property name="text">
<string>Basic.Settings.Accessibility.ColorOverrides.MixerRedActive</string>
</property>
<property name="buddy">
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<cstring>choose9</cstring>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
</widget>
</item>
<item row="9" column="1">
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<layout class="QHBoxLayout" name="colorSelectLayout_9">
<property name="leftMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="topMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="rightMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<property name="bottomMargin">
<number>0</number>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</property>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<item>
<widget class="QLabel" name="color9">
<property name="sizePolicy">
<sizepolicy hsizetype="Preferred" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="minimumSize">
<size>
<width>80</width>
<height>0</height>
</size>
</property>
<property name="maximumSize">
<size>
<width>16777215</width>
<height>16777215</height>
</size>
</property>
<property name="text">
<string notr="true">color here</string>
</property>
<property name="alignment">
<set>Qt::AlignCenter</set>
</property>
</widget>
</item>
<item>
<widget class="QPushButton" name="choose9">
<property name="minimumSize">
<size>
<width>0</width>
<height>0</height>
</size>
</property>
<property name="maximumSize">
<size>
<width>16777215</width>
<height>16777215</height>
</size>
</property>
<property name="text">
<string>Basic.PropertiesWindow.SelectColor</string>
</property>
</widget>
</item>
<item>
<spacer name="colorSpacer_9">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>40</width>
<height>0</height>
</size>
</property>
</spacer>
</item>
</layout>
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
</item>
</layout>
</widget>
</item>
<item>
UI: Deduplicate UI element names Prevent some warnings from AutoUIC.
2022-07-28 11:29:45 -07:00
<spacer name="verticalSpacer_7">
UI: Add Accessibility menu to settings This change introduces an accessibility menu to settings, along with options for overriding the colors used by OBS in the mixer and in the preview to be more color blind friendly than the options provided by the current theme.
2021-07-02 22:55:47 -07:00
<property name="orientation">
<enum>Qt::Vertical</enum>
</property>
<property name="sizeType">
<enum>QSizePolicy::Expanding</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>20</width>
<height>40</height>
</size>
</property>
</spacer>
</item>
</layout>
</item>
</layout>
</widget>
</widget>
</item>
</layout>
</widget>
UI: Add 'Advanced' settings section Currently, this allows the setting of values such as: - Audio buffering time - Color format (still somewhat unsupported) - YUV color space (if a YUV format) = YUV color range (if a YUV format) More color formats will be added in the future, such as RGB and YUV 4:2:2 formats.
2015-02-11 12:55:06 -08:00
<widget class="QWidget" name="advancedPage">
UI: Add adv. settings checkbox for browser HW accel Adds a checkbox to advanced settings that allows the user to enable/disable browser source hardware acceleration on windows.
2018-08-10 06:12:16 -07:00
<layout class="QVBoxLayout" name="verticalLayout_16">
UI: Add 'Advanced' settings section Currently, this allows the setting of values such as: - Audio buffering time - Color format (still somewhat unsupported) - YUV color space (if a YUV format) = YUV color range (if a YUV format) More color formats will be added in the future, such as RGB and YUV 4:2:2 formats.
2015-02-11 12:55:06 -08:00
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QScrollArea" name="scrollArea">
<property name="frameShape">
<enum>QFrame::NoFrame</enum>
</property>
<property name="frameShadow">
<enum>QFrame::Plain</enum>
</property>
<property name="widgetResizable">
<bool>true</bool>
</property>
<widget class="QWidget" name="scrollAreaWidgetContents">
<property name="geometry">
<rect>
<x>0</x>
UI: Add dynamic bitrate support to the UI Adds dynamic bitrate support (marked as beta) to the advanced settings for now.
2019-08-15 08:50:09 -07:00
<y>0</y>
UI: Fix buttons in settings dialog - The buttons in the accessibility settings were a fixed height, so they would be rendered in a undesirable way with the Yami theme. - Also fixes clear button sizing issues in hotkeys sections
2022-08-04 16:58:09 -07:00
<width>826</width>
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<height>1000</height>
UI: Add 'Advanced' settings section Currently, this allows the setting of values such as: - Audio buffering time - Color format (still somewhat unsupported) - YUV color space (if a YUV format) = YUV color range (if a YUV format) More color formats will be added in the future, such as RGB and YUV 4:2:2 formats.
2015-02-11 12:55:06 -08:00
</rect>
</property>
UI: Add adv. settings checkbox for browser HW accel Adds a checkbox to advanced settings that allows the user to enable/disable browser source hardware acceleration on windows.
2018-08-10 06:12:16 -07:00
<layout class="QVBoxLayout" name="verticalLayout_23">
UI: Add 'Advanced' settings section Currently, this allows the setting of values such as: - Audio buffering time - Color format (still somewhat unsupported) - YUV color space (if a YUV format) = YUV color range (if a YUV format) More color formats will be added in the future, such as RGB and YUV 4:2:2 formats.
2015-02-11 12:55:06 -08:00
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>9</number>
</property>
UI: Add adv. settings checkbox for browser HW accel Adds a checkbox to advanced settings that allows the user to enable/disable browser source hardware acceleration on windows.
2018-08-10 06:12:16 -07:00
<item>
UI: Clean up Settings form markup This continues work from #5133 to correct UI file markup and save correctly in Qt Creator Defining alignment as an attribute in the <item> tag seems to be old behaviour that current versions of Qt Creator do not respect and will clobber these entries on save. The correct approach is to have alignment as a property element in the widget. As well, QWidgets that contain property definitions as well as a layout child item do not properly show up in the Qt Creator hierarchy. These properties are still invisibly applied but the QWidgets are not shown in Qt Creator and will get removed from the file after saving.
2021-08-16 22:41:57 -07:00
<widget class="QFrame" name="widget_11">
UI: Add adv. settings checkbox for browser HW accel Adds a checkbox to advanced settings that allows the user to enable/disable browser source hardware acceleration on windows.
2018-08-10 06:12:16 -07:00
<layout class="QVBoxLayout" name="verticalLayout_24">
UI: Make settings margins consistant Some settings pages would have different margins than others.
2022-08-27 03:26:19 -07:00
<property name="leftMargin">
<number>9</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
UI: Add process priority option for windows
2016-07-01 10:27:27 -07:00
<item>
<widget class="QGroupBox" name="advancedGeneralGroupBox">
<property name="title">
<string>Basic.Settings.General</string>
</property>
<layout class="QFormLayout" name="formLayout_22">
UI: Fix some settings layouts on non-windows systems Form layouts should laways have the setting "all non-fixed fields grow" to make it look consistent across operating systems.
2017-02-25 06:31:06 -08:00
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="topMargin">
<number>2</number>
</property>
UI: Add process priority option for windows
2016-07-01 10:27:27 -07:00
<item row="0" column="0">
<widget class="QLabel" name="processPriorityLabel">
<property name="text">
<string>Basic.Settings.Advanced.General.ProcessPriority</string>
</property>
<property name="buddy">
<cstring>processPriority</cstring>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QComboBox" name="processPriority"/>
</item>
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
<item row="1" column="0">
<spacer name="horizontalSpacer_13">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
<height>0</height>
</size>
</property>
</spacer>
</item>
UI: Add ShutDownActiveOutputsOnExit setting Adds a new setting to the general OBS settings, which can be checked in order to no longer show the "confirm close" dialog when there are still streams/recordings running.
2020-11-20 03:04:26 -08:00
<item row="2" column="1">
UI: Fixup minor Qt Creator inconsistencies Qt Creator automatically adjusts these files when opened. Rather than contributors having to manually undo these changes, just apply them directly into the repository.
2022-03-19 16:32:07 -07:00
<widget class="QCheckBox" name="confirmOnExit">
<property name="text">
<string>Basic.Settings.Advanced.General.ConfirmOnExit</string>
</property>
</widget>
UI: Add ShutDownActiveOutputsOnExit setting Adds a new setting to the general OBS settings, which can be checked in order to no longer show the "confirm close" dialog when there are still streams/recordings running.
2020-11-20 03:04:26 -08:00
</item>
UI: Add process priority option for windows
2016-07-01 10:27:27 -07:00
</layout>
</widget>
</item>
UI: Add 'Advanced' settings section Currently, this allows the setting of values such as: - Audio buffering time - Color format (still somewhat unsupported) - YUV color space (if a YUV format) = YUV color range (if a YUV format) More color formats will be added in the future, such as RGB and YUV 4:2:2 formats.
2015-02-11 12:55:06 -08:00
<item>
<widget class="QGroupBox" name="advancedVideoContainer">
<property name="title">
<string>Basic.Settings.Video</string>
</property>
<layout class="QFormLayout" name="formLayout_14">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
<property name="topMargin">
<number>2</number>
</property>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<item row="0" column="0">
<widget class="QLabel" name="rendererLabel">
<property name="text">
<string>Basic.Settings.Video.Renderer</string>
</property>
<property name="buddy">
<cstring>renderer</cstring>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QComboBox" name="renderer">
<property name="currentText">
<string notr="true"/>
</property>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="adapterLabel">
<property name="text">
<string>Basic.Settings.Video.Adapter</string>
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="buddy">
<cstring>adapter</cstring>
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QComboBox" name="adapter">
<property name="enabled">
<bool>false</bool>
</property>
<property name="currentText">
<string notr="true"/>
</property>
</widget>
</item>
UI: Move Renderer/Adapter to advanced These really are advanced options that users shouldn't need to change normally, so moving them to advanced makes sense, and keeps them away from users who don't know what they're doing.
2016-01-25 05:55:01 -08:00
<item row="2" column="0">
UI: Add 'Advanced' settings section Currently, this allows the setting of values such as: - Audio buffering time - Color format (still somewhat unsupported) - YUV color space (if a YUV format) = YUV color range (if a YUV format) More color formats will be added in the future, such as RGB and YUV 4:2:2 formats.
2015-02-11 12:55:06 -08:00
<widget class="QLabel" name="label_30">
<property name="minimumSize">
<size>
UI: Implement theme selection option OBS will offer the user a list of themes which are .qss files inside data/obs-studio/themes. If no theme is found in the configuration, it loads the default theme for the system.
2015-02-16 23:45:34 -08:00
<width>0</width>
UI: Add 'Advanced' settings section Currently, this allows the setting of values such as: - Audio buffering time - Color format (still somewhat unsupported) - YUV color space (if a YUV format) = YUV color range (if a YUV format) More color formats will be added in the future, such as RGB and YUV 4:2:2 formats.
2015-02-11 12:55:06 -08:00
<height>0</height>
</size>
</property>
<property name="text">
<string>Basic.Settings.Advanced.Video.ColorFormat</string>
</property>
<property name="alignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
UI: Add label/control buddy pairs for main windows
2016-02-21 11:19:26 -08:00
<property name="buddy">
<cstring>colorFormat</cstring>
</property>
UI: Add 'Advanced' settings section Currently, this allows the setting of values such as: - Audio buffering time - Color format (still somewhat unsupported) - YUV color space (if a YUV format) = YUV color range (if a YUV format) More color formats will be added in the future, such as RGB and YUV 4:2:2 formats.
2015-02-11 12:55:06 -08:00
</widget>
</item>
UI: Move Renderer/Adapter to advanced These really are advanced options that users shouldn't need to change normally, so moving them to advanced makes sense, and keeps them away from users who don't know what they're doing.
2016-01-25 05:55:01 -08:00
<item row="2" column="1">
UI: Add more information to describe output format In advanced settings Also enable translation for color format
2022-07-12 03:08:26 -07:00
<widget class="QComboBox" name="colorFormat"/>
UI: Add 'Advanced' settings section Currently, this allows the setting of values such as: - Audio buffering time - Color format (still somewhat unsupported) - YUV color space (if a YUV format) = YUV color range (if a YUV format) More color formats will be added in the future, such as RGB and YUV 4:2:2 formats.
2015-02-11 12:55:06 -08:00
</item>
libobs, UI: Add SDR white nits option
2022-02-20 20:31:30 -08:00
<item row="3" column="0">
<widget class="QLabel" name="label_33">
<property name="text">
<string>Basic.Settings.Advanced.Video.ColorSpace</string>
UI: Add 'Advanced' settings section Currently, this allows the setting of values such as: - Audio buffering time - Color format (still somewhat unsupported) - YUV color space (if a YUV format) = YUV color range (if a YUV format) More color formats will be added in the future, such as RGB and YUV 4:2:2 formats.
2015-02-11 12:55:06 -08:00
</property>
libobs, UI: Add SDR white nits option
2022-02-20 20:31:30 -08:00
<property name="buddy">
<cstring>colorSpace</cstring>
UI: Add label/control buddy pairs for main windows
2016-02-21 11:19:26 -08:00
</property>
libobs, UI: Add SDR white nits option
2022-02-20 20:31:30 -08:00
</widget>
UI: Move Renderer/Adapter to advanced These really are advanced options that users shouldn't need to change normally, so moving them to advanced makes sense, and keeps them away from users who don't know what they're doing.
2016-01-25 05:55:01 -08:00
</item>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<item row="3" column="1">
<layout class="QHBoxLayout" name="horizontalLayout_20">
<property name="leftMargin">
<number>0</number>
UI: Move Renderer/Adapter to advanced These really are advanced options that users shouldn't need to change normally, so moving them to advanced makes sense, and keeps them away from users who don't know what they're doing.
2016-01-25 05:55:01 -08:00
</property>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<property name="topMargin">
<number>0</number>
UI: Add label/control buddy pairs for main windows
2016-02-21 11:19:26 -08:00
</property>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<property name="rightMargin">
<number>0</number>
UI: Move Renderer/Adapter to advanced These really are advanced options that users shouldn't need to change normally, so moving them to advanced makes sense, and keeps them away from users who don't know what they're doing.
2016-01-25 05:55:01 -08:00
</property>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<property name="bottomMargin">
<number>0</number>
UI: Move Renderer/Adapter to advanced These really are advanced options that users shouldn't need to change normally, so moving them to advanced makes sense, and keeps them away from users who don't know what they're doing.
2016-01-25 05:55:01 -08:00
</property>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<item>
UI: Add Rec. 2020 space and I010/P010 formats Also localize color spaces with improved naming. Should be compatible with existing user profiles.
2022-01-19 00:51:25 -08:00
<widget class="QComboBox" name="colorSpace"/>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
</item>
<item>
<widget class="QLabel" name="label_34">
<property name="sizePolicy">
<sizepolicy hsizetype="Maximum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string>Basic.Settings.Advanced.Video.ColorRange</string>
</property>
<property name="buddy">
<cstring>colorRange</cstring>
</property>
</widget>
</item>
<item>
<widget class="QComboBox" name="colorRange"/>
</item>
</layout>
UI: Move Renderer/Adapter to advanced These really are advanced options that users shouldn't need to change normally, so moving them to advanced makes sense, and keeps them away from users who don't know what they're doing.
2016-01-25 05:55:01 -08:00
</item>
libobs, UI: Add SDR white nits option
2022-02-20 20:31:30 -08:00
<item row="4" column="0">
<widget class="QLabel" name="label_sdrWhiteLevel">
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
<property name="text">
libobs, UI: Add SDR white nits option
2022-02-20 20:31:30 -08:00
<string>Basic.Settings.Advanced.Video.SdrWhiteLevel</string>
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
</property>
<property name="buddy">
libobs, UI: Add SDR white nits option
2022-02-20 20:31:30 -08:00
<cstring>sdrWhiteLevel</cstring>
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
</property>
</widget>
</item>
libobs, UI: Add SDR white nits option
2022-02-20 20:31:30 -08:00
<item row="4" column="1">
<layout class="QHBoxLayout" name="horizontalLayout_sdrPaperWhite">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QSpinBox" name="sdrWhiteLevel">
UI: Move HDR units for settings to suffix
2022-06-30 03:55:21 -07:00
<property name="suffix">
<string notr="true"> nits</string>
</property>
libobs, UI: Add SDR white nits option
2022-02-20 20:31:30 -08:00
<property name="minimum">
<number>80</number>
</property>
<property name="maximum">
<number>480</number>
</property>
</widget>
</item>
libobs,UI: Support HLG nominal peak level HLG output uses MovieLabs-recommended procedure. - If peak luminance is greater than 1000, use maxRGB EETF to 1000. - Otherwise, don't tonemap. - Then use normal HLG conversion procedure with gamma 1.2 (1000 nits).
2022-04-10 12:31:08 -07:00
<item>
<widget class="QLabel" name="label_hdrNominalPeakLevel">
<property name="sizePolicy">
<sizepolicy hsizetype="Maximum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string>Basic.Settings.Advanced.Video.HdrNominalPeakLevel</string>
</property>
<property name="buddy">
<cstring>hdrNominalPeakLevel</cstring>
</property>
</widget>
</item>
<item>
<widget class="QSpinBox" name="hdrNominalPeakLevel">
UI: Move HDR units for settings to suffix
2022-06-30 03:55:21 -07:00
<property name="suffix">
<string notr="true"> nits</string>
</property>
libobs,UI: Support HLG nominal peak level HLG output uses MovieLabs-recommended procedure. - If peak luminance is greater than 1000, use maxRGB EETF to 1000. - Otherwise, don't tonemap. - Then use normal HLG conversion procedure with gamma 1.2 (1000 nits).
2022-04-10 12:31:08 -07:00
<property name="minimum">
<number>400</number>
</property>
<property name="maximum">
<number>10000</number>
</property>
</widget>
</item>
libobs, UI: Add SDR white nits option
2022-02-20 20:31:30 -08:00
</layout>
</item>
<item row="5" column="1">
<layout class="QHBoxLayout" name="horizontalLayout_18">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QCheckBox" name="disableOSXVSync">
<property name="text">
<string>DisableOSXVSync</string>
</property>
</widget>
</item>
<item>
<widget class="QCheckBox" name="resetOSXVSync">
<property name="text">
<string>ResetOSXVSyncOnExit</string>
</property>
</widget>
</item>
</layout>
</item>
<item row="6" column="0">
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
<spacer name="horizontalSpacer_12">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
<height>20</height>
</size>
</property>
</spacer>
</item>
UI: Add 'Advanced' settings section Currently, this allows the setting of values such as: - Audio buffering time - Color format (still somewhat unsupported) - YUV color space (if a YUV format) = YUV color range (if a YUV format) More color formats will be added in the future, such as RGB and YUV 4:2:2 formats.
2015-02-11 12:55:06 -08:00
</layout>
</widget>
</item>
UI: Add file formatting options for recording Allows the user to specify custom formatting for their recording file names with many formatting options, viewed via tooltip. The options have been added to the advanced settings section. Closes jp9000/obs-studio#507
2016-03-25 02:43:38 -07:00
<item>
<widget class="QGroupBox" name="groupBox_6">
<property name="title">
<string>Basic.Settings.Output.Adv.Recording</string>
</property>
<layout class="QFormLayout" name="formLayout_17">
UI: Fix some settings layouts on non-windows systems Form layouts should laways have the setting "all non-fixed fields grow" to make it look consistent across operating systems.
2017-02-25 06:31:06 -08:00
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
UI: Add file prefix/suffix options for replay buffer Adds the ability to use a specific prefix and/or suffix on replay buffer filenames to distinguish them from normal recordings. Defaults to having the prefix "Replay".
2016-12-09 14:42:14 -08:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
<property name="topMargin">
<number>2</number>
</property>
UI: Add file formatting options for recording Allows the user to specify custom formatting for their recording file names with many formatting options, viewed via tooltip. The options have been added to the advanced settings section. Closes jp9000/obs-studio#507
2016-03-25 02:43:38 -07:00
<item row="0" column="0">
<widget class="QLabel" name="label_7">
<property name="text">
<string>Basic.Settings.Output.Adv.Recording.Filename</string>
</property>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<property name="buddy">
<cstring>filenameFormatting</cstring>
</property>
UI: Add file formatting options for recording Allows the user to specify custom formatting for their recording file names with many formatting options, viewed via tooltip. The options have been added to the advanced settings section. Closes jp9000/obs-studio#507
2016-03-25 02:43:38 -07:00
</widget>
</item>
<item row="0" column="1">
<widget class="QLineEdit" name="filenameFormatting"/>
</item>
<item row="1" column="1">
<widget class="QCheckBox" name="overwriteIfExists">
<property name="text">
<string>Basic.Settings.Output.Adv.Recording.OverwriteIfExists</string>
</property>
</widget>
</item>
UI: Add option to auto remux
2017-05-08 04:53:35 -07:00
<item row="3" column="1">
UI: Add file prefix/suffix options for replay buffer Adds the ability to use a specific prefix and/or suffix on replay buffer filenames to distinguish them from normal recordings. Defaults to having the prefix "Replay".
2016-12-09 14:42:14 -08:00
<layout class="QHBoxLayout" name="horizontalLayout_14">
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QLineEdit" name="simpleRBPrefix"/>
</item>
<item>
<widget class="QLabel" name="label_58">
<property name="text">
<string>Basic.Settings.Output.ReplayBuffer.Suffix</string>
</property>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<property name="buddy">
<cstring>simpleRBSuffix</cstring>
</property>
UI: Add file prefix/suffix options for replay buffer Adds the ability to use a specific prefix and/or suffix on replay buffer filenames to distinguish them from normal recordings. Defaults to having the prefix "Replay".
2016-12-09 14:42:14 -08:00
</widget>
</item>
<item>
<widget class="QLineEdit" name="simpleRBSuffix"/>
</item>
</layout>
</item>
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
<item row="3" column="0">
<widget class="QLabel" name="label_57">
<property name="text">
<string>Basic.Settings.Output.ReplayBuffer.Prefix</string>
</property>
<property name="buddy">
<cstring>simpleRBPrefix</cstring>
</property>
</widget>
</item>
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
<item row="1" column="0">
<spacer name="horizontalSpacer_10">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
<height>20</height>
</size>
</property>
UI: Add option to auto remux
2017-05-08 04:53:35 -07:00
</spacer>
</item>
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
<item row="2" column="1">
<widget class="QCheckBox" name="autoRemux">
<property name="text">
<string>Basic.Settings.Advanced.AutoRemux</string>
</property>
</widget>
</item>
UI: Add option to auto remux
2017-05-08 04:53:35 -07:00
<item row="2" column="0">
<spacer name="horizontalSpacer_16">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>40</width>
<height>20</height>
</size>
</property>
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
</spacer>
</item>
UI: Add file formatting options for recording Allows the user to specify custom formatting for their recording file names with many formatting options, viewed via tooltip. The options have been added to the advanced settings section. Closes jp9000/obs-studio#507
2016-03-25 02:43:38 -07:00
</layout>
</widget>
</item>
UI: Add stream delay options to advanced settings I added stream delay options to advanced settings not just because I feel it's an advanced option, but also to reduce clutter in the outputs section and its sub-sections, which already have far too many options as it is.
2015-09-06 16:12:03 -07:00
<item>
<widget class="QGroupBox" name="groupBox_5">
<property name="title">
<string>Basic.Settings.Advanced.StreamDelay</string>
</property>
<layout class="QFormLayout" name="formLayout_18">
UI: Fix some settings layouts on non-windows systems Form layouts should laways have the setting "all non-fixed fields grow" to make it look consistent across operating systems.
2017-02-25 06:31:06 -08:00
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<property name="topMargin">
<number>2</number>
</property>
UI: Add stream delay options to advanced settings I added stream delay options to advanced settings not just because I feel it's an advanced option, but also to reduce clutter in the outputs section and its sub-sections, which already have far too many options as it is.
2015-09-06 16:12:03 -07:00
<item row="1" column="0">
<widget class="QLabel" name="label_56">
<property name="text">
<string>Basic.Settings.Advanced.StreamDelay.Duration</string>
</property>
UI: Add label/control buddy pairs for main windows
2016-02-21 11:19:26 -08:00
<property name="buddy">
<cstring>streamDelaySec</cstring>
</property>
UI: Add stream delay options to advanced settings I added stream delay options to advanced settings not just because I feel it's an advanced option, but also to reduce clutter in the outputs section and its sub-sections, which already have far too many options as it is.
2015-09-06 16:12:03 -07:00
</widget>
</item>
<item row="1" column="1">
UI: Clean up Settings form markup This continues work from #5133 to correct UI file markup and save correctly in Qt Creator Defining alignment as an attribute in the <item> tag seems to be old behaviour that current versions of Qt Creator do not respect and will clobber these entries on save. The correct approach is to have alignment as a property element in the widget. As well, QWidgets that contain property definitions as well as a layout child item do not properly show up in the Qt Creator hierarchy. These properties are still invisibly applied but the QWidgets are not shown in Qt Creator and will get removed from the file after saving.
2021-08-16 22:41:57 -07:00
<widget class="QFrame" name="widget_12">
UI: Add stream delay options to advanced settings I added stream delay options to advanced settings not just because I feel it's an advanced option, but also to reduce clutter in the outputs section and its sub-sections, which already have far too many options as it is.
2015-09-06 16:12:03 -07:00
<property name="enabled">
<bool>true</bool>
</property>
<layout class="QHBoxLayout" name="horizontalLayout_13">
<property name="spacing">
<number>5</number>
</property>
<property name="leftMargin">
<number>0</number>
</property>
<property name="topMargin">
<number>0</number>
</property>
<property name="rightMargin">
<number>0</number>
</property>
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QSpinBox" name="streamDelaySec">
<property name="enabled">
<bool>true</bool>
</property>
<property name="sizePolicy">
<sizepolicy hsizetype="Maximum" vsizetype="Fixed">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="minimumSize">
<size>
<width>80</width>
<height>0</height>
</size>
</property>
<property name="suffix">
UI, obs-plugins: Add spinbox suffixes where necessary
2019-07-18 00:38:50 -07:00
<string notr="true"> s</string>
UI: Add stream delay options to advanced settings I added stream delay options to advanced settings not just because I feel it's an advanced option, but also to reduce clutter in the outputs section and its sub-sections, which already have far too many options as it is.
2015-09-06 16:12:03 -07:00
</property>
<property name="minimum">
<number>1</number>
</property>
<property name="maximum">
<number>1800</number>
</property>
</widget>
</item>
<item>
<widget class="QLabel" name="streamDelayInfo">
<property name="text">
<string notr="true">Estimated RAM goes here</string>
</property>
</widget>
</item>
</layout>
</widget>
</item>
<item row="2" column="1">
<widget class="QCheckBox" name="streamDelayPreserve">
<property name="text">
<string>Basic.Settings.Advanced.StreamDelay.Preserve</string>
</property>
</widget>
</item>
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
<item row="0" column="1">
<widget class="QCheckBox" name="streamDelayEnable">
<property name="text">
<string>Enable</string>
</property>
<property name="checked">
<bool>true</bool>
</property>
</widget>
</item>
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
<item row="2" column="0">
<spacer name="horizontalSpacer_9">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
<height>20</height>
</size>
</property>
</spacer>
</item>
UI: Add stream delay options to advanced settings I added stream delay options to advanced settings not just because I feel it's an advanced option, but also to reduce clutter in the outputs section and its sub-sections, which already have far too many options as it is.
2015-09-06 16:12:03 -07:00
</layout>
</widget>
</item>
UI: Move reconnect options to advanced settings This is mostly just to remove the unnecessary clutter from the output sections. The reconnect settings are generally rarely modified by users as it is.
2015-09-10 19:10:40 -07:00
<item>
<widget class="QGroupBox" name="groupBox_7">
<property name="title">
<string>Basic.Settings.Output.Reconnect</string>
</property>
<layout class="QFormLayout" name="formLayout_19">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="topMargin">
<number>2</number>
</property>
UI: Move reconnect options to advanced settings This is mostly just to remove the unnecessary clutter from the output sections. The reconnect settings are generally rarely modified by users as it is.
2015-09-10 19:10:40 -07:00
<item row="0" column="1">
<widget class="QCheckBox" name="reconnectEnable">
<property name="text">
<string>Enable</string>
</property>
<property name="checked">
<bool>true</bool>
</property>
</widget>
</item>
<item row="1" column="1">
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<layout class="QHBoxLayout" name="horizontalLayout_19">
<property name="leftMargin">
<number>0</number>
UI: Move reconnect options to advanced settings This is mostly just to remove the unnecessary clutter from the output sections. The reconnect settings are generally rarely modified by users as it is.
2015-09-10 19:10:40 -07:00
</property>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<property name="topMargin">
<number>0</number>
UI: Move reconnect options to advanced settings This is mostly just to remove the unnecessary clutter from the output sections. The reconnect settings are generally rarely modified by users as it is.
2015-09-10 19:10:40 -07:00
</property>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<property name="rightMargin">
<number>0</number>
UI: Add label/control buddy pairs for main windows
2016-02-21 11:19:26 -08:00
</property>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<property name="bottomMargin">
<number>0</number>
</property>
<item>
<widget class="QSpinBox" name="reconnectRetryDelay">
UI, obs-plugins: Add spinbox suffixes where necessary
2019-07-18 00:38:50 -07:00
<property name="suffix">
<string> s</string>
</property>
UI: Force minimum reconnect delay of 1 second Setting this to zero breaks reconnecting (and OBS) entirely as various parts of the reconnect system do not handle zero values properly, and there are also possible race conditions with the reconnect thread. Set a minimum of 1 second to avoid this.
2021-09-15 11:16:07 -07:00
<property name="minimum">
<number>1</number>
</property>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<property name="maximum">
<number>30</number>
</property>
</widget>
</item>
<item>
<widget class="QLabel" name="label_22">
<property name="sizePolicy">
<sizepolicy hsizetype="Maximum" vsizetype="Preferred">
<horstretch>0</horstretch>
<verstretch>0</verstretch>
</sizepolicy>
</property>
<property name="text">
<string>Basic.Settings.Output.MaxRetries</string>
</property>
<property name="buddy">
<cstring>reconnectMaxRetries</cstring>
</property>
</widget>
</item>
<item>
<widget class="QSpinBox" name="reconnectMaxRetries">
<property name="minimum">
<number>1</number>
</property>
<property name="maximum">
<number>10000</number>
</property>
</widget>
</item>
</layout>
UI: Move reconnect options to advanced settings This is mostly just to remove the unnecessary clutter from the output sections. The reconnect settings are generally rarely modified by users as it is.
2015-09-10 19:10:40 -07:00
</item>
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
<item row="1" column="0">
<widget class="QLabel" name="label_17">
<property name="text">
<string>Basic.Settings.Output.RetryDelay</string>
</property>
<property name="buddy">
<cstring>reconnectRetryDelay</cstring>
</property>
</widget>
</item>
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
<item row="0" column="0">
<spacer name="horizontalSpacer_8">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
<height>20</height>
</size>
</property>
</spacer>
</item>
UI: Move reconnect options to advanced settings This is mostly just to remove the unnecessary clutter from the output sections. The reconnect settings are generally rarely modified by users as it is.
2015-09-10 19:10:40 -07:00
</layout>
</widget>
</item>
UI: Add "Bind to IP" setting to advanced settings
2016-07-29 08:30:54 -07:00
<item>
UI: Disable network settings while outputs active
2017-03-05 14:24:29 -08:00
<widget class="QGroupBox" name="advNetworkGroupBox">
UI: Add "Bind to IP" setting to advanced settings
2016-07-29 08:30:54 -07:00
<property name="title">
<string>Basic.Settings.Advanced.Network</string>
</property>
<layout class="QFormLayout" name="formLayout_23">
<property name="fieldGrowthPolicy">
<enum>QFormLayout::AllNonFixedFieldsGrow</enum>
</property>
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
<property name="topMargin">
<number>2</number>
</property>
UI: Hide network features if a non-RTMP service is set Reimplementation of bc80d0c and f2e6122, because they have to be reverted by 0b9a8aa.
2022-07-18 22:44:12 -07:00
<item row="0" column="1">
<widget class="QLabel" name="advNetworkDisabled">
<property name="text">
<string>Basic.Settings.Advanced.Network.Disabled</string>
</property>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="bindToIPLabel">
UI: Add "Bind to IP" setting to advanced settings
2016-07-29 08:30:54 -07:00
<property name="text">
<string>Basic.Settings.Advanced.Network.BindToIP</string>
</property>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<property name="buddy">
<cstring>bindToIP</cstring>
</property>
UI: Add "Bind to IP" setting to advanced settings
2016-07-29 08:30:54 -07:00
</widget>
</item>
UI: Hide network features if a non-RTMP service is set Reimplementation of bc80d0c and f2e6122, because they have to be reverted by 0b9a8aa.
2022-07-18 22:44:12 -07:00
<item row="1" column="1">
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
<widget class="QComboBox" name="bindToIP"/>
</item>
UI: Hide network features if a non-RTMP service is set Reimplementation of bc80d0c and f2e6122, because they have to be reverted by 0b9a8aa.
2022-07-18 22:44:12 -07:00
<item row="3" column="1">
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<widget class="QCheckBox" name="enableNewSocketLoop">
<property name="text">
<string>Basic.Settings.Advanced.Network.EnableNewSocketLoop</string>
</property>
</widget>
</item>
UI: Hide network features if a non-RTMP service is set Reimplementation of bc80d0c and f2e6122, because they have to be reverted by 0b9a8aa.
2022-07-18 22:44:12 -07:00
<item row="4" column="1">
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<widget class="QCheckBox" name="enableLowLatencyMode">
<property name="enabled">
<bool>false</bool>
</property>
<property name="text">
<string>Basic.Settings.Advanced.Network.EnableLowLatencyMode</string>
</property>
</widget>
</item>
UI: Hide network features if a non-RTMP service is set Reimplementation of bc80d0c and f2e6122, because they have to be reverted by 0b9a8aa.
2022-07-18 22:44:12 -07:00
<item row="3" column="0">
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
<spacer name="horizontalSpacer_7">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
UI: Add dynamic bitrate support to the UI Adds dynamic bitrate support (marked as beta) to the advanced settings for now.
2019-08-15 08:50:09 -07:00
<height>1</height>
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
</size>
</property>
</spacer>
</item>
UI: Hide network features if a non-RTMP service is set Reimplementation of bc80d0c and f2e6122, because they have to be reverted by 0b9a8aa.
2022-07-18 22:44:12 -07:00
<item row="2" column="1">
Revert "UI: Various screen reader fixes" This reverts commit b5843caa484068d6fcc5f5fe8ee2dc06078500ff. This breaks some hotkeys because the signals are tied to a signal which is now triggered because "toggled" is used instead of "clicked", so just revert it for now for the release and look at it later post-patch.
2019-09-12 13:55:31 -07:00
<widget class="QCheckBox" name="dynBitrate">
<property name="toolTip">
<string>Basic.Settings.Output.DynamicBitrate.TT</string>
</property>
<property name="text">
<string>Basic.Settings.Output.DynamicBitrate.Beta</string>
</property>
</widget>
</item>
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
</layout>
</widget>
</item>
UI: Add adv. settings checkbox for browser HW accel Adds a checkbox to advanced settings that allows the user to enable/disable browser source hardware acceleration on windows.
2018-08-10 06:12:16 -07:00
<item>
<widget class="QGroupBox" name="sourcesGroup">
<property name="title">
<string>Basic.Main.Sources</string>
</property>
<layout class="QFormLayout" name="formLayout_34">
<property name="topMargin">
<number>2</number>
</property>
<item row="0" column="0">
<spacer name="horizontalSpacer_15">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
<height>20</height>
</size>
</property>
</spacer>
</item>
<item row="0" column="1">
<widget class="QCheckBox" name="browserHWAccel">
<property name="text">
<string>BrowserSource.EnableHardwareAcceleration</string>
</property>
</widget>
</item>
</layout>
</widget>
</item>
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
<item>
<widget class="QGroupBox" name="groupBox_17">
<property name="title">
<string>Basic.Settings.Hotkeys</string>
</property>
<layout class="QFormLayout" name="formLayout_33">
UI: Add ability to disable hotkeys when not in focus
2019-07-22 01:20:12 -07:00
<property name="labelAlignment">
<set>Qt::AlignRight|Qt::AlignTrailing|Qt::AlignVCenter</set>
</property>
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
<property name="topMargin">
<number>2</number>
</property>
UI: Add ability to disable hotkeys when not in focus
2019-07-22 01:20:12 -07:00
<item row="0" column="0">
<widget class="QLabel" name="label_21">
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
<property name="text">
UI: Add ability to disable hotkeys when not in focus
2019-07-22 01:20:12 -07:00
<string>Basic.Settings.Advanced.Hotkeys.HotkeyFocusBehavior</string>
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
</property>
</widget>
</item>
UI: Add ability to disable hotkeys when not in focus
2019-07-22 01:20:12 -07:00
<item row="0" column="1">
<widget class="QComboBox" name="hotkeyFocusType"/>
</item>
<item row="1" column="0">
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
<spacer name="horizontalSpacer_14">
<property name="orientation">
<enum>Qt::Horizontal</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>170</width>
UI: Add ability to disable hotkeys when not in focus
2019-07-22 01:20:12 -07:00
<height>0</height>
UI: Add opt. to enable/disable in-focus hotkey blocking Adds an option to enable/disable blocking hotkeys when the window is in focus which is normally used in order to prevent hotkey/shortcut conflicts. This does not apply to the settings window; the hotkey behavior is unchanged with the settings window (in order to prevent hotkeys from being used while setting hotkeys for example). Closes obsproject/obs-studio#1267
2018-05-06 16:48:27 -07:00
</size>
</property>
</spacer>
</item>
UI: Add "Bind to IP" setting to advanced settings
2016-07-29 08:30:54 -07:00
</layout>
</widget>
</item>
UI: Add 'Advanced' settings section Currently, this allows the setting of values such as: - Audio buffering time - Color format (still somewhat unsupported) - YUV color space (if a YUV format) = YUV color range (if a YUV format) More color formats will be added in the future, such as RGB and YUV 4:2:2 formats.
2015-02-11 12:55:06 -08:00
</layout>
</widget>
</item>
</layout>
</widget>
</widget>
</item>
UI: Add adv. settings checkbox for browser HW accel Adds a checkbox to advanced settings that allows the user to enable/disable browser source hardware acceleration on windows.
2018-08-10 06:12:16 -07:00
<item>
<layout class="QVBoxLayout" name="verticalLayout_17">
<property name="leftMargin">
<number>10</number>
</property>
<property name="topMargin">
<number>10</number>
</property>
<property name="rightMargin">
<number>10</number>
</property>
<property name="bottomMargin">
<number>10</number>
</property>
<item>
<widget class="QLabel" name="advancedMsg">
<property name="text">
<string notr="true"/>
</property>
<property name="wordWrap">
<bool>true</bool>
</property>
UI: Add 4th aux audio input device Closes obsproject/obs-studio#1343
2018-06-26 11:41:32 -07:00
<property name="themeID" stdset="0">
<string>error</string>
</property>
UI: Add adv. settings checkbox for browser HW accel Adds a checkbox to advanced settings that allows the user to enable/disable browser source hardware acceleration on windows.
2018-08-10 06:12:16 -07:00
</widget>
</item>
<item>
<widget class="QLabel" name="advancedMsg2">
<property name="text">
<string notr="true"/>
</property>
<property name="wordWrap">
<bool>true</bool>
</property>
UI: Add 4th aux audio input device Closes obsproject/obs-studio#1343
2018-06-26 11:41:32 -07:00
<property name="themeID" stdset="0">
<string>error</string>
</property>
UI: Add adv. settings checkbox for browser HW accel Adds a checkbox to advanced settings that allows the user to enable/disable browser source hardware acceleration on windows.
2018-08-10 06:12:16 -07:00
</widget>
</item>
</layout>
</item>
UI: Add 'Advanced' settings section Currently, this allows the setting of values such as: - Audio buffering time - Color format (still somewhat unsupported) - YUV color space (if a YUV format) = YUV color range (if a YUV format) More color formats will be added in the future, such as RGB and YUV 4:2:2 formats.
2015-02-11 12:55:06 -08:00
</layout>
</widget>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</widget>
</item>
</layout>
</item>
<item>
<widget class="QDialogButtonBox" name="buttonBox">
<property name="standardButtons">
<set>QDialogButtonBox::Apply|QDialogButtonBox::Cancel|QDialogButtonBox::Ok</set>
</property>
</widget>
</item>
</layout>
</widget>
UI: Upgrade stream link hotlink to a button Most of the top streaming services now have a link in the stream key label. Upgrading this button to a button clarifies the assistance for the important step of setting up a stream. Creates a new type of button for URL opening simply which also automatically updates the tootip to the current URL. Includes addition of Twitter/Periscope URL to make this feature more complete.
2019-10-24 21:05:43 -07:00
<customwidgets>
<customwidget>
<class>UrlPushButton</class>
<extends>QPushButton</extends>
<header>url-push-button.hpp</header>
</customwidget>
UI: Don't recreate entire Hotkey Settings tab This replaces the programmatic generation of the hotkeys tab with XML. Also fixes a memory leak. Reuses concepts from LoadAudioSources().
2022-01-02 22:41:28 -08:00
<customwidget>
<class>OBSHotkeyEdit</class>
<extends>QLineEdit</extends>
<header>hotkey-edit.hpp</header>
</customwidget>
UI: Upgrade stream link hotlink to a button Most of the top streaming services now have a link in the stream key label. Upgrading this button to a button clarifies the assistance for the important step of setting up a stream. Creates a new type of button for URL opening simply which also automatically updates the tootip to the current URL. Includes addition of Twitter/Periscope URL to make this feature more complete.
2019-10-24 21:05:43 -07:00
</customwidgets>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
<tabstops>
<tabstop>listWidget</tabstop>
UI: Update tab stop order in Settings
2019-03-02 15:50:54 -08:00
<tabstop>scrollArea_2</tabstop>
<tabstop>language</tabstop>
<tabstop>theme</tabstop>
<tabstop>enableAutoUpdates</tabstop>
<tabstop>openStatsOnStartup</tabstop>
<tabstop>warnBeforeStreamStart</tabstop>
<tabstop>warnBeforeStreamStop</tabstop>
UI: Add option to warn on stop recording OBS has an option to warn before stopping a stream, but it doesn't have a similar warning for recording. This can result in a recording being unintentionally stopped. Add an option to warn when the "Stop Recording" button is pressed. Note: While OBS also has an option to warn on stream start, this patch purposefully does not add similar warn on recording start option. This is because accidentally starting to record isn't risky in the same way that accidentally starting to stream is.
2019-06-17 07:14:14 -07:00
<tabstop>warnBeforeRecordStop</tabstop>
UI: Update tab stop order in Settings
2019-03-02 15:50:54 -08:00
<tabstop>recordWhenStreaming</tabstop>
<tabstop>keepRecordStreamStops</tabstop>
<tabstop>replayWhileStreaming</tabstop>
<tabstop>keepReplayStreamStops</tabstop>
<tabstop>snappingEnabled</tabstop>
<tabstop>snapDistance</tabstop>
<tabstop>screenSnapping</tabstop>
<tabstop>sourceSnapping</tabstop>
<tabstop>centerSnapping</tabstop>
<tabstop>hideProjectorCursor</tabstop>
<tabstop>projectorAlwaysOnTop</tabstop>
<tabstop>saveProjectors</tabstop>
<tabstop>systemTrayEnabled</tabstop>
<tabstop>systemTrayWhenStarted</tabstop>
<tabstop>systemTrayAlways</tabstop>
<tabstop>overflowHide</tabstop>
<tabstop>overflowAlwaysVisible</tabstop>
<tabstop>overflowSelectionHide</tabstop>
UI: Fix tab stop order for Draw safe areas A tabstop definition was missing on the commit afd58a78e.
2021-10-02 00:06:37 -07:00
<tabstop>previewSafeAreas</tabstop>
UI: Add missing tab stop fields in Settings
2020-08-27 04:17:35 -07:00
<tabstop>automaticSearch</tabstop>
UI: Update tab stop order in Settings
2019-03-02 15:50:54 -08:00
<tabstop>doubleClickSwitch</tabstop>
<tabstop>studioPortraitLayout</tabstop>
UI: Add missing tab stop fields in Settings
2020-08-27 04:17:35 -07:00
<tabstop>prevProgLabelToggle</tabstop>
UI: Update tab stop order in Settings
2019-03-02 15:50:54 -08:00
<tabstop>multiviewMouseSwitch</tabstop>
<tabstop>multiviewDrawNames</tabstop>
<tabstop>multiviewDrawAreas</tabstop>
<tabstop>multiviewLayout</tabstop>
<tabstop>service</tabstop>
<tabstop>connectAccount</tabstop>
<tabstop>useStreamKey</tabstop>
<tabstop>server</tabstop>
<tabstop>customServer</tabstop>
<tabstop>key</tabstop>
<tabstop>show</tabstop>
UI: Add missing tab stop fields in Settings
2020-08-27 04:17:35 -07:00
<tabstop>getStreamKeyButton</tabstop>
UI: Update tab stop order in Settings
2019-03-02 15:50:54 -08:00
<tabstop>connectAccount2</tabstop>
<tabstop>disconnectAccount</tabstop>
UI: Add missing tab stop fields in Settings
2020-08-27 04:17:35 -07:00
<tabstop>bandwidthTestEnable</tabstop>
UI: Update tab stop order in Settings
2019-03-02 15:50:54 -08:00
<tabstop>useAuth</tabstop>
UI: Add missing tab stop fields in Settings
2020-08-27 04:17:35 -07:00
<tabstop>twitchAddonDropdown</tabstop>
UI: Update tab stop order in Settings
2019-03-02 15:50:54 -08:00
<tabstop>authUsername</tabstop>
<tabstop>authPw</tabstop>
<tabstop>authPwShow</tabstop>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<tabstop>outputMode</tabstop>
<tabstop>simpleOutputVBitrate</tabstop>
<tabstop>simpleOutputABitrate</tabstop>
UI: Move Simple Mode audio bitrate above encoder
2022-06-25 10:16:14 -07:00
<tabstop>simpleOutStrEncoder</tabstop>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<tabstop>simpleOutPreset</tabstop>
UI: Move Simple Mode encoder preset out of Advanced
2022-06-25 10:24:04 -07:00
<tabstop>simpleOutAdvanced</tabstop>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<tabstop>simpleOutCustom</tabstop>
<tabstop>simpleOutputPath</tabstop>
<tabstop>simpleOutputBrowse</tabstop>
<tabstop>simpleNoSpace</tabstop>
<tabstop>simpleOutRecQuality</tabstop>
<tabstop>simpleOutRecFormat</tabstop>
<tabstop>simpleOutRecEncoder</tabstop>
<tabstop>simpleOutMuxCustom</tabstop>
<tabstop>simpleReplayBuf</tabstop>
<tabstop>simpleRBSecMax</tabstop>
<tabstop>simpleRBMegsMax</tabstop>
<tabstop>advOutTabs</tabstop>
<tabstop>advOutTrack1</tabstop>
<tabstop>advOutTrack2</tabstop>
<tabstop>advOutTrack3</tabstop>
<tabstop>advOutTrack4</tabstop>
<tabstop>advOutTrack5</tabstop>
<tabstop>advOutTrack6</tabstop>
<tabstop>advOutEncoder</tabstop>
<tabstop>advOutUseRescale</tabstop>
<tabstop>advOutRescale</tabstop>
<tabstop>advOutRecType</tabstop>
<tabstop>advOutRecPath</tabstop>
<tabstop>advOutRecPathBrowse</tabstop>
<tabstop>advOutRecFormat</tabstop>
<tabstop>advOutRecTrack1</tabstop>
<tabstop>advOutRecTrack2</tabstop>
<tabstop>advOutRecTrack3</tabstop>
<tabstop>advOutRecTrack4</tabstop>
<tabstop>advOutRecTrack5</tabstop>
<tabstop>advOutRecTrack6</tabstop>
<tabstop>advOutRecRescale</tabstop>
UI: Add automatic file splitting This commit implements a new feature to split recordings in split files in Advanced output mode. These basic settings are implemented. - Enable/disable the feature. Default is disabled. - Select a type of the limit, time or size. - Specifies the limit in seconds or MiB.
2021-10-03 03:06:46 -07:00
<tabstop>advOutSplitFile</tabstop>
<tabstop>advOutSplitFileType</tabstop>
<tabstop>advOutSplitFileTime</tabstop>
<tabstop>advOutSplitFileSize</tabstop>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<tabstop>advOutTrack1Bitrate</tabstop>
<tabstop>advOutTrack1Name</tabstop>
<tabstop>advOutTrack2Bitrate</tabstop>
<tabstop>advOutTrack2Name</tabstop>
<tabstop>advOutTrack3Bitrate</tabstop>
<tabstop>advOutTrack3Name</tabstop>
<tabstop>advOutTrack4Bitrate</tabstop>
<tabstop>advOutTrack4Name</tabstop>
<tabstop>advOutTrack5Bitrate</tabstop>
<tabstop>advOutTrack5Name</tabstop>
<tabstop>advOutTrack6Bitrate</tabstop>
<tabstop>advOutTrack6Name</tabstop>
UI: Update tab stop order in Settings
2019-03-02 15:50:54 -08:00
<tabstop>advRBSecMax</tabstop>
<tabstop>advRBMegsMax</tabstop>
UI: Add missing tab stop fields in Settings
2020-08-27 04:17:35 -07:00
<tabstop>scrollArea_50</tabstop>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<tabstop>sampleRate</tabstop>
<tabstop>channelSetup</tabstop>
<tabstop>desktopAudioDevice1</tabstop>
<tabstop>desktopAudioDevice2</tabstop>
<tabstop>auxAudioDevice1</tabstop>
<tabstop>auxAudioDevice2</tabstop>
<tabstop>auxAudioDevice3</tabstop>
UI: Update tab stop order in Settings
2019-03-02 15:50:54 -08:00
<tabstop>auxAudioDevice4</tabstop>
<tabstop>meterDecayRate</tabstop>
<tabstop>peakMeterType</tabstop>
UI: Refactor Audio Settings tab structure - Now uses a QVBoxLayout with a QScrollArea for the container - Uses QGroupBox for each section - Moved Monitoring and ducking settings out of the Advanced tab - Push-to hotkeys are no longer in a child scroll area - Renamed device labels for consistency
2019-02-02 03:09:47 -08:00
<tabstop>monitoringDevice</tabstop>
<tabstop>disableAudioDucking</tabstop>
UI: Add low latency audio buffering mode to UI This feature is meant to reduce maximum audio buffering and turn off dynamic buffering mode. This allows the lowest possible consistent latency for audio buffering, which is useful for the decklink and NDI outputs which cannot rely on audio timestamps for synchronization. This can have a negative effect of making audio segments (partial or in full) cut out. So audio glitching or audio loss can occur if this is enabled.
2022-07-18 14:25:06 -07:00
<tabstop>lowLatencyBuffering</tabstop>
UI: Add missing tab stop fields in Settings
2020-08-27 04:17:35 -07:00
<tabstop>outputResolution</tabstop>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<tabstop>downscaleFilter</tabstop>
<tabstop>fpsType</tabstop>
<tabstop>fpsCommon</tabstop>
<tabstop>fpsInteger</tabstop>
<tabstop>fpsNumerator</tabstop>
<tabstop>fpsDenominator</tabstop>
<tabstop>scrollArea</tabstop>
<tabstop>processPriority</tabstop>
UI: Add ShutDownActiveOutputsOnExit setting Adds a new setting to the general OBS settings, which can be checked in order to no longer show the "confirm close" dialog when there are still streams/recordings running.
2020-11-20 03:04:26 -08:00
<tabstop>confirmOnExit</tabstop>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<tabstop>renderer</tabstop>
<tabstop>adapter</tabstop>
<tabstop>colorFormat</tabstop>
<tabstop>colorSpace</tabstop>
<tabstop>colorRange</tabstop>
<tabstop>disableOSXVSync</tabstop>
<tabstop>resetOSXVSync</tabstop>
<tabstop>filenameFormatting</tabstop>
<tabstop>overwriteIfExists</tabstop>
UI: Update tab stop order in Settings
2019-03-02 15:50:54 -08:00
<tabstop>autoRemux</tabstop>
UI: Make advanced settings pane a bit more compact Packs related controls together and makes a bit more room for more advanced settings.
2017-01-08 15:26:33 -08:00
<tabstop>simpleRBPrefix</tabstop>
<tabstop>simpleRBSuffix</tabstop>
<tabstop>streamDelayEnable</tabstop>
<tabstop>streamDelaySec</tabstop>
<tabstop>streamDelayPreserve</tabstop>
<tabstop>reconnectEnable</tabstop>
<tabstop>reconnectRetryDelay</tabstop>
<tabstop>reconnectMaxRetries</tabstop>
<tabstop>bindToIP</tabstop>
UI: Add missing tab stop fields in Settings
2020-08-27 04:17:35 -07:00
<tabstop>dynBitrate</tabstop>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<tabstop>enableNewSocketLoop</tabstop>
<tabstop>enableLowLatencyMode</tabstop>
UI: Update tab stop order in Settings
2019-03-02 15:50:54 -08:00
<tabstop>browserHWAccel</tabstop>
UI: Add missing tab stop fields in Settings
2020-08-27 04:17:35 -07:00
<tabstop>hotkeyFocusType</tabstop>
UI: Add low latency audio buffering mode to UI This feature is meant to reduce maximum audio buffering and turn off dynamic buffering mode. This allows the lowest possible consistent latency for audio buffering, which is useful for the decklink and NDI outputs which cannot rely on audio timestamps for synchronization. This can have a negative effect of making audio segments (partial or in full) cut out. So audio glitching or audio loss can occur if this is enabled.
2022-07-18 14:25:06 -07:00
<tabstop>hideOBSFromCapture</tabstop>
<tabstop>closeProjectors</tabstop>
<tabstop>moreInfoButton</tabstop>
<tabstop>ignoreRecommended</tabstop>
<tabstop>useStreamKeyAdv</tabstop>
<tabstop>baseResolution</tabstop>
<tabstop>hotkeyFilterSearch</tabstop>
<tabstop>hotkeyFilterInput</tabstop>
<tabstop>hotkeyFilterReset</tabstop>
<tabstop>hotkeyScrollArea</tabstop>
<tabstop>sdrWhiteLevel</tabstop>
<tabstop>hdrNominalPeakLevel</tabstop>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</tabstops>
<resources>
<include location="obs.qrc"/>
</resources>
<connections>
<connection>
<sender>listWidget</sender>
<signal>currentRowChanged(int)</signal>
<receiver>settingsPages</receiver>
<slot>setCurrentIndex(int)</slot>
<hints>
<hint type="sourcelabel">
<x>75</x>
<y>35</y>
</hint>
<hint type="destinationlabel">
<x>199</x>
<y>50</y>
</hint>
</hints>
</connection>
<connection>
Fix/update forms for main and settings window - Had the wrong names set for the up/down widgets for sources/scenes - Updated the settings dialog and gave most of the widgets actual object names - Added code for the settings window. Settings window should now at least display.
2014-01-24 20:19:50 -08:00
<sender>fpsType</sender>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
<signal>currentIndexChanged(int)</signal>
Finish the rest of the settings dialog code - Move over the last of the original settings dialog code to QT. It was actually a bit easier to write in the QT version. wxWidgets was definitely not ideal for that because the pages would fully create/destroy every time. - [Win32] Fix os_dlopen so that it only appends .dll if not present - [MacOS] Fix name dialog text edit widget issue (it would be better if we could just use the list widget for editing labels, will have to look in to that in the future) - Tweak the settings UI a bit more and make 30 FPS default - Add a macro to convert a QString to a UTF-8 const char * string - Rename build/plugins to build/obs-plugins - Remove the last of the wxWidgets code
2014-01-26 14:36:15 -08:00
<receiver>fpsTypes</receiver>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
<slot>setCurrentIndex(int)</slot>
<hints>
<hint type="sourcelabel">
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<x>310</x>
<y>29</y>
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
</hint>
<hint type="destinationlabel">
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
<x>241</x>
UI: Add replay buffer options to simple output mode
2016-12-07 05:21:44 -08:00
<y>30</y>
obs-studio UI: Implement stream settings UI - Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
2014-04-24 01:49:07 -07:00
</hint>
</hints>
</connection>
<connection>
<sender>outputMode</sender>
<signal>currentIndexChanged(int)</signal>
<receiver>outputModePages</receiver>
<slot>setCurrentIndex(int)</slot>
<hints>
<hint type="sourcelabel">
UI: Add auto-start replay buf. opt. when stream starts Closes jp9000/obs-studio#748
2017-01-04 13:11:52 -08:00
<x>241</x>
<y>16</y>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</hint>
<hint type="destinationlabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>401</x>
<y>64</y>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</hint>
</hints>
</connection>
Basic UI: Add advanced encoder settings
2014-08-25 07:48:51 -07:00
<connection>
<sender>simpleOutAdvanced</sender>
<signal>toggled(bool)</signal>
UI: Rename 'Custom x264 Settings' Rename 'Custom x264 Settings' to 'Custom Encoder Settings', because it may be useful to use this for encoders other than x264
2015-01-18 06:29:24 -08:00
<receiver>simpleOutCustom</receiver>
Basic UI: Add advanced encoder settings
2014-08-25 07:48:51 -07:00
<slot>setVisible(bool)</slot>
<hints>
<hint type="sourcelabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>251</x>
<y>64</y>
Basic UI: Add advanced encoder settings
2014-08-25 07:48:51 -07:00
</hint>
<hint type="destinationlabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>251</x>
<y>64</y>
Basic UI: Add advanced encoder settings
2014-08-25 07:48:51 -07:00
</hint>
</hints>
</connection>
<connection>
<sender>simpleOutAdvanced</sender>
<signal>toggled(bool)</signal>
<receiver>label_23</receiver>
<slot>setVisible(bool)</slot>
<hints>
<hint type="sourcelabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>251</x>
<y>64</y>
Basic UI: Add advanced encoder settings
2014-08-25 07:48:51 -07:00
</hint>
<hint type="destinationlabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>251</x>
<y>64</y>
Basic UI: Add "Use Constant Bitrate" advanced option. It's better to use VBR for local recordings, so this option should be nice for people who want to do that.
2014-09-24 20:23:42 -07:00
</hint>
</hints>
</connection>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
<connection>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<sender>systemTrayEnabled</sender>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
<signal>toggled(bool)</signal>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<receiver>systemTrayWhenStarted</receiver>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
<slot>setEnabled(bool)</slot>
<hints>
<hint type="sourcelabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>933</x>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<y>579</y>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</hint>
<hint type="destinationlabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>933</x>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<y>602</y>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</hint>
</hints>
</connection>
<connection>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<sender>systemTrayEnabled</sender>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
<signal>toggled(bool)</signal>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<receiver>systemTrayAlways</receiver>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
<slot>setEnabled(bool)</slot>
<hints>
<hint type="sourcelabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>933</x>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<y>579</y>
UI: Set simple mode reconnect signal to toggled() clicked() is the wrong signal to use, it only activates on actual user click, not when the value is changed. toggle() activates whenever the value itself is changed.
2015-02-10 19:35:33 -08:00
</hint>
<hint type="destinationlabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>933</x>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<y>625</y>
UI: Set simple mode reconnect signal to toggled() clicked() is the wrong signal to use, it only activates on actual user click, not when the value is changed. toggle() activates whenever the value itself is changed.
2015-02-10 19:35:33 -08:00
</hint>
</hints>
</connection>
UI: Add snap options to general settings section Allows the user to disable snapping all together or control the snap threshold.
2016-04-06 18:03:29 -07:00
<connection>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<sender>enableNewSocketLoop</sender>
UI: Add snap options to general settings section Allows the user to disable snapping all together or control the snap threshold.
2016-04-06 18:03:29 -07:00
<signal>toggled(bool)</signal>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<receiver>enableLowLatencyMode</receiver>
<slot>setEnabled(bool)</slot>
UI: Add snap options to general settings section Allows the user to disable snapping all together or control the snap threshold.
2016-04-06 18:03:29 -07:00
<hints>
<hint type="sourcelabel">
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<x>250</x>
<y>39</y>
UI: Add snap options to general settings section Allows the user to disable snapping all together or control the snap threshold.
2016-04-06 18:03:29 -07:00
</hint>
<hint type="destinationlabel">
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<x>250</x>
<y>39</y>
UI: Add snap options to general settings section Allows the user to disable snapping all together or control the snap threshold.
2016-04-06 18:03:29 -07:00
</hint>
</hints>
</connection>
<connection>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<sender>snappingEnabled</sender>
UI: Add snap options to general settings section Allows the user to disable snapping all together or control the snap threshold.
2016-04-06 18:03:29 -07:00
<signal>toggled(bool)</signal>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<receiver>label_9</receiver>
UI: Add snap options to general settings section Allows the user to disable snapping all together or control the snap threshold.
2016-04-06 18:03:29 -07:00
<slot>setEnabled(bool)</slot>
<hints>
<hint type="sourcelabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>933</x>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<y>340</y>
UI: Add snap options to general settings section Allows the user to disable snapping all together or control the snap threshold.
2016-04-06 18:03:29 -07:00
</hint>
<hint type="destinationlabel">
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<x>347</x>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<y>366</y>
UI: Add snap options to general settings section Allows the user to disable snapping all together or control the snap threshold.
2016-04-06 18:03:29 -07:00
</hint>
</hints>
</connection>
<connection>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<sender>snappingEnabled</sender>
UI: Add snap options to general settings section Allows the user to disable snapping all together or control the snap threshold.
2016-04-06 18:03:29 -07:00
<signal>toggled(bool)</signal>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<receiver>snapDistance</receiver>
UI: Add snap options to general settings section Allows the user to disable snapping all together or control the snap threshold.
2016-04-06 18:03:29 -07:00
<slot>setEnabled(bool)</slot>
<hints>
<hint type="sourcelabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>933</x>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<y>340</y>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</hint>
UI: Add option to snap to edges of other sources Allows the user to snap sources to the edges of other sources, on by default. Closes jp9000/obs-studio#530
2016-04-06 18:13:56 -07:00
<hint type="destinationlabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>933</x>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<y>366</y>
UI: Add option to snap to edges of other sources Allows the user to snap sources to the edges of other sources, on by default. Closes jp9000/obs-studio#530
2016-04-06 18:13:56 -07:00
</hint>
</hints>
</connection>
<connection>
<sender>snappingEnabled</sender>
<signal>toggled(bool)</signal>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<receiver>screenSnapping</receiver>
UI: Add option to snap to edges of other sources Allows the user to snap sources to the edges of other sources, on by default. Closes jp9000/obs-studio#530
2016-04-06 18:13:56 -07:00
<slot>setEnabled(bool)</slot>
<hints>
<hint type="sourcelabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>933</x>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<y>340</y>
UI: Add option to snap to edges of other sources Allows the user to snap sources to the edges of other sources, on by default. Closes jp9000/obs-studio#530
2016-04-06 18:13:56 -07:00
</hint>
UI: Add option to snap to vertical/horizontal center Allows users to snap sources to the horizontal or vertical centers of the screen. Off by default. Closes jp9000/obs-studio#528
2016-04-06 18:10:39 -07:00
<hint type="destinationlabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>933</x>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<y>389</y>
UI: Add option to snap to vertical/horizontal center Allows users to snap sources to the horizontal or vertical centers of the screen. Off by default. Closes jp9000/obs-studio#528
2016-04-06 18:10:39 -07:00
</hint>
</hints>
</connection>
<connection>
<sender>snappingEnabled</sender>
<signal>toggled(bool)</signal>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<receiver>sourceSnapping</receiver>
UI: Add option to snap to vertical/horizontal center Allows users to snap sources to the horizontal or vertical centers of the screen. Off by default. Closes jp9000/obs-studio#528
2016-04-06 18:10:39 -07:00
<slot>setEnabled(bool)</slot>
<hints>
<hint type="sourcelabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>933</x>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<y>340</y>
UI: Add option to snap to vertical/horizontal center Allows users to snap sources to the horizontal or vertical centers of the screen. Off by default. Closes jp9000/obs-studio#528
2016-04-06 18:10:39 -07:00
</hint>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
<hint type="destinationlabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>933</x>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<y>412</y>
UI: Add "Enforce streaming bitrate limits" setting Allows the user to disable streaming bitrate limits in simple output mode if they so choose. This option is enabled by default.
2016-04-10 03:10:36 -07:00
</hint>
</hints>
</connection>
<connection>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<sender>snappingEnabled</sender>
UI: Add "Enforce streaming bitrate limits" setting Allows the user to disable streaming bitrate limits in simple output mode if they so choose. This option is enabled by default.
2016-04-10 03:10:36 -07:00
<signal>toggled(bool)</signal>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<receiver>centerSnapping</receiver>
UI: Clean up general pane of settings dialog So many checkboxes were together almost senselessly.
2017-02-20 03:53:34 -08:00
<slot>setEnabled(bool)</slot>
UI: Add "Enforce streaming bitrate limits" setting Allows the user to disable streaming bitrate limits in simple output mode if they so choose. This option is enabled by default.
2016-04-10 03:10:36 -07:00
<hints>
<hint type="sourcelabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>933</x>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<y>340</y>
UI: Add option to automatically record while streaming Allows the ability for users to make it so recording automatically starts when they start streaming. Also adds the option to allow the recording to continue when stream is stopped. Closes jp9000/obs-studio#554
2016-06-16 10:59:36 -07:00
</hint>
<hint type="destinationlabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>933</x>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<y>435</y>
UI: Add option to automatically record while streaming Allows the ability for users to make it so recording automatically starts when they start streaming. Also adds the option to allow the recording to continue when stream is stopped. Closes jp9000/obs-studio#554
2016-06-16 10:59:36 -07:00
</hint>
</hints>
</connection>
<connection>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<sender>recordWhenStreaming</sender>
UI: Add option to automatically record while streaming Allows the ability for users to make it so recording automatically starts when they start streaming. Also adds the option to allow the recording to continue when stream is stopped. Closes jp9000/obs-studio#554
2016-06-16 10:59:36 -07:00
<signal>toggled(bool)</signal>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<receiver>keepRecordStreamStops</receiver>
UI: Add option to automatically record while streaming Allows the ability for users to make it so recording automatically starts when they start streaming. Also adds the option to allow the recording to continue when stream is stopped. Closes jp9000/obs-studio#554
2016-06-16 10:59:36 -07:00
<slot>setEnabled(bool)</slot>
<hints>
<hint type="sourcelabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>933</x>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<y>222</y>
UI: Add "Enforce streaming bitrate limits" setting Allows the user to disable streaming bitrate limits in simple output mode if they so choose. This option is enabled by default.
2016-04-10 03:10:36 -07:00
</hint>
<hint type="destinationlabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>933</x>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<y>245</y>
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it
2015-01-26 13:41:22 -08:00
</hint>
</hints>
</connection>
UI: Add system tray capability This adds a system tray when enabled. There is also a option to minimize to the system tray when the app is started. Closes jp9000/obs-studio#595
2016-08-13 07:36:17 -07:00
<connection>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<sender>replayWhileStreaming</sender>
UI: Add system tray capability This adds a system tray when enabled. There is also a option to minimize to the system tray when the app is started. Closes jp9000/obs-studio#595
2016-08-13 07:36:17 -07:00
<signal>toggled(bool)</signal>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<receiver>keepReplayStreamStops</receiver>
UI: Add system tray capability This adds a system tray when enabled. There is also a option to minimize to the system tray when the app is started. Closes jp9000/obs-studio#595
2016-08-13 07:36:17 -07:00
<slot>setEnabled(bool)</slot>
<hints>
<hint type="sourcelabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>933</x>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<y>268</y>
UI: Add system tray capability This adds a system tray when enabled. There is also a option to minimize to the system tray when the app is started. Closes jp9000/obs-studio#595
2016-08-13 07:36:17 -07:00
</hint>
<hint type="destinationlabel">
UI: Improve/refactor autoconfig/settings service UI Makes it so that services can have custom handling on a per-service basis. The bottom part of the service pane is now a stacked widget which can now be customized for different types of services (particularly OAuth services).
2019-02-06 19:19:17 -08:00
<x>933</x>
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<y>291</y>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
</hint>
</hints>
</connection>
<connection>
<sender>streamDelayEnable</sender>
<signal>toggled(bool)</signal>
<receiver>label_56</receiver>
<slot>setEnabled(bool)</slot>
<hints>
<hint type="sourcelabel">
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<x>250</x>
<y>39</y>
UI: Add system tray capability This adds a system tray when enabled. There is also a option to minimize to the system tray when the app is started. Closes jp9000/obs-studio#595
2016-08-13 07:36:17 -07:00
</hint>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<hint type="destinationlabel">
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<x>250</x>
<y>39</y>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
</hint>
UI: Add system tray capability This adds a system tray when enabled. There is also a option to minimize to the system tray when the app is started. Closes jp9000/obs-studio#595
2016-08-13 07:36:17 -07:00
</hints>
</connection>
UI: Add option to always minimize to tray Closes jp9000/obs-studio#737
2017-01-24 23:01:24 -08:00
<connection>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<sender>streamDelayEnable</sender>
UI: Add option to always minimize to tray Closes jp9000/obs-studio#737
2017-01-24 23:01:24 -08:00
<signal>toggled(bool)</signal>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<receiver>streamDelaySec</receiver>
UI: Add option to always minimize to tray Closes jp9000/obs-studio#737
2017-01-24 23:01:24 -08:00
<slot>setEnabled(bool)</slot>
UI: Add option to save projectors This adds an option to the general settings to save the opened projectors on exit. (Note: Fixed conflicts -Jim) Closes jp9000/obs-studio#743
2016-12-29 07:21:53 -08:00
<hints>
<hint type="sourcelabel">
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<x>250</x>
<y>39</y>
UI: Add auto-start replay buf. opt. when stream starts Closes jp9000/obs-studio#748
2017-01-04 13:11:52 -08:00
</hint>
<hint type="destinationlabel">
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<x>250</x>
<y>39</y>
UI: Add auto-start replay buf. opt. when stream starts Closes jp9000/obs-studio#748
2017-01-04 13:11:52 -08:00
</hint>
</hints>
</connection>
<connection>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<sender>streamDelayEnable</sender>
UI: Add auto-start replay buf. opt. when stream starts Closes jp9000/obs-studio#748
2017-01-04 13:11:52 -08:00
<signal>toggled(bool)</signal>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
<receiver>streamDelayInfo</receiver>
<slot>setEnabled(bool)</slot>
<hints>
<hint type="sourcelabel">
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<x>250</x>
<y>39</y>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
</hint>
<hint type="destinationlabel">
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<x>250</x>
<y>39</y>
UI: Add options for new socket loop
2017-02-21 17:05:45 -08:00
</hint>
</hints>
</connection>
<connection>
<sender>streamDelayEnable</sender>
<signal>toggled(bool)</signal>
<receiver>streamDelayPreserve</receiver>
UI: Add auto-start replay buf. opt. when stream starts Closes jp9000/obs-studio#748
2017-01-04 13:11:52 -08:00
<slot>setEnabled(bool)</slot>
<hints>
<hint type="sourcelabel">
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<x>250</x>
<y>39</y>
UI: Add option to save projectors This adds an option to the general settings to save the opened projectors on exit. (Note: Fixed conflicts -Jim) Closes jp9000/obs-studio#743
2016-12-29 07:21:53 -08:00
</hint>
<hint type="destinationlabel">
UI: Add option to show stats on startup to general
2017-05-13 20:47:47 -07:00
<x>250</x>
<y>39</y>
UI: Add option to save projectors This adds an option to the general settings to save the opened projectors on exit. (Note: Fixed conflicts -Jim) Closes jp9000/obs-studio#743
2016-12-29 07:21:53 -08:00
</hint>
</hints>
UI: Add option to always minimize to tray Closes jp9000/obs-studio#737
2017-01-24 23:01:24 -08:00
</connection>
UI: Add auth. support to settings/autoconfig Adds the ability to connect/login to an account via the settings and auto-configuration dialogs. Checks registered Auth objects, and if the Auth object matches the currently selected service in the settings window or auto-configuration dialog, will display "connect account" buttons for the user to be able to click (which are optional, they can still use stream keys if they'd prefer).
2019-02-06 22:37:36 -08:00
<connection>
<sender>connectAccount2</sender>
<signal>clicked()</signal>
<receiver>connectAccount</receiver>
<slot>click()</slot>
<hints>
<hint type="sourcelabel">
<x>484</x>
<y>142</y>
</hint>
<hint type="destinationlabel">
<x>454</x>
<y>87</y>
</hint>
</hints>
</connection>
UI: Add automatic file splitting This commit implements a new feature to split recordings in split files in Advanced output mode. These basic settings are implemented. - Enable/disable the feature. Default is disabled. - Select a type of the limit, time or size. - Specifies the limit in seconds or MiB.
2021-10-03 03:06:46 -07:00
<connection>
<sender>advOutSplitFile</sender>
<signal>toggled(bool)</signal>
<receiver>advOutSplitFileType</receiver>
<slot>setEnabled(bool)</slot>
<hints>
<hint type="sourcelabel">
<x>327</x>
<y>355</y>
</hint>
<hint type="destinationlabel">
<x>701</x>
<y>355</y>
</hint>
</hints>
</connection>
UI: Clean up Settings Output form - Adds frames around certain elements for a better element hierarchy - Moves the scroll areas into the tabs themselves - Hides stacked widgets that aren't visible to prevent scrolling of invisible content
2021-08-21 21:18:26 -07:00
<connection>
<sender>advOutUseRescale</sender>
<signal>toggled(bool)</signal>
<receiver>advOutRescale</receiver>
<slot>setEnabled(bool)</slot>
<hints>
<hint type="sourcelabel">
<x>269</x>
<y>192</y>
</hint>
<hint type="destinationlabel">
<x>656</x>
<y>192</y>
</hint>
</hints>
</connection>
<connection>
<sender>advOutRecType</sender>
<signal>currentIndexChanged(int)</signal>
<receiver>stackedWidget</receiver>
<slot>setCurrentIndex(int)</slot>
<hints>
<hint type="sourcelabel">
<x>663</x>
<y>106</y>
</hint>
<hint type="destinationlabel">
<x>560</x>
<y>391</y>
</hint>
</hints>
</connection>
<connection>
<sender>advOutRecUseRescale</sender>
<signal>toggled(bool)</signal>
<receiver>advOutRecRescale</receiver>
<slot>setEnabled(bool)</slot>
<hints>
<hint type="sourcelabel">
<x>289</x>
<y>317</y>
</hint>
<hint type="destinationlabel">
<x>662</x>
<y>317</y>
</hint>
</hints>
</connection>
<connection>
<sender>advOutFFUseRescale</sender>
<signal>toggled(bool)</signal>
<receiver>advOutFFRescale</receiver>
<slot>setEnabled(bool)</slot>
<hints>
<hint type="sourcelabel">
<x>334</x>
<y>377</y>
</hint>
<hint type="destinationlabel">
<x>685</x>
<y>377</y>
</hint>
</hints>
</connection>
<connection>
<sender>advOutFFType</sender>
<signal>currentIndexChanged(int)</signal>
<receiver>stackedWidget_2</receiver>
<slot>setCurrentIndex(int)</slot>
<hints>
<hint type="sourcelabel">
<x>685</x>
<y>163</y>
</hint>
<hint type="destinationlabel">
<x>685</x>
<y>191</y>
</hint>
</hints>
</connection>
Change the UI to Qt (work in progress) -------------------------------------------------- Notes and details -------------------------------------------------- Why was this done? Because wxWidgets was just lacking in many areas. I know wxWidgets is designed to be used with native controls, and that's great, but wxWidgets just is not a feature-complete toolkit for multiplatform applications. It lacks in dialog editors, its code is archaic and outdated, and I just feel frustrated every time I try to do things with it. Qt on the other hand.. I had to actually try Qt to realize how much better it was as a toolkit. They've got everything from dialog editors, to an IDE, a debugger, build tools, just everything, and it's all top-notch and highly maintained. The focus of the toolkit is application development, and they spend their time trying to help people do exactly that: make programs. Great support, great tools, and because of that, great toolkit. I just didn't want to alienate any developers by being stubborn about native widgets. There *are* some things that are rather lackluster about it and design choices I disagree with though. For example, I realize that to have an easy to use toolkit you have to have some level of code generation. However, in my personal and humble opinion, moc just feels like a terrible way to approach the problem. Even now I feel like there are a variety of ways you could handle code generation and automatic management of things like that. I don't like the idea of circumventing the language itself like that. It feels like one giant massive hack. -------------------------------------------------- Things that aren't working properly: -------------------------------------------------- - Settings dialog is not implemented. The dialog is complete but the code to handle the dialog hasn't been constructed yet. - There is a problem with using Qt widgets as a device target on windows, with at least OpenGL: if I have the preview widget automatically resize itself, it seems to cause some sort of video card failure that I don't understand. - Because of the above, resizing the preview widget has been disabled until I can figure out what's going on, so it's currently only a 32x32 area. - Direct3D doesn't seem to render correctly either, seems that the viewport is messed up or something. I'm sort of confused about what's going on with it. - The new main window seems to be triggering more race conditions than the wxWidgets main window dialog did. I'm not entirely sure what's going on here, but this may just be existing race conditions within libobs itself that I just never spotted before (even though I tend to be very thorough with race conditions any time I use variables cross-thread)
2014-01-23 10:53:55 -08:00
</connections>
</ui>