Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] configure: select subordinate formats for HLS
Date: Tue, 14 Feb 2023 14:16:22 +0530
Message-ID: <00d936b9-2741-85a5-4de6-9ffd3475d2a4@gyani.pro> (raw)
In-Reply-To: <20230211123604.19494-1-ffmpeg@gyani.pro>



On 2023-02-11 06:06 pm, Gyan Doshi wrote:
> HLS segments may be MPEG-TS or fragmented MP4, so those (de)muxers are
> required for reading/writing HLS media segments.
>
> Fixes functionality with --disable-everything --enable-demuxer=hls
> --enable-muxer=hls
Comments?

> ---
>   configure | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/configure b/configure
> index d38613309d..2f1771c336 100755
> --- a/configure
> +++ b/configure
> @@ -3436,8 +3436,8 @@ flac_demuxer_select="flac_parser"
>   flv_muxer_select="aac_adtstoasc_bsf"
>   gxf_muxer_select="pcm_rechunk_bsf"
>   hds_muxer_select="flv_muxer"
> -hls_demuxer_select="adts_header ac3_parser"
> -hls_muxer_select="mpegts_muxer"
> +hls_demuxer_select="adts_header ac3_parser mov_demuxer mpegts_demuxer"
> +hls_muxer_select="mov_muxer mpegts_muxer"
>   hls_muxer_suggest="gcrypt openssl"
>   image2_alias_pix_demuxer_select="image2_demuxer"
>   image2_brender_pix_demuxer_select="image2_demuxer"

_______________________________________________
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-02-14  8:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11 12:36 Gyan Doshi
2023-02-14  8:46 ` Gyan Doshi [this message]
2023-02-15  4:32   ` Gyan Doshi
2023-02-18  9:02     ` 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=00d936b9-2741-85a5-4de6-9ffd3475d2a4@gyani.pro \
    --to=ffmpeg@gyani.pro \
    --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