Sorry posted wrong logcat fragment in my last update.
During playback I keep getting messages like these below, though no image
is shown:
...
V/ACodec ( 75): [OMX.ffmpeg.h264.decoder] calling emptyBuffer 0x2a06c4f0
w/ time 53232200 us
V/ACodec ( 75): [OMX.google.aac.decoder] onOMXFillBuffe
MX.google.aac.decoder] calling fillBuffer 0x2a06a998
V/ACodec ( 75): [OMX.google.aac.decoder] onOMXEmptyBufferDone 0x2a0df9c0
V/ACodec ( 75): [OMX.google.aac.decoder] calling emptyBuffer 0x2a0df9c0
w/ time 92877 us
...
Could something still be missing in ACodec?
Thanks once again in advan
Btw - testing downloaded files (as suggested in
https://github.com/omxcodec/stagefright-plugins), playback is fine, at east
with respect to image quality. Similar for both the test .mov and .mp4
files.
Playback hangs and locks once in a while, for a few seconds, with logcat
showing lots of:
second example attachement *20141106_163805.jpg *was missing ...
On Sunday, 11 August 2013 10:25:25 UTC+2, Chih-Wei Huang wrote:
>
> Hello ffmpeg list,
> I'm planning to integrate the latest ffmpeg as
> a stagefright OMXPlugin with Android-x86 4.3.
> I found the stagefright-plugins developed by
Hi Chih,
I've completed the merge of frameworks/av and framewroks/native and added
the stagefright-plugins and ffmpeg to my project. I enabld the USES_NAM and
built new system.
Startup wnet fine, but on YouTube test playback (which went just fine
before), I get a crash (below).
Note how I hav
/system/lib/libstagefright.so
(android::AwesomePlayer::~AwesomePlayer()+288)
On Thursday, 30 October 2014 03:09:35 UTC-7, Fabio Fumi wrote:
>
> Hi Chih,
>
> I've completed the merge of frameworks/av and framewroks/native and added
> the stagefright-plugins and ffmpeg to my proj
M, Michael Chen wrote:
> Hi,
> Oh, NO, it is easy that Compatible with older Android versions， like
> 4.1.2 or 4.0.4 AOSP
>
> On Mon, Oct 13, 2014 at 6:24 PM, Fabio Fumi
> wrote:
>
>> Hi,
>>
>> I'd like to ask for your generic advice in back
Hi,
I'd like to ask for your generic advice in back-porting your work to my
build, which is a slightly customized 4.1.2 AOSP (found here:
https://github.com/Renesas-EMEV2).
I think the pieces are all there already, but I'm wondering whether there's
something preventing that, or making it too c
