Re: [FFmpeg-user] problems consuming live single file hls

2019-01-11 Thread Daniel Oberhoff

Am 10.01.19 um 18:04 schrieb Carl Eugen Hoyos:
> 2019-01-10 14:59 GMT+01:00, Daniel Oberhoff :
>
>> I previously reported on problems with consuming a live single
>> file hls stream. It was quite embedded in the application so i
>> failed to make a good reproducible case. Now i reduced it.
> Please test current FFmpeg git head.

same behavior (i attach logs again)

> Are you missing the "-re" option?
> Iiuc, you trying to read as-fast-as-possible an input
> that is just created: How is this supposed to work,
> what behaviour do you expect?

I dont think -re is applicable. Actually it may be the consumer is
slower than the producer, which is ok. Or it may be slower for some time
and later catch up. So, yes, i want to consume as fast as possible.
Since hls is a streaming format i would actually expect this to work. It
does for multi file. The rationale is simple: the producer produces a
m3u8 plalist, appending to it new segments as they are produced. i.e.
after they have been fully written. Then the consumer sees them (by
polling the m3u8) and consumes them. This is how i would expect it to
work over http also, i.e. the consumer polls the playlist and consumes
any new segments. We simply shortcut here and do it locally via the file
system, which should be ok. Am I missing something? As I said, for
multi-file hls we dont have these problems, and i am not sure why single
file should be different. The only difference really is that instead of
whole files the data is in a byte range of a file.

Best


Daniel


ffmpeg version N-92950-gc65c4ce773 Copyright (c) 2000-2019 the FFmpeg developers
  built with Apple LLVM version 10.0.0 (clang-1000.11.45.5)
  configuration: 
  libavutil  56. 25.100 / 56. 25.100
  libavcodec 58. 43.100 / 58. 43.100
  libavformat58. 25.100 / 58. 25.100
  libavdevice58.  6.101 / 58.  6.101
  libavfilter 7. 47.100 /  7. 47.100
  libswscale  5.  4.100 /  5.  4.100
  libswresample   3.  4.100 /  3.  4.100
[hls,applehttp @ 0x7fb60e00] Opening 'test_single_file_mp4.m4s' for reading
Last message repeated 1 times
Input #0, hls,applehttp, from 'test_single_file_mp4.m3u8':
  Duration: N/A, start: 28.00, bitrate: 51 kb/s
  Program 0 
Metadata:
  variant_bitrate : 0
Stream #0:0: Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 
1:1 DAR 16:9], 51 kb/s, 30 fps, 30 tbr, 15360 tbn, 30720 tbc
Metadata:
  variant_bitrate : 0
  compatible_brands: iso6mp41
  major_brand : iso5
  minor_version   : 512
  encoder : Lavf58.25.100
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> wrapped_avframe (native))
Press [q] to stop, [?] for help
Output #0, null, to '/dev/null':
  Metadata:
encoder : Lavf58.25.100
Stream #0:0: Video: wrapped_avframe, yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 
q=2-31, 200 kb/s, 30 fps, 30 tbn, 30 tbc
Metadata:
  variant_bitrate : 0
  compatible_brands: iso6mp41
  major_brand : iso5
  minor_version   : 512
  encoder : Lavc58.43.100 wrapped_avframe
[hls,applehttp @ 0x7fb60e00] Opening 'test_single_file_mp4.m4s' for reading
Last message repeated 3 times
[h264 @ 0x7fb60100d600] Invalid NAL unit 0, skipping.
frame=  156 fps= 79 q=-0.0 size=N/A time=00:00:05.20 bitrate=N/A speed=2.64x
[h264 @ 0x7fb60100dc00] Invalid NAL unit size (-503519357 > 3150).
[h264 @ 0x7fb60100dc00] Error splitting the input into NAL units.
[h264 @ 0x7fb601810800] Invalid NAL unit size (-1920240576 > 3132).
[h264 @ 0x7fb601810800] Error splitting the input into NAL units.
[h264 @ 0x7fb601002800] Invalid NAL unit size (-805746105 > 3132).
[h264 @ 0x7fb601002800] Error splitting the input into NAL units.
[h264 @ 0x7fb60100d000] Invalid NAL unit size (271284657 > 3114).
[h264 @ 0x7fb60100d000] Error splitting the input into NAL units.
[h264 @ 0x7fb60100d600] error while decoding MB 34 8, bytestream -6
[h264 @ 0x7fb60100d600] data partitioning is not implemented. Update your 
FFmpeg version to the newest one from Git. If the problem still occurs, it 
means that your file has a feature which has not been implemented.
[h264 @ 0x7fb60100d600] If you want to help, upload a sample of this file to 
ftp://upload.ffmpeg.org/incoming/ and contact the ffmpeg-devel mailing list. 
(ffmpeg-de...@ffmpeg.org)
[h264 @ 0x7fb60100d600] concealing 2975 DC, 2975 AC, 2975 MV errors in I frame
Error while decoding stream #0:0: Invalid data found when processing input
[h264 @ 0x7fb60100d600] Invalid NAL unit size (453635919 > 3121).
[h264 @ 0x7fb60100d600] Error splitting the input into NAL units.
Error while decoding stream #0:0: Invalid data found when processing input
[h264 @ 0x7fb60100dc00] Invalid NAL unit size (-1955315659 > 3109).
[h264 @ 0x7fb60100dc00] Error splitting the input into NAL units.
Error while decoding stream #0:0: Invalid data found when processing input
[h264 @ 0x7fb601810800] Invalid NAL unit size (-653815108 > 3125).
[h264 @ 0x7fb601810800] Error splitting the 

Re: [FFmpeg-user] Calculating offset of shifted line

2019-01-11 Thread Carl Zwanzig

On 1/11/2019 1:11 AM, Ulf Zibis wrote:

a polite ping ...


Certainly- please don't top-post on this list.





Regarding pixel values, it could be that nobody directly knows; could also 
be that it's not possible from the command line.


You probably need to look into using the various ffmpeg libraries, and 
they're discussed on a different mailing list.


z!
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] Calculating offset of shifted line

2019-01-11 Thread Ulf Zibis
Hi,

a polite ping ...

-Ulf

Am 09.01.19 um 01:22 schrieb Ulf Zibis:
> Hi,
>
> I would like to calculate how much a special line in the video is
> irregularly shifted to right or left. For this I want to compare the
> line with the adjacent line above by calculating the minimum of the
> quadratic mean for each shift.
>
> I'm first looking for something like:
> x:=0; y:=123; diff:= 0; while(x++ < in_w, diff += (luma(x,y) - luma(x,y
> - 1))²);
>
> So the first question is: how to get the luma value of a pixel?
>
> Thanks
>
> -Ulf
>
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

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