Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Steven Liu <lingjiujianke@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v1] avformat/rtmpproto: support fourCcList property in enhanced rtmp
Date: Thu, 24 Aug 2023 13:33:37 +0800
Message-ID: <CADxeRw=vnrQmyJASaQiXZ-eM+=ptkxdV0MhDAwcoGOV4Tb2=_g@mail.gmail.com> (raw)
In-Reply-To: <92a9bf80-8ac0-4cc5-982-9934b5d8c430@passwd.hu>

Marton Balint <cus@passwd.hu> 于2023年8月24日周四 01:43写道:
>
>
>
> On Wed, 23 Aug 2023, Martin Storsjö wrote:
>
> > On Wed, 23 Aug 2023, Jean-Baptiste Kempf wrote:
> >
> >>  Hello,
> >>
> >>  On Mon, 21 Aug 2023, at 03:35, Steven Liu wrote:
> >>>  Jean-Baptiste Kempf <jb@videolan.org> 于2023年8月20日周日 16:29写道:
> >>>>
> >>>>  Hello,
> >>>  Hi
> >>>>
> >>>>  On Sun, 20 Aug 2023, at 06:10, Steven Liu wrote:
> >>>> >  As the enhanced rtmp Extending NetConnection connect Command section
> >>>> >  said, the rtmp should add a property named fourCcLive, but there
> >>>> >  should
> >>>> >  only one codec can be set for the video stream in rtmp+flv, so user
> >>>> >  can
> >>>> >  use the option rtmp_enhanced_flags to set the enhanced rtmp with av1,
> >>>> >  hevc or vp9.
> >>>>
> >>>>  Technically, the protocol allows any type of FourCC, no?
> >>>  The protocol should allows any type of FourCC, i saw there have three
> >>>  codecs in the example["av01", "vp09", "hvc1"].
> >>
> >>  My question is then why have 0,1,2,3 and not a fourcc then? Or does this
> >>  question make no sense on the protocol level?
> >
> > Put another way, why map a string to a number and back to a string - why not
> > just keep it a string throughout?
>
> Agreed. Plus it is actually list, so you eventually you might want to
> support multiple fourcc-s by splitting the fourcc list. And the
> type is a strict array, so simply putting a string wihtout array length
> seems suspicious anyway.

new version patchset is comming:
https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2023-August/313444.html

>
> Regards,
> Marton
> _______________________________________________
> 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-08-24  5:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-20  4:10 Steven Liu
2023-08-20  8:28 ` Jean-Baptiste Kempf
2023-08-21  1:35   ` Steven Liu
2023-08-23 15:39     ` Jean-Baptiste Kempf
2023-08-23 16:17       ` Martin Storsjö
2023-08-23 17:40         ` Marton Balint
2023-08-24  5:33           ` Steven Liu [this message]

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='CADxeRw=vnrQmyJASaQiXZ-eM+=ptkxdV0MhDAwcoGOV4Tb2=_g@mail.gmail.com' \
    --to=lingjiujianke@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