GNOME Bugzilla – Bug 614738
New album list art too big, should be an option for older style
Last modified: 2011-02-08 21:36:45 UTC
The new album list using large previews of the album art is less useful to the user, because the size of the art prevents one from seeing many albums at one time. I have a 1900x1080 display, and in normal usage, I can see 1.75 albums in my album list. That means, I need to scroll to select when an artist has only three albums, and nevermind if I have many--in that case, it's a slow, stupid sort of hunt-and-peck choosing method, scrolling up and down, and seeing only one new album at a time (that is, I can only ever at one time see some of the album I just saw, and the new one). This is much less functional than the previous version, which allowed more albums to be seen at one time.
What would you consider an appropriate solution? If you just want to be able to resize the covers so you can see more albums, then Bug 614687 is what you're looking for. If you want the option to switch the album browser back to the old list format, I don't think there's a report open for that yet, but I read somewhere that a preference option is planned for future Banshee releases.
I think the old interface did a fine job, and the option to switch between them would be a good fix. I just changed the title of this bug so it can serve for that, if you like.
Created attachment 157825 [details] Screenshot of UI If this helps to communicate why the size of it is important. I just can't run Banshee maximized, because that makes it annoying to switch frequently between applications; and when maximized, its UI looks very much out of balance, much too large with a huge bunch of mostly white space for the track list and a lot of mouse work for small changes.
You can switch to the previous album by setting the BANSHEE_DISABLE_GRID environment variable. Just run banshee like that : BANSHEE_DISABLE_GRID=1 banshee
The bug has been fixed in the meantime, see Preference / Source specific / Music / Disable album grid.
*** This bug has been marked as a duplicate of bug 618122 ***