Recherche avancée

Sur d’autres sites (8855)

• avfilter/vf_dnn_processing.c : add frame size change support for planar yuv format

  21 février 2020, par Guo, Yejun

  avfilter/vf_dnn_processing.c : add frame size change support for planar yuv format
  The Y channel is handled by dnn, and also resized by dnn. The UV channels
  
  are resized with swscale.
  The command to use espcn.pb (see vf_sr) looks like :
  
  ./ffmpeg -i 480p.jpg -vf format=yuv420p,dnn_processing=dnn_backend=tensorflow:model=espcn.pb:input=x:output=y -y tmp.espcn.jpg
  Signed-off-by : Guo, Yejun <yejun.guo@intel.com>
  
  Reviewed-by : Pedro Arthur <bygrandao@gmail.com>
  

  • [DH] doc/filters.texi
  • [DH] libavfilter/vf_dnn_processing.c

• What are supported ffmpeg rtp_mpegts Muxer options ? (mpegts Muxer options are ignored)

  7 mars 2020, par drake7

  I created a UDP stream with -f mpegts and some options like -mpegts_transport_stream_id.

  I received the stream with "StreamXpert - Real-time stream analyzer" that shows all options are in the output. See my ffmpeg parameters and the StreamXpert at the end.

  The same Muxer options seem to be ignored with -f rtp_mpegts.

  I have tried to use -f mpegts and pipe it to -f rtp_mpegts like so :

  ffmpeg -i ... -f mpegts pipe: | ffmpeg pipe: -c copy -f rtp_mpegts "rtp://239.1.1.9:1234?pkt_size=1316"

  The options are still ignored.

  This ticket "support options for MPEGTS muxer when using RTP_MPEGTS" also notices the ignored option. Furthermore in this comment, "thovo" gives an analysis and suggests a solution.

  Obviously the problem still exists. Anybody found a workaround for this ?

  My additional question : I have not questioned if my project really needs rtp in the first place. Maybe my coworker didn’t know better and requested rtp when udp would be sufficient as well.

  The aim was to receive the RTP stream with a TV using DVB via IP. This was successful an a Panasonic TV.

  The SAT>IP Specification on page 10 requires rtp for Media Transport :

  The SAT>IP protocol makes use of :

  • UPnP for Addressing, Discovery and Description,
  • RTSP or HTTP for Control,
  • RTP or HTTP for Media Transport.

  Is udp out of the equation ?

  ---

  ffmpeg : (all options are in the output with -f mpegts)

  (HEX to decimal : 0x005A = 90, 0x005B = 91 0x005C = 92, 0x005D = 93, 0x005E= 94)

  ffmpeg -f lavfi -i testsrc \
  
  -r 25 \
  
  -c:v libx264 \
  
  -pix_fmt yuv420p \
  
  -profile:v main -level 3.1 \
  
  -preset veryfast \
  
  -vf scale=1280:720,setdar=dar=16/9 \
  
  -an \
  
  -bsf:v h264_mp4toannexb \
  
  -flush_packets 0 \
  
  -b:v 4M \
  
  -muxrate 8M \
  
  -pcr_period 20 \
  
  -pat_period 0.10 \
  
  -sdt_period 0.25 \
  
  -metadata:s:a:0 language=nya \
  
  -mpegts_flags +pat_pmt_at_frames \
  
  -mpegts_transport_stream_id 0x005A \
  
  -mpegts_original_network_id 0x005B \
  
  -mpegts_service_id 0x005C \
  
  -mpegts_pmt_start_pid 0x005D \
  
  -mpegts_start_pid 0x005E \
  
  -mpegts_service_type advanced_codec_digital_hdtv \
  
  -metadata service_provider='WI' \ 
  
  -metadata service_name='W' \
  
  -mpegts_flags system_b -flush_packets 0 \
  
  -f mpegts "udp://239.1.1.10:1234?pkt_size=1316"

  StreamXpert Output :

  -mpegts_transport_stream_id = Transport Stream ID (yellow text highlight)

  -mpegts_original_network_id = Original Network ID, onw (green text highlight)

  -mpegts_service_id = Program, service (pink text highlight)

  -mpegts_pmt_start_pid = PMT PID, Table PID (turquoise text highlight)

  -mpegts_start_pid = PID, PCR PID (red text highlight)

  -mpegts_service_type = service type (blue text)

  service_name = Service name (orange text)

  service_provider = Service provider (pink text)

  

• Unrecognized option '-enable-libx264'. Error splitting the argument list : Option not found

  9 mars 2020, par DigM

  I’m trying to stream MP4 videos from my server to YouTube and so I installed FFMPEG version. When I then look at the configuration of FFMPEG, I am then presented with the following :

  ffmpeg version 3.3.6 Copyright (c) 2000-2017 the FFmpeg developers
  
    built with gcc 4.9.2 (Debian 4.9.2-10)
  
    configuration: --enable-cross-compile --arch=i686 --target-os=linux --disable-yasm --disable-static --enable-shared --enable-gpl --enable-libmp3lame --enable-libx264 --enable-libsoxr --enable-version3 --enable-nonfree --enable-openssl --disable-decoder=ac3 --disable-decoder=ac3_fixed --disable-decoder=eac3 --disable-decoder=dca --disable-decoder=truehd --disable-encoder=ac3 --disable-encoder=ac3_fixed --disable-encoder=eac3 --disable-encoder=dca --disable-decoder=hevc --disable-decoder=hevc_cuvid --disable-encoder=hevc_nvenc --disable-encoder=nvenc_hevc --extra-ldflags='-L/root/daily_build/64_05/4.4.1/LinkFS/usr/lib -L/root/daily_build/64_05/4.4.1/Model/TS-X72/build/RootFS/usr/local/medialibrary/lib -Wl,--rpath -Wl,/usr/local/medialibrary/lib' --extra-cflags='-I/root/daily_build/64_05/4.4.1/LinkFS/usr/include -I/root/daily_build/64_05/4.4.1/Model/TS-X72/build/RootFS/usr/local/medialibrary/include -D_GNU_SOURCE -DQNAP' --prefix=/root/daily_build/64_05/4.4.1/Model/TS-X72/build/RootFS/usr/local/medialibrary
  
    libavutil      55. 58.100 / 55. 58.100
  
    libavcodec     57. 89.100 / 57. 89.100
  
    libavformat    57. 71.100 / 57. 71.100
  
    libavdevice    57.  6.100 / 57.  6.100
  
    libavfilter     6. 82.100 /  6. 82.100
  
    libswscale      4.  6.100 /  4.  6.100
  
    libswresample   2.  7.100 /  2.  7.100
  
    libpostproc    54.  5.100 / 54.  5.100

  However, when I then try

  ffmpeg ---enable-libx264

  I then get an error saying :

  Unrecognized option '--enable-libx264'.
  
  Error splitting the argument list: Option not found

  Do I need to change the configuaration of FFMPEG somehow or run another configuration option first or is there just something wrong with my call to enable libx264 ?