Recherche avancée

Sur d’autres sites (15879)

• Can ffmpeg create folder by itself in windows ?

  20 octobre 2022, par ThanhPhan

  I'm recording RTSP stream from camera into mp4 files in Windows machine and I want to save files in separate folder by day using strftime option (name format like D:/Video/YYYY-MM-DD/). I really want to know that does ffmpeg have ability to create folder by itself or do I have to create it by external programs ?

  



  For example, I want to use ffmpeg command like below :

  



  ffmpeg -rtsp_transport tcp -i  \
    -f segment -strftime 1 -segment_time 01:00:00 -segment_atclocktime 1 \
    -segment_clocktime_offset 30 -segment_format mp4 \ 
    -an -vcodec copy -reset_timestamps 1 \
    D:/Video/%Y-%m-%d/record_%H_%M_%S.mp4


  


• Restore the previous system path variable (windows)

  17 septembre 2022, par NaRas

  a question regarding messing with Windows Path variable.
My situation is quite specific :

  


  

  • I was trying to install ffmpeg according to this tutorial https://www.geeksforgeeks.org/how-to-install-ffmpeg-on-windows/

  


  • The last step was setting the path variable setx /m PATH "C:\ffmpeg\bin;%PATH%"

  


  • It worked, however afterwards I noticed that if I try to call python from the command prompt or the powershell if run as administrator, I started getting 'chcp' is not recognized as an internal or external command, (although works fine if run as user), indicating that something is wrong with PATH variables.

  


  • I looked into my variables and saw this edit.

  


  


  Path

  


  It seems to me that the command added the ffmpeg line to the system path and possibly overwritten the original, which is why there are issues when using command prompt as administrator. It probably should have added it to the user Path (not system Path variable)

  


  If that is the case, is there a way to restore the previous system Path variable. Maybe I can paste it from the user Path variable ?

  


• Using DirectX from subprocess executed by windows service

  26 mai 2019, par Igor Gorelik

  I need to execute ffmpeg process from windows service and capture it’s standard output. It works fine until I use hardware acceleration. Because accessing DirectX from windows service is restricted, the subprocess also fails to access it.

  When I’m executing the same code from console application, everything works OK, but the same code executed from windows service fails to use hardware acceleration.

          string ffmpegArgs = /*-hwaccel dxva2 */"-threads 0 -probesize 100512 -i c:/Temp/test.mp4 -vf yadif -vcodec libx264 -preset ultrafast -tune zerolatency -profile baseline -x264-params keyint=20:min-keyint=20:scenecut=-1 -acodec aac -b:a 48k -flags +cgop -f mp4 -movflags empty_moov+default_base_moof+frag_keyframe c:/temp/output.avi";
  
  
  
          var psi = new ProcessStartInfo
  
          {
  
              FileName = "c:/Temp/ffmpeg4/ffmpeg.exe",
  
              Arguments = ffmpegArgs,
  
              WorkingDirectory = "c:/Temp/ffmpeg4",
  
              CreateNoWindow = false,
  
              WindowStyle = ProcessWindowStyle.Hidden,
  
              RedirectStandardInput = false,
  
              RedirectStandardOutput = true,
  
              RedirectStandardError = true,
  
              UseShellExecute = false
  
          };
  
  
  
          var processVideo = new Process { StartInfo = psi }.Start();

  I need somehow break the inherited restrictions to be able to execute ffmpeg with hardware acceleration (access DirectX API). Any suggestions ?