Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
O
obs-studio
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Yunxiang Li
obs-studio
Commits
7e4972e7
Commit
7e4972e7
authored
10 years ago
by
fryshorts
Browse files
Options
Downloads
Patches
Plain Diff
Small cleanups in v4l2 plugin.
parent
07d4c5f0
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
plugins/linux-v4l2/v4l2-input.c
+0
-3
0 additions, 3 deletions
plugins/linux-v4l2/v4l2-input.c
with
0 additions
and
3 deletions
plugins/linux-v4l2/v4l2-input.c
+
0
−
3
View file @
7e4972e7
...
...
@@ -696,7 +696,6 @@ static bool resolution_selected(obs_properties_t props, obs_property_t p,
static
obs_properties_t
v4l2_properties
(
void
)
{
/* TODO: locale */
obs_properties_t
props
=
obs_properties_create
();
obs_property_t
device_list
=
obs_properties_add_list
(
props
,
...
...
@@ -889,8 +888,6 @@ static void v4l2_update(void *vptr, obs_data_t settings)
static
void
*
v4l2_create
(
obs_data_t
settings
,
obs_source_t
source
)
{
UNUSED_PARAMETER
(
settings
);
struct
v4l2_data
*
data
=
bzalloc
(
sizeof
(
struct
v4l2_data
));
data
->
dev
=
-
1
;
data
->
source
=
source
;
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment