存储在缓存失败的元数据，不知道颜色格式 [英] store meta data in buffer failed and do not know color format

查看：1087
本文介绍了存储在缓存失败的元数据，不知道颜色格式的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

我收到以下错误

02-13 15:22:23.807: E/ACodec(8137): [OMX.qcom.video.decoder.avc] storeMetaDataInBuffers failed w/ err -2147483648
02-13 15:22:23.808: W/ACodec(8137): do not know color format 0x7fa30c03 = 2141391875 .

在实施
http://bigflake.com/media$c$cc/ExtractMpegFramesTest_egl14.java.txt 结果
完整的日志：

in implementing http://bigflake.com/mediacodec/ExtractMpegFramesTest_egl14.java.txt
complete log : 

02-13 16:51:14.275: D/ExtractMpegFramesTest(11294):testExtractMpegFrames
02-13 16:51:14.337: D/ExtractMpegFramesTest(11294): Extractor selected track 0 (video/avc): {height=640, width=640, csd-1=java.nio.ByteArrayBuffer[position=0,limit=8,capacity=8], max-input-size=97334, mime=video/avc, durationUs=13940988, csd-0=java.nio.ByteArrayBuffer[position=0,limit=17,capacity=17]}
02-13 16:51:14.338: D/ExtractMpegFramesTest(11294): Video size is 640x640
02-13 16:51:14.339: I/Adreno-EGL(11294): <qeglDrvAPI_eglInitialize:410>: QUALCOMM Build: 10/28/14, c33033c, Ia6306ec328
02-13 16:51:14.370: D/ExtractMpegFramesTest(11294): textureID=1
02-13 16:51:14.375: I/OMXClient(11294): Using client-side OMX mux.
02-13 16:51:14.405: E/ACodec(11294): [OMX.qcom.video.decoder.avc] storeMetaDataInBuffers failed w/ err -2147483648
02-13 16:51:14.407: W/ACodec(11294): do not know color format 0x7fa30c03 = 2141391875
02-13 16:51:14.471: D/ExtractMpegFramesTest(11294): loop
02-13 16:51:14.482: D/ExtractMpegFramesTest(11294): input buffer not available
02-13 16:51:14.492: D/ExtractMpegFramesTest(11294): no output from decoder available
02-13 16:51:14.492: D/ExtractMpegFramesTest(11294): loop
02-13 16:51:14.503: D/ExtractMpegFramesTest(11294): input buffer not available
02-13 16:51:14.513: D/ExtractMpegFramesTest(11294): no output from decoder available
02-13 16:51:14.513: D/ExtractMpegFramesTest(11294): loop
02-13 16:51:14.524: D/ExtractMpegFramesTest(11294): input buffer not available
02-13 16:51:14.534: D/ExtractMpegFramesTest(11294): no output from decoder available
02-13 16:51:14.534: D/ExtractMpegFramesTest(11294): loop
02-13 16:51:14.544: D/ExtractMpegFramesTest(11294): input buffer not available
02-13 16:51:14.555: D/ExtractMpegFramesTest(11294): no output from decoder available
02-13 16:51:14.555: D/ExtractMpegFramesTest(11294): loop
02-13 16:51:14.566: D/ExtractMpegFramesTest(11294): input buffer not available
02-13 16:51:14.576: D/ExtractMpegFramesTest(11294): no output from decoder available
02-13 16:51:14.576: D/ExtractMpegFramesTest(11294): loop
02-13 16:51:14.586: D/ExtractMpegFramesTest(11294): input buffer not available
02-13 16:51:14.597: D/ExtractMpegFramesTest(11294): no output from decoder available
02-13 16:51:14.597: D/ExtractMpegFramesTest(11294): loop
02-13 16:51:14.607: D/ExtractMpegFramesTest(11294): input buffer not available
02-13 16:51:14.617: D/ExtractMpegFramesTest(11294): no output from decoder available
02-13 16:51:14.617: D/ExtractMpegFramesTest(11294): loop
02-13 16:51:14.620: D/ExtractMpegFramesTest(11294): submitted frame 0 to dec, size=25
02-13 16:51:14.630: D/ExtractMpegFramesTest(11294): no output from decoder available
02-13 16:51:14.630: D/ExtractMpegFramesTest(11294): loop
02-13 16:51:14.632: D/ExtractMpegFramesTest(11294): submitted frame 1 to dec, size=4605
02-13 16:51:14.642: D/ExtractMpegFramesTest(11294): no output from decoder available
02-13 16:51:14.642: D/ExtractMpegFramesTest(11294): loop
02-13 16:51:14.643: D/ExtractMpegFramesTest(11294): submitted frame 2 to dec, size=2771
02-13 16:51:14.654: D/ExtractMpegFramesTest(11294): no output from decoder available
02-13 16:51:14.654: D/ExtractMpegFramesTest(11294): loop
02-13 16:51:14.655: D/ExtractMpegFramesTest(11294): submitted frame 3 to dec, size=4670
02-13 16:51:14.665: D/ExtractMpegFramesTest(11294): no output from decoder available
02-13 16:51:14.666: D/ExtractMpegFramesTest(11294): loop
02-13 16:51:14.666: D/ExtractMpegFramesTest(11294): submitted frame 4 to dec, size=8319
02-13 16:51:14.677: D/ExtractMpegFramesTest(11294): no output from decoder available
02-13 16:51:14.677: D/ExtractMpegFramesTest(11294): loop
02-13 16:51:14.677: D/ExtractMpegFramesTest(11294): submitted frame 5 to dec, size=12703
02-13 16:51:14.689: D/ExtractMpegFramesTest(11294): no output from decoder available
02-13 16:51:14.689: D/ExtractMpegFramesTest(11294): loop
02-13 16:51:14.702: D/ExtractMpegFramesTest(11294): input buffer not available
02-13 16:51:14.714: D/ExtractMpegFramesTest(11294): no output from decoder available
02-13 16:51:14.714: D/ExtractMpegFramesTest(11294): loop
02-13 16:51:14.731: D/ExtractMpegFramesTest(11294): input buffer not available
02-13 16:51:14.732: D/ExtractMpegFramesTest(11294): decoder output buffers changed
02-13 16:51:14.732: D/ExtractMpegFramesTest(11294): loop
02-13 16:51:14.734: D/ExtractMpegFramesTest(11294): submitted frame 6 to dec, size=18290
02-13 16:51:14.742: W/ACodec(11294): do not know color format 0x7fa30c03 = 2141391875
02-13 16:51:14.745: D/ExtractMpegFramesTest(11294): decoder output format changed: {mime=video/raw, crop-top=0, crop-right=639, slice-height=640, color-format=2141391875, height=640, width=640, what=1869968451, crop-bottom=639, crop-left=0, stride=640}
02-13 16:51:14.745: D/ExtractMpegFramesTest(11294): loop
02-13 16:51:14.748: D/ExtractMpegFramesTest(11294): submitted frame 7 to dec, size=13304
02-13 16:51:14.753: D/ExtractMpegFramesTest(11294): surface decoder given buffer 0 (size=614400)
02-13 16:51:14.753: D/ExtractMpegFramesTest(11294): awaiting decode of frame 0
02-13 16:51:17.256: D/Gulshan(11294): java.lang.RuntimeException: frame wait timed out
02-13 16:51:17.256: W/System.err(11294): java.lang.RuntimeException: frame wait timed out
02-13 16:51:17.257: W/System.err(11294):    at com.example.cameratomp4.ExtractMpegFramesTest$CodecOutputSurface.awaitNewImage(ExtractMpegFramesTest.java:491)
02-13 16:51:17.257: W/System.err(11294):    at com.example.cameratomp4.ExtractMpegFramesTest.doExtract(ExtractMpegFramesTest.java:282)
02-13 16:51:17.258: W/System.err(11294):    at com.example.cameratomp4.ExtractMpegFramesTest.extractMpegFrames(ExtractMpegFramesTest.java:160)
02-13 16:51:17.258: W/System.err(11294):    at com.example.cameratomp4.ExtractMpegFramesTest.access$0(ExtractMpegFramesTest.java:120)
02-13 16:51:17.258: W/System.err(11294):    at com.example.cameratomp4.ExtractMpegFramesTest$ExtractMpegFramesWrapper.run(ExtractMpegFramesTest.java:94)
02-13 16:51:17.258: W/System.err(11294):    at java.lang.Thread.run(Thread.java:818)
02-13 16:51:17.305: D/OpenGLRenderer(11294): Render dirty regions requested: true
02-13 16:51:17.320: D/Atlas(11294): Validating map...
02-13 16:51:17.328: D/ExtractMpegFramesTest(11294): new frame available
02-13 16:51:17.357: I/OpenGLRenderer(11294): Initialized EGL, version 1.4
02-13 16:51:17.361: D/OpenGLRenderer(11294): Enabling debug mode 0
02-13 16:52:35.984: E/BufferQueueProducer(11294): [unnamed-11294-0] cancelBuffer: BufferQueue has been abandoned
02-13 16:52:35.988: E/BufferQueueProducer(11294): [unnamed-11294-0] cancelBuffer: BufferQueue has been abandoned
02-13 16:52:35.988: E/BufferQueueProducer(11294): [unnamed-11294-0] cancelBuffer: BufferQueue has been abandoned

我认为有一些问题与媒体格式。
我尝试添加一些色彩格式mediaformat但没有解决的问题，为什么storeMetaDatainBuffer失败？

I think there is some issue with media format. I tried to add some color format to mediaformat but nothing solved problem why storeMetaDatainBuffer fails ?

推荐答案

关于颜色格式的消息从 describeDefaultColorFormat未来（）在<一个href=\"https://android.googlesource.com/platform/frameworks/av/+/lollipop-release/media/libstagefright/A$c$cc.cpp\"相对=nofollow>一个codec.cpp 。 0x7fa30c03是高通专有的 OMX_QCOM_COLOR_FormatYUV420PackedSemiPlanar64x32Tile2m8ka ，所以我相信这条消息的预期，而只是一个警告。

The message about the color format is coming from describeDefaultColorFormat() in ACodec.cpp . 0x7fa30c03 is the Qualcomm-proprietary OMX_QCOM_COLOR_FormatYUV420PackedSemiPlanar64x32Tile2m8ka, so I believe this message is expected, and is just a warning.

您日志显示您的应用程序开始处理数据，然后摊位并抛出一个异常时，超时。这很可能是由于与线程被设置方式的一个问题;特别是，如果你有ExtractMpegFramesWrapper做的时候，你将有这个问题。有一个计算器Q＆放大器;从bigflake页的ExtractMpegFramesTest部分（<一个链接的href=\"http://stackoverflow.com/questions/22457623/surfacetextures-onframeavailable-method-always-called-too-late\">to这），提供一些背景知识。

Your log shows that your app begins processing data, then stalls and throws an exception when it times out. This is most likely due to an issue with the way the threading was set up; in particular, if you did away with ExtractMpegFramesWrapper, you're going to have this problem. There's a stackoverflow Q&A linked from the ExtractMpegFramesTest section of the bigflake page (to this) that provides some background.

的 storeMetaDataInBuffers 投诉也是无害的警告;这是在 Q12 注意到bigflake。

The storeMetaDataInBuffers complaint is also a harmless warning; this is noted in Q12 on bigflake.

这篇关于存储在缓存失败的元数据，不知道颜色格式的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！

查看全文
相关文章
移动开发最新文章
热门教程
热门工具
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆