Recherche avancée

Sur d’autres sites (6914)

• errors of 'vaGetDisplay' and `vaGetDisplayDRM' [duplicate]

  29 novembre 2018, par Kindermann

  This question already has an answer here :

  • errors when compiling c code with ffmpeg library
    
    1 answer
    

  After updating my ubuntu OS from 14.04 to 16.04, I installed the ffmpeg library using the following configurations :

  PATH="$HOME/bin:$PATH" PKG_CONFIG_PATH="$HOME/ffmpeg_build/lib/pkgconfig" ./configure \
  
    --prefix="$HOME/ffmpeg_build" \
  
    --pkg-config-flags="--static" \
  
    --extra-cflags="-I$HOME/ffmpeg_build/include" \
  
    --extra-ldflags="-L$HOME/ffmpeg_build/lib" \
  
    --bindir="$HOME/bin" \
  
    --enable-gpl \
  
    --enable-libass \
  
    --enable-libfdk-aac \
  
    --enable-libfreetype \
  
    --enable-libmp3lame \
  
    --enable-libopus \
  
    --enable-libtheora \
  
    --enable-libvorbis \
  
    --enable-libvpx \
  
    --enable-libx264 \
  
    --enable-nonfree
  
  PATH="$HOME/bin:$PATH" make
  
  make install

  It seemed to me the installation process was ok. After that, I tried to compile my own C source code with the following Makefile :

  EDITTED(adding -lva-drm -lva-x11 at line 10)

  FFMPEG_LIBS=    libavdevice                        \
  
                  libavformat                        \
  
                  libavfilter                        \
  
                  libavcodec                         \
  
                  libswresample                      \
  
                  libswscale                         \
  
                  libavutil                          \
  
  
  
  TARGET = video_analysis
  
  LIBS = -lva -lX11 -lvdpau -lm -lva-drm -lva-x11
  
  CC = gcc
  
  CFLAGS += -O2 -g -O0
  
  CFLAGS := $(shell pkg-config --cflags $(FFMPEG_LIBS)) $(CFLAGS)
  
  LDLIBS := $(shell pkg-config --libs $(FFMPEG_LIBS)) $(LDLIBS)
  
  
  
  .PHONY: default all clean
  
  
  
  default: $(TARGET)
  
  all: default
  
  
  
  OBJECTS = $(patsubst %.c, %.o, $(wildcard *.c))
  
  HEADERS = $(wildcard *.h)
  
  
  
  %.o: %.c $(HEADERS)
  
          $(CC) $(CFLAGS) -c $< -o $@
  
  
  
  .PRECIOUS: $(TARGET) $(OBJECTS)
  
  
  
  $(TARGET): $(OBJECTS)
  
      $(CC) $(OBJECTS) $(LDLIBS) $(LIBS) -o $@
  
  
  
  clean:
  
      -rm -f *.o
  
      -rm -f $(TARGET)

  However, my compiler complained the following errors :

  /root/ffmpeg_build/lib/libavutil.a(hwcontext_vaapi.o): In function `vaapi_device_create':
  
  /home/widerstand/ffmpeg_sources/ffmpeg/libavutil/hwcontext_vaapi.c:896: undefined reference to `vaGetDisplay'
  
  /home/widerstand/ffmpeg_sources/ffmpeg/libavutil/hwcontext_vaapi.c:917: undefined reference to `vaGetDisplayDRM'
  
  collect2: error: ld returned 1 exit status
  
  Makefile:30: recipe for target 'video_analysis' failed
  
  make: *** [video_analysis] Error 1

  My question is : in which library do ’vaGetDisplay’ and `vaGetDisplayDRM’ exist ? It’s for sure that libva functions properly. I have no clue how to fix the bugs...Thank you in advance !

• C# UWP Desktop Bridge start ffmpeg with command

  4 décembre 2019, par iNCEPTiON_

  I have a UWP Application which starts a WPF app and communicates via AppServiceConnection which works well,
  what I want to do is to start FFmpeg / FFplay with the command to play a video.

  The code in the WPF app for starting FFmpeg / FFplay via AppServiceConnection

  private void Connection_RequestReceivedAsync(AppServiceConnection sender, AppServiceRequestReceivedEventArgs args)
  
          {
  
              var value = args.Request.Message["REQUEST"] as string;
  
              switch (value)
  
              {
  
                  case "StartFFmpeg":
  
                      Test();
  
                      break;
  
              }
  
          }
  
  
  
          private void Test()
  
          {
  
              var process = new Process();
  
              process.StartInfo.RedirectStandardOutput = true;
  
              process.StartInfo.RedirectStandardError = true;
  
              process.StartInfo.FileName = Path.GetDirectoryName(Process.GetCurrentProcess().MainModule.FileName) + @"\ffplay.exe";
  
              process.StartInfo.Arguments = @"-i C:\Users\test\video.mp4";
  
  
  
  
  
              process.StartInfo.UseShellExecute = false;
  
              process.StartInfo.CreateNoWindow = true;
  
              process.Start();
  
          }

  this fails with the following error in the UWP app :

  The target process exited without raising a CoreCLR started event. Ensure that the target process is configured to use .NET Core. This may be expected if the target process did not run on .NET Core.
  
  The program '[16824] FFmpeg.Bridge.exe' has exited with code -532462766 (0xe0434352).

  now my question is, is it possible to start FFmpeg / FFplay with the desktop bridge ? or can we only start .net core processes, the process is running with full privileges so why is that not possible ?

  The UWP App won’t be published on the store, it will only run on a local windows machine.

• Synchronize + merge audio of one video file into another

  19 juillet 2021, par TRH

  Suppose the following :

  


  

  • I got two video files with audio

  


  • They are pretty much the same (going by 'images'), but differ in codec, quality, .. and audio.

  


  


  To have a more specific example, furtermore suppose :

  


  

  • Video 1 (the 'target') is running @24 FPS in 2160p [HEVC]. The first 25 seconds of audio and video are not "belonging"/unessential to the video depicted.

  


  • Video 2 is running @30 FPS in 720p [X264]. The first 19 seconds of audio and video are not "belonging"/unessential to the video depicted.

  


  


  I now want to perfectly merge the audio of "Video 2" into the target Video, so that the audio of both videos pretty match (except e.g. language)

  


  My initial thought would be to synchronize both videos by frames using fingerprinting/hashes similar to various repost checker bots.

  


  Is there an easier method, how would I go from there (preferably using ffmpeg) ?
Bonus points if the first 25 seconds of the "Video 1" audio are prepended to the "Video 2" audio while the first 19 seconds are omitted.