From: hung kuishing <hungkuishing@outlook.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] use bits_per_coded_sample if bits_per_raw_sample equal to 0 in pcmc tag, fix bug #10433 Date: Wed, 26 Jul 2023 05:12:49 +0000 Message-ID: <PH7PR11MB7430C85EF6E68623E6679FD7C400A@PH7PR11MB7430.namprd11.prod.outlook.com> (raw) In-Reply-To: <tencent_C793015C6C4B9D2607909226F667CEEABD06@qq.com> > > On Jul 24, 2023, at 10:41, hung kuishing <hungkuishing@outlook.com> > wrote: > > > > Signed-off-by: clarkh <hungkuishing@outlook.com> > > --- > > libavformat/movenc.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/libavformat/movenc.c b/libavformat/movenc.c > > index f1cc80b1b3..d08c056438 100644 > > --- a/libavformat/movenc.c > > +++ b/libavformat/movenc.c > > @@ -1237,7 +1237,7 @@ static int > mov_write_pcmc_tag(AVFormatContext *s, AVIOContext *pb, > MOVTrack *tra > > track->par->codec_id == > AV_CODEC_ID_PCM_S24LE || > > track->par->codec_id == > AV_CODEC_ID_PCM_S32LE); > > avio_w8(pb, format_flags); > > - avio_w8(pb, track->par->bits_per_raw_sample); > > + avio_w8(pb, track->par->bits_per_raw_sample ? > track->par->bits_per_raw_sample : > track->par->bits_per_coded_sample); > > Thanks for the bug report. I didn’t notice bits_per_raw_sample isn’t > available > when remux raw PCM. It looks like a defect but I’m not sure. > > Since both bits_per_raw_sample and bits_per_coded_sample can be 0 > as the > comments in codec_par.h says, I decided to fallback to > av_get_exact_bits_per_sample(). > > http://ffmpeg.org/pipermail/ffmpeg-devel/2023-July/312653.html I'm glad you fixed this bug. > PS: Please follow the commit message format next time: > > 2.10 Writing a commit message > https://ffmpeg.org/git-howto.html#Writing-a-commit-message Thank you for your guidance! _______________________________________________ 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:[~2023-07-26 5:13 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-24 2:41 hung kuishing 2023-07-26 4:02 ` "zhilizhao(赵志立)" 2023-07-26 5:12 ` hung kuishing [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=PH7PR11MB7430C85EF6E68623E6679FD7C400A@PH7PR11MB7430.namprd11.prod.outlook.com \ --to=hungkuishing@outlook.com \ --cc=ffmpeg-devel@ffmpeg.org \ /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