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 142493 - default fragment size in osssink is too small
default fragment size in osssink is too small
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins
0.8.1
Other Linux
: Normal normal
: 0.8.2
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-05-13 20:18 UTC by David Moore
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4



Description David Moore 2004-05-13 20:18:30 UTC
The default value of the "fragment" parameter in osssink is 6.  This means that
the fragment size is 2^6 = 64.  On two of my machines, whenever there is a
moderate amount of I/O activity, osssink produces lots of static in addition to
the proper output.  Changing the "fragment" value to 8 (a fragment size of 256
bytes) solves the problem.

According to the 4front documentation for OSS at
http://www.4front-tech.com/pguide/audio2.html:

"With relatively short fragments this may cause whining sound which is very
difficult to identify. Using fragment sizes shorter than 256 bytes is not
recommended as the default mode of application. Short fragments should only be
used when explicitly requested by user."

So I would suggest changing the default value of "fragment" from 6 to 8.
Comment 1 Benjamin Otte (Company) 2004-05-17 17:33:36 UTC
I changed osssink to not set fragment size anymore by default. THis should fix
your issue. If it doesn't, please reopen.
Comment 2 David Moore 2004-05-17 19:45:50 UTC
Yes, your fix solves my issue.  You didn't really intend to leave that g_print()
in your checkin though did you?
Comment 3 Thomas Vander Stichele 2004-05-22 22:37:36 UTC
no more g_print's in cvs