Re: [FFmpeg-trac] #4910(avfilter:closed): support for nl-means denoise filter

[FFmpeg]

#4910: support for nl-means denoise filter
-+
 Reporter:  ponpon   |Owner:  ubitux
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avfilter
  Version:  git-master   |   Resolution:  fixed
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by ponpon):

 Replying to [comment:17 ubitux]:
 i think the default value is too strong for SD video and slow for HD.
 i try to change them in source from
 {{{
 static const AVOption nlmeans_options[] = {
 { "s",  "denoising strength", OFFSET(sigma), AV_OPT_TYPE_DOUBLE, {
 .dbl = 1.0 }, 1.0, 30.0, FLAGS },
 { "r",  "research window",   OFFSET(research_size),
 AV_OPT_TYPE_INT, { .i64 = 7*2+1 }, 0, 99, FLAGS },
 }}}
 to
 {{{
 static const AVOption nlmeans_options[] = {
 { "s",  "denoising strength", OFFSET(sigma), AV_OPT_TYPE_DOUBLE, {
 .dbl = 0.85 }, 0.01, 30.0, FLAGS },
 { "r",  "research window",   OFFSET(research_size),
 AV_OPT_TYPE_INT, { .i64 = 3*2+1 }, 0, 99, FLAGS },
 }}}
 doesn't this brake the work of nlmeans?

 is support for SIMD completed?

 i have requests for nlmeans. should i write them here or open a new
 ticket?

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7066(avfilter:new): Video filter enhancement: fieldhint

[FFmpeg]

#7066: Video filter enhancement: fieldhint
-+
 Reporter:  ssp43|Owner:
 Type:  enhancement  |   Status:  new
 Priority:  wish |Component:  avfilter
  Version:  unspecified  |   Resolution:
 Keywords:  fieldhint|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by ssp43):

 Another reason to implement this case is that one of two fields can be
 broken.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7055(undetermined:new): Using decimate allows EIA-608 captions to pass through to MP4 files even when the -sn option is used

[FFmpeg]

#7055: Using decimate allows EIA-608 captions to pass through to MP4 files even
when the -sn option is used
-+-
 Reporter:  navilor  |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  decimate cc  |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by navilor):

 Thank you very much for providing me information on the -a53cc option. It
 is working as expected. What baffles me entirely is that the -ac option
 removes EIA-608 captions when I do not use decimate. I have been using
 that option for years.

 Will the mpeg2_metadata_bsf option work with both MPEG Video Version 2 and
 H.264 content in an MPEG-TS container, specifically the m2ts container? I
 ask because I am hoping that it will be a codec neutral option.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7084(avfilter:new): Memory leak in libavfilter/graphparser.c

[FFmpeg]

#7084: Memory leak in libavfilter/graphparser.c
-+
 Reporter:  Kira |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  avfilter
  Version:  unspecified  |   Resolution:
 Keywords:  leak |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by Kira):

 I'm terribly sorry about the copyright problem. I'm not a professional
 software developer, so I'm not familiar with the LICENSE stuff. Please
 forgive me about it. If anyone can help me make up for the problem I will
 be very grateful.
 Back to the bug, actually the bug is found during my fuzz. I fuzz the
 second parameter of `avfilter_graph_parse_ptr` which is `filters_descr`. I
 found the leak when `filters_descr` is an invalid value "spectrumsynth".
 The key point is to trigger the error in function `link_filter`. I don't
 know how `ffmpeg` resolves the input. But I think the problem is still
 there. If you really need to reproduce it with `ffmpeg`, maybe I will
 spend a lot of time on it...

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7055(undetermined:new): Using decimate allows EIA-608 captions to pass through to MP4 files even when the -sn option is used

[FFmpeg]

#7055: Using decimate allows EIA-608 captions to pass through to MP4 files even
when the -sn option is used
-+-
 Reporter:  navilor  |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  decimate cc  |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by tmm1):

 I'm not sure why decimate changes behavior, but caption data is embedded
 in mpeg2 user data and is not considered a subtitle by ffmpeg. You can
 control whether or not the libx264 encoder includes the caption data in
 the output video using the -a53cc option. There is also a patch on the
 list I submitted a couple days ago for a mpeg2_metadata_bsf option to
 remove a53 data from the mpeg2 bitstream.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7081(ffmpeg:new): ffmpeg drops frames when transcoding a looped video stream

[FFmpeg]

#7081: ffmpeg drops frames when transcoding a looped video stream
+--
 Reporter:  Gyan|Owner:
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  ffmpeg
  Version:  git-master  |   Resolution:
 Keywords:  loop|   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+--

Comment (by Gyan):

 I don't know. I haven't looked :)

 This is about a bug with `stream_loop`. I have got it working with
 multiple input files but I wanted to get this resolved first. Speaking of
 the `concat demuxer`, I glanced at it and see decoders aren't flushed
 there when switching to new files. Why was the step added for
 `stream_loop`?

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7055(undetermined:new): Using decimate allows EIA-608 captions to pass through to MP4 files even when the -sn option is used

[FFmpeg]

#7055: Using decimate allows EIA-608 captions to pass through to MP4 files even
when the -sn option is used
-+-
 Reporter:  navilor  |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  decimate cc  |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by navilor):

 > Why? Do you believe it is a good idea to use a de-interlacer for the
 inverse telecine process? (It usually is not a good idea because it
 permanently damages your video while the inverse telecine process should
 be lossless.)

 The output of the file can have some interlacing artifacts. The same thing
 happens with pullup. I added yadif only after I found interlacing
 artifacts in the output file.

 > Sorry for being unclear: If -r is needed (it should not but this likely
 an effect of using decimate incorrectly), the correct syntax would be -r
 24000/1001.
 Please try to simplify the command line and please provide command line
 including complete, uncut console output to make this a valid ticket.

 Thank you for the clarification. I will update my script accordingly

 I have been in the streaming media industry for ten years. The reason the
 command line structure is like that is that streaming media requires a few
 things.

 1) Constant frame rate.
 2) A perfect GOP.
 3) A bitrate based encode.

 Things that are nice to have are.
 4) Finding a better bitrate for your content.
 5) Hitting your target bitrate.
 6) Audio encoding without A/V drift.
 7) Proper encoding for your target audiences.

 In the end my content has perfect PTS/DTS time stamps, an exact GOP, the
 audio and video do not drift, and the bitrate is precise based off of a
 CRF 23 encode where the "bitrate" is extracted via FFprobe for two pass
 average bitrate encoding.

 I detail the reasoning for my command line structure in my personal blog.
 Effectively I cannot trust that the content that is provided to me is
 clean and will convert nicely. One of my posts on my blog is featured in
 an article by Jan Ozer. It is also referenced in his book Video Encoding
 by the Numbers in Chapter 7: Choosing Data Rate.

 [https://videoblerg.wordpress.com/2017/11/10/ffmpeg-and-how-to-use-it-
 wrong/]

 I have, over time, created a 1,600 line heavily documented bash shell
 script that analyzes incoming content and creates a command line that will
 compensate for most forms of bad content.

 I will work on simplifying the command line and hope to have a reply with
 one soon.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7055(undetermined:new): Using decimate allows EIA-608 captions to pass through to MP4 files even when the -sn option is used

[FFmpeg]

#7055: Using decimate allows EIA-608 captions to pass through to MP4 files even
when the -sn option is used
-+-
 Reporter:  navilor  |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  decimate cc  |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by cehoyos):

 Replying to [ticket:7055 navilor]:
 > I have some MPEG-PS content that is behind NTSC hard telecine. As such I
 am using both yadif and decimate to remove that.
 Why? Do you believe it is a good idea to use a de-interlacer for the
 inverse telecine process? (It usually is not a good idea because it
 permanently damages your video while the inverse telecine process should
 be lossless.)
 You may or may not have found a bug but using a command line that never
 makes sense makes me wonder if there really is an issue.

 > And please simplify your command line: The -r option is wrong, others
 should be unneeded.
 Sorry for being unclear: If `-r` is needed (it should not but this likely
 an effect of using `decimate` incorrectly), the correct syntax would be
 `-r 24000/1001`.
 Please try to simplify the command line and please provide command line
 including complete, uncut console output to make this a valid ticket.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7081(ffmpeg:new): ffmpeg drops frames when transcoding a looped video stream

[FFmpeg]

#7081: ffmpeg drops frames when transcoding a looped video stream
+--
 Reporter:  Gyan|Owner:
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  ffmpeg
  Version:  git-master  |   Resolution:
 Keywords:  loop|   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+--
Changes (by cehoyos):

 * keywords:   => loop
 * component:  undetermined => ffmpeg


Comment:

 What's wrong with the concat demuxer?

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7082(undetermined:closed): HLS: m3u8 file is missing the first segment

[FFmpeg]

#7082: HLS: m3u8 file is missing the first segment
-+-
 Reporter:   |Owner:
  stefantalpalaru|   Status:  closed
 Type:  defect   |Component:
 Priority:  normal   |  undetermined
  Version:  unspecified  |   Resolution:  invalid
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * version:  3.4 => unspecified
 * resolution:  fixed => invalid


--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7083(avcodec:new): Decoder playing out frames at double speed

[FFmpeg]

#7083: Decoder playing out frames at double speed
+---
 Reporter:  baudouin0   |Owner:
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  avcodec
  Version:  git-master  |   Resolution:
 Keywords:  h264|   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+---
Changes (by cehoyos):

 * keywords:  double playout rate => h264


Comment:

 You put a complete analysis into your description (which usually indicates
 you could fix the issue instead of filing a bug report) but I wonder how I
 can reproduce the original issue: How can I get ''double speed'' output,
 how does your ''fix'' change timestamps?

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7023(undetermined:new): mediastreamvalidator failed with "Error injecting segment data"

[FFmpeg]

#7023: mediastreamvalidator failed with "Error injecting segment data"
-+-
 Reporter:  loki5100 |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:  hls  |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by loki5100):

 Sad I can't compile it because I don't have the tool to do it :( maybe you
 can gave me a link the the compiled exe that i can try ?

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

[FFmpeg-trac] #7084(avfilter:new): Memory leak in libavfilter/graphparser.c

[FFmpeg]

#7084: Memory leak in libavfilter/graphparser.c
-+-
 Reporter:  Kira | Type:  defect
   Status:  new  | Priority:  normal
Component:  avfilter |  Version:
 Keywords:  memory   |  unspecified
  leak, parse_outputs|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 parse_outputs from libavfilter/graphparser.c
 {{{
 #!div style="font-size: 80%"
   {{{#!C
  static int parse_outputs(const char **buf, AVFilterInOut **curr_inputs,
  AVFilterInOut **open_inputs,
  AVFilterInOut **open_outputs, void *log_ctx)
 {
 int ret, pad = 0;

 while (**buf == '[') {
 char *name = parse_link_name(buf, log_ctx);
 AVFilterInOut *match;

 AVFilterInOut *input = *curr_inputs;

 if (!name)
 return AVERROR(EINVAL);

 if (!input) {
 av_log(log_ctx, AV_LOG_ERROR,
"No output pad can be associated to link label
 '%s'.\n", name);
 av_free(name);
 return AVERROR(EINVAL);
 }
 *curr_inputs = (*curr_inputs)->next;

 /* First check if the label is not in the open_inputs list */
 match = extract_inout(name, open_inputs);

 if (match) {
 if ((ret = link_filter(input->filter_ctx, input->pad_idx,
match->filter_ctx, match->pad_idx,
 log_ctx)) < 0) {
 av_free(name);
 return ret;
 }
 av_freep(>name);
 av_freep();
 av_freep();
 av_freep();
 } else {
 /* Not in the list, so add the first input as an open_output
 */
 input->name = name;
 insert_inout(open_outputs, input);
 }
 *buf += strspn(*buf, WHITESPACES);
 pad++;
 }

 return pad;
 }
   }}}
 }}}
 line 361:
 match = extract_inout(name, open_inputs);
 Extract a node from the linked list open_inputs, the origin linked list
 changed here.
 extract_inout from libavfilter/graphparser.c
 {{{
 #!div style="font-size: 80%"
   {{{#!C
 static AVFilterInOut *extract_inout(const char *label, AVFilterInOut
 **links)
 {
 AVFilterInOut *ret;

 // find the first node whose name is same as label.
 while (*links && (!(*links)->name || strcmp((*links)->name, label)))
 links = &((*links)->next);

 ret = *links;

 if (ret) {  // off the chain
 *links = ret->next;
 ret->next = NULL;
 }

 return ret;
 }
   }}}
 }}}

 If the match found, we enter here.
 {{{
 #!div style="font-size: 80%"
   {{{#!C
 if (match) {
 if ((ret = link_filter(input->filter_ctx, input->pad_idx,
match->filter_ctx, match->pad_idx,
 log_ctx)) < 0) {
 av_free(name);
 return ret;
 }
 av_freep(>name);
 av_freep();
 av_freep();
 av_freep();
 }
   }}}
 }}}

 If the link_filter call fails, the variable match will never be freed!

 So the memory leak happens here.

 Compile the leak_poc.c

 Run it and use htop or something else to monitor the memory consumption of
 the process. You will see the leak.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7023(undetermined:new): mediastreamvalidator failed with "Error injecting segment data"

[FFmpeg]

#7023: mediastreamvalidator failed with "Error injecting segment data"
-+-
 Reporter:  loki5100 |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:  hls  |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by stevenliu):

 try this patch set please: https://patchwork.ffmpeg.org/patch/7960/

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7083(avcodec:new): Decoder playing out frames at double speed

[FFmpeg]

#7083: Decoder playing out frames at double speed
-+-
 Reporter:  baudouin0|Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  double   |   Blocked By:
  playout rate   |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by baudouin0):

 I can fix the issue by adding

 h264_init_context(AVCodecContext *avctx, H264Context *h) {

 + h->x264_build = -1;
 }

 but don't think this is correct fix.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

[FFmpeg-trac] #7083(avcodec:new): Decoder playing out frames at double speed

[FFmpeg]

#7083: Decoder playing out frames at double speed
-+-
 Reporter:  baudouin0| Type:  defect
   Status:  new  | Priority:  normal
Component:  avcodec  |  Version:  git-
 Keywords:  double   |  master
  playout rate   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 Summary of the bug:

 sps->time_scale is being doubled on h264_slice_header_init().
 After second frame h->x264_build is set to zero rather than -1 causing
 frame rate to be doubled.

 How to reproduce:

 ffmpeg -i test.264 out%d.bmp


 // Added printf to check:
 static int h264_slice_header_init(H264Context *h)
 {
 const SPS *sps = h->ps.sps;
 int i, ret;

 ff_set_sar(h->avctx, sps->sar);
 av_pix_fmt_get_chroma_sub_sample(h->avctx->pix_fmt,
  >chroma_x_shift,
 >chroma_y_shift);

 if (sps->timing_info_present_flag) {
 int64_t den = sps->time_scale;
 printf("h264_slice_header_init() build=%d time_scale=%d
 ticks_per_frame=%d num_units_in_tick=%d\n", h->x264_build,
 sps->time_scale, h->avctx->ticks_per_frame, sps->num_units_in_tick);
 if (h->x264_build < 44U)
 den *= 2;
 av_reduce(>avctx->framerate.den, >avctx->framerate.num,
   sps->num_units_in_tick * h->avctx->ticks_per_frame, den,
 1 << 30);
 }

 Output from decoder is:ffmpeg version N-90264-g80798e3 Copyright (c)
 2000-2018 the FFmpeg developers
   built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.4)
   configuration:
   libavutil  56.  8.100 / 56.  8.100
   libavcodec 58. 14.100 / 58. 14.100
   libavformat58. 10.100 / 58. 10.100
   libavdevice58.  2.100 / 58.  2.100
   libavfilter 7. 12.100 /  7. 12.100
   libswscale  5.  0.102 /  5.  0.102
   libswresample   3.  0.101 /  3.  0.101
 h264_slice_header_init() build=-1 time_scale=5 ticks_per_frame=2
 num_units_in_tick=1000
 Input #0, h264, from 'test.264':
   Duration: N/A, bitrate: N/A
 Stream #0:0: Video: h264 (High), yuv420p(progressive), 704x576 [SAR
 12:11 DAR 4:3], 25 fps, 25 tbr, 1200k tbn, 50 tbc
 Stream mapping:
   Stream #0:0 -> #0:0 (h264 (native) -> bmp (native))
 Press [q] to stop, [?] for help
 h264_slice_header_init() build=-1 time_scale=5 ticks_per_frame=2
 num_units_in_tick=1000
 h264_slice_header_init() build=0 time_scale=5 ticks_per_frame=2
 num_units_in_tick=1000
 h264_slice_header_init() build=0 time_scale=5 ticks_per_frame=2
 num_units_in_tick=1000
 h264_slice_header_init() build=0 time_scale=5 ticks_per_frame=2
 num_units_in_tick=1000
 h264_slice_header_init() build=0 time_scale=5 ticks_per_frame=2
 num_units_in_tick=1000
 h264_slice_header_init() build=0 time_scale=5 ticks_per_frame=2
 num_units_in_tick=1000
 h264_slice_header_init() build=0 time_scale=5 ticks_per_frame=2
 num_units_in_tick=1000
 h264_slice_header_init() build=0 time_scale=5 ticks_per_frame=2
 num_units_in_tick=1000
 h264_slice_header_init() build=0 time_scale=5 ticks_per_frame=2
 num_units_in_tick=1000
 Output #0, image2, to 'xxx%d.bmp':
   Metadata:
 encoder : Lavf58.10.100
 Stream #0:0: Video: bmp, bgr24, 704x576 [SAR 12:11 DAR 4:3], q=2-31,
 200 kb/s, 25 fps, 25 tbn, 25 tbc
 Metadata:
   encoder : Lavc58.14.100 bmp

 Note x264_build becomes zero.
 Built ob x64 linux with gcc 4.8.4

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7021(undetermined:new): ffmpeg with -hls_flags single_file return incorrect byterange in playlist

[FFmpeg]

#7021: ffmpeg with -hls_flags single_file return incorrect byterange in playlist
-+-
 Reporter:  loki5100 |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:  hls  |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by loki5100):

 ok thanks Steven I hope the other ticket will also get corrected soon ...

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7021(undetermined:new): ffmpeg with -hls_flags single_file return incorrect byterange in playlist

[FFmpeg]

#7021: ffmpeg with -hls_flags single_file return incorrect byterange in playlist
-+-
 Reporter:  loki5100 |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:  hls  |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by stevenliu):

 Replying to [comment:7 loki5100]:
 > thanks Steven, i fell useless that i can't compile it :( did this patch
 will also correct this bug: https://trac.ffmpeg.org/ticket/7023 ?

 no just this ticket, that ticket need new patch to fix it.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7021(undetermined:new): ffmpeg with -hls_flags single_file return incorrect byterange in playlist

[FFmpeg]

#7021: ffmpeg with -hls_flags single_file return incorrect byterange in playlist
-+-
 Reporter:  loki5100 |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:  hls  |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by loki5100):

 thanks Steven, i fell useless that i can't compile it :( did this patch
 will also correct this bug: https://trac.ffmpeg.org/ticket/7023 ?

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7021(undetermined:new): ffmpeg with -hls_flags single_file return incorrect byterange in playlist

[FFmpeg]

#7021: ffmpeg with -hls_flags single_file return incorrect byterange in playlist
-+-
 Reporter:  loki5100 |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:  hls  |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by stevenliu):

 Replying to [comment:5 loki5100]:
 > thanks Steven, unfortunatly I under windows and I don't know how to
 compile ffmpeg and I don't have the tools to compile it... maybe i can
 wait the next nightly build of ffmpeg to try ?

 I test it have been fixed local, so need full review.
 That's ok, just wait the patch full reviewed by other guys, don't worry :D

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7021(undetermined:new): ffmpeg with -hls_flags single_file return incorrect byterange in playlist

[FFmpeg]

#7021: ffmpeg with -hls_flags single_file return incorrect byterange in playlist
-+-
 Reporter:  loki5100 |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:  hls  |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by loki5100):

 thanks Steven, unfortunatly I under windows and I don't know how to
 compile ffmpeg and I don't have the tools to compile it... maybe i can
 wait the next nightly build of ffmpeg to try ?

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac