Recherche avancée

Sur d’autres sites (6513)

• ffmpeg/h265/opencv/c++ A method to resize frame after decoding on client side

  18 janvier 2018, par 8793

  I’ve just joined a project to build a realtime video streaming application using ffmpeg/opencv/c++ via udp socket. On server side, they want to transmit a video size (640x480) to client, in order to reduce data transmission through network I resize the video to (320x240) and send frame. On client side (client), after receiving frame, we will upscale the frame back to (640x480). Using H265 for encode/decoding.

  As I am just a beginner with video encoding, I would like to understand how to down-sampling & up-sampling the frame at server & client side in which we can incorporate with the video encoder/decoder.

  A simple idea came into my mind that after decoding avframe -> Mat frame, I will upsampling this frame then display it.

  I am not sure my idea is right or wrong. I would like to seek advice from any people who had experience in this area. Thank you very much !

  static void updateFrameCallback(AVFrame *avframe, void* userdata) {
  
      VideoStreamUDPClient* streamer = static_cast (userdata);
  
      TinyClient* client = static_cast (streamer->userdata);
  
  
  
      //Update Frame
  
      pthread_mutex_lock(&client->mtx_updateFrame);
  
      if (streamer->irect.width == client->frameSize.width
  
              && streamer->irect.height == client->frameSize.height) {
  
          cvtAVFrameYUV4202Frame(&avframe, client->frame);
  
          printf("TinyClient: Received Full Frame\n");
  
      } else {
  
          Mat block;
  
          cvtAVFrameYUV4202Frame(&avframe, block);
  
          block.copyTo(client->frame(streamer->irect));
  
      }
  
  
  
      //How to resize frame before display it!!!
  
  
  
      imshow("Frame", client->frame);
  
      waitKey(1);
  
      pthread_mutex_unlock(&client->mtx_updateFrame);
  
  }

• libavutil/hwcontext_qsv : clean padding when upload qsv frames

  23 décembre 2021, par Wenbin Chen

  libavutil/hwcontext_qsv : clean padding when upload qsv frames
  Fix #7830
  
  When we upload a frame that is not padded as MSDK requires, we create a
  
  new AVFrame to copy data. The frame's padding data is uninitialized so
  
  it brings run to run problem. For example, If we run the following
  
  command serveral times we will get different outputs.
  ffmpeg -init_hw_device qsv=qsv:hw -qsv_device /dev/dri/renderD128 \
  
   filter_hw_device qsv -f rawvideo -s 192x200 -pix_fmt p010 \
  
   i 192x200_P010.yuv -vf "format=nv12,hwupload=extra_hw_frames=16" \
  
   c:v hevc_qsv output.265
  According to https://github.com/Intel-Media-SDK/MediaSDK/blob/master/doc/mediasdk-man.md#encoding-procedures
  
  "Note : It is the application's responsibility to fill pixels outside
  
  of crop window when it is smaller than frame to be encoded. Especially
  
  in cases when crops are not aligned to minimum coding block size (16
  
  for AVC, 8 for HEVC and VP9)"
  I add a function to fill padding area with border pixel to fix this
  
  run2run problem, and also move the new AVFrame to global structure
  
  to reduce redundant allocation operation to increase preformance.
  Signed-off-by : Wenbin Chen <wenbin.chen@intel.com>
  
  Signed-off-by : Haihao Xiang <haihao.xiang@intel.com>
  

  • [DH] libavutil/hwcontext_qsv.c

• ffmpeg - ffmpeg aws lamnda function error

  30 novembre 2018, par Pramod Gehlot

  I am getting error

  Execution result : failed(logs)
  Details

  The area below shows the result returned by your function execution. Learn more about returning results from your function.

  {
  
    "errorMessage": "RequestId: eb7906af-f46d-11e8-ae3b-45487c02a68e Process exited before completing request"
  
  }

  Summary

  Code SHA-256
  
  ca50xloHl4xLOSWox2xidHxC1VHyNqwq3kECKraw7/c=
  
  Request ID
  
  eb7906af-f46d-11e8-ae3b-45487c02a68e
  
  Duration
  
  38.73 ms
  
  Billed duration
  
  100 ms
  
  Resources configured
  
  128 MB
  
  Max memory used
  
  19 MB

  Log output

  The section below shows the logging calls in your code. These correspond to a single row within the CloudWatch log group corresponding to this Lambda function. Click here to view the CloudWatch log group.

  START RequestId: eb7906af-f46d-11e8-ae3b-45487c02a68e Version: $LATEST
  
  2018-11-30T07:02:38.509Z    eb7906af-f46d-11e8-ae3b-45487c02a68e    TypeError: Cannot create property 'stack' on string 'Could not find ffmpeg executable, tried "/var/task/node_modules/@ffmpeg-installer/linux-x64/ffmpeg" and "/var/task/node_modules/@ffmpeg-installer/ffmpeg/node_modules/@ffmpeg-installer/linux-x64/ffmpeg"'
  
  
  
  END RequestId: eb7906af-f46d-11e8-ae3b-45487c02a68e
  
  REPORT RequestId: eb7906af-f46d-11e8-ae3b-45487c02a68e  Duration: 38.73 ms  Billed Duration: 100 ms     Memory Size: 128 MB Max Memory Used: 19 MB  
  
  RequestId: eb7906af-f46d-11e8-ae3b-45487c02a68e Process exited before completing request