Recherche avancée

Sur d’autres sites (6503)

• ffmpeg x11grab Fedora 22 cannot open display [on hold]

  4 août 2015, par voor

  Running a fairly recent version of Fedora 22 :

  Linux localhost 4.1.3-200.fc22.x86_64 #1 SMP Wed Jul 22 19:51:58 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

  Dual screen Acer XB270HU and AOC 2369. Also uses NVIDIA Drivers :

  ➜  ~  rpm -qa | grep nvidia
  
  nvidia-driver-libs-352.30-1.fc22.x86_64
  
  nvidia-driver-352.30-1.fc22.x86_64
  
  nvidia-settings-352.30-1.fc22.x86_64
  
  nvidia-libXNVCtrl-352.30-1.fc22.x86_64
  
  dkms-nvidia-352.30-1.fc22.x86_64
  
  nvidia-driver-libs-352.30-1.fc22.i686

  Whenever I attempt to do a x11grab in ffmpeg I get an error :

  ➜  ~  ffmpeg -f x11grab -r 15 -s 1920x1080 -i :0 -vcodec h264 -crf 30 -y output.mp4
  
  ffmpeg version 2.6.3 Copyright (c) 2000-2015 the FFmpeg developers
  
    built with gcc 5.1.1 (GCC) 20150422 (Red Hat 5.1.1-1)
  
    configuration: --prefix=/usr --bindir=/usr/bin --datadir=/usr/share/ffmpeg --incdir=/usr/include/ffmpeg --libdir=/usr/lib64 --mandir=/usr/share/man --arch=x86_64 --optflags='-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic' --enable-bzlib --disable-crystalhd --enable-frei0r --enable-gnutls --enable-ladspa --enable-libass --enable-libcdio --enable-libdc1394 --disable-indev=jack --enable-libfreetype --enable-libgsm --enable-libmp3lame --enable-openal --enable-libopencv --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libvorbis --enable-libv4l2 --enable-libvpx --enable-libx264 --enable-libx265 --enable-libxvid --enable-x11grab --enable-avfilter --enable-avresample --enable-postproc --enable-pthreads --disable-static --enable-shared --enable-gpl --disable-debug --disable-stripping --shlibdir=/usr/lib64 --enable-runtime-cpudetect
  
    libavutil      54. 20.100 / 54. 20.100
  
    libavcodec     56. 26.100 / 56. 26.100
  
    libavformat    56. 25.101 / 56. 25.101
  
    libavdevice    56.  4.100 / 56.  4.100
  
    libavfilter     5. 11.102 /  5. 11.102
  
    libavresample   2.  1.  0 /  2.  1.  0
  
    libswscale      3.  1.101 /  3.  1.101
  
    libswresample   1.  1.100 /  1.  1.100
  
    libpostproc    53.  3.100 / 53.  3.100
  
  Invalid MIT-MAGIC-COOKIE-1 key[x11grab @ 0x1fe1d40] Cannot open display :0, error 1.
  
  :0: Input/output error

  I’ve tried a few different commands basically copy/pasta from the web on how to do screengrabs. I don’t need audio, just video, and all of them result in the same error.

  I am able to do xwininfo without any problems :

  ➜  ~  xwininfo    
  
  
  
  xwininfo: Please select the window about which you
  
            would like information by clicking the
  
            mouse in that window.
  
  
  
  xwininfo: Window id: 0x1e0006c "linux - ffmpeg x11grab Fedora 22 cannot open display - Stack Overflow - Google Chrome"
  
  
  
    Absolute upper-left X:  0
  
    Absolute upper-left Y:  27
  
    Relative upper-left X:  0
  
    Relative upper-left Y:  27
  
    Width: 2560
  
    Height: 1413
  
    Depth: 24
  
    Visual: 0x21
  
    Visual Class: TrueColor
  
    Border width: 0
  
    Class: InputOutput
  
    Colormap: 0x20 (installed)
  
    Bit Gravity State: ForgetGravity
  
    Window Gravity State: NorthWestGravity
  
    Backing Store State: NotUseful
  
    Save Under State: no
  
    Map State: IsViewable
  
    Override Redirect State: no
  
    Corners:  +0+27  -1920+27  -1920-0  0
  
    -geometry 2560x14130

• Import BMP file into quicktime .mov file ?

  23 juillet 2015, par Neal Davis

  I am creating a quicktime container .mov file from one BMP file ; I am doing this in two ways :

  1. using the quicktime COM object API for .NET C# under windows
  2. using ffmpeg command line (rawvideo codec)

  Both resulting .MOV files open with quicktime player pro just fine and they look identical to my eyes. Both resulting .MOV files are either the same size as the original BMP or a larger.

  However when viewing the track properties under QT Player PRO of movie file number 1. track format = BMP ; when viewing track properties of number 2. track format = NONE.

  Is there likely a difference - since in 1. above I do not set a track properties format ? In other words is there likely any changes being made to the BMP bits in number 1 above (like compression, or alpha, or ???) ?

• Force a vbscript to open command prompt in 64bit instead of 32bit

  26 juin 2015, par Arvo Bowen

  I have been trying to get this script to work all day !

  Here are some facts about my situation...

  • I have a program named "ffmpeg.exe" in my "C :\Windows\System32\" folder.
  • I DO NOT have that program in my "C :\Windows\SysWOW64\" folder.

  Currently this is the script I have...

  Option Explicit
  
  
  
  Dim oFSO, oShell, sCommand
  
  Dim sFilePath, sTempFilePath
  
  
  
  Set oFSO = CreateObject("Scripting.FileSystemObject")
  
  
  
  sFilePath = "C:\test\in_video.mkv"
  
  sTempFilePath = "C:\test\out_video.mp4"
  
  
  
  sCommand = "%comspec% /k ffmpeg -n -i """ + sFilePath + """ -c:v copy -c:a copy """ + sTempFilePath + """"
  
  WScript.Echo sCommand
  
  Set oShell = WScript.CreateObject("WScript.Shell")
  
  oShell.Run sCommand, 1, True
  
  Set oShell = Nothing
  
  
  
  Set oFSO = Nothing

  If I run this script manually at a command prompt then it seems to work just fine. But if I let another app run it (for example in this case uTorrent), it runs the script as expected but when it tries to process the oShell.Run command it runs that in a 32bit environment ! Then I get this...
  

  If I try to open up a new command prompt (nothing special) i seems to default to a 64bit environment and then I can type "ffmpeg" and it shows me the help content as expected.

  So for some reason I can’t get the script to run applications (specifically CMD) in the 64bit environment. Anyone know how I can achieve this ?

  ---

  Update

  Seems that my script is in fact being ran in 32bit mode ! Even though the script title bar says "C :\Windows\System32\cscript.exe", which is a 64bit environment !!

  I used the following script to determine that it was running in a 32bit environment...

  Dim WshShell
  
  Dim WshProcEnv
  
  Dim system_architecture
  
  Dim process_architecture
  
  
  
  Set WshShell =  CreateObject("WScript.Shell")
  
  Set WshProcEnv = WshShell.Environment("Process")
  
  
  
  process_architecture= WshProcEnv("PROCESSOR_ARCHITECTURE") 
  
  
  
  If process_architecture = "x86" Then    
  
      system_architecture= WshProcEnv("PROCESSOR_ARCHITEW6432")
  
  
  
      If system_architecture = ""  Then    
  
          system_architecture = "x86"
  
      End if    
  
  Else    
  
      system_architecture = process_architecture    
  
  End If
  
  
  
  WScript.Echo "Running as a " & process_architecture & " process on a " _ 
  
      & system_architecture & " system."