From: Kieran Kunhya <kierank@obe.tv>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 5/8] lavu: add a JSON writer API (WIP)
Date: Sun, 30 Apr 2023 22:51:36 +0100
Message-ID: <CAK+ULv7-dQw5dEkYS3nSsTXUyi7QMzamnvZJe69cupBeRsJTRQ@mail.gmail.com> (raw)
In-Reply-To: <20230430150636.GK275832@pb2>
> There are many projects which use libavcodec, format, filter
> Human users use these projects
>
> If the standarization is at a C struct level only then the human interface
> for each application can be different.
> Thats fine if the 2 cases use fundamentally different interfaces like a
> GUI draging, droping and connecting components vs some command line
> interface.
> But if 2 applications both use command line / string based interfaces
> it would be nice to the human user if she could use/learn the same syntax
> and transfer a working example / script from one to the other.
>
> So i think strings do matter for C libs because of that.
>
> thx
>
The interface and the exchange format are completely different things.
Kieran
_______________________________________________
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-04-30 21:51 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 9:55 [FFmpeg-devel] [PATCH 1/8] lavu: add macros to help making future-proof structures Nicolas George
2023-04-28 9:55 ` [FFmpeg-devel] [PATCH 2/8] lavu: new AVWriter API Nicolas George
2023-04-28 10:37 ` Rodney Baker
2023-04-28 11:20 ` Nicolas George
2023-05-02 15:53 ` Rémi Denis-Courmont
2023-05-02 16:53 ` Nicolas George
2023-05-02 18:29 ` Rémi Denis-Courmont
2023-05-02 18:36 ` Nicolas George
2023-05-02 18:46 ` Rémi Denis-Courmont
2023-05-02 18:47 ` Nicolas George
2023-04-28 9:55 ` [FFmpeg-devel] [PATCH 3/8] lavu/writer: add test Nicolas George
2023-04-28 9:55 ` [FFmpeg-devel] [PATCH 4/8] lavf/dump: use a writer Nicolas George
2023-04-28 9:55 ` [FFmpeg-devel] [PATCH 5/8] lavu: add a JSON writer API (WIP) Nicolas George
2023-04-29 9:11 ` Nicolas George
2023-04-29 9:41 ` Anton Khirnov
2023-04-29 14:06 ` James Almer
2023-04-29 17:17 ` Nicolas George
2023-04-29 15:06 ` Derek Buitenhuis
2023-04-30 0:29 ` Kieran Kunhya
2023-05-01 6:20 ` Vittorio Giovara
2023-04-29 17:11 ` Nicolas George
2023-04-29 18:27 ` Anton Khirnov
2023-04-29 18:33 ` Nicolas George
2023-05-01 6:57 ` Leo Izen
2023-05-01 9:51 ` Nicolas George
2023-05-01 10:18 ` Jean-Baptiste Kempf
2023-04-30 15:06 ` Michael Niedermayer
2023-04-30 21:51 ` Kieran Kunhya [this message]
2023-05-01 9:46 ` Nicolas George
2023-04-28 9:55 ` [FFmpeg-devel] [PATCH 6/8] lavu: add JSON writer test (WIP) Nicolas George
2023-04-28 9:55 ` [FFmpeg-devel] [PATCH 7/8] lavf/options: add av_disposition_write() Nicolas George
2023-04-28 9:55 ` [FFmpeg-devel] [PATCH 8/8] lavf/dump: use av_disposition_write() Nicolas George
2023-04-29 8:17 ` [FFmpeg-devel] [PATCH 1/8] lavu: add macros to help making future-proof structures Anton Khirnov
2023-04-29 15:11 ` Derek Buitenhuis
2023-05-02 15:36 ` Rémi Denis-Courmont
2023-05-02 16:42 ` Nicolas George
2023-05-02 18:31 ` Rémi Denis-Courmont
2023-05-02 18:38 ` Nicolas George
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=CAK+ULv7-dQw5dEkYS3nSsTXUyi7QMzamnvZJe69cupBeRsJTRQ@mail.gmail.com \
--to=kierank@obe.tv \
--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