From: Paul B Mahol <onemda@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/mjpegdec: add frame threading for mjpeg decoder Date: Thu, 7 Sep 2023 19:48:10 +0200 Message-ID: <CAPYw7P6CcOZYcuAhta1_3-Cj90y6eNgcZ=3ZF_b1qDtnnU_tOA@mail.gmail.com> (raw) In-Reply-To: <CAPYw7P6YG03=kn8EDrS1yUWnJ4w_oxtuE9kNMET_qoTx9wkaFg@mail.gmail.com> On Thu, Sep 7, 2023 at 7:34 PM Paul B Mahol <onemda@gmail.com> wrote: > > > On Thu, Sep 7, 2023 at 7:21 PM Andreas Rheinhardt < > andreas.rheinhardt@outlook.com> wrote: > >> Paul B Mahol: >> > Attached. >> > >> > >> >> Haven't you sent a patch exactly like this before, which led to Michael >> Niedermayer providing a command line where this changes the output? >> > > That was not me. > > But I know what thread you are referring to. > Checked that file, my patch does not fix nor break playing of that .avi That AVI with mjpeg codec is not decoding with latest FFmpeg master code. Even if I extract mjpeg losslessly from avi It still decodes just fine without and with this patch applied. > > >> - Andreas >> >> _______________________________________________ >> 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-09-07 17:40 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-07 16:44 Paul B Mahol 2023-09-07 17:07 ` Andreas Rheinhardt 2023-09-07 17:34 ` Paul B Mahol 2023-09-07 17:48 ` Paul B Mahol [this message] 2023-09-07 21:17 ` Michael Niedermayer 2023-09-07 21:39 ` Paul B Mahol 2023-09-07 21:57 ` 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='CAPYw7P6CcOZYcuAhta1_3-Cj90y6eNgcZ=3ZF_b1qDtnnU_tOA@mail.gmail.com' \ --to=onemda@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