From: Stefano Sabatini <stefasab@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] 0001-fix-segment-fault-in-function-decode Date: Sun, 21 Jan 2024 19:31:05 +0100 Message-ID: <Za1i6a5sjkHIaAtL@mariano> (raw) In-Reply-To: <26ea83a1.3c.18cffadf18e.Coremail.cnduxd@163.com> On date Saturday 2024-01-13 05:57:18 +0800, 陈督 wrote: > > > /*When it is not a planar arrangement, data[1] is empty, > > and all the data is interleaved in data[0]. > > This can result in a segmentation fault when accessing data[ch] .*/ > > //So I delete the code below: > > for (i = 0; i < frame->nb_samples; i++) > > for (ch = 0; ch < dec_ctx->ch_layout.nb_channels; ch++) > > fwrite(frame->data[ch] + data_size*i, 1, data_size, outfile); > > > > > //And I write this instead > > // L R data order > > if (av_sample_fmt_is_planar(dec_ctx->sample_fmt)) > > { > > // planar:LLL...RRR... in different data[ch] > > for (ch = 0; ch < dec_ctx->ch_layout.nb_channels; ch++) > > { > > fwrite(frame->data[ch], 1, frame->linesize[0], outfile); // only linesize[0] has data. > The problem with this approach is that this is generating output in a format which cannot be played by ffplay, which is assuming packed (i.e. non planar) format. So it is expecting the output file to be written as: LRLRLR... rather than as: LLLLLL....RRRRR also because ffplay does not know the linesize. ... But I see the example code should be fixed, it was designed with the assumption that the input sample format was always packed, which is not the case anymore. [...] _______________________________________________ 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:[~2024-01-21 18:31 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-12 21:57 陈督 2024-01-21 18:31 ` Stefano Sabatini [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=Za1i6a5sjkHIaAtL@mariano \ --to=stefasab@gmail.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