Recherche avancée

Sur d’autres sites (17928)

• How to restore a recorded mkv video back to its original state [closed]

  5 avril 2023, par itpotatoes

  The mkv video recorded with the Kinect camera was converted to mp4 after converting the color, depth, and ir video to avi using mkvtoolnix.
When I try to convert this back to avi with ffmpeg, it says that the depth and ir images cannot contain rawvideo gray16be in the avi container. Does anyone know of another way ?

  


  I could change it to another codec, but I couldn't convert it to rawvideo gray16be format.

  


• Pass ID3D11Texture2D back buffer to libx264 encoder

  17 janvier 2019, par Chris Sixsmith

  I’m writing a C++ program to encode frames from a DirectX game to the H.264/MPEG-4 AVC format. I am using libx264 alone with no other dependencies at the moment.

  I have a ID3D11Texture2D* resolved back buffer of the next game frame. I need to somehow copy this into the x264_picture input (apparently YUV420P format according to limited help I’ve found) but I cannot find any way to do so online.

  Here is my code at the moment :

  void Fx264VideoEncoder::Fx264VideoEncoderImpl::InitFrameInputBuffer(const FTexture2DRHIRef& BackBuffer, FFrame& Frame)
  
  {
  
      x264_picture_alloc(Frame.InputPicture, X264_CSP_I420, x264Parameters.i_width, x264Parameters.i_height);
  
  
  
      // We need to take the back buffer and convert it to an input format that libx264 can understand
  
      {
  
          ID3D11Texture2D* ResolvedBackBufferDX11 = (ID3D11Texture2D*)(GetD3D11TextureFromRHITexture(Frame.ResolvedBackBuffer)->GetResource());
  
          EPixelFormat PixelFormat = Frame.ResolvedBackBuffer->GetFormat();
  
  
  
          // ...?
  
      }
  
  }

• avcodec/rv34 : Don't needlessly copy VLC length and symbol arrays

  22 octobre 2020, par Andreas Rheinhardt

  avcodec/rv34 : Don't needlessly copy VLC length and symbol arrays
  Most of the VLCs used by RealVideo 3 and 4 obey three simple rules :
  
  Shorter codes are on the left of the tree, for each length, the symbols
  
  are ascending from left to right and the symbols either form a
  
  permutation of 1..size or 0..(size - 1). For the latter case, one just
  
  needs to store the length of each symbol and create the codes according
  
  to the other rules ; no explicit code or symbol array must be stored.
  
  The former case is also treated in much the same way by artificially
  
  assigning a length of zero to the symbol 0 ; when a length of zero was
  
  encountered, the element was ignored except that the symbol counter was
  
  still incremented. If the length was nonzero, the symbol would be
  
  assigned via the symbol counter and the length copied over into a new
  
  array.
  Yet this is unnecessary, as ff_init_vlc_sparse() follows exactly the
  
  same pattern : If a length of zero is encountered, the element is ignored
  
  and only the symbol counter incremented. So one can directly forward the
  
  length array and also need not create a symbol table oneself, because
  
  ff_init_vlc_sparse() will infer the same symbol table in this case.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  

  • [DH] libavcodec/rv34.c