Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 154942 - sound-juicer ignores gstreamer ogg vorbis encoding quality settings
Summary: sound-juicer ignores gstreamer ogg vorbis encoding quality settings
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: sound-juicer
Version: 4.0
Hardware: i686
OS: Linux
Target Milestone: ---
: ---
Assignee: Colin Walters
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-04-14 22:13 UTC by Attila Balazs
Modified: 2012-06-20 16:16 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-06-20 16:16:35 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Attila Balazs 2005-04-14 22:13:55 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050322 Firefox/1.0.2 Red Hat/1.0.2-1.4.1

Description of problem:
The in my opinion the quality float value in the system/streamer/audio/profiles/cdlossy pipeline string should have effect on the encoding settings of sound-juicer however according my tests it entirely ignores this string. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Change the quality value in gconf or in the xml file (between 0-1)
2. Try to encode with new qulity setting

Actual Results:  The quality setting remains unchanged

Expected Results:  The quality setting should change appropriatetly

Additional info:

Comment 1 Jiri Pallich 2012-06-20 16:16:35 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

Note You need to log in before you can comment on or make changes to this bug.