After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 346527 - alsasrc get_range does not respect requested size
alsasrc get_range does not respect requested size
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
0.10.8
Other All
: Normal normal
: 0.10.9
Assigned To: Wim Taymans
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-04 09:41 UTC by Thomas Vander Stichele
Modified: 2006-07-06 16:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
sample app (251 bytes, text/x-python)
2006-07-04 09:41 UTC, Thomas Vander Stichele
  Details
updated example. (590 bytes, patch)
2006-07-06 16:01 UTC, Wim Taymans
reviewed Details | Review

Description Thomas Vander Stichele 2006-07-04 09:41:09 UTC
Please describe the problem:
alsasrc get_range does not respect requested size

Steps to reproduce:
1. run the python app attached
2. 
3. 


Actual results:
get a 7520 byte buffer

Expected results:
get a 100 byte buffer

Does this happen every time?


Other information:
Comment 1 Thomas Vander Stichele 2006-07-04 09:41:44 UTC
Created attachment 68340 [details]
sample app
Comment 2 Wim Taymans 2006-07-06 15:55:26 UTC
First part of solution. Will attach an updated example app.

        * gst-libs/gst/audio/gstbaseaudiosrc.c:
        (gst_base_audio_src_class_init), (gst_base_audio_src_init),
        (gst_base_audio_src_set_clock), (gst_base_audio_src_provide_clock),
        (gst_base_audio_src_get_time),
        (gst_base_audio_src_check_get_range), (gst_base_audio_src_create),
        (gst_base_audio_src_create_ringbuffer):
        Fix latency and buffer-time constants and properties ala basesink.
        Implement pull based scheduling. Fixes #346527.
        Set default blocksize in GstBaseSrc to 0, we default to pushing out
        one segment.
        Refuse slaving to another clock instead of silently not working.
        Only provide a clock when we are actually able to do so.
        Various small cleanups and compiler hints.
Comment 3 Wim Taymans 2006-07-06 16:01:08 UTC
Created attachment 68478 [details] [review]
updated example.

updated example, activating a pad in pull mode needs this sequence.