[FFmpeg-devel] avformat/avformat.h: update the comment from deprecated to new API

Submitted by Steven Liu on Feb. 21, 2019, 7:16 a.m.

Details

Message ID 20190221071624.26150-1-lq@chinaffmpeg.org
State New
Headers show

Commit Message

Steven Liu Feb. 21, 2019, 7:16 a.m.
Signed-off-by: Steven Liu <lq@chinaffmpeg.org>
---
 libavformat/avformat.h | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

Comments

Steven Liu March 11, 2019, 2:18 a.m.
> 在 2019年2月21日,下午3:16,Steven Liu <lq@chinaffmpeg.org> 写道:
> 
> Signed-off-by: Steven Liu <lq@chinaffmpeg.org>
> ---
> libavformat/avformat.h | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/libavformat/avformat.h b/libavformat/avformat.h
> index fdaffa5bf4..12cc8387ed 100644
> --- a/libavformat/avformat.h
> +++ b/libavformat/avformat.h
> @@ -36,15 +36,14 @@
>  * into component streams, and the reverse process of muxing - writing supplied
>  * data in a specified container format. It also has an @ref lavf_io
>  * "I/O module" which supports a number of protocols for accessing the data (e.g.
> - * file, tcp, http and others). Before using lavf, you need to call
> - * av_register_all() to register all compiled muxers, demuxers and protocols.
> + * file, tcp, http and others).
>  * Unless you are absolutely sure you won't use libavformat's network
>  * capabilities, you should also call avformat_network_init().
>  *
>  * A supported input format is described by an AVInputFormat struct, conversely
>  * an output format is described by AVOutputFormat. You can iterate over all
> - * registered input/output formats using the av_iformat_next() /
> - * av_oformat_next() functions. The protocols layer is not part of the public
> + * input/output formats using the  av_demuxer_iterate /
> + * av_muxer_iterate() functions. The protocols layer is not part of the public
>  * API, so you can only get the names of supported protocols with the
>  * avio_enum_protocols() function.
>  *
> -- 
> 2.15.2 (Apple Git-101.1)
> 
> 
> 
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
ping
James Almer March 11, 2019, 2:34 a.m.
On 2/21/2019 4:16 AM, Steven Liu wrote:
> Signed-off-by: Steven Liu <lq@chinaffmpeg.org>
> ---
>  libavformat/avformat.h | 7 +++----
>  1 file changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/libavformat/avformat.h b/libavformat/avformat.h
> index fdaffa5bf4..12cc8387ed 100644
> --- a/libavformat/avformat.h
> +++ b/libavformat/avformat.h
> @@ -36,15 +36,14 @@
>   * into component streams, and the reverse process of muxing - writing supplied
>   * data in a specified container format. It also has an @ref lavf_io
>   * "I/O module" which supports a number of protocols for accessing the data (e.g.
> - * file, tcp, http and others). Before using lavf, you need to call
> - * av_register_all() to register all compiled muxers, demuxers and protocols.
> + * file, tcp, http and others).
>   * Unless you are absolutely sure you won't use libavformat's network
>   * capabilities, you should also call avformat_network_init().
>   *
>   * A supported input format is described by an AVInputFormat struct, conversely
>   * an output format is described by AVOutputFormat. You can iterate over all
> - * registered input/output formats using the av_iformat_next() /
> - * av_oformat_next() functions. The protocols layer is not part of the public
> + * input/output formats using the  av_demuxer_iterate /
> + * av_muxer_iterate() functions. The protocols layer is not part of the public

You can add av_muxer_iterate() to the previous line, and after
rearranging the following sentence you'd save an entire line.

Like so:

>  * A supported input format is described by an AVInputFormat struct, conversely
>  * an output format is described by AVOutputFormat. You can iterate over all
>  * input/output formats using the av_demuxer_iterate / av_muxer_iterate() functions.
>  * The protocols layer is not part of the public API, so you can only get the names
>  * of supported protocols with the avio_enum_protocols() function.
Steven Liu March 11, 2019, 3:24 a.m.
> 在 2019年3月11日,上午10:34,James Almer <jamrial@gmail.com> 写道:
> 
> On 2/21/2019 4:16 AM, Steven Liu wrote:
>> Signed-off-by: Steven Liu <lq@chinaffmpeg.org>
>> ---
>> libavformat/avformat.h | 7 +++----
>> 1 file changed, 3 insertions(+), 4 deletions(-)
>> 
>> diff --git a/libavformat/avformat.h b/libavformat/avformat.h
>> index fdaffa5bf4..12cc8387ed 100644
>> --- a/libavformat/avformat.h
>> +++ b/libavformat/avformat.h
>> @@ -36,15 +36,14 @@
>>  * into component streams, and the reverse process of muxing - writing supplied
>>  * data in a specified container format. It also has an @ref lavf_io
>>  * "I/O module" which supports a number of protocols for accessing the data (e.g.
>> - * file, tcp, http and others). Before using lavf, you need to call
>> - * av_register_all() to register all compiled muxers, demuxers and protocols.
>> + * file, tcp, http and others).
>>  * Unless you are absolutely sure you won't use libavformat's network
>>  * capabilities, you should also call avformat_network_init().
>>  *
>>  * A supported input format is described by an AVInputFormat struct, conversely
>>  * an output format is described by AVOutputFormat. You can iterate over all
>> - * registered input/output formats using the av_iformat_next() /
>> - * av_oformat_next() functions. The protocols layer is not part of the public
>> + * input/output formats using the  av_demuxer_iterate /
>> + * av_muxer_iterate() functions. The protocols layer is not part of the public
> 
> You can add av_muxer_iterate() to the previous line, and after
> rearranging the following sentence you'd save an entire line.
> 
> Like so:
> 
>> * A supported input format is described by an AVInputFormat struct, conversely
>> * an output format is described by AVOutputFormat. You can iterate over all
>> * input/output formats using the av_demuxer_iterate / av_muxer_iterate() functions.
>> * The protocols layer is not part of the public API, so you can only get the names
>> * of supported protocols with the avio_enum_protocols() function.

Thanks James,

	new patch submit: https://patchwork.ffmpeg.org/patch/12284/
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Patch hide | download patch | download mbox

diff --git a/libavformat/avformat.h b/libavformat/avformat.h
index fdaffa5bf4..12cc8387ed 100644
--- a/libavformat/avformat.h
+++ b/libavformat/avformat.h
@@ -36,15 +36,14 @@ 
  * into component streams, and the reverse process of muxing - writing supplied
  * data in a specified container format. It also has an @ref lavf_io
  * "I/O module" which supports a number of protocols for accessing the data (e.g.
- * file, tcp, http and others). Before using lavf, you need to call
- * av_register_all() to register all compiled muxers, demuxers and protocols.
+ * file, tcp, http and others).
  * Unless you are absolutely sure you won't use libavformat's network
  * capabilities, you should also call avformat_network_init().
  *
  * A supported input format is described by an AVInputFormat struct, conversely
  * an output format is described by AVOutputFormat. You can iterate over all
- * registered input/output formats using the av_iformat_next() /
- * av_oformat_next() functions. The protocols layer is not part of the public
+ * input/output formats using the  av_demuxer_iterate /
+ * av_muxer_iterate() functions. The protocols layer is not part of the public
  * API, so you can only get the names of supported protocols with the
  * avio_enum_protocols() function.
  *