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
37f2ac36
Commit
37f2ac36
authored
Apr 24, 2013
by
Michael Niedermayer
Committed by
Martin Storsjö
May 15, 2013
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
vc1: Simplify code by using INIT_LUT()
Signed-off-by:
Martin Storsjö
<
martin@martin.st
>
parent
0379fc14
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
16 deletions
+1
-16
vc1.c
libavcodec/vc1.c
+1
-16
No files found.
libavcodec/vc1.c
View file @
37f2ac36
...
...
@@ -693,22 +693,7 @@ int ff_vc1_parse_frame_header(VC1Context *v, GetBitContext* gb)
v
->
lumshift
=
get_bits
(
gb
,
6
);
v
->
use_ic
=
1
;
/* fill lookup tables for intensity compensation */
if
(
!
v
->
lumscale
)
{
scale
=
-
64
;
shift
=
(
255
-
v
->
lumshift
*
2
)
<<
6
;
if
(
v
->
lumshift
>
31
)
shift
+=
128
<<
6
;
}
else
{
scale
=
v
->
lumscale
+
32
;
if
(
v
->
lumshift
>
31
)
shift
=
(
v
->
lumshift
-
64
)
<<
6
;
else
shift
=
v
->
lumshift
<<
6
;
}
for
(
i
=
0
;
i
<
256
;
i
++
)
{
v
->
luty
[
i
]
=
av_clip_uint8
((
scale
*
i
+
shift
+
32
)
>>
6
);
v
->
lutuv
[
i
]
=
av_clip_uint8
((
scale
*
(
i
-
128
)
+
128
*
64
+
32
)
>>
6
);
}
INIT_LUT
(
v
->
lumscale
,
v
->
lumshift
,
v
->
luty
,
v
->
lutuv
);
}
v
->
qs_last
=
v
->
s
.
quarter_sample
;
if
(
v
->
mv_mode
==
MV_PMODE_1MV_HPEL
||
v
->
mv_mode
==
MV_PMODE_1MV_HPEL_BILIN
)
...
...
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