Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in / Register
Toggle navigation
F
ffmpeg.wasm-core
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Linshizhi
ffmpeg.wasm-core
Commits
6c0318c4
Commit
6c0318c4
authored
Feb 07, 2016
by
Clément Bœsch
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
lavfi/fieldmatch: fix fields copy when plane height is odd
Fixes Ticket 5187
parent
f5c3f85e
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
2 deletions
+5
-2
vf_fieldmatch.c
libavfilter/vf_fieldmatch.c
+5
-2
No files found.
libavfilter/vf_fieldmatch.c
View file @
6c0318c4
...
...
@@ -608,10 +608,13 @@ static void copy_fields(const FieldMatchContext *fm, AVFrame *dst,
const
AVFrame
*
src
,
int
field
)
{
int
plane
;
for
(
plane
=
0
;
plane
<
4
&&
src
->
data
[
plane
]
&&
src
->
linesize
[
plane
];
plane
++
)
for
(
plane
=
0
;
plane
<
4
&&
src
->
data
[
plane
]
&&
src
->
linesize
[
plane
];
plane
++
)
{
const
int
plane_h
=
get_height
(
fm
,
src
,
plane
);
const
int
nb_copy_fields
=
(
plane_h
>>
1
)
+
(
field
?
0
:
(
plane_h
&
1
));
av_image_copy_plane
(
dst
->
data
[
plane
]
+
field
*
dst
->
linesize
[
plane
],
dst
->
linesize
[
plane
]
<<
1
,
src
->
data
[
plane
]
+
field
*
src
->
linesize
[
plane
],
src
->
linesize
[
plane
]
<<
1
,
get_width
(
fm
,
src
,
plane
),
get_height
(
fm
,
src
,
plane
)
/
2
);
get_width
(
fm
,
src
,
plane
),
nb_copy_fields
);
}
}
static
AVFrame
*
create_weave_frame
(
AVFilterContext
*
ctx
,
int
match
,
int
field
,
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment