Jump to content

Option to remove or toggle 4MB size limit for cover / album art


Recommended Posts

Hi there. I'm new to Poweramp. Before that, I briefly went to AIMP and, before that, I was a foobar2000 Mobile user.

In my Foobar2000 Mobile days, it would just load anything that was cover.jpg/.jpeg/.png etc. in the folder and be done with it. It was great! With AIMP, I discovered that they limit this to 500KB (WTF?!) so most of my large artworks wouldn't even show up.

Now, that I moved to Poweramp, I see a similar situation to AIMP but much less restrictive. 4 Megabytes. I would be nice to have an option to override this. I assume this is so for RAM usage control. I would love to see just a toggle to remove that restriction.

I have a 10k+ song selection in OPUS and checking for >4MB JPEG/PNG files before I update would be incredibly annoying.

Cheers.

Sorry I read, but couldn't understand you very well, but if you are talking about downloading album art, I will suggest you use a third party app, like AutoTagger, so it will embed it to the file, you can even choose the size of images. 

No, the OP has already downloaded artwork which they have saved on their device as individual cover.jpg / folder.jpg / albumname.jpg / etc. However some of these images are bigger than 4Mb (I really can't think why that would be necessary on a phone, but hey) which is PA's limit for performance and caching reasons.

Embedded artwork can be bigger (8-24Mb per song file, depending on device and memory) but that would beg the question of whether it's worth having artwork that takes up more space than the music in some cases.

Andre

9 hours ago, andrewilley said:

No, the OP has already downloaded artwork which they have saved on their device as individual cover.jpg / folder.jpg / albumname.jpg / etc. However some of these images are bigger than 4Mb (I really can't think why that would be necessary on a phone, but hey) which is PA's limit for performance and caching reasons.

Embedded artwork can be bigger (8-24Mb per song file, depending on device and memory) but that would beg the question of whether it's worth having artwork that takes up more space than the music in some cases.

Andre

Yep, you got it. I don't embed images because it quite literally multiplies the file's size times the number of songs I have from one album / compilation. On top of that, I would have to manually embed the cover art for my phone separately........
Again, all I ask is a toggle. People who prefer performance and caching performance, can leave the toggle to OFF. For those, like me, that has a HUGE collection of music on their device and love HUGE artwork art, this is a god sent.
Otherwise, I will have to literally go through my whole folder hierarchy and convert down any image file that's over 4MB.

I agree. I think your best solution all-round would be to reduce the size of the files and save yourself some space. 4Mb is pretty excessive for what are basically intended to be thumbnail / small cover images on a phone screen.

I tend to use between 500x500 and 1000x1000 mostly, moving towards 1000x1000 as my overall goal. I do have a few images as large as 1500x1500, but I feel that is a bit redundant as that is larger than even my 32-inch WQHD primary PC monitor can display. With reasonable JPG compression, those images vary from under 100Kb up to a maximum of 1Mb or so in a few rare instances.

You could easily process all of the larger files as a single batch task in any decent image handling program, preferably on a computer rather than on your phone. Using a Save-for-Web option is a good idea as it optimises and strips out all the unnecessary clutter.

Andre

29 minutes ago, andrewilley said:

I agree. I think your best solution all-round would be to reduce the size of the files and save yourself some space. 4Mb is pretty excessive for what are basically intended to be thumbnail / small cover images on a phone screen.

I tend to use between 500x500 and 1000x1000 mostly, moving towards 1000x1000 as my overall goal. I do have a few images as large as 1500x1500, but I feel that is a bit redundant as that is larger than even my 32-inch WQHD primary PC monitor can display. With reasonable JPG compression, those images vary from under 100Kb up to a maximum of 1Mb or so in a few rare instances.

You could easily process all of the larger files as a single batch task in any decent image handling program, preferably on a computer rather than on your phone. Using a Save-for-Web option is a good idea as it optimises and strips out all the unnecessary clutter.

Andre

I know I could just process them just before transfering everything to my phone and that's extra work I'm not really keen on doing because of the complexity of my folder structure.
Also, downscaled artwork from an higher resolution to a lower gives better image quality than a native resolution picture if handled correctly. That's why I use and love huge artwork.

This limit is only for in-folder images. Tag based album art is already limited to 24mb (which is huge and resized anyway), and build 891 also updates this limit for in-folder images as well (on devices with 256+mb per-app memory).

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...