From: Zhao Zhili <quinkblack@foxmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: angus.chen@intel.com Subject: Re: [FFmpeg-devel] [PATCH] fftools/ffmpeg_mux: keep write_header and write_packet in the same thread Date: Wed, 1 Nov 2023 19:17:38 +0800 Message-ID: <tencent_4135053EF556099D14E1DA5BF234E3809609@qq.com> (raw) In-Reply-To: <20231101090115.10655-1-angus.chen@intel.com> > On Nov 1, 2023, at 17:01, angus.chen-at-intel.com@ffmpeg.org wrote: > > From: "Chen, Angus" <angus.chen@intel.com> > > sdl2_muxer(wayland): > In ffmpeg6, we create a separate thread for muxer after calling avformat_write_header(). > It may generate EGL_BAD_ACCESS when we call write_packet. This is because egl_context > is bound to previous thread. > From EGL spec: If ctx is current to some other thread, or if either draw or read are > bound to contexts in another thread, an EGL_BAD_ACCESS error is generated. As I replied in https://patchwork.ffmpeg.org/project/ffmpeg/patch/20230918063728.198377-1-haihao.xiang@intel.com/ The patch only works on some platforms. SDL should run in main thread. I don’t think it can be fixed at here. There are at least two methods: 1. Use ffmpeg main thread to handle special tasks like this. 2. Give up and suggests user to pipe ffmpeg output to ffplay, or something like this. > > Signed-off-by: Chen, Angus <angus.chen@intel.com> > --- > fftools/ffmpeg_mux.c | 18 +++++++++--------- > 1 file changed, 9 insertions(+), 9 deletions(-) > > diff --git a/fftools/ffmpeg_mux.c b/fftools/ffmpeg_mux.c > index 7a924dba6c..d9eee3bb6d 100644 > --- a/fftools/ffmpeg_mux.c > +++ b/fftools/ffmpeg_mux.c > @@ -215,12 +215,21 @@ static void *muxer_thread(void *arg) > OutputFile *of = &mux->of; > AVPacket *pkt = NULL; > int ret = 0; > + AVFormatContext *fc = mux->fc; > > pkt = av_packet_alloc(); > if (!pkt) { > ret = AVERROR(ENOMEM); > goto finish; > } > + ret = avformat_write_header(fc, &mux->opts); > + if (ret < 0) { > + av_log(mux, AV_LOG_ERROR, "Could not write header (incorrect codec " > + "parameters ?): %s\n", av_err2str(ret)); > + goto finish; > + } > + //assert_avoptions(of->opts); > + mux->header_written = 1; > > thread_set_name(of); > > @@ -599,15 +608,6 @@ int mux_check_init(Muxer *mux) > return 0; > } > > - ret = avformat_write_header(fc, &mux->opts); > - if (ret < 0) { > - av_log(mux, AV_LOG_ERROR, "Could not write header (incorrect codec " > - "parameters ?): %s\n", av_err2str(ret)); > - return ret; > - } > - //assert_avoptions(of->opts); > - mux->header_written = 1; > - > av_dump_format(fc, of->index, fc->url, 1); > nb_output_dumped++; > > -- > 2.29.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".
next prev parent reply other threads:[~2023-11-01 11:18 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-01 9:01 angus.chen-at-intel.com 2023-11-01 11:17 ` Zhao Zhili [this message] 2023-11-01 21:44 ` Michael Niedermayer
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_4135053EF556099D14E1DA5BF234E3809609@qq.com \ --to=quinkblack@foxmail.com \ --cc=angus.chen@intel.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