GNOME Bugzilla – Bug 527974
Cannot Create or Use New Profiles
Last modified: 2008-04-21 04:01:07 UTC
Please describe the problem: When I try to make a new profile for "preferred format" in rhythmbox (or "output format" in sound-juicer), it does not allow me to select it as the preferred format, even if I check the "active" box. I reinstalled the gstreamer plugins, which re-created the original (FLAC, ogg, speex, WAV) profiles, but nothing re-creates the MP3 profiles. If I make them myself, either through sound-juicer or using a script like [url=http://ubuntuforums.org/showpost.php?p=2009576&postcount=2]this one[/url], they are never recognized in sound-juicer, even though I set their permissions the same as the others in that folder. Steps to reproduce: 1. Edit --> Preferences --> Music --> Preferred Format 2. Add a new format and set it active 3. Attempt to use the format OR 1. Create an xml file manually in the gstreamer profiles path 2. Restart gstreamer 3. Rhythmbox --> Preferences --> Music --> Preferred Format Actual results: I cannot see the format anywhere if it was created manually, and not in the list of possible preferred formats if created through the program. Expected results: I should be able to see this format profile and use it. Does this happen every time? Yes Other information: Bug also reported downstream to https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/217135
That generally means that the pipeline cannot be constructed, either due to a syntax error or because one of the elements is not available. In the example you provided in launchpad, you might be missing the id3mux element, which is more or less obsolete and probably broken. Use id3v2mux instead.
(In reply to comment #1) > That generally means that the pipeline cannot be constructed, either due to a > syntax error or because one of the elements is not available. In the example > you provided in launchpad, you might be missing the id3mux element, which is > more or less obsolete and probably broken. Use id3v2mux instead. > Even using id3v2mux, the problem persists. It's ANY profile, even if it's not MP3.
> Steps to reproduce: > 1. Edit --> Preferences --> Music --> Preferred Format > 2. Add a new format and set it active > 3. Attempt to use the format > > OR > 1. Create an xml file manually in the gstreamer profiles path There is no 'gstreamer profiles path'. The profiles are stored in gconf. If you've been creating files under ~/.gconf by hand, I'm not surprised things are getting screwed up. > 2. Restart gstreamer What do you mean by this? Anyway, here I just need to restart rhythmbox for the new profile to appear (due to bug 309897).
(In reply to comment #3) > > Steps to reproduce: > > 1. Edit --> Preferences --> Music --> Preferred Format > > 2. Add a new format and set it active > > 3. Attempt to use the format > > > > OR > > 1. Create an xml file manually in the gstreamer profiles path > > There is no 'gstreamer profiles path'. The profiles are stored in gconf. If > you've been creating files under ~/.gconf by hand, I'm not surprised things are > getting screwed up. I understand that now. Ignore the "OR". The top is still an issue. However I did successfully add a new format, using the default settings (hit new, leave everything as is, give it a name, make it active, restart rhythmbox, and it's there) > > > 2. Restart gstreamer > > What do you mean by this? Wasn't sure if it was relevant, but I restarted. > > Anyway, here I just need to restart rhythmbox for the new profile to appear > (due to bug 309897). > How can I see what is wrong with the gstreamer pipeline I'm using (if there is something wrong with it)? audio/x-raw-int,rate=44100,channels=2 ! lame name=enc vbr=false bitrate=192 ! id3v2mux
Nix that, I figured it out. sound-juicer AND rhythmbox MUST be restarted after each profile change. Having one in the background will cause the new profile to not be recognized. Unless someone disagrees, this bug could be closed and attention focused on 309897, as I can no longer replicate any of the issues I originally reported (now that I'm ensuring both programs are closed).
OK, closing. *** This bug has been marked as a duplicate of 309897 ***