Recherche avancée

Sur d’autres sites (5335)

• Burning subtitles into video with ffmpeg with specific margin not working

  17 mai 2024, par Anthony

  I am trying to build a tool where people can position their subtitles on an HTML5 video and then I will burn the subtitles into the video for them.

  


  I can easily get the position of the subtitles, in whatever format I need, that's easy. However, no combination of values that I feed to ffmpeg are working.

  


  My holy grail is an x and y offest (aka offset 5% from the left, 10% from the bottom, in terms of video height/width).

  


  To achieve this, I would like the subtitles to start in the very bottom-left corner.

  


  ffmpeg -y -i english.mp4 -vf "subtitles=english.srt:force_style='Alignment=1,OutlineColour=&H100000000,BorderStyle=3,Outline=1,Shadow=0,FontName=Arial,FontSize=24,MarginL=140,MarginV=0'"  -c:v libx264 -crf 23 -c:a copy output_video.mp4


  


  Here is something that is approaching working, but it's behaving very strangely. The video is 850x480 but when I do a margin of 140 it goes way past the midway point of the video.

  


  Am I missing something ? How can I start the margin in the bottom left, and then apply the margin I want to push it away from the left and away from the bottom ? I can do it either as a percentage of the video height/width if that API is supported or just pixels is fine too (but clearly doesn't seem to be working)

  


• Revision c24d922396 : Add averaging-SAD functions for 8-point comp-inter motion search. Makes first 5

  25 juin 2013, par Ronald S. Bultje

  Changed Paths :
   Modify /vp9/common/vp9_rtcd_defs.sh

  
   Modify /vp9/encoder/vp9_mcomp.c

  
   Modify /vp9/encoder/vp9_onyx_if.c

  
   Modify /vp9/encoder/vp9_sad_c.c

  
   Modify /vp9/encoder/vp9_variance.h

  
   Modify /vp9/encoder/x86/vp9_sad_sse2.asm

  
  
  Add averaging-SAD functions for 8-point comp-inter motion search.

  Makes first 50 frames of bus @ 1500kbps encode from 3min22.7 to 3min18.2,
  i.e. 2.3% faster. In addition, use the sub_pixel_avg functions to calc
  the variance of the averaging predictor. This is slightly suboptimal
  because the function is subpixel-position-aware, but it will (at least
  for the SSE2 version) not actually use a bilinear filter for a full-pixel
  position, thus leading to approximately the same performance compared to
  if we implemented an actual average-aware full-pixel variance function.
  That gains another 0.3 seconds (i.e. encode time goes to 3min17.4), thus
  leading to a total gain of 2.7%.

  Change-Id : I3f059d2b04243921868cfed2568d4fa65d7b5acd

• Raspberry Pi cannot connect to IP camera, while Windows PC can ?

  28 novembre 2020, par gf000

  I have an IP camera (Provision ISR, DI-320IPS-VF, 2MP IR Vari-Focal Dome IP Camera). When I connect it to my router (it is a 10 or 12 years old TP-LINK TL-WR1043ND), it will immediately show up in "IP Manager" (this is a program by the manufacturer) on my Windows PC. If I double click on the camera's row, Internet Explorer opens up, and everything is working fine. On the same Windows PC, if I open VLC Media Player, and paste this URL : rtsp ://username:password@localipaddress:554/profile1
It works fine.

  


  I have also a "Raspberry Pi 4 model B 4 GB RAM", which is connected to the same router. If I open VLC Media Player, and I paste the same URL, it doesn't work. I also created an ffmpeg one-liner, which would take a photo, but that is also not working.

  


  My final goal would be to be able to take photos with that ffmpeg one-liner, on the Raspberry Pi.

  


  Maybe the Raspberry Pi is not powerful enough to handle the stream ? Or, could it be the problem that the IP-camera is sending H-264 / H-265 video stream, and the Raspberry Pi cannot handle it ?

  


  Thank you for your help. Any idea could help me.