Support and General Use > Plugins/Viewers

pictureflow problem - any suggestions for a fix/workaround?

<< < (2/12) > >>

chris_s:
For what it’s worth, the PF plugin, unlike the playback engine of Rockbox, doesn’t look at embedded artwork, only at separately stored artwork files, so you should probably make sure the latter are of an appropriate size. The order used by Rockbox is also described in the manual: https://download.rockbox.org/daily/manual/rockbox-ipod6g/rockbox-buildap3.html#x19-430000C

My understanding would be that “insufficient memory” refers to the plugin buffer only (so part of RAM), but Bilgus is obviously better equipped to speak on that.

Frankenpod:

--- Quote from: chris_s on November 24, 2021, 02:23:38 AM ---For what it’s worth, the PF plugin, unlike the playback engine of Rockbox, doesn’t look at embedded artwork, only at separately stored artwork files, so you should probably make sure the latter are of an appropriate size.

--- End quote ---

That's helpful to know.  At some point I guess I'll try bulk-resizing all the cover.jpg files (leaving the embedded art untouched - I mostly have cover.jpg files in each directory with just the first track having the same art embedded in it), and see if that makes any difference with building the PF DB.

Frankenpod:
Drat.  Even after downsizing every cover.jpg to 160 pixels width, I still get the 'insufficient memory for album art cache' error message at the end of the initialising process.  Not sure what is the issue.

amachronic:
"Not enough memory for album art cache" means the artist & album index is too big and there is not enough memory left over for buffering the cover images as they are loaded. You can look for the pictureflow_album.idx file (it'll be somewhere under the .rockbox folder) and see how big it is. The size of that file should be approximately how much RAM is being used for the index. If it's too big, that'd be the problem.

The size of your cover art shouldn't matter too much -- I think it's only read in small chunks and gets re-scaled on the fly.

Frankenpod:
Thanks.  I'll have a look and see if it's there and what size it is - assuming it actually succeeded in creating that file - it seemed as if the whole initialisation process failed at that point, but not really sure.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version