Recherche avancée

Sur d’autres sites (8116)

• How to use Intel Quick Sync/iGPU in OVH dedicated server

  3 octobre 2022, par Meir

  I have a dedicated server with the following HW :

  


  CPU: Intel(R) Xeon(R) E-2386G CPU @ 3.50GHz
Motherboard: Manufacturer: ASRockRack, Product Name: E3C252D4U-2T/OVH


  


  According to the Intel website, E-2386G has Intel Quick Sync, and I want to use it.
I tried to check which VGA I have in the system (expected to see Intel + the local), and this is the output :

  


  05:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 41)


  


  I.e., the Intel iGPU doesn't recognize at all in the system, I tried to check in /dev/dri what are the existing devices there, and this is the output :

  


  ls -alh /dev/dri
total 0
drwxr-xr-x  3 root root      80 Sep 19 10:28 .
drwxr-xr-x 18 root root    4.2K Sep 20 13:05 ..
drwxr-xr-x  2 root root      60 Sep 19 10:28 by-path
crw-rw----  1 root video 226, 0 Sep 19 10:28 card0


  


  When I tried to run vainfo tool, I get the following results :

  


  Vanilla run :

  


  vainfo
error: can't connect to X server!
libva info: VA-API version 1.7.0
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
vaInitialize failed with error code -1 (unknown libva error),exit


  


  Run after setting export LIBVA_DRIVER_NAME=i965 :

  


  vainfo
error: can't connect to X server!
libva info: VA-API version 1.7.0
libva info: User environment variable requested driver 'i965'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_6
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit


  


  Run with sudo :

  


  sudo vainfo
error: XDG_RUNTIME_DIR not set in the environment.
error: can't connect to X server!
libva info: VA-API version 1.7.0
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
vaInitialize failed with error code -1 (unknown libva error),exit


  


  How can I use Intel Quick Sync ?

  


  --- edit ---

  


  Running the suggested commands :

  


  vainfo --display DRM
libva info: VA-API version 1.7.0
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
vaInitialize failed with error code -1 (unknown libva error),exit

vainfo --display wayland
error: failed to initialize display 'wayland'

vainfo --display help
Available displays:
  wayland
  x11
  DRM


sudo journalctl -b | grep i965  (no results)


  


• How do you display things in the rails console for the user in Rails ?

  30 décembre 2014, par Swaathi K

  I am using Streamio-ffmpeg to process files. The gem shows the progress of the transcoding in the console. I want to display this progress to the user. Is there anyway of doing this ?

  This is my helper : (Where the transcoding is done)

  if myfile.filetype == "video"
  
          movie = FFMPEG::Movie.new(oldpath(myfile))
  
          movie.transcode(newpath(myfile),"-deadline realtime -aq 10 -qmax 25") { |progress| puts progress }
  
  
  
          FileUtils.rm_rf(oldpath(myfile))

  The { |progress| puts progress } is responsible for printing the progress to the console. Can I display this in my views instead ?

• avutil/file_open : avoid file handle inheritance on Windows

  29 octobre 2015, par Tobias Rapp

  avutil/file_open : avoid file handle inheritance on Windows
  Avoids inheritance of file handles on Windows systems similar to the
  
  O_CLOEXEC/FD_CLOEXEC flag on Linux.
  Fixes file lock issues in Windows applications when a child process
  
  is started with handle inheritance enabled (standard input/output
  
  redirection) while a FFmpeg transcoding is running in the parent
  
  process.
  Links relevant to the subject :
  https://msdn.microsoft.com/en-us/library/w7sa2b22.aspx
  Describes the _wsopen() function and the O_NOINHERIT flag. File handles
  
  opened by _wsopen() are inheritable by default.
  https://msdn.microsoft.com/en-us/library/windows/desktop/ms682425%28v=vs.85%29.aspx
  Describes handle inheritance when creating new processes. Handle
  
  inheritance must be enabled (bInheritHandles = TRUE) e.g. when you want
  
  to pass handles for stdin/stdout via lpStartupInfo.
  Signed-off-by : Tobias Rapp <t.rapp@noa-audio.com>
  
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavutil/file_open.c