From: compn <ff@hawaiiantel.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCHv3 7/8] avformat/aiff: G.728 muxing and demuxing
Date: Mon, 9 Jun 2025 14:07:07 -1000
Message-ID: <20250609140707.00002838@hawaiiantel.net> (raw)
In-Reply-To: <GV1P250MB0737B292BE5B0EFE4C64BA4D8F6BA@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>
On Tue, 10 Jun 2025 00:25:24 +0200, Andreas Rheinhardt wrote:
> Peter Ross:
> > ---
> > libavformat/aiff.c | 1 +
> > libavformat/aiffdec.c | 3 +++
> > 2 files changed, 4 insertions(+)
> >
> > diff --git a/libavformat/aiff.c b/libavformat/aiff.c
> > index 1ceac69a70..907f7d8d28 100644
> > --- a/libavformat/aiff.c
> > +++ b/libavformat/aiff.c
> > @@ -40,6 +40,7 @@ const AVCodecTag ff_codec_aiff_tags[] = {
> > { AV_CODEC_ID_GSM, MKTAG('G','S','M',' ') },
> > { AV_CODEC_ID_ADPCM_G722, MKTAG('G','7','2','2') },
> > { AV_CODEC_ID_ADPCM_G726LE, MKTAG('G','7','2','6') },
> > + { AV_CODEC_ID_G728, MKTAG('G','7','2','8') },
> > { AV_CODEC_ID_PCM_S16BE, MKTAG('t','w','o','s') },
> > { AV_CODEC_ID_PCM_S16LE, MKTAG('s','o','w','t') },
> > { AV_CODEC_ID_ADPCM_IMA_QT, MKTAG('i','m','a','4') },
> > diff --git a/libavformat/aiffdec.c b/libavformat/aiffdec.c
> > index bd5bd2e4bb..aeb00cccd0 100644
> > --- a/libavformat/aiffdec.c
> > +++ b/libavformat/aiffdec.c
> > @@ -174,6 +174,9 @@ static int get_aiff_header(AVFormatContext *s, int64_t size,
> > case AV_CODEC_ID_GSM:
> > par->block_align = 33;
> > break;
> > + case AV_CODEC_ID_G728:
> > + par->block_align = 5;
> > + break;
> > default:
> > aiff->block_duration = 1;
> > break;
> >
> Is this and the riff patch based on some spec or are you just inventing
> things here?
maybe i can help.
https://wiki.multimedia.cx/index.php/G.728
lists 0xCD02 and 0x0041
according to the history of that wiki page, the 0xCD02 comes from
"plcmg728.acm" binary codec.
other list of twocc here: https://wiki.multimedia.cx/index.php/TwoCC
i havent myself tested plcmg728.acm , but its on my list to investigate
here https://wiki.multimedia.cx/index.php/Category_talk:Audio_Codecs
plcmg728.acm should be included with the software:
Polycom PVX
"Create video conferences with a USB webcam"
did Polycom make up that entry or should we support it anyways? i say
support it until another 0xCD02 shows up. and then we deal with the
conflict at that time.
if you go to the spec page
https://www-mmsp.ece.mcgill.ca/Documents/AudioFormats/AIFF/AIFF.html
and click samples
https://www-mmsp.ece.mcgill.ca/Documents/AudioFormats/AIFF/Samples.html
at the bottom is g728 sample
o2_728.aiff (1 kB) *
AIFF-C file: G.728 data (compression code: G728)
hopefully that answers all riff/aiff questions.
-compn
_______________________________________________
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:[~2025-06-10 0:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 10:05 [FFmpeg-devel] [PATCHv3 0/8] G.728 decoding Peter Ross
2025-06-09 10:06 ` [FFmpeg-devel] [PATCHv3 1/8] avcodec/g728_template: do_hybrid_window() template Peter Ross
2025-06-09 21:56 ` Tomas Härdin
2025-06-09 10:06 ` [FFmpeg-devel] [PATCHv3 2/8] avcodec/g728_template: make hist parameter constant Peter Ross
2025-06-09 10:06 ` [FFmpeg-devel] [PATCHv3 3/8] avcodec/lpc_functions: compute_lpc_coefs: add starting lpc order and err cache parameters Peter Ross
2025-06-09 10:07 ` [FFmpeg-devel] [PATCHv3 4/8] avcodec/g728dec: G.728 decoder Peter Ross
2025-06-09 10:07 ` [FFmpeg-devel] [PATCHv3 5/8] avformat/g728dec: raw G.728 demuxer Peter Ross
2025-06-09 10:08 ` [FFmpeg-devel] [PATCHv3 6/8] avformat/riff: G.728 muxing and demuxing Peter Ross
2025-06-09 10:08 ` [FFmpeg-devel] [PATCHv3 7/8] avformat/aiff: " Peter Ross
2025-06-09 22:25 ` Andreas Rheinhardt
2025-06-10 0:07 ` compn [this message]
2025-06-10 0:29 ` Peter Ross
2025-06-11 14:45 ` compn
2025-06-09 10:08 ` [FFmpeg-devel] [PATCHv3 8/8] avformat/rtp: " Peter Ross
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=20250609140707.00002838@hawaiiantel.net \
--to=ff@hawaiiantel.net \
--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