-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add RFC: Scene setup wizard #32
base: master
Are you sure you want to change the base?
Conversation
2a653b5
to
8e140dc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added some initial thoughts. I'll add more over time.
### Wizard page 2 | ||
- If the user selects scene template, show them different scene collections they could choose from | ||
- The scene collections will have image previews as well | ||
- If the user selects screen recording, ask them what monitor they want to record |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'd have to be extra clear here for a couple reasons:
- When people say "my screen", sometimes they mean "Photoshop" or a game.
- On a laptop on Windows, "choosing a monitor" will result in no input, causing confusion (until the GPU is toggled)
### Wizard page 3 | ||
- Have the user select their microphone and webcam | ||
- The webcam would have a preview | ||
- The microphone would also show a volume meter |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd personally vote that this should be where we include other basic things like choosing default microphone filters (ideally, at least, a noise suppression filter & a compressor). We should also make it super clear to the user if their mic is peaking.
Speaking of peaking, I wonder if it'd be possible to determine what a device's system volume is in dB. Windows does have the UI for it, and being able to notify a user that their mic is "above the recommended range" (ie above 0dB).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One easy way to include the filters, is to have them in the scene template, which is just a scene collection.
|
||
# Additional Information | ||
|
||
- Should it be a seperate wizard than the auto-config? Or combined into a single wizard? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think a combined wizard would be preferred, and steps should be clearly skippable. We don't want to overwhelm the user, and spamming them with new popups after each "mini-wizard" is complete would not be a good experience.
The user will also be able to open the wizard in the scene collection menu. | ||
|
||
### Wizard page 1 | ||
- Buttons that allow the user to select how they want to use OBS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think stylised buttons would be good - big icon, short text. Make it SUPER user-friendly - this'll be their first interaction with the program.
One thing that would need to be implemented to make this work properly, is a containerized scene collection file. This way, image files, etc. can be added to the template and loaded seamlessly. |
I have the beginnings of an RFC for this started. |
Description
This proposal is for adding a scene wizard for new users when first loading OBS.
Motivation and Context
Users often find it difficult to set up OBS.
Link to RFC
https://github.com/cg2121/rfcs/blob/rfc-scene-wizard/accepted/0032-scene-wizard.md