Recherche avancée

Sur d’autres sites (3929)

• Error writing to file when saving matplotlib animation with a given codec

  31 mars 2017, par idesh

  I’ve had trouble saving an mp4 animation created with matplotlib with a given codec. However I should mention beforehand that I could save the mp4 animation without specifying codecs and that seems to work fine, except that I am not able to insert this mp4 animation into powerpoint for a presentation. Powerpoint says it cannot read the file because it is missing 64bit codec.

  When digging further I discovered that Windows media player which is used by power point for the animations, has already some video codecs installed.

  So I thought of saving the initial matplotlib animation with one of these codecs, which is also compatible with ffmpeg. The command ffmpeg -codecs on terminal lists the supported codecs and I could spot the codecs common with ffmpeg and windows media player, ex : MSS1, MSS2

  So I tried to save the animation with the argument codec set as follows.

  anim = animation.FuncAnimation(fig, animate, 158,interval=300, blit=True)
  
  writer = animation.writers['ffmpeg']
  
  anim.save('film_v5.mp4', codec='mss1')

  Nevertheless it leads to an error, no matter what type of codec argument I put.

  So I was wondering perhaps there was someone savvy, willing to help me troubleshoot this problem. Despite my attempts I could not find any solution in the stackoverflow forum.

  Thank you in advance for your attention.

• lavu/tx : improve 3-point fixed precision

  14 février 2020, par Lynne

  lavu/tx : improve 3-point fixed precision
  There's just no reason not to when its so easy (albeit messy) and its also
  
  reducing the precision of all non-power-of-two transforms that use it.
  

  • [DH] libavutil/tx_priv.h
  • [DH] libavutil/tx_template.c

• 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.