Recherche avancée

Sur d’autres sites (11363)

• lavc/flacdsp : optimise RVV vector type for lpc16

  14 mai 2024, par Rémi Denis-Courmont

  lavc/flacdsp : optimise RVV vector type for lpc16
  This calculates the optimal vector type value at run-time based on the
  
  hardware vector length and the FLAC LPC prediction order. In this
  
  particular case, the additional computation is easily amortised over
  
  the loop iterations :
  T-Head C908 :
  
      C     V before  V after
  
   1   48.0    214.7     95.2
  
   2   64.7    214.2     94.7
  
   3   79.7    213.5     94.5
  
   4   96.2    196.5     94.2 #
  
   5  111.0    195.7    118.5
  
   6  127.0    211.2    102.0
  
   7  143.7    194.2    101.5
  
   8  175.7    193.2    101.2 #
  
   9  176.2    224.2    126.0
  
  10  191.5    192.0    125.5
  
  11  224.5    191.2    124.7
  
  12  223.0    190.2    124.2
  
  13  239.2    189.5    123.7
  
  14  253.7    188.7    139.5
  
  15  286.2    188.0    122.7
  
  16  284.0    187.0    122.5 #
  
  17  300.2    186.5    186.5
  
  18  314.0    185.5    185.7
  
  19  329.7    184.7    185.0
  
  20  343.0    184.2    184.2
  
  21  358.7    199.2    183.7
  
  22  371.7    182.7    182.7
  
  23  387.5    181.7    182.0
  
  24  400.7    181.0    181.2
  
  25  431.5    180.2    196.5
  
  26  443.7    195.5    196.0
  
  27  459.0    178.7    196.2
  
  28  470.7    177.7    194.2
  
  29  470.0    177.0    193.5
  
  30  481.2    176.2    176.5
  
  31  496.2    175.5    175.7
  
  32  507.2    174.7    191.0 #
   # Power of two boundary.
  With 128-bit vectors, improvements are expected for the first two
  
  test cases only. For the other two, there is overhead but below noise.
  
  Improvements should be better observable with prediction order of 8
  
  and less, or on hardware with larger vector sizes.
  

  • [DH] libavcodec/riscv/flacdsp_init.c
  • [DH] libavcodec/riscv/flacdsp_rvv.S

• Combine many videos in list using FFMPEG

  2 septembre 2022, par anoor1234

  I have a bunch of videos that are MP4s with different FPS, resolution, aspect ratio, basically everything. I'm trying to see if its possible to use FFMPEG to combine them into a single 1080/720 video using a single command, or at least make them all similar format so that combining is easy. Speed and less CPU power would be preferred but I'm in no rush and

  


  I found this command on another stack overflow question :

  


  ffmpeg -i 1.mp4 -i 2.mp4 -i 3.mp4 -filter_complex \
"[0:v]scale=1280:720:force_original_aspect_ratio=decrease,pad=1280:720:-1:-1,setsar=1,fps=30,format=yuv420p[v0];
 [1:v]scale=1280:720:force_original_aspect_ratio=decrease,pad=1280:720:-1:-1,setsar=1,fps=30,format=yuv420p[v1];
 [2:v]scale=1280:720:force_original_aspect_ratio=decrease,pad=1280:720:-1:-1,setsar=1,fps=30,format=yuv420p[v2];
 [v0][0:a][v1][1:a][v2][2:a]concat=n=3:v=1:a=1[v][a]" \
-map "[v]" -map "[a]" -c:v libx264 -c:a aac -movflags +faststart output.mp4


  


  The problem is that I have more that 3 videos to combine and I don't know how to work this command with more, I have an entire list of videos in a list.txt file structured as such :

  


  file './videos/video1.mp4'
file './videos/video2.mp4'
file './videos/video3.mp4'


  


  The code that somewhat worked for me was this

  


  ffmpeg -safe 0 -f concat -i list.txt -c copy output.mp4


  


  It combines the video well and fairly fast but I get weird glitches with the audio and the resolution is weird (I'm hoping for 1920x1080). I suspect this is due to the varying attributes of each video but I'm not sure. I'm familiar with Python but I have found no Python script that can do what I ask. If there any way to combine my list into one video (using FFMPEG or not) reliably ?

  


• ffmpeg encoder streaming issues

  8 août 2017, par bobsingh1

  I am trying to build ffmpeg encoder on linux. I started with a custom built server Dual 1366 2.6 Ghz Xeon CPUs (6 cores) with 16 GB RAM with Ubuntu 16.04 minimal install. Built ffmpeg with h264 and aac. I am taking live source OTA channels and encoding/streaming them with following parameters

  -vcodec libx264 -preset superfast -crf 25 -x264opts keyint=60:min-keyint=60:scenecut=-1 -bufsize 7000k -b:v 6000k -maxrate 6300k -muxrate 6000k -s 1920x1080 -format yuv420p -g 60 -sn -c:a aac -b:a 384k -ar 44100

  And I am able to successfully udp out using mpegts. My problem starts with 5th stream. The server can handle four streams and as soon as I introduce 5th stream I start seeing hiccups in output. Looking at my cpu usage using top I still see only 65% to 75% usage with occasional 80% hit. Memory usage is well within acceptable parameters. So I am wondering either top is not giving me accurate cpu usage or something is not right with ffmpeg. The server is isolated for udp in/out on a 1 Gbps network.

  I decided to up the cpu power and installed two 3.5 Ghz CPUs (6 cores) thinking it was perhaps the cpu clock. To my surprise the results were no different. So now I am wondering is there some built in limit I am hitting when I process at 1080p. If I change the resolution to 720p it is able to process 8 streams but 720 is not acceptable.
  My target is 10 1080p streams per server.
  So my questions are
  1. If I use a quad motherboard and up the cpu count to 4 (6 or 8 cores) will I get 10 1080p streams ? Is there any theoretical max I can go with ffmpeg per machine ?
  2. Do cores matter more or does clock matter more ?
  3. Any suggestions in improvement with my options. I have tried ultrafast preset but the output quality is unacceptable.

  Thanks in advance