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
69673138
Commit
69673138
authored
Sep 23, 2012
by
Martin Storsjö
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
rtpdec: Remove a useless ff_ prefix from a static symbol
Signed-off-by:
Martin Storsjö
<
martin@martin.st
>
parent
b6bf1490
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
rtpdec.c
libavformat/rtpdec.c
+2
-2
No files found.
libavformat/rtpdec.c
View file @
69673138
...
...
@@ -43,7 +43,7 @@
'ffio_open_dyn_packet_buf')
*/
static
RTPDynamicProtocolHandler
ff_
realmedia_mp3_dynamic_handler
=
{
static
RTPDynamicProtocolHandler
realmedia_mp3_dynamic_handler
=
{
.
enc_name
=
"X-MP3-draft-00"
,
.
codec_type
=
AVMEDIA_TYPE_AUDIO
,
.
codec_id
=
AV_CODEC_ID_MP3ADU
,
...
...
@@ -83,7 +83,7 @@ void av_register_rtp_dynamic_payload_handlers(void)
ff_register_dynamic_payload_handler
(
&
ff_mp4a_latm_dynamic_handler
);
ff_register_dynamic_payload_handler
(
&
ff_vp8_dynamic_handler
);
ff_register_dynamic_payload_handler
(
&
ff_qcelp_dynamic_handler
);
ff_register_dynamic_payload_handler
(
&
ff_
realmedia_mp3_dynamic_handler
);
ff_register_dynamic_payload_handler
(
&
realmedia_mp3_dynamic_handler
);
ff_register_dynamic_payload_handler
(
&
speex_dynamic_handler
);
ff_register_dynamic_payload_handler
(
&
ff_ms_rtp_asf_pfv_handler
);
...
...
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