Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Unterweger <dustsigns@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v7 4/4] doc/examples/transcode_aac: Bump date
Date: Mon, 2 May 2022 10:19:58 +0200
Message-ID: <CAKp+PPqmOaAB8sktqSW-t5N8HrB8Nvxz1AZWHqDuE1G6Mzj-_A@mail.gmail.com> (raw)
In-Reply-To: <CAKp+PPoy5coryr7Qj4O2ZnupmrHi2dsVNLe76wLiRBJ1i0Xipw@mail.gmail.com>

On Mon, 2 May 2022 at 09:31, Andreas Unterweger <dustsigns@gmail.com> wrote:
>
> Signed-off-by: Andreas Unterweger <dustsigns@gmail.com>
> ---
>  doc/examples/transcode_aac.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/examples/transcode_aac.c b/doc/examples/transcode_aac.c
> index 909aa1cb73..1b372782ab 100644
> --- a/doc/examples/transcode_aac.c
> +++ b/doc/examples/transcode_aac.c
> @@ -1,5 +1,5 @@
>  /*
> - * Copyright (c) 2013-2018 Andreas Unterweger
> + * Copyright (c) 2013-2022 Andreas Unterweger
>   *
>   * This file is part of FFmpeg.
>   *
> --
> 2.30.2
>
>

Patchwork is again not happy with this (newly rebased) patch and it
does not give any comprehensive indication why. I've been trying to
get this patch in since February with minimal feedback and I have
neither got the time nor the patience to pursue this for another
month.
Unfortunately, it seems that the documentation and examples of libav*
are a very low priority. My repeated, mostly unanswered questions on
IRC and on the FFmpeg user mailing list about how to access or build
the documentation for any of the recent stable libav*/FFmpeg versions
seem to support this. The most recent stable online libav*
documentation is from 2018 (version 4.1); the build instructions for
the documentation are insufficient and my questions about how to build
the documentation without installing all dependencies have been
effectively unanswered.
All of the libav* are very complex already and it is next to
impossible for beginners to get started without easily accessible
documentation and up-to-date examples. I have been trying to keep the
transcode_aac example up to date, but it seems like a futile effort.
Please use or adapt this patch however you see fit. I will stay
subscribed to this mailing list until the end of next week before
moving on. Any further communication can be directed towards my e-mail
address which is also in the transcode_aac header. I sincerely hope
that libav*/FFmpeg will become more beginner-friendly again in the
future.

Best,
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".

  reply	other threads:[~2022-05-02  8:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02  7:31 Andreas Unterweger
2022-05-02  8:19 ` Andreas Unterweger [this message]
2022-05-02  8:39   ` Gyan Doshi
2022-05-02  8:53     ` Andreas Unterweger
2022-05-02  9:37       ` Gyan Doshi
2022-05-02  9:43         ` Andreas Unterweger
2022-05-02  9:48           ` Gyan Doshi

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=CAKp+PPqmOaAB8sktqSW-t5N8HrB8Nvxz1AZWHqDuE1G6Mzj-_A@mail.gmail.com \
    --to=dustsigns@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