Recherche avancée

Sur d’autres sites (12277)

• Gstreamer : Hauppauge HD PVR and Multi-video file output

  7 juin 2014, par user3716978

  I have very specific requirements for a Gstreamer pipeline that I can’t seem to create. I’m running Linux Mint Mate 14 (Nadia).

  I have an HD PVR, which records in MPEG TS. It presents, as its interface, a V4L2 device at /dev/video0. What I need is to somehow have it output the captured video to multiple files. That is, like dvgrab’s autosplit, it would output, say, 1800 frames, then create a new output file, then capture another 1800, and on and on.

  I’ve tried numerous methods. First, using multifilesink with the keyframe next-file option does what I want, but it doesn’t seem to add stream headers to the segment files, so that they cannot play properly and/or are missing their initial keyframe.

  I’ve tried limiting each individual capture length using num-buffers, and just restarting the capture after the previous one ends. This works for maybe 30 or 40 files but all the switching on and off eventually locks up the HD PVR, and it has to be power-cycled.

  I could also have it dump images to the disk and work with the individual frames, but this is very slow with MPEG TS since it has to demux, decode, and reencode every frame. It eats up 100% cpu and drops about 60% of the frames on my computer.

  ffmpeg doesn’t work, because the HD PVR driver doesn’t support ioctl. I can’t seem to get mencoder to stream it this way either, but maybe it’s possible ?

  What I need is to :

  • Have a single capture stream, to avoid pissing off the HD PVR
  • Have it split the stream into multiple files which can be individually analyzed
  • Have those multiple files be valid videos
  • Not eat up 100% of my CPU (although high utilization is ok, it needs to run at full speed). Since the stream is 1920x1080x60fps, anything to do with reencoding won’t work. It pretty much needs to be a stream copy.

  Thank you

• From time to time ffmpeg makes my computer unable to restart

  6 juin 2022, par principal-ideal-domain

  I'm doing very time consuming ffmpeg video editing. That's why I put my commands into a .bat file and run them over night. Usually that works fine but from time to time when I look at the next moring a see an error message of this kind :

  


  

  


  From that state on I didn't find any good way to close the console. When I press the x in the top right corner, it freezes. When I try to kill it using the task manager nothing happens. Even explorer.exe can't be closed using the task manager. A shutdown won't do anything. During the last month I had this problem about three times and the only way I could close it was to long press the power button of the computer until it was turned off this hard way.

  


  Any ideas what to in such situations ? Or even better : Any ideas how to prevent those situations ? What is the reason for the error ? Do you understand the message ? By the way, when the computer is started again then at the next morining and I run the same bat file again everything works fine. So the same error does not repeat and the video is edited nicely.

  


  Edit : Now, about one week after posting this question the problem occurred many more times. It is very annoying. I guess it has to do with the external hard drive connected by USB. Sometimes it randomly interrupts the connection. That might be the reason for the behavior. However that be, I want to learn a solution how to deal with this in future. I don't want to always push the reset button of my computer. I want a proper way to shut it down.

  


• 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