From: Zhao Zhili <quinkblack-at-foxmail.com@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Jack Lau <jacklau1222@qq.com> Subject: Re: [FFmpeg-devel] [PATCH] avformat/rtpdec_mpeg4: add need_parsing for rtsp AAC Date: Wed, 9 Apr 2025 11:06:31 +0800 Message-ID: <tencent_1FD968BE7C06AF6A3945C19DB4BC689A020A@qq.com> (raw) In-Reply-To: <tencent_4C958DF143216885BDA89D908C8CCE92F30A@qq.com> > On Apr 9, 2025, at 08:07, Jack Lau via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> wrote: > > fix ticket #11531 > > the rtsp aac did not marked keyframe which cannot easy copy to output. > because f265f9c9d04863180503707bfad285f48e6bf080 commit change the AAC props to match xHE-AAC. > in some formats like MOV, need_parsing is set, so AAC can be still parsed be keyframe > but rtsp did not, so this patch add it > > Signed-off-by: Jack Lau <jacklau1222@qq.com> > --- > libavformat/rtpdec_mpeg4.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/libavformat/rtpdec_mpeg4.c b/libavformat/rtpdec_mpeg4.c > index 6531632b2d..c506bcbed1 100644 > --- a/libavformat/rtpdec_mpeg4.c > +++ b/libavformat/rtpdec_mpeg4.c > @@ -363,6 +363,7 @@ const RTPDynamicProtocolHandler ff_mpeg4_generic_dynamic_handler = { > .enc_name = "mpeg4-generic", > .codec_type = AVMEDIA_TYPE_AUDIO, > .codec_id = AV_CODEC_ID_AAC, > + .need_parsing = AVSTREAM_PARSE_HEADERS, > .priv_data_size = sizeof(PayloadContext), > .parse_sdp_a_line = parse_sdp_line, > .close = close_context, LGTM, thanks. > -- > 2.49.0 > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2025-04-09 3:07 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-04-09 0:07 Jack Lau via ffmpeg-devel 2025-04-09 3:06 ` Zhao Zhili [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=tencent_1FD968BE7C06AF6A3945C19DB4BC689A020A@qq.com \ --to=quinkblack-at-foxmail.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=jacklau1222@qq.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git