Recherche avancée

Sur d’autres sites (10234)

• How to re-encode to rgb pixel_format properly in ffmpeg

  1er février 2020, par captain_majid

  I’m using this command to record from multiple inputs :

  ffmpeg -y
  
  -f dshow -rtbufsize 1024M -thread_queue_size 1024 -probesize 64M -i video="screen-capture-recorder" -framerate 30
  
  -f dshow -rtbufsize 16M -i audio="virtual-audio-capturer"
  
  -f dshow -rtbufsize 16M -i audio="Microphone (DroidCam Virtual Audio)"
  
  -f dshow -rtbufsize 512M -thread_queue_size 512 -probesize 50M -i video="DroidCam Source 3"
  
  -stream_loop -1 -i ".\media\background sounds\blue.mp4"
  
  -i ".\media\pictures\Webcam Overlay\blue_.png"
  
  -i ".\media\pictures\Webcam Overlay\red.png"
  
  -f gdigrab -rtbufsize 512M -thread_queue_size 512 -probesize 64M -itsoffset 0.80 -i title="NohBoard v1.2.2" -framerate 60 -draw_mouse 0
  
  
  
  -filter_complex "
  
  [0:v] scale=1366x768 [desktop];
  
  [3:v] hue=s=-5, scale=240x160 [webcam];
  
  [desktop][webcam] overlay=x=W-w-285:y=H-h-7:format=rgb [deskCam];
  
  [4:v] format=rgba,colorchannelmixer=aa=0.5, scale=240x160 [vid];
  
  [deskCam][vid] overlay=x=W-w-5:y=H-h-245:format=rgb [deskCamVid];
  
  [deskCamVid][5:v] overlay=x=W-w-280:y=H-h-0:format=rgb [deskCamVidBlue];
  
  [deskCamVidBlue][6:v] overlay=x=W-w-0:y=H-h-238:format=rgb [deskCamVidBlueRed];
  
  [7:v] chromakey=0x00FF00:similarity=.200, scale=420x140 [kb];
  
  [deskCamVidBlueRed][kb] overlay=x=W-w-945:y=H-h-285:format=rgb [final];
  
  [1][2] amix [aud1]; [1][2][4] amix=inputs=3 [aud2]"
  
  -map "[final]" -map "[aud1]" -map "[aud2]" -metadata:s:a:0 title="No Music" -metadata:s:a:1 title="All sounds" out.mkv

  The problem is the colors are not as bright as I want unless adding :format=rgb to all overlays like seen above, but this delays my encoding a lot, also when I press ’Q’, only a small part of the video (like 1m of 3m) is produced.

  Also If you see any unnecessary switches or non-optimal ones, please advise.

• running ffmpeg from Popen inside (twisted) timer.LoopingCall() stalls

  14 février 2014, par user1913115

  I have an RTSP stream which i need to re-stream as HLS. When RTSP stream goes down (e.g. camera disconnects) I put a blue screen to let the user know that the camera went offline. HLS segmenter is running separately, listening on port 22200 for incoming packets.

  in python the code essentially boils down to this :

  import psutil, subprocess as sb
  
  from twisted.internet import reactor, task
  
  from cameraControls import camStatus, camURL
  
  ffOn = False
  
  psRef = False
  
  def monitor():
  
   print "TIMER TICK"
  
   if camStatus()=='ON' and not ffOn: #camera just came online
  
    cmd = ["ffmpeg", "-i", camURL, "-codec", "copy", "-f", "mpegts", "udp://127.0.0.1:22200"]
  
    ps = sb.Popen(cmd,stderr=sb.PIPE)
  
    psRef=ps
  
   #check the stream:
  
   psmon = psutil.Process(psRef.pid)
  
   if psmon.status!=psutil.STATUS_RUNNING: 
  
    print "FFMPEG STOPPED"
  
  
  
  tmr = task.LoopingCall(monitor)
  
  tmr.start(2)
  
  reactor.run()

  it works fine for 5-6 minutes, then i see the video stall and if i check the cpu usage of the ffmpeg it shows 0, the ffmpeg output doesn't change, as if paused. however psmon.status shows as running, and the timer is still going (i see "TIMER TICK" message pop up every 2 seconds in the command line.

  if i simply run the ffmpeg command from the command line (not from python) then it works for hours no problem.

  does anybody know if the twisted reactor is stalling the process ? or is it the subprocess.Popen itself issue ? or the timer itself is glitching somehow(even though it gets to the 'monitor' function) ? i have other timers running also in the same reactor (same thread), could that be an issue ?

• How to make videos .mp4 for a Phillips Media Player GO GEAR VIBE models ? [closed]

  14 avril 2023, par Ivan Rojas Calvo

  Here is the answer by steps (4/13/23) :

  


  


  1. First download and install the software WinFF here

     


  


  2. Check the specificacions of your media player, mine is the GoGearVibe SA2VBE08K/55 model

     


  


  3. Look for the video specification : mine says that the video format needs to match this specifications :

     


     Format = MJPEG (.mp4)

     


     Resolution = 128 x 128 píxeles

     


     Frames per second = 30 cps (fps)

     


     Bitrate = 512 kpbs

     


  


  4. Read this tutorial to create a preset in WinFF here

     


  


  5. Create a preset that turns ANY mp4 video you have into an MJPEG video with the properties shown above with this info :

     


     name : GoGearVibe55

     


     preset label : MJPEG GOGEAR

     


     Preset command line :

     


     -f mov -vf scale=128:128 -c:v mjpeg -b:v 512k -r 25 -c:a adpcm_ima_wav -b:a 192k -ar 22050 -ac 2


     


     output file : mp4

     


  


  6. Understand how to adapt the code to your necessities with this image
enter image description here

     


  


  


  Do not change what is mark in red, that's the resolution of the screen and the encoder of the video. You can change the value mark in blue, which means the bitrate, more bitrate the video will have more definition without changing the resolution. Tha value in green refers to the fps and the ones marked in yellow is the audio settings, don't worry about that, are good audio settings.

  


  Done. I did'n know how to create an article so I let you try this solution, good luck !