-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
linux-pipewire: Use list-based format selector for video capture #11741
base: master
Are you sure you want to change the base?
Conversation
1fdcb9b
to
65891c4
Compare
We had a lot of discussion about the string formatting for #10895 so I'd like to copy that as closely as possible for this. |
Negotiation is now made with the user selected format. Also fixes a typo in the name of a structure.
65891c4
to
9ae7734
Compare
uint32_t n_framerates; | ||
enum spa_choice_type framerate_choice; | ||
const struct spa_fraction *framerate_values; | ||
g_autoptr(GArray) framerates = NULL; |
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.
The code above this line feels just a little bit squished. Doesn't particularly matter though I suppose.
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.
Added a new line before the framerate related variable from the second commit.
But many variable/pointer is expected from PipeWire/SPA API when you parse properties.
9ae7734
to
f7f7068
Compare
@Warchamp7 does this now copy #10895 as closely as possible to be acceptable? |
Description
Change the video capture source UX to choose between formats provided as is by PipeWire and avoid providing non-functional combination.
Also it avoid the user to check every format to find the right resolution.
Negotiation is now made with the user selected format (the choice was ignored before).
Also fixes a typo in the name of a structure.
Note
Formatting of the strings case can be discussed, and FPS values (mainly multiple choices per format) could be added.
Before:
After first commit:

After second commit:

Motivation and Context
Inspired by #10895 and the fact the actual code was not respecting the user chosen format and potentially showing non-available resolution for some formats.
How Has This Been Tested?
Types of changes
Checklist: