Bug 460751

Summary: Editing output format profiles don't work as expected
Product: [Fedora] Fedora Reporter: Stewart Williams <stewart>
Component: sound-juicerAssignee: Bastien Nocera <bnocera>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-05 21:14:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Stewart Williams 2008-08-30 22:50:11 UTC
Description of problem:

When creating a new profile in "Edit GNOME Audio Profiles" and closing the dialogue, the new profile is not available for selection in sound-juicer's preference dialogue (Output Format).

Also if I edit the GStreamer pipeline string in a profile it has no effect when Extracting the audio from CD - it ignores the change completely.

What I wanted to do, was Edit the "CD Quality, MP3 (MP3 Audio) profile and change the lame command line to be able to get a higher bitrate, as sound-juicer defaults to 128. 

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


How reproducible:

Every time

Steps to Reproduce:
1. Open sound-juicer, click Edit -> Preferences
2. Click Edit Profiles and create a new profile or edit one (if creating a new one, click Active? check box)
3. Click close and select drop down box under Output Format. New profile is not avaible
Actual results:

Cannot select newly created profile and edit's have not effect

Expected results:

New profile should be selectable and edit's should have desired effect
Additional info:

Comment 1 Stewart Williams 2008-09-05 21:14:34 UTC
I've solved it. If you make an error in the GStreamer Pipeline then the profile doesn't show up in the combo box.

I found this out by launching from a terminal which gives the error.