From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] QOA decoding support
Date: Wed, 27 Sep 2023 15:05:07 +0200
Message-ID: <GV1P250MB0737D98AAF03ACF7649803948FC2A@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <ZRQnAmSqXcwb2tVS@phare.normalesup.org>
Nicolas George:
> Andreas Rheinhardt (12023-09-27):
>> Then you could simply reuse the code inside libavformat.
>
> Do you finally support merging the libraries then?
>
> Because otherwise, using from libavformat code for an individual
> component of libavcodec requires adding a new avpriv function.
>
What I meant was: He shall write a simple function which reads from the
input, determines the size of the packet, allocates and reads the actual
packet (thereby avoiding memcpy's) and sets the codec parameters based
upon the input (changes may need to be propagated via side-data
updates). This is supposed to do what the parser does and it is supposed
to stay completely inside libavformat to be reused by e.g. the Wav
demuxer if needed. There is no need for a separate copy of this code
inside libavcodec, so whether the libraries are split or not is
irrelevant here.
- 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".
next prev parent reply other threads:[~2023-09-27 13:04 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
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 [this message]
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=GV1P250MB0737D98AAF03ACF7649803948FC2A@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM \
--to=andreas.rheinhardt@outlook.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