From: Antoine Soulier via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Antoine Soulier <asoulier@google.com> Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/liblc3: Add encoding/decoding support of LC3 audio codec Date: Fri, 29 Mar 2024 11:41:58 -0700 Message-ID: <CA+wrVda85xp+LoHKmhTTuErPKEqxkhw-D_jzRMrVDkyxgDGTqw@mail.gmail.com> (raw) In-Reply-To: <GV1P250MB07376C7C3CB42AFFF17E98678F3A2@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> With free licensed code, I don't think that will happen; the core algorithm is the same. LC3 is like a subset of LC3plus, but also adds 7.5ms frame duration. I acknowledged the use of only one Codec Id, because it makes sense to me to distinguish both as different profiles / feature sets. Moreover, LC3 and LC3plus declares both the 10ms frame duration. It's impossible to distinguish such a stream as LC3 or LC3plus. The main difference between the 2 codecs are licenses: - LC3 will only be used, and is free to use, over Bluetooth on standard profile claiming it. - LC3plus can be used anywhere, but is under license fee. So it makes sense to me to cover both as LC3. _______________________________________________ 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-03-29 18:42 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-29 17:30 Antoine Soulier via ffmpeg-devel 2024-03-29 17:30 ` [FFmpeg-devel] [PATCH 2/2] avformat/lc3: Add file format for LC3/LC3plus transport Antoine Soulier via ffmpeg-devel 2024-03-30 11:45 ` Paul B Mahol 2024-03-30 21:51 ` Antoine Soulier via ffmpeg-devel 2024-03-30 23:15 ` Paul B Mahol 2024-03-29 17:50 ` [FFmpeg-devel] [PATCH 1/2] avcodec/liblc3: Add encoding/decoding support of LC3 audio codec Andreas Rheinhardt 2024-03-29 18:41 ` Antoine Soulier via ffmpeg-devel [this message] 2024-03-29 18:52 ` Andreas Rheinhardt 2024-04-02 17:56 ` Stefano Sabatini -- strict thread matches above, loose matches on Subject: below -- 2024-04-01 21:32 Antoine Soulier via ffmpeg-devel 2024-04-04 15:39 ` Stefano Sabatini 2024-04-04 16:22 ` James Almer 2024-04-04 16:27 ` Andreas Rheinhardt 2024-03-28 22:33 Antoine Soulier via ffmpeg-devel 2024-03-28 21:35 Antoine Soulier via ffmpeg-devel
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=CA+wrVda85xp+LoHKmhTTuErPKEqxkhw-D_jzRMrVDkyxgDGTqw@mail.gmail.com \ --to=ffmpeg-devel@ffmpeg.org \ --cc=asoulier@google.com \ /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