Re: [FFmpeg-devel] [PATCH v2] libavformat: Add ZeroMQ as a protocol option

2019-08-06 Thread Jack Waller
On Wed, Aug 7, 2019 at 10:22 AM Andriy Gelman 
wrote:

> On Sun, 04. Aug 14:36, Andriy Gelman wrote:
> > Changes in v2:
> >   1. Replaced zmq_poll with zmq_msg_recv.
> >   2. Remove user timeout option as zmq_msg_recv(.., .., ZMQ_DONTWAIT) is
> a
> >   non-blocking call.
> >   3. Updated docs.
> >
> > Andriy
>
> > diff --git a/libavformat/Makefile b/libavformat/Makefile
> > index a434b005a4..4a535429b7 100644
> > --- a/libavformat/Makefile
> > +++ b/libavformat/Makefile
> > @@ -631,6 +631,7 @@ OBJS-$(CONFIG_LIBRTMPTE_PROTOCOL)+= librtmp.o
> >  OBJS-$(CONFIG_LIBSMBCLIENT_PROTOCOL) += libsmbclient.o
> >  OBJS-$(CONFIG_LIBSRT_PROTOCOL)   += libsrt.o
> >  OBJS-$(CONFIG_LIBSSH_PROTOCOL)   += libssh.o
> > +OBJS-$(CONFIG_LIBZMQ_PROTOCOL)
> += libzmq.o
> >
>

There is a TAB here,
Please remove it


> >  # libavdevice dependencies
> >  OBJS-$(CONFIG_IEC61883_INDEV)+= dv.o
>
>

>
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-devel] [PATCH] avformat/libsrt: Change latency option to milliseconds

2020-04-08 Thread Jack Waller
On Wed, Apr 8, 2020 at 3:34 PM pkv  wrote:

>
> Le 08/04/2020 à 3:45 am, Limin Wang a écrit :
> > On Wed, Apr 08, 2020 at 02:16:23AM +0200, pkv wrote:
> >> Hi
> >>
> >> Le 08/04/2020 à 12:33 am, Limin Wang a écrit :
> >>> On Tue, Apr 07, 2020 at 08:25:44PM +0200, pkv wrote:
>  Hi
> 
>  new patch for latency option following the comments from N. George.
> >>> I recall I had submit a patchset for related option incliding latency.
> >>>
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/20200331140808.8839-2-lance.lmw...@gmail.com/
> >> hadn't spotted it; why was it not merged ?
> >>
> >>
> >>> Why I haven't change to use AV_OPT_TYPE_DURATION, for the latency can
> >>> be used in format srt://:port?latency=?, it's in unit of ms,
> >>> in addition, AV_OPT_TYPE_DURATION is in unit of second default, it'll
> >>> break the old user.
> >> i tested with ffmpeg.exe; the change to
> >>
> >> AV_OPT_TYPE_DURATION
> >>
> >> didn't seem to break anything.
> >>
> >> The default is still set to whatever the libsrt API has set (120 ms
> >> for transtype=live).
> >>
> >> Can you produce code broken by that change ?
> > What's your command line?
> > I recall If use AV_OPT_TYPE_DURATION for option, the default is in unit
> of second if your
> > don't add suffix of ms, us. However the old is us, so it'll cause old
> user
> > setting broken.
> >
> Ok I get your point.
>
> here are the commands I tested with:
>
> ffmpeg.exe -re -i source.mp4 -c copy -f mpegts srt:://dest:port
>
> and
>
> ffmpeg.exe -re -i source.mp4 -c copy -f mpegts
> srt:://dest:port?latency=40
>
> These two don't break anything.
>
> But indeed
>
> ffmpeg.exe -re -i source.mp4 -c copy -latency=40 -f mpegts
> srt:://dest:port
>
> is breaking stuff.
>
> I'll revert the change suggested by N. George in that case.
>

DO NOT CHANGE,

Microsecond is better than millisecond. it's compatible with other ffmpeg
options

The fault is srt's implementation, not ffmpeg's
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-devel] [PATCH 48/48] fftools/ffmpeg: use av_packet_alloc() to allocate packets

2021-03-05 Thread Jack Waller
On Sat, Mar 6, 2021 at 12:44 AM James Almer  wrote:

> Signed-off-by: James Almer 
> ---
>  fftools/ffmpeg.c | 318 +++
>  fftools/ffmpeg.h |   4 +
>  fftools/ffmpeg_opt.c |   5 +-
>  3 files changed, 177 insertions(+), 150 deletions(-)
>
> diff --git a/fftools/ffmpeg.c b/fftools/ffmpeg.c
> index 2abbc0ff29..46bb014de8 100644
> --- a/fftools/ffmpeg.c
> +++ b/fftools/ffmpeg.c
>
> @@ -610,9 +611,9 @@ static void ffmpeg_cleanup(int ret)
>
>  if (ost->muxing_queue) {
>  while (av_fifo_size(ost->muxing_queue)) {
> -AVPacket pkt;
> +AVPacket *pkt;
>  av_fifo_generic_read(ost->muxing_queue, &pkt,
> sizeof(pkt), NULL);
>

Should you modify av_fifo_generic_read() for its second arguments( &pkt) as
well?
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-devel] Patch: aligin fix

2021-04-07 Thread Jack Waller
Dear:

In doc/example/resampling_audio.c

/* buffer is going to be directly written to a rawaudio file, no alignment
*/
dst_nb_channels = av_get_channel_layout_nb_channels(dst_ch_layout);
ret = av_samples_alloc_array_and_samples(&dst_data, &dst_linesize,
dst_nb_channels,
 dst_nb_samples, dst_sample_fmt, 0);

if the comment "no alignment" is right, we should change the last parameter
of  av_samples_alloc_array_and_samples() from 0 to 1.

patch is attached.


align_fix.diff
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-devel] Fix x264 SEI offset

2021-07-26 Thread Jack Waller
Oops

Sent wrong patch, Please use the following:

diff --git a/libavcodec/libx264.c b/libavcodec/libx264.c
index 9afaf19547..f78365a4f7 100644
--- a/libavcodec/libx264.c
+++ b/libavcodec/libx264.c
@@ -936,7 +936,7 @@ static av_cold int X264_init(AVCodecContext *avctx)
 for (i = 0; i < nnal; i++) {
 /* Don't put the SEI in extradata. */
 if (nal[i].i_type == NAL_SEI) {
-av_log(avctx, AV_LOG_INFO, "%s\n", nal[i].p_payload+25);
+av_log(avctx, AV_LOG_INFO, "%s\n", nal[i].p_payload+24);
 x4->sei_size = nal[i].i_payload;
 x4->sei  = av_malloc(x4->sei_size);
 if (!x4->sei)



On Mon, Jul 26, 2021 at 8:09 PM Jack Waller  wrote:

> Dear:
>
> The libavcodec/libx264.c uses the wrong offset to obtain the SEI
>
> diff --git a/libavcodec/libx264.c b/libavcodec/libx264.c
> index f78365a4f7..9afaf19547 100644
> --- a/libavcodec/libx264.c
> +++ b/libavcodec/libx264.c
> @@ -936,7 +936,7 @@ static av_cold int X264_init(AVCodecContext *avctx)
>  for (i = 0; i < nnal; i++) {
>  /* Don't put the SEI in extradata. */
>  if (nal[i].i_type == NAL_SEI) {
> -av_log(avctx, AV_LOG_INFO, "%s\n", nal[i].p_payload+24);
> +av_log(avctx, AV_LOG_INFO, "%s\n", nal[i].p_payload+25);
>  x4->sei_size = nal[i].i_payload;
>  x4->sei  = av_malloc(x4->sei_size);
>  if (!x4->sei)
>


fix_x264_SEI_offset_2.diff
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".


[FFmpeg-devel] Fix x264 SEI offset

2021-07-26 Thread Jack Waller
Dear:

The libavcodec/libx264.c uses the wrong offset to obtain the SEI

diff --git a/libavcodec/libx264.c b/libavcodec/libx264.c
index f78365a4f7..9afaf19547 100644
--- a/libavcodec/libx264.c
+++ b/libavcodec/libx264.c
@@ -936,7 +936,7 @@ static av_cold int X264_init(AVCodecContext *avctx)
 for (i = 0; i < nnal; i++) {
 /* Don't put the SEI in extradata. */
 if (nal[i].i_type == NAL_SEI) {
-av_log(avctx, AV_LOG_INFO, "%s\n", nal[i].p_payload+24);
+av_log(avctx, AV_LOG_INFO, "%s\n", nal[i].p_payload+25);
 x4->sei_size = nal[i].i_payload;
 x4->sei  = av_malloc(x4->sei_size);
 if (!x4->sei)


fix_x264_SEI_offset.diff
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-devel] Possibly a little bug in af_loudnorm.c

2022-08-20 Thread Jack Waller
Please check the code:line 209

if (c == 0 || fabs(buf[index + c]) > max_peak)
max_peak = fabs(buf[index + c]);

'max_peak' is initialized.


On Sat, Aug 20, 2022 at 5:39 PM jagad hariseno 
wrote:

> Hi All,
>
> at af_loudnorm.c in line number 188:
> double this, next, max_peak;
>
> max_peak is not initialized with 0. and could be contains any value or
> noise.
> I could be wrong but I think init with 0. should be better:
>
> double this, next, max_peak=0.;
>
> Best Regards
>
> jagad.
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@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-requ...@ffmpeg.org with subject "unsubscribe".