Recherche avancée

Sur d’autres sites (6941)

• Find files that have been only once modified in last 24 hours [duplicate]

  4 janvier 2020, par Vijay Chandra

  This question already has an answer here :

  • How to find the number of times particular file has been modified in given time range [closed]
    
    2 answers
    

  I’m using this command to get all modified files in the last 24 hours on Ubuntu.

  find -type f -name "*.mp4" -mtime -1 -printf "%f\n"

  How can I modify this to detect that a file has been modified more than a single time ? And if so, ignore it.

  I need this to create a watermarking script which will find the latest files within 24 hours and save the list to a text file and with the help of this text file, I use ffmpeg to watermark the videos and move them to the original location.

  If I do this, the find command considers the new updated video as a modified file and adds the watermark repeatedly.

  My code is attached below :

  #!/bin/bash
  
  find -type f -name "*.mp4" -mtime -1 -printf "%f\n" >> filename='/home/domain.com/public_html/admin_panel/public_html/uploads/mp4/temp/file.txt'
  
  all_lines=`cat $filename` 
  
  for item in $all_lines; do  
  
    cp $item /home/domain.com/public_html/admin_panel/public_html/uploads/mp4/temp 
  
    ffmpeg -i $item -i watermark.png -filter_complex "[1][0]scale2ref=w='iw*30/100':h='ow/mdar'[wm][vid];[vid][wm]overlay=(main_w-overlay_w):(main_h-overlay_h)"
  
  -y /home/domain.com/public_html/admin_panel/public_html/uploads/mp4/temp/$item 
  
  done

• AutoKill process on Centos 6.5 Using WHM

  30 janvier 2014, par Will R.

  I have 3gp files that are uploaded to my server via php.
  From there FFmpeg will convert the 3gp files to mp3 files.
  Sometimes the 3gp files are corrupt and FFmpeg will hang on that file and max out that core until the process is killed manually via WHm using the process manager.

  There have been times when several of these files bring the server to a grinding halt because ffmpeg has maxed out all cores.

  Is there a plugin or script or something I can install on the server that can auto kill any process that exceeds a certain amount of time and 90% cpu ?

  Centos 6.5 Using WHM I have root access.

• avcodec/h264_slice : Fix decoding undamaged input with slices

  24 mars 2022, par Andreas Rheinhardt

  avcodec/h264_slice : Fix decoding undamaged input with slices
  ff_er_frame_start() initializes ERContext.error_count
  
  to three times the number of macroblocks to decode.
  
  Later ff_er_add_slice() reduces this number by the amount
  
  of macroblocks whose AC resp. DC resp. MV have been finished
  
  (so every correctly decoded MB counts three times).
  
  So the frame has been decoded correctly if error_count is zero
  
  at the end.
  The H.264 decoder uses multiple ERContexts when using
  
  slice threading and therefore combines these error counts :
  
  The first slice's ERContext is intended to be initialized
  
  by ff_er_frame_start(), error_count of all the other
  
  slice contexts is intended to be zeroed initially and
  
  all afterwards all the error_counts are summed.
  Yet commit 43b434210e597d484aef57c4139c3126d22b7e2b
  
  (probably unintentionally) changed the code to set
  
  the first slice's error_count to zero as well.
  
  This leads to bogus error messages in case one decodes
  
  an input video using multiple slices with slice threading
  
  with error concealment enabled (which is not the default)
  
  ("concealing 0 DC, 0 AC, 0 MV errors in [IPB] frame") ;
  
  furthermore the returned frame is marked as corrupt as well
  
  (ffmpeg reports "corrupt decoded frame in stream %d" for this).
  This can be fixed easily given that only the first ERContext
  
  is really used since 7be2d2a70cd20d88fd826a83f87037d14681a579 :
  
  Don't reset the error_count ; and don't sum the error counts as well.
  Reviewed-by : Michael Niedermayer <michael@niedermayer.cc>
  
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] libavcodec/h264_slice.c