Bug 63978 - seek does not work in a reliable way
Summary: seek does not work in a reliable way
Status: NEW
Alias: None
Product: GStreamer SDK
Classification: Unclassified
Component: Android SDK distribution (show other bugs)
Version: 2012.11
Hardware: Other All
: medium normal
Assignee: bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-26 21:43 UTC by Nicola
Modified: 2013-04-27 13:58 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Nicola 2013-04-26 21:43:10 UTC
please copy this file on an android device:

http://195.250.34.59/temp/2013_04_12_17_22_11-h264,mulaw.mkv

modify android tutorial 5 changing the media uri to:

file:///<path>/2013_04_12_17_22_11-h264,mulaw.mkv

and try to seek using the slider, often you'll hear the audio but the video will be frozen, if instead you change the state to pause before seek will work better,

if you play the file over http the seek work as expected,

any ideas? something in filesrc specific to android?
Comment 1 Nicola 2013-04-27 12:11:02 UTC
tested using gstreamer-1.0-sdk-android-arm-2013.04 too, similar results, since 1.0 actually does not ship ffmpeg I'm using amc for video decoding on a device with android 4.1 (I need ffmpeg for older android versions) and I can see errors like these:

gstamc.c:702:gst_amc_codec_dequeue_output_buffer Failed to call Java method
gststreamsynchronizer:c:357:gst_stream_synchronizer_sink_event:<streamsynchronizer0:sink2> Non-TIME segment: bytes

using ffmpeg for decoding (with 0.10 sdk) give similar seek issues
Comment 2 Nicola 2013-04-27 13:58:58 UTC
using 2012.11 debug variant I see this warnings:

W/GStreamer+ebmlread( 3412): 0:01:07.453766000 0x5f98f2f0 ebml-read.c:140:gst_ebml_peek_id_length:<demux> peek failed, ret = -2

W/GStreamer+matroskademux( 3412): 0:01:07.453919000 0x5f98f2f0 matroska-demux.c:3990:gst_matroska_demux_check_parse_error:<demux> parse error, looking for next cluster


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.