Recherche avancée

Sur d’autres sites (5745)

• "Unknown Encoder 'libx264'" error while using FFMPEG

  9 juillet 2018, par newuser

  I have followed the guide given here @ traq.ffmpeg. And everything goes smoothly. But when I try to run a command with FFMPEG to convert something to h.264, I get the error :

  Unknown Encoder ’libx264’

  I’m using Ubuntu 16.04 LTS.

• FFmpeg - HLS MUXER producing 0 bytes chunks as well as ) bytes manifest [closed]

  30 avril 2024, par Mohideen Irfan

  My ffmpeg code produces 0 bytes chunks as well as 0 bytes manifest. can someone tell what may be the cause for that. AVPacket contains the data too. Whether the data is valid or not valid that's off-topic here, right ? As it writes any data into the muxer right ? But why I am receiving ffmpeg log like :

  


  [hls @ 0x617000084280] write_packet_common size:128 dts:192060 pts:192060
[hls @ 0x617000084280] compute_muxer_pkt_fields: pts:192060 dts:192060 cur_dts:186030 b:0 size:128 st:1
[hls @ 0x617000084280] av_write_frame: pts2:192060 dts2:192060
[hls @ 0x617000084280] Opening '/media/RT_RT_1_12345_1698653290847_8749823174342/hls/wmslive_media_video_0.ts' for writing
[file @ 0x611000351f00] Setting default whitelist 'file,crypto,data'
[AVIOContext @ 0x6130003b0400] Statistics: 0 bytes written, 0 seeks, 1 writeouts
[hls @ 0x617000084280] Opening '/media/RT_RT_1_12345_1698653290847_8749823174342/hls/temporarymanifest_hls_wmslive_video.m3u8.tmp' for writing
[file @ 0x612000941d40] Setting default whitelist 'file,crypto,data'
EXT-X-MEDIA-SEQUENCE:0
[AVIOContext @ 0x6130003b05c0] Statistics: 0 bytes written, 0 seeks, 1 writeouts"


  


  I am working on this issue for almost a week. There were no errors. when I write av_frame_write it returns success. chunks are getting generated but nothing present inside the chunks or manifest. How to resolve this ?

  


• movenc : Add an option for delaying writing the moov with empty_moov

  3 novembre 2014, par Martin Storsjö

  movenc : Add an option for delaying writing the moov with empty_moov
  This delays writing the moov until the first fragment is written,
  
  or can be flushed by the caller explicitly when wanted. If the first
  
  sample in all streams is available at this point, we can write
  
  a proper editlist at this point, allowing streams to start at
  
  something else than dts=0. For AC3 and DNXHD, a packet is
  
  needed in order to write the moov header properly.
  This isn’t added to the normal behaviour for empty_moov, since
  
  the behaviour that ftyp+moov is written during avformat_write_header
  
  would be changed. Callers that split the output stream into header+segments
  
  (either by flushing manually, with the custom_frag flag set, or by
  
  just differentiating between data written during avformat_write_header
  
  and the rest) will need to be adjusted to take this option into use.
  For handling streams that start at something else than dts=0, an
  
  alternative would be to use different kinds of heuristics for
  
  guessing the start dts (using AVCodecContext delay or has_b_frames
  
  together with the frame rate), but this is not reliable and doesn’t
  
  necessarily work well with stream copy, and wouldn’t work for getting
  
  the right initialization data for AC3 or DNXHD either.
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DBH] libavformat/movenc.c
  • [DBH] libavformat/movenc.h
  • [DBH] libavformat/version.h