Recherche avancée

Sur d’autres sites (12437)

• Android Exoplayer garbled mp4 video output on imagereader surface while playing fine on SurfaceView (Samsung galaxy tab s7)

  29 mars 2023, par Orcun

  Problem :

  


  I am trying to play an mp4 video file on Samsung Galaxy Tab S7 for video processing purposes. For the purpose, I use Exoplayer(v2.18.4) library to be able to play the video onto an ImageReader surface so that I can grab the frames in ImageReader.OnImageAvailableListener.

  


  I do not have any problems in getting the frames. However, the frames I acquire are garbled/corrupted like :

  


  

  


  When I saw this frame, it made me think that it is some sort of color format or codec issue for the mp4 file or device I use. In logcat, there are no errors reported.
Device uses [OMX.qcom.video.decoder.avc] decoder. Also, same video plays nicely on some other devices that use exactly the same decoder.

  


  What I tried so far :

  


  I tried a lot of things to understand the root cause and also find a solution, so my brain currently is free flowing stream. I will try to summarise, please bear with me.

  


  I use a CustomMediaCodecVideoRenderer in my app which overrides MediaCodecVideoRenderer.getMediaFormat of Exoplayer to set color format like :

  


  setInteger(MediaFormat.KEY_COLOR_FORMAT, MediaCodecInfo.CodecCapabilities.COLOR_FormatYUV420Flexible)


  


  This step proved itself necessary. Without it I get a crash simply because I cannot access the image planes of an image frame in expected YUV image format.
This unfortunately was not enough for the Samsung Galaxy Tab 7 although it was already enough for another device like Xiaomi to render the image correctly.

  


  Then I decided to use a library like ffmpeg to modify the mp4 file itself to maybe use a different profile, color format, resolution that is widely compatible in android devices. No luck so far.
a quick ffprobe on my mp4 file shows :

  


  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'outputyuv169.mp4':
Metadata:
  major_brand     : isom
  minor_version   : 512
  compatible_brands: isomiso2avc1mp41
  encoder         : Lavf59.16.100
Duration: 00:03:00.02, start: 0.000000, bitrate: 4823 kb/s
Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(progressive), 
1280x720 [SAR 1:1 DAR 16:9], 4820 kb/s, 30 fps, 30 tbr, 360k tbn (default)


  


  I tried even recording a simple video on the tablet itself and using that as my input file. Nevertheless, still getting similarly garbled frames.

  


  One thing I keep noticing in logcat is this line :

  


  [OMX.qcom.video.decoder.avc] using color format 0x7fa30c04 in place of 0x7f420888

  


  and

  


  [OMX.qcom.video.decoder.avc] Requested output format 0x7f420888 and got 0x7fa30c04

  


  where 0x7fa30c04 refers to YCbCr_420_SP_VENUS_UBWC. Not really sure If this has anything to do with it. I did not dive too deep into that because same log is present also on other device that renders the mp4 correctly.

  


  I would be grateful for any clue.

  


• vaapi_h264 : Add trivial support for low-power encoding

  18 mai 2016, par Mark Thompson

  vaapi_h264 : Add trivial support for low-power encoding
  Experimental ; requires Skylake and VAAPI 0.39.1 (not yet released).
  
  Also increases the allowed range of the quality option - in low-power
  
  mode, the Intel driver supports levels 1-8 (and 0 meaning default).
  

  • [DBH] libavcodec/vaapi_encode_h264.c

• avcodec/prores_ks : use official quant_matrix (for proxy and xq codec luma and chroma...

  13 avril 2018, par Martin Vignali

  avcodec/prores_ks : use official quant_matrix (for proxy and xq codec luma and chroma quant matrix is not the same)
  disable the use of the official luma xq matrix for now (output
  
  appear to be desaturate)
  

  • [DH] libavcodec/proresenc_kostya.c