[gstreamer-bugs] [Bug 520300] New: [alsasrc] provide-clock=false messes up buffer durations
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Tue Mar 4 06:40:02 PST 2008
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=520300
GStreamer | gst-plugins-base | Ver: HEAD CVS
Summary: [alsasrc] provide-clock=false messes up buffer durations
Product: GStreamer
Version: HEAD CVS
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: gst-plugins-base
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: mail at renestadler.de
QAContact: gstreamer-bugs at lists.sourceforge.net
GNOME version: Unspecified
GNOME milestone: Unspecified
This outputs some funny buffer durations:
gst-launch-0.10 -v alsasrc provide-clock=false ! fakesink
...
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:00.018047808, duration: 0:00:00.00326738
4, offset: 0, offset_end: 940, flags: 32) 0x8197a80"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:00.039414808, duration: 0:00:00.00321557
7, offset: 940, offset_end: 1880, flags: 0) 0x8197ad0"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:00.060690808, duration: 0:00:00.00325477
0, offset: 1880, offset_end: 2820, flags: 0) 0x8197b20"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:00.082106808, duration: 0:00:00.00315396
2, offset: 2820, offset_end: 3760, flags: 0) 0x8197b70"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:00.124777808, duration: 5124095:34:33.69
1349771, offset: 3760, offset_end: 4700, flags: 0) 0x819e820"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:00.124881808, duration: 0:00:00.00300934
8, offset: 4700, offset_end: 5640, flags: 0) 0x819e870"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:00.167540808, duration: 5124095:34:33.69
1217157, offset: 5640, offset_end: 6580, flags: 0) 0x819e8c0"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:00.167631808, duration: 0:00:00.00288973
3, offset: 6580, offset_end: 7520, flags: 0) 0x819e910"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:00.210081808, duration: 5124095:34:33.69
1306542, offset: 7520, offset_end: 8460, flags: 0) 0x819e960"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:00.210163808, duration: 0:00:00.00298811
9, offset: 8460, offset_end: 9400, flags: 0) 0x819e9b0"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:00.231378808, duration: 0:00:00.00308831
2, offset: 9400, offset_end: 10340, flags: 0) 0x819ea00"
Broken duration values like 5124095:34:33.69 keep popping up. Also, the
duration seems to decrease over time. When they reach almost 0, only values
very close to 5124095:34:33.688102923 and 5124095:34:33.709365730 appear:
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:03.580915808, duration: 5124095:34:33.688272996, offset:
156040, offset_end: 156980, flags: 0) 0x819eb40"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:03.581023808, duration: 5124095:34:33.709480188, offset:
156980, offset_end: 157920, flags: 0) 0x819eb90"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:03.623544808, duration: 5124095:34:33.688274381, offset:
157920, offset_end: 158860, flags: 0) 0x819ec00"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:03.623646808, duration: 5124095:34:33.709487574, offset:
158860, offset_end: 159800, flags: 0) 0x819ec50"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:03.666242808, duration: 5124095:34:33.688206767, offset:
159800, offset_end: 160740, flags: 0) 0x819eca0"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:03.666396808, duration: 5124095:34:33.709367959, offset:
160740, offset_end: 161680, flags: 0) 0x819ecf0"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:03.708885808, duration: 5124095:34:33.688194152, offset:
161680, offset_end: 162620, flags: 0) 0x819eca0"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:03.709002808, duration: 5124095:34:33.709392345, offset:
162620, offset_end: 163560, flags: 0) 0x819ec50"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:03.751543808, duration: 5124095:34:33.688166538, offset:
163560, offset_end: 164500, flags: 0) 0x819ec00"
/pipeline0/fakesink0: last-message = "chain ******* < ( 7520 bytes,
timestamp: 0:00:03.751659808, duration: 5124095:34:33.709365730, offset:
164500, offset_end: 165440, flags: 0) 0x819eb90"
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=520300.
More information about the Gstreamer-bugs
mailing list