From: Paul B Mahol <onemda@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC PATCH 3/3] HACK: avformat: rawenc: allow to output a raw PRFT Date: Fri, 22 Sep 2023 13:41:02 +0200 Message-ID: <CAPYw7P6hGaCC=FjQ=7Zs=-N=Qx7+TbWyjp1u8DRZ8Jr7Ex_3_w@mail.gmail.com> (raw) In-Reply-To: <CAJiuCceMRc+DEwiRi5dFwjYX0GSy1bc_71Q0sTwuhAPvEXWGJw@mail.gmail.com> On Fri, Sep 22, 2023 at 12:06 PM Clément Péron <peron.clem@gmail.com> wrote: > Hi Paul > > On Fri, 22 Sept 2023 at 11:27, Paul B Mahol <onemda@gmail.com> wrote: > > > > On Fri, Sep 22, 2023 at 10:38 AM Clément Péron <peron.clem@gmail.com> > wrote: > > > > > Hi Andreas, > > > > > > On Fri, 22 Sept 2023 at 09:58, Andreas Rheinhardt > > > <andreas.rheinhardt@outlook.com> wrote: > > > > > > > > Clément Péron: > > > > > Hi Michael, Andreas, > > > > > > > > > > On Thu, 21 Sept 2023 at 22:50, Andreas Rheinhardt > > > > > <andreas.rheinhardt@outlook.com> wrote: > > > > >> > > > > >> Michael Niedermayer: > > > > >>> On Thu, Sep 21, 2023 at 02:17:00PM +0200, Clément Péron wrote: > > > > >>>> Output the producer reference time to a dirty raw output. > > > > >>>> > > > > >>>> Signed-off-by: Clément Péron <peron.clem@gmail.com> > > > > >>>> --- > > > > >>>> libavformat/rawenc.c | 122 > > > +++++++++++++++++++++++++++++++++++++++++++ > > > > >>>> 1 file changed, 122 insertions(+) > > > > >>> > > > > >>> this breaks fate-filter-volume and others > > > > >>> (Segmentation fault) > > > > >>> > > > > >>> I can rerun it with debug symbols and provide peoper gdb output > > > > >>> but i suspect given this has "HACK" in the title you are aware of > > > this > > > > > > > > > > The "HACK" tag meaning was not supposed to be: "it's ok if it > > > > > segfaults", but more to trigger a discussion is it possible to > > > > > properly support an output timestamp in the raw video demux, and if > > > > > yes how to do it :) > > > > > > > > If you need a timestamp for raw video, then use a proper container > and > > > > not raw video. In fact, this patch basically creates new formats > > > > different from all the raw formats. > > > > > > Yes I agree, but I do not want to add too much overhead nor > > > computation processing or memory copy to my pipeline just to mux and > > > demux between ffmpeg and my python script. > > > > > > The idea is to have a very light structure to easily pipe it. > > > > > > I'm not familiar with audio/video container but it seems to me that > > > parsing containers are not very light no? > > > > > > > > Containers range from almost no processing like .y4m to complex monsters > > like .mxf > > .y4m doesn't contain a timestamp either, and I don't want to use a > complex container :), > I doubt storing clock time in container for each frame is correct approach. Is this variable frame rate video? One can always add another, trivial container with just one field having whatever you want and with optional magic string in header. Or can try/explore NUT container in FFmpeg. > > > > > This patch is hack and approach/solution it tries is flawed. > > 100% agree with you that's why I prefix the patch with "HACK:", > > Regards, > Clement > > > > > > > > > Thanks, > > > Clement > > > > > > > > > > > > > > - 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". > > > > > _______________________________________________ > > 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". > _______________________________________________ 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-22 11:41 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-21 12:16 [FFmpeg-devel] [RFC PATCH 0/3] Propagate PRFT side data Clément Péron 2023-09-21 12:16 ` [FFmpeg-devel] [RFC PATCH 1/3] frame: decode: propagate PRFT side data packet to frame Clément Péron 2023-09-21 12:16 ` [FFmpeg-devel] [RFC PATCH 2/3] avcodec: rawenc: Forward PRFT frame data to packet Clément Péron 2023-09-21 12:17 ` [FFmpeg-devel] [RFC PATCH 3/3] HACK: avformat: rawenc: allow to output a raw PRFT Clément Péron 2023-09-21 20:09 ` Michael Niedermayer 2023-09-21 20:51 ` Andreas Rheinhardt 2023-09-22 7:44 ` Clément Péron 2023-09-22 7:59 ` Andreas Rheinhardt 2023-09-22 8:38 ` Clément Péron 2023-09-22 9:26 ` Paul B Mahol 2023-09-22 10:05 ` Clément Péron 2023-09-22 11:41 ` Paul B Mahol [this message] 2023-09-22 12:39 ` Clément Péron 2023-09-22 13:16 ` Paul B Mahol 2023-09-22 14:29 ` Clément Péron 2023-09-22 17:39 ` Paul B Mahol 2023-09-22 10:02 ` Andreas Rheinhardt 2023-09-22 10:10 ` Clément Péron 2023-09-22 11:34 ` Andreas Rheinhardt 2023-09-22 12:31 ` Clément Péron 2023-09-21 13:12 ` [FFmpeg-devel] [RFC PATCH 0/3] Propagate PRFT side data Kieran Kunhya 2023-09-21 15:41 ` Clément Péron 2023-09-24 9:12 ` Clément Péron 2023-10-24 15:10 ` Clément Péron
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='CAPYw7P6hGaCC=FjQ=7Zs=-N=Qx7+TbWyjp1u8DRZ8Jr7Ex_3_w@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