From: Anton Khirnov <anton@khirnov.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Devin Heitmueller <dheitmueller@ltnglobal.com> Subject: Re: [FFmpeg-devel] [PATCH v4 1/6] ccfifo: Properly handle CEA-708 captions through framerate conversion Date: Wed, 03 May 2023 11:20:19 +0200 Message-ID: <168310561962.3843.17840126335542048705@lain.khirnov.net> (raw) In-Reply-To: <1682699871-22331-2-git-send-email-dheitmueller@ltnglobal.com> Quoting Devin Heitmueller (2023-04-28 18:37:46) > +void ff_ccfifo_freep(AVCCFifo **ccf) > +{ > + if (ccf && *ccf) { Don't check for ccf, it makes no sense to call this function with ccf==NULL, so silently ignoring it can hide bugs. > + AVCCFifo *tmp = *ccf; > + if (tmp->cc_608_fifo) > + av_fifo_freep2(&tmp->cc_608_fifo); Useless checks, av_fifo_freep2 can be called on &NULL. > + if (tmp->cc_708_fifo) > + av_fifo_freep2(&tmp->cc_708_fifo); > + av_freep(*ccf); > + } > +} > + > +AVCCFifo *ff_ccfifo_alloc(AVRational *framerate, void *log_ctx) We typically pass AVRational directly, not as pointers. That also makes it clear that the passed value is not modified. > +{ > + AVCCFifo *ccf; > + int i; > + > + ccf = av_mallocz(sizeof(*ccf)); > + if (!ccf) > + return NULL; > + > + if (!(ccf->cc_708_fifo = av_fifo_alloc2(MAX_CC_ELEMENTS, CC_BYTES_PER_ENTRY, 0))) > + goto error; > + > + if (!(ccf->cc_608_fifo = av_fifo_alloc2(MAX_CC_ELEMENTS, CC_BYTES_PER_ENTRY, 0))) > + goto error; > + > + /* Based on the target FPS, figure out the expected cc_count and number of > + 608 tuples per packet. See ANSI/CTA-708-E Sec 4.3.6.1. */ > + for (i = 0; i < FF_ARRAY_ELEMS(cc_lookup_vals); i++) { > + if (framerate->num == cc_lookup_vals[i].num && > + framerate->den == cc_lookup_vals[i].den) { > + ccf->expected_cc_count = cc_lookup_vals[i].cc_count; > + ccf->expected_608 = cc_lookup_vals[i].num_608; > + break; > + } > + } > + > + if (ccf->expected_608 == 0) { > + /* We didn't find an output frame we support. We'll let the call succeed > + and the FIFO to be allocated, but the extract/inject functions will simply > + leave everything the way it is */ > + av_log(ccf->log_ctx, AV_LOG_WARNING, "cc_fifo cannot transcode captions fps=%d/%d\n", > + framerate->num, framerate->den); Won't this result in spurious warnings for users who are just converting framerates and don't have any captions. If so it should probably be printed the first time we actually see caption side data. > + ccf->passthrough = 1; > + } > + > + return ccf; > + > +error: > + ff_ccfifo_freep(&ccf); > + return NULL; > +} > + > +int ff_ccfifo_injectbytes(AVCCFifo *ccf, uint8_t **data, size_t *len) > +{ > + char *cc_data; > + int cc_filled = 0; > + int i; > + > + if (!ccf) > + return AVERROR(EINVAL); For all the extract/inject functions: it should be invalid to call them with a NULL context, so this should be an av_assert0() or not be here at all. > + > + if (ccf->passthrough) { > + *data = NULL; > + *len = 0; > + return 0; > + } > + > + cc_data = av_mallocz(ccf->expected_cc_count * CC_BYTES_PER_ENTRY); This buffer size is constant for a given AVCCFifo object, so perhaps ff_ccfifo_alloc() could return required buffer size and this function could write into a user-provided buffer and avoid constant dynamic allocation. > + if (!cc_data) { > + return AVERROR(ENOMEM); > + } > + > + for (i = 0; i < ccf->expected_608; i++) { > + if (av_fifo_can_read(ccf->cc_608_fifo) >= CC_BYTES_PER_ENTRY) { > + av_fifo_read(ccf->cc_608_fifo, &cc_data[cc_filled * CC_BYTES_PER_ENTRY], > + CC_BYTES_PER_ENTRY); This looks wrong, as fifo operations are in elements, and your elements are already CC_BYTES_PER_ENTRY. So every read actually writes CC_BYTES_PER_ENTRY * CC_BYTES_PER_ENTRY bytes to cc_data. I think you can also do this as a single av_fifo_read() call without a loop. -- Anton Khirnov _______________________________________________ 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-05-03 9:20 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-28 16:37 [FFmpeg-devel] [PATCH v4 0/6] Add support for Closed Caption FIFO Devin Heitmueller 2023-04-28 16:37 ` [FFmpeg-devel] [PATCH v4 1/6] ccfifo: Properly handle CEA-708 captions through framerate conversion Devin Heitmueller 2023-05-03 9:20 ` Anton Khirnov [this message] 2023-05-03 13:15 ` Devin Heitmueller 2023-04-28 16:37 ` [FFmpeg-devel] [PATCH v4 2/6] vf_fps: properly preserve CEA-708 captions Devin Heitmueller 2023-04-28 16:37 ` [FFmpeg-devel] [PATCH v4 3/6] yadif: Properly preserve CEA-708 closed captions Devin Heitmueller 2023-04-28 16:37 ` [FFmpeg-devel] [PATCH v4 4/6] tinterlace: " Devin Heitmueller 2023-04-28 16:37 ` [FFmpeg-devel] [PATCH v4 5/6] vf_ccrepack: Add new filter to repack CEA-708 side data Devin Heitmueller 2023-04-30 22:42 ` Lance Wang 2023-05-02 14:17 ` Devin Heitmueller 2023-04-28 16:37 ` [FFmpeg-devel] [PATCH v4 6/6] decklink_enc: add support for playout of 608 captions in MOV files Devin Heitmueller 2023-04-30 23:01 ` Lance Wang 2023-05-02 14:47 ` Devin Heitmueller 2023-05-03 7:36 ` Lance Wang
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=168310561962.3843.17840126335542048705@lain.khirnov.net \ --to=anton@khirnov.net \ --cc=dheitmueller@ltnglobal.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