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
c387c45e
Commit
c387c45e
authored
Aug 15, 2013
by
Michael Niedermayer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
ffv1: fix plane_count at version 1.4
Signed-off-by:
Michael Niedermayer
<
michaelni@gmx.at
>
parent
8ec61882
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
4 additions
and
1 deletion
+4
-1
ffv1dec.c
libavcodec/ffv1dec.c
+1
-1
ffv1enc.c
libavcodec/ffv1enc.c
+3
-0
No files found.
libavcodec/ffv1dec.c
View file @
c387c45e
...
...
@@ -499,7 +499,7 @@ static int read_extra_header(FFV1Context *f)
f
->
chroma_h_shift
=
get_symbol
(
c
,
state
,
0
);
f
->
chroma_v_shift
=
get_symbol
(
c
,
state
,
0
);
f
->
transparency
=
get_rac
(
c
,
state
);
f
->
plane_count
=
2
+
f
->
transparency
;
f
->
plane_count
=
1
+
(
f
->
chroma_planes
||
f
->
version
<
4
)
+
f
->
transparency
;
f
->
num_h_slices
=
1
+
get_symbol
(
c
,
state
,
0
);
f
->
num_v_slices
=
1
+
get_symbol
(
c
,
state
,
0
);
...
...
libavcodec/ffv1enc.c
View file @
c387c45e
...
...
@@ -797,6 +797,9 @@ static av_cold int encode_init(AVCodecContext *avctx)
if
(
!
s
->
transparency
)
s
->
plane_count
=
2
;
if
(
!
s
->
chroma_planes
&&
s
->
version
>
3
)
s
->
plane_count
--
;
avcodec_get_chroma_sub_sample
(
avctx
->
pix_fmt
,
&
s
->
chroma_h_shift
,
&
s
->
chroma_v_shift
);
s
->
picture_number
=
0
;
...
...
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