From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/6] avformat/s337m: Consider container bit resolution
Date: Tue, 21 Feb 2023 10:47:25 +0100
Message-ID: <50aca536d2be633d23e66dab0457e47b8cde9981.camel@haerdin.se> (raw)
In-Reply-To: <MR1P264MB2483BD964F0097624092701C9BA19@MR1P264MB2483.FRAP264.PROD.OUTLOOK.COM>
fre 2023-02-17 klockan 09:44 +0000 skrev Nicolas Gaullier:
> > > @@ -56,6 +56,12 @@ static int s337m_get_offset_and_codec(void
> > > *avc,
> > > avpriv_report_missing_feature(avc, "Data type %#x in
> > > SMPTE 337M", data_type & 0x1F);
> > > return AVERROR_PATCHWELCOME;
> > > }
> > > + if (container_word_bits &&
> > > + !(container_word_bits == 16 && word_bits == 16) &&
> > > + !(container_word_bits == 24 && word_bits == 20) &&
> >
> > I presume 20/24 is intentional. Does WAV not support signalling 20-
> > bit?
> >
> > The rest looks OK enough
> >
> > /Tomas
>
> You are true, I meant "container_word_bits" as "block_size" rather
> than "valid bits per sample" and
> I think this should be clarified is the latter integration code in
> "wavdec: s337m support" patch where
> I use par->bits_per_coded_sample...
> But I should have rather coded "AV_CODEC_ID_PCM_S16LE ? 16 : 24"
> This is in case a wav file would be detected as 20 bits in a 24 bits
> container (I don't think it is supported yet, but it could as
> bitspersample and validbitpersample are two different fields in
> WAVE_FORMAT_EXTENSIBLE).
> Are you ok with this ?
I haven't worked enough with S377m to really know, but I do know it's a
mess. Is there a way to differentiate "regular" packed 20-bit audio
from S377m in wav?
/Tomas
_______________________________________________
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-02-21 9:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 18:09 [FFmpeg-devel] [PATCH 0/6] wavdev: s337m support Nicolas Gaullier
2023-02-13 18:09 ` [FFmpeg-devel] [PATCH 1/6] avformat/s337m: Split read_packet/get_packet Nicolas Gaullier
2023-02-16 10:36 ` Tomas Härdin
2023-02-13 18:09 ` [FFmpeg-devel] [PATCH 2/6] avformat/s337m: Consider container bit resolution Nicolas Gaullier
2023-02-16 10:36 ` Tomas Härdin
2023-02-17 9:44 ` Nicolas Gaullier
2023-02-21 9:47 ` Tomas Härdin [this message]
2023-02-21 10:43 ` Nicolas Gaullier
2023-02-22 10:07 ` Tomas Härdin
2023-02-13 18:09 ` [FFmpeg-devel] [PATCH 3/6] avformat/s337m: New ff_s337m_probe() Nicolas Gaullier
2023-02-16 10:36 ` Tomas Härdin
2023-02-17 10:12 ` Nicolas Gaullier
2023-02-21 9:41 ` Tomas Härdin
2023-02-21 10:57 ` Nicolas Gaullier
2023-02-13 18:09 ` [FFmpeg-devel] [PATCH 4/6] avformat/wavdec: s337m support Nicolas Gaullier
2023-02-16 10:36 ` Tomas Härdin
2023-02-17 10:30 ` Nicolas Gaullier
2023-02-21 9:53 ` Tomas Härdin
2023-02-21 12:30 ` Nicolas Gaullier
2023-02-22 10:10 ` Tomas Härdin
2023-02-13 18:09 ` [FFmpeg-devel] [PATCH 5/6] avformat/wavdec.c: Reindent after last commit Nicolas Gaullier
2023-02-13 18:09 ` [FFmpeg-devel] [PATCH 6/6] avformat/wavdec: Test s337m Nicolas Gaullier
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=50aca536d2be633d23e66dab0457e47b8cde9981.camel@haerdin.se \
--to=git@haerdin.se \
--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