Recherche avancée

Médias (3)

Mot : - Tags -/image

Autres articles (63)

Sur d’autres sites (6905)

  • FFMPEG profile-level-id size is invalid

    18 février 2020, par Mulham Aryan

    I’m trying to record a RTSP streaming from JVC KY-PZ 100.
    So for that i’m using ffmpeg with some parameters like segmentation, hls, ts, m3u8 etc ...
    i’m always getting an error The profile-level-id field size is invalid (41) and Error parsing AU headers

    This is the output of FFPROBE to debug the RTSP

    ffprobe -loglevel verbose  -i rtsp://jvc:0000@192.168.0.124:554/stream

    ffprobe version 4.2.2 Copyright (c) 2007-2019 the FFmpeg developers
     built with Apple LLVM version 10.0.0 (clang-1000.11.45.5)
     configuration: --prefix=/usr/local/Cellar/ffmpeg/4.2.2 --enable-shared --enable-pthreads --enable-version3 --enable-avresample --cc=clang --host-cflags='-I/Library/Java/JavaVirtualMachines/adoptopenjdk-13.0.1.jdk/Contents/Home/include -I/Library/Java/JavaVirtualMachines/adoptopenjdk-13.0.1.jdk/Contents/Home/include/darwin' --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libbluray --enable-libmp3lame --enable-libopus --enable-librubberband --enable-libsnappy --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librtmp --enable-libspeex --enable-libsoxr --enable-videotoolbox --disable-libjack --disable-indev=jack
     libavutil      56. 31.100 / 56. 31.100
     libavcodec     58. 54.100 / 58. 54.100
     libavformat    58. 29.100 / 58. 29.100
     libavdevice    58.  8.100 / 58.  8.100
     libavfilter     7. 57.100 /  7. 57.100
     libavresample   4.  0.  0 /  4.  0.  0
     libswscale      5.  5.100 /  5.  5.100
     libswresample   3.  5.100 /  3.  5.100
     libpostproc    55.  5.100 / 55.  5.100
    [tcp @ 0x7fa99ee001c0] Starting connection attempt to 192.168.0.124 port 554
    [tcp @ 0x7fa99ee001c0] Successfully connected to 192.168.0.124 port 554
    [rtsp @ 0x7fa99f807200] SDP:
    v=0
    o=- 1581949225269357 1 IN IP4 192.168.0.124
    s=KY-PZ100
    i=KY-PZ100
    t=0 0
    a=tool:LIVE555 Streaming Media v2013.10.03
    a=type:broadcast
    a=control:*
    a=range:npt=0-
    a=x-qt-text-nam:KY-PZ100
    a=x-qt-text-inf:KY-PZ100
    m=audio 0 RTP/AVP 96
    c=IN IP4 0.0.0.0
    b=AS:96
    a=rtpmap:96 mpeg4-generic/48000/2
    a=fmtp:96 streamtype=5;profile-level-id=41;mode=AAC-hbr;sizelength=13;indexlength=3;indexdeltalength=3;config=1190
    a=control:track1
    m=video 0 RTP/AVP 97
    c=IN IP4 0.0.0.0
    b=AS:1500
    a=rtpmap:97 H264/90000
    a=fmtp:97 packetization-mode=1;profile-level-id=4D401E;sprop-parameter-sets=Z01AHqtgUBf8uAqQEBAUAAAPpAADqYOlABksDcoUQDuLFIs=,aM48gA==
    a=control:track2

    [rtsp @ 0x7fa99f807200] The profile-level-id field size is invalid (41)
    [rtsp @ 0x7fa99f807200] setting jitter buffer size to 500
       Last message repeated 1 times
    [rtsp @ 0x7fa99f807200] Error parsing AU headers
       Last message repeated 4 times
    [h264 @ 0x7fa9a0806600] Reinit context to 640x368, pix_fmt: yuv420p
    [rtsp @ 0x7fa99f807200] Error parsing AU headers
       Last message repeated 235 times
    [rtsp @ 0x7fa99f807200] max_analyze_duration 5000000 reached at 5005000 microseconds st:1
    Input #0, rtsp, from 'rtsp://jvc:0000@192.168.0.124:554/stream':
     Metadata:
       title           : KY-PZ100
       comment         : KY-PZ100
     Duration: N/A, start: 0.066733, bitrate: N/A
       Stream #0:0: Audio: aac, 48000 Hz, stereo, fltp
       Stream #0:1: Video: h264 (Main), 1 reference frame, yuv420p(tv, bt709, progressive, left), 640x360 (640x368) [SAR 1:1 DAR 16:9], 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc
  • How to run the set of commands in windows command line

    24 février 2020, par robert.little

    x264-preset is used in the second command (Cmd 2). Is it substitution or ?

    Cmd 1 :

    x264-preset:
    vcodec=libx264
    thread_type=slice
    slices=1
    profile=baseline
    level=32
    preset=superfast
    tune=zerolatency
    intra-refresh=1
    crf=15
    x264-params=vbv-maxrate=5000:vbv-bufsize=1:slice-max-size=1500:keyint=60

    Cmd 2

    $ ffmpeg -r 30 -f dshow -i video="devicename" -pix_fmt yuv420p -an -vpre
    x264-preset -f mpegts udp://127.0.0.1:8888

    When I run the Cmd 1 it doesn’t work. Even with the SET like :

    x264-preset:
    SET vcodec=libx264
    SET thread_type=slice
    SET slices=1
    SET profile=baseline
    SET level=32
    SET preset=superfast
    SET tune=zerolatency
    SET intra-refresh=1
    SET crf=15
    SET x264-params=vbv-maxrate=5000:vbv-bufsize=1:slice-max-size=1500:keyint=60

    Source :
    https://lists.ffmpeg.org/pipermail/ffmpeg-user/2016-January/030127.html

  • ffmpeg crashes on crossfades between 3 clips if 2 clips coming from same input file [closed]

    14 avril 2020, par Erik

    I observed that ffmpeg 4.2.2 (macOS) crashes in particular cases of crossfades between clips, if one clip comes from file 1.dv, and two clips are cut out of file 2.dv, as shown below :

    



    ffmpeg -f lavfi -i color=black:size=720x576:duration=11:rate=25 -i 1.dv -i 2.dv -filter_complex "\
    [1:v]trim=5:10,setpts=expr=PTS-STARTPTS,yadif,fade=alpha=1:d=2:st=3:type=out,setpts=expr=PTS-STARTPTS,fifo[s5];\
    [2:v]split=2[s7][s8];\
    [s7]trim=5:10,setpts=expr=PTS-STARTPTS,yadif,fade=alpha=1:d=2:type=in,fade=alpha=1:d=2:st=6:type=out,setpts=expr=PTS-STARTPTS+(3/TB),fifo[s15];\
    [s8]trim=12:17,setpts=expr=PTS-STARTPTS,yadif,fade=alpha=1:d=2:type=in,setpts=expr=PTS-STARTPTS+(6/TB),fifo[s22];\
    [0:v][s5]overlay=eof_action=repeat[s6];\
    [s6][s15]overlay=eof_action=repeat[s16];\
    [s16][s22]overlay=eof_action=repeat[s24];\
    [1:a]atrim=5:10,asetpts=expr=PTS-STARTPTS[s26];\
    [2:a]asplit=2[s27][s28];\
    [s27]atrim=5:10,asetpts=expr=PTS-STARTPTS[s30];\
    [s28]atrim=12:17,asetpts=expr=PTS-STARTPTS[s33];\
    [s26][s30]acrossfade=d=2[s31];\
    [s31][s33]acrossfade=d=2[s36]" \
     -map "[s24]" -map "[s36]" -ab 128k -acodec aac -crf 23 -movflags faststart -preset medium -tune film -vcodec libx264 -aspect 1024:576 out.mp4 -y


    



    The order makes a difference : if the two clips from 2.dv are used first and then the clip from 1.dv is appended, everything works fine. Also, if all clips are coming from different files.

    



    ffmpeg 3.4.6 (ubuntu 18.04) shows no issues in any case.

    



    A self-compiled ffmpeg version N-97322-gb1699f4 (commit 2020-04-13) works with short clips as above, but crashes if one of the two clips taken from 2.dv is getting longer. In my tests 1500 frames (64 sec) is OK, 1700 (68 sec) leads to a segmentation fault. That is, if you replace in the command line above :

    



      

    • [s7]trim=5:10... -> [s7]trim=0:68 and accordingly
    • 


    • [s27]atrim=5:10... -> [s27]atrim=0:68
    • 


    



    Interestingly, the length of the clip taken from 1.dv does not play a role.

    



    The ffmpeg output shows about 20 times :

    



    frame=    0 fps=0.0 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x  


    



    before it continues (seg fault case) :

    



    frame=    4 fps=0.3 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    
frame=   24 fps=1.6 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    
frame=   25 fps=1.5 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    
frame=   34 fps=1.9 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    
frame=   36 fps=2.0 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    
frame=   39 fps=2.1 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    
frame=   40 fps=2.0 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    
frame=   40 fps=2.0 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    
frame=   40 fps=1.9 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    



    



    success case :

    



    frame=    5 fps=0.4 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    
frame=   42 fps=3.2 q=28.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    
frame=   53 fps=3.9 q=28.0 size=       0kB time=00:00:00.36 bitrate=   2.9kbits/s speed=0.0264x    
frame=   65 fps=4.6 q=28.0 size=       0kB time=00:00:00.84 bitrate=   1.2kbits/s speed=0.0594x 
...   


    



    Slightly older versions included in the newest MacOS builds from zeranoe.com (git-2020-04-13-59e3a9a) and evermeet.cx (N-97308-g14dd0a9057-tessus, from 2020-04-12) are working nicely - also on my production cases (longer clips).

    



    Any feedback would be appreciated !