Android 6.0 gstreamer 1.0: frame is not writable

Sebastian Dröge sebastian at centricular.com
Tue Dec 1 00:35:40 PST 2015


On Do, 2015-11-26 at 11:11 -0800, Gregoire Gentil wrote:
> 
> On 11/25/2015 11:41 PM, Gregoire Gentil wrote:
> > 
> > 
> > On 11/25/2015 07:43 PM, Sebastian Dröge wrote:
> > > On Mi, 2015-11-25 at 12:40 -0800, Gregoire Gentil wrote:
> > > > Hello,
> > > > 
> > > > Do understand that the same code is working on Nexus 7 2013
> > > > running
> > > > Android 5.1.1.
> > > > 
> > > > To answer precisely your question, I do:
> > > > 
> > > > playbin uri=... video-sink="... ! glimagesink"
> > > > 
> > > > video_sink = gst_bin_get_by_interface(GST_BIN(bin),
> > > > GST_TYPE_VIDEO_OVERLAY);
> > > > GstPad *pad = gst_element_get_static_pad(video_sink, "sink");
> > > > gst_pad_add_probe(pad, GST_PAD_PROBE_TYPE_BUFFER,
> > > > (GstPadProbeCallback)cb, NULL, NULL);
> > > 
> > > You need to provide some more details about your pipeline here,
> > > what
> > > are those dots exactly and what kind of media file are you
> > > playing?
> > > 
> > > Did you also check that the same decoder (or at least another
> > > amcvideodec-* decoder) is used in both cases? Which version of
> > > GStreamer are you using, 1.6.1 or something else?
> > On Android 6.0, it seems to be working with 1.6.1 + ndk-r10e (not
> > r9
> > which prevents from compiling) but then the performance becomes
> > catastrophic on Android 5.1.1,
> > 
> > Grégoire
> > 
> For the records, the problem is that on Android 6.0, the system was 
> using software decoding and the buffer going out of the decoder are
> not writable while on Android 5.1.1, the system was using hardware
> decoding and the buffer is writable. The problem boils down to make
> work hardware decoding on Android 6.0 which works with Gstreamer
> latest 1.6.1 while it's not with 1.5.0. But 1.6.1 on Android 5.1.1
> has catastrophic performance...

Can you provide a clear list of observations? Which versions of
GStreamer and the NDK are working on which Android version, and which
codecs are being used then?
Also what are the devices you're testing on?

Once you did that, it might make sense to file a bug at
  https://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer
but let's wait with that until we have a better overview of what goes
wrong.

Also debug logs with "2,amc*:6" would be good to have for all the
cases.

-- 
Sebastian Dröge, Centricular Ltd · http://www.centricular.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20151201/cca741bb/attachment.sig>


More information about the gstreamer-devel mailing list