Recherche avancée

Sur d’autres sites (12834)

• movenc : Ensure no separate moof written for empty track

  12 août 2021, par Hu Weiwen

  movenc : Ensure no separate moof written for empty track
  track->mdat_buf can be not NULL while the track is still empty if the
  
  last packet write failed.
  Signed-off-by : Hu Weiwen <sehuww@mail.scut.edu.cn>
  
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] libavformat/movenc.c

• vulkan : add support for encode and decode queues and refactor queue code

  7 novembre 2021, par Lynne

  vulkan : add support for encode and decode queues and refactor queue code
  This simplifies and makes queue family picking simpler and more robust.
  
  The requirements on the device context are relaxed. They made no sense
  
  in the first place.
  The video encode/decode extension is still in beta, at least on paper,
  
  but I really doubt they'd change needing a separate queue family.
  

  • [DH] libavfilter/vf_avgblur_vulkan.c
  • [DH] libavfilter/vf_chromaber_vulkan.c
  • [DH] libavfilter/vf_overlay_vulkan.c
  • [DH] libavfilter/vf_scale_vulkan.c
  • [DH] libavfilter/vulkan.h
  • [DH] libavutil/hwcontext_vulkan.c
  • [DH] libavutil/hwcontext_vulkan.h

• Linux : Create a file for writing with controlled flushing to disk in large chunks [closed]

  12 août 2023, par Pete

  On Linux I have a process (ffmpeg) that writes very slowly (even slower than 1kb / s sometimes) to disk. Ffmpeg can buffer this to 256kb chunks that get written infrequently but ffmpeg hangs occasionally and if I try to detect these hangs by checking that the file is being updated I need to wait a long time between updates, up to 10 or 15 mins, otherwise I can sometimes mistakenly kill the ffmpeg process when it appears to have stopped writing when it fact its still filling its internal buffer.

  


  Theres no way to detect this it seems unless I use strace (that I can find anyway). So I am wondering about turning off buffering in ffmpeg and writing unbuffered to disk from ffmpeg.

  


  This will result in the disk constantly making tiny writes and wasting power (and probably, if I use a SSD, mess with wear levelling too).

  


  So I would like to make ffmpeg write to a 'virtual file' (in memory - either kernel memory or a process) which I can specify the flushing characteristics of. The idea being to perhaps specify flush every 2 minutes, then I can keep an eye on the file size and make sure its still being written.

  


  I don't think I've missed any other ways to do this job - even if I could watch the socket stream incoming to ffpmeg the process itself could still stop writing and lose data. Doing the buffering outside of ffmpeg seems like the best way.

  


  Is there a built in way to do this in Linux or does it mean a custom process ? I guess I know how to do this with a small C program and pipe the data in but I wonder if theres a neater way.