From: Stefano Sabatini <stefasab@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avformat/lc3: Add file format for LC3/LC3plus transport Date: Wed, 10 Apr 2024 23:22:21 +0200 Message-ID: <ZhcDDb4+QAk1bSkA@mariano> (raw) In-Reply-To: <AS8P250MB07443711134687B6AD72AD1C8F062@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> On date Wednesday 2024-04-10 20:26:01 +0200, Andreas Rheinhardt wrote: > Antoine Soulier via ffmpeg-devel: [...] > > +#if CONFIG_LC3_DEMUXER > > +const FFInputFormat ff_lc3_demuxer = { > > + .p.name = "lc3", > > + .p.long_name = NULL_IF_CONFIG_SMALL("LC3 (Low Complexity > > Communication Codec)"), > > + .p.extensions = "lc3", > > + .p.flags = AVFMT_GENERIC_INDEX, > > + .priv_data_size = sizeof(LC3DemuxContext), > > + .read_probe = lc3_read_probe, > > + .read_header = lc3_read_header, > > + .read_packet = lc3_read_packet, > > +}; > > +#endif > > + > > +#if CONFIG_LC3_MUXER > > +const FFOutputFormat ff_lc3_muxer = { > > + .p.name = "lc3", > > + .p.long_name = NULL_IF_CONFIG_SMALL("LC3 (Low Complexity > > Communication Codec)"), > > + .p.extensions = "lc3", > > + .p.audio_codec = AV_CODEC_ID_LC3, > > + .p.video_codec = AV_CODEC_ID_NONE, > > + .p.flags = AVFMT_NOTIMESTAMPS, > > + .init = lc3_muxer_init, > > + .write_header = lc3_write_header, > > + .write_packet = lc3_write_packet, > > +}; > > +#endif > > You only put the muxer and demuxer inside #if guards. If only one of > these two is enabled, the other's functions will not be used and lead to > compiler warnings. This can be fixed by putting all the stuff for only > the muxer/demuxer inside the #if (see argo_cvg.c for an example). Note: I pointed to codec2.c, which seems to suffer from the same issue, argo_cvg.c is indeed a better example. _______________________________________________ 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:[~2024-04-10 21:22 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-08 22:27 Antoine Soulier via ffmpeg-devel 2024-04-10 9:11 ` Stefano Sabatini 2024-04-10 17:41 ` Antoine Soulier via ffmpeg-devel 2024-04-10 18:26 ` Andreas Rheinhardt 2024-04-10 21:22 ` Stefano Sabatini [this message] 2024-04-10 23:46 ` Antoine Soulier via ffmpeg-devel 2024-04-12 13:05 ` Stefano Sabatini 2024-04-12 23:46 ` Antoine Soulier via ffmpeg-devel 2024-04-13 8:54 ` Stefano Sabatini 2024-04-15 16:40 ` Stefano Sabatini -- strict thread matches above, loose matches on Subject: below -- 2024-04-06 21:08 Antoine Soulier via ffmpeg-devel 2024-04-08 14:30 ` Stefano Sabatini
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=ZhcDDb4+QAk1bSkA@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