Bug 154942 - sound-juicer ignores gstreamer ogg vorbis encoding quality settings
sound-juicer ignores gstreamer ogg vorbis encoding quality settings
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: sound-juicer (Show other bugs)
4.0
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Colin Walters
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-14 18:13 EDT by Attila Balazs
Modified: 2012-06-20 12:16 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 12:16:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Attila Balazs 2005-04-14 18:13:55 EDT
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):
sound-juicer-0.5.14-2.EL

How reproducible:
Always

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
3.
  

Actual Results:  The quality setting remains unchanged

Expected Results:  The quality setting should change appropriatetly

Additional info:
Comment 1 Jiri Pallich 2012-06-20 12:16:35 EDT
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 https://access.redhat.com/support/policy/updates/errata/

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.