Recherche avancée

Sur d’autres sites (6263)

• avcodec/mediacodecdec : restructure mediacodec_receive_frame

  24 avril 2018, par Aman Gupta

  avcodec/mediacodecdec : restructure mediacodec_receive_frame
  The new logic follows a recommendation by @rcombs to use
  
  dequeueInputBuffer with a timeout of 0 as a way to detect
  
  whether the codec wants more data. The dequeued buffer index is
  
  kept in MediaCodecDecContext until it can be used next.
  A similar technique is also used by the Google's official media
  
  player Exoplayer : see MediaCodecRenderer.feedInputBuffer().
  Signed-off-by : Aman Gupta <aman@tmm1.net>
  
  Signed-off-by : Matthieu Bouron <matthieu.bouron@gmail.com>
  

  • [DH] libavcodec/mediacodecdec.c
  • [DH] libavcodec/mediacodecdec_common.c
  • [DH] libavcodec/mediacodecdec_common.h

• lavu/opencl : replace va_ext.h with standard name

  23 novembre 2018, par Ruiling Song

  lavu/opencl : replace va_ext.h with standard name
  Khronos OpenCL header (https://github.com/KhronosGroup/OpenCL-Headers)
  
  uses cl_va_api_media_sharing_intel.h. And Intel's official OpenCL driver
  
  for Intel GPU (https://github.com/intel/compute-runtime) was compiled
  
  against Khronos OpenCL header. So it's better to align with Khronos.
  Signed-off-by : Ruiling Song <ruiling.song@intel.com>
  

  • [DH] configure
  • [DH] libavutil/hwcontext_opencl.c

• How to pack the pyav.packet and distribute to another computer

  31 juillet 2024, par lambertk

  I'm currently working on projects which needs to read frames from RTSP server on single entry of computer, do some preprocessing and distribute these frames with preprocessed metadata to different backend for different purpose.

  


  And after googling, I found that PyAV could be the solution which can retrieve the video from RTSP source and make it packets, which could possibly be sent to another computer.

  


  Considering the network bandwidth, transmit the packets instead of the decoded frames could be better choice.

  


  But now comes the problem, socket/MQ, usually only allows to send bytes or string.
  
Encode the PyAV.packet.Packet object into byte is easy by bytes(packet), but I couldn't find out the way to decode it back to PyAV.packet.Packet object.

  


  I've tried to use pickle to serialize the packet, but this method is not implemented in PyAV, and was rejected by the official team.

  


  I've also tried to use another package called msgpack, which also failed to serialize the packet.

  


  I've tried the following code after reading the source code of PyAV

  


  packet_bytes = bytes(packet)
pt = av.packet.Packet(len(packet_bytes))
pt.update(packet_bytes)


  


  the update function seems did not update anything

  


  Is there anyway to decode the bytes back to packet object ?

  


  Or, can someone give out a way to encode the frame packet and the preprocessed metadata (which is differ frame by frame) together (like H264 SEI Message, which I tried, but could not be inserted when using Python) then send to backend ?