Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] QOA decoding support
Date: Wed, 27 Sep 2023 14:52:35 +0200
Message-ID: <CAPYw7P4+mavmtnPtMSEkzeZwV5aEi-=N6hd_uQAdYQX-dH+cSA@mail.gmail.com> (raw)
In-Reply-To: <GV1P250MB0737817238637E88318840128FC2A@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>

On Wed, Sep 27, 2023 at 2:51 PM Andreas Rheinhardt <
andreas.rheinhardt@outlook.com> wrote:

> Paul B Mahol:
> > On Sun, Sep 24, 2023 at 2:04 AM Andreas Rheinhardt <
> > andreas.rheinhardt@outlook.com> wrote:
> >
> >> Paul B Mahol:
> >>>
> >>> +        if (!qoa->frame_size) {
> >>> +            for (; i < buf_size; i++) {
> >>> +                state = (state << 8) | buf[i];
> >>> +                if (((state & 0xFFFF) > 0 && (state >> 56))) {
> >>> +                    qoa->frame_size = state & 0xFFFF;
> >>> +                    qoa->duration = (state >> 16) & 0xFFFF;
> >>> +                    break;
> >>> +                }
> >>> +            }
> >>> +        }
> >>
> >> So this codec uses a length field. In this case it is quite simple to
> >> avoid the parser (and its implicit memcpy) altogether and just make the
> >> demuxer directly output packets of the correct size. This is quite
> >> natural given that this format does not seem to provide any features
> >> like resyncing support (or at least the parser does not implement them).
> >>
> >
> > But channels/sample rate may differ between packets.
>
> And?
>
> > Also it may be in other formats, like wav. So I picked parser as more
> > valuable implementation.
> >
>
> Then you could simply reuse the code inside libavformat.
>

What code?
I think that having parser is much more useful.


>
> - Andreas
>
> _______________________________________________
> 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".
>
_______________________________________________
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".

  reply	other threads:[~2023-09-27 12:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-23 21:39 Paul B Mahol
2023-09-24  0:05 ` Andreas Rheinhardt
2023-09-24  0:48   ` Paul B Mahol
2023-09-27 12:52     ` Andreas Rheinhardt
2023-09-27 12:52       ` Paul B Mahol [this message]
2023-09-27 12:57         ` Nicolas George
2023-09-27 13:00           ` Paul B Mahol
2023-09-27 18:37             ` Michael Niedermayer
2023-09-27 19:59               ` Paul B Mahol
2023-10-06 11:54                 ` Paul B Mahol
2023-09-27 13:02           ` Paul B Mahol
2023-09-27 12:58       ` Nicolas George
2023-09-27 13:05         ` Andreas Rheinhardt
2023-09-27 13:09           ` Paul B Mahol
2023-09-24  0:50 ` Paul B Mahol
2023-09-27 12:44   ` Paul B Mahol
2023-09-27 12:54   ` Tomas Härdin
2023-09-27 12:56     ` Paul B Mahol
2023-09-27 12:57       ` Tomas Härdin
2023-09-27 12:59         ` Paul B Mahol
2023-09-27 13:05           ` Tomas Härdin

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='CAPYw7P4+mavmtnPtMSEkzeZwV5aEi-=N6hd_uQAdYQX-dH+cSA@mail.gmail.com' \
    --to=onemda@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