This is the bug/patch tracker for Rockbox. Click here for more information.
Quick links: Bugs · Patches · Rockbox frontpage
FS#9665 - pictureflow resize-on-load
Attached to Project:
Rockbox
Opened by Andrew Mahone (Unhelpful) - Thursday, 18 December 2008, 11:02 GMT+2
Last edited by Andrew Mahone (Unhelpful) - Saturday, 17 January 2009, 01:37 GMT+2
Opened by Andrew Mahone (Unhelpful) - Thursday, 18 December 2008, 11:02 GMT+2
Last edited by Andrew Mahone (Unhelpful) - Saturday, 17 January 2009, 01:37 GMT+2
|
DetailsThis is a first attempt at pictureflow resize-on-load using the new core scaler. It uses the BM_*_SIZE macros to calculate static buffer sizes, so you will need to apply the most recent scaler update patches from
|
Closed by Andrew Mahone (Unhelpful)
Saturday, 17 January 2009, 01:37 GMT+2
Reason for closing: Accepted
Additional comments about closing: superceded by work already committed in r19598
Saturday, 17 January 2009, 01:37 GMT+2
Reason for closing: Accepted
Additional comments about closing: superceded by work already committed in r19598
FS#8335.Note that you directly influence the album art search (success rate) with changing PREFERRED_IMG_WIDTH/_HEIGHT as those are used for the size string in cover.<size>.bmp too at the search. I suppose leaving those as they are, and use other symbols for resizing target size.
ALso, it doesn't really make sense to search for covers that already have the target dimensions, does it? :)
Can you explain the LCD_WIDTH*10/32 part? I guess this should be for portrait targets, but 1/3 the screen width is pretty small (that's just 60 on a e200, which has 220 pixel rows). Just use LCD_HEIGHT/2. It's fine, I've been using that in
FS#8335for a while now too and it looks great.The key to see other covers is to change center margin (i.e. the space between the center and the side cover) in the settings, not reducing the imagine size. The default value is bad anyway, it's like miles away.
As far as PREFERRED_HEIGHT and searching for covers by size, that should probably just go away. PF can't reasonably guess what size AA the user might have, and can't search for every possibility. Removing the size-based search would probably also get back a little bit of the binsize that resize-on-load cost.
I'd keep zoom, and add a bool option whether to resize or not upon the next cache creation. I guess there's people who don't want them resized in pf, or have bigger album art where resizing would just make them too small for them.