Recherche avancée

Sur d’autres sites (7099)

• Is it possible to adjust position of gdigrab recording region during recording ?

  30 novembre 2020, par adelima

  I'm using ffmpeg for recording video from defined desktop region by starting ffmpeg.exe as process with arguments like so :

  


      public static void StartRecording(Video v) {
        string outPath = Path.Combine(Application.StartupPath, "rec", $"{v.FileName}.mkv");
        v.FFMPEG = new Process {
            StartInfo = new ProcessStartInfo() {
                Arguments = $"-hide_banner -y -thread_queue_size 512 -f gdigrab -offset_x {v.Bounds.X} -offset_y {v.Bounds.Y} -video_size {v.Bounds.Width}x{v.Bounds.Height} -show_region 0 -i desktop -vf \"scale=trunc(iw/2)*2:trunc(ih/2)*2\" -c:v libx264 -preset ultrafast -crf 18 -pix_fmt yuv420p \"{outPath}\"",
                WindowStyle = ProcessWindowStyle.Hidden,
                CreateNoWindow = true,
                UseShellExecute = false,
                FileName = Path.Combine(Application.StartupPath, "bin", "ffmpeg.exe"),
                RedirectStandardOutput = true,
                RedirectStandardInput = true,
                RedirectStandardError = true,
            }
        };
        v.FFMPEG.Start();

        new Thread(() => {
            using(StreamReader sr = v.FFMPEG.StandardError) {
                while(!sr.EndOfStream) {
                    Debug.WriteLine(sr.ReadLine());
                }
            }
        }).Start();
    }

    public static void StopRecording(Video v) {
        using(StreamWriter sw = v.FFMPEG.StandardInput) {
            sw.WriteLine("q\n");
        }
        v.FFMPEG.WaitForExit();
        v.FFMPEG.Dispose();
    }


  


  Is it possible to make changes to the -offset_x and -offset_y arguments during recording ? I'm drawing the recording region bounds with directx and want to add a titlebar to it which can be dragged to move the recording region, but I'm not sure how I would let ffmpeg know that I want these offsets changed or whether it's even possible.

  


• Evolution #4754 : Mettre à jeu le jeu des icônes de extensions

  30 avril 2021

  Yaru est trop détaillé, trop OS.

  Les 3 autres me semblent vraiment bien :
  - les couleurs sont franches
  - les codes sont universels
  - c’est plat mais pas trop :p

  A titre de test, voici le rendu du fichier .doc (j’ai fait exprès de prendre un format bien propriétaire car cela finit souvent en pièce jointe d’article)
  - vince https://github.com/vinceliuice/vimix-icon-theme/blob/master/src/scalable/mimetypes/application-vnd.ms-word.svg
  - papirus https://github.com/PapirusDevelopmentTeam/papirus-icon-theme/blob/master/Papirus/64x64/mimetypes/x-office-document.svg
  - numix https://github.com/numixproject/numix-icon-theme/blob/master/Numix/64/mimetypes/wps-office-doc.svg

  mes préférences vont à numix (on voit l’extension doc) ou papirus (carrement l’icône office).

• avutil : add ROI (Region Of Interest) data struct and bump version

  10 janvier 2019, par Guo, Yejun

  avutil : add ROI (Region Of Interest) data struct and bump version
  The encoders such as libx264 support different QPs offset for different MBs,
  
  it makes possible for ROI-based encoding. It makes sense to add support
  
  within ffmpeg to generate/accept ROI infos and pass into encoders.
  Typical usage : After AVFrame is decoded, a ffmpeg filter or user's code
  
  generates ROI info for that frame, and the encoder finally does the
  
  ROI-based encoding.
  The ROI info is maintained as side data of AVFrame.
  Signed-off-by : Guo, Yejun <yejun.guo@intel.com>
  
  Signed-off-by : Derek Buitenhuis <derek.buitenhuis@gmail.com>
  

  • [DH] doc/APIchanges
  • [DH] libavutil/frame.c
  • [DH] libavutil/frame.h
  • [DH] libavutil/version.h