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 351682 - Non-existant property causes loads of dialogues
Non-existant property causes loads of dialogues
Status: RESOLVED OBSOLETE
Product: rhythmbox
Classification: Other
Component: Importing
HEAD
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-16 21:25 UTC by Bastien Nocera
Modified: 2011-07-18 11:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bastien Nocera 2006-08-16 21:25:35 UTC 
1. Insert an Audio CD
2. Select all the tracks, and click on "Import"
3. Get as many dialogues as there are songs saying:
"
Error transferring track
could not set property "vbr" in element "enc" to "1"
"

The profile I selected was a lame one:
audio/x-raw-int,rate=44100,channels=2 ! lame name=enc vbr=1 bitrate=192 ! id3v2mux
and vbr=1 isn't a supported value for lame on my system:
"
  vbr                 : Specify bitrate mode
                        flags: readable, writable
                        Enum "GstLameVbrmode" Current: 0, "none"
                           0) none             - No VBR (Constant Bitrate)
                           2) old              - Lame's old VBR algorithm
                           3) abr              - VBR Average Bitrate
                           4) new              - Lame's new VBR algorithm
"

I should get only one error message, and the files shouldn't be created (they're all empty files)
Comment 1 James "Doc" Livingston 2006-08-17 01:14:34 UTC 
There are two issues here:

1) we should somehow detect when the error causing the rip to fail applies to all the tracks and only report it once, or better yet realise that it will cause the others to fail too and not start them

2) when there is an error ripping (other than "can't create because user said no to overwrite") we should probably delete the files.

Whilest on the topic of the exception to (2), we should have "yes to all", "no to all" and "cancel transfer" in the overwrite confirmation dialog.
Comment 2 Alex Lancaster 2006-08-18 00:44:13 UTC 
Bug #350041 is also somewhat related to this bug.
Comment 3 Jonathan Matthew 2011-07-18 11:56:50 UTC 
Not a problem with the new profile system.