Artwork resolution

[Buntobox]

Hi
I have an issue with artwork resolution in Asset. I have a classical music library on my PC and it is catalogued in the following manner: Composer/Album/Tracks. My artwork is all 600x600 pixels but when they are shown in their largest form as tiles in the composer view they are very low definition and unreadable. If, however, I select a composer, thereby opening up the Album view one level down in the hierarchy, the display then shows that album cover perfectly clearly.
Is there anything that can be done to prevent this problem from occurring?

[mville]

Please can you specify in which program you are viewing the artwork?

[Buntobox]

Please can you specify in which program you are viewing the artwork?

I'm using the Naim app on my iPad

[mville]

I'm using the Naim app on my iPad

Perhaps there is a display setting in the Naim app?

[Buntobox]

Perhaps there is a display setting in the Naim app?

There isn't. I've spoken to Naim and they say it's an Asset issue.

[mville]

There isn't. I've spoken to Naim and they say it's an Asset issue.

Does Naim wish to elaborate on how/why it is an Asset issue, so the problem can maybe be rectified?

[Spoon]

asset sets the size of the art when browsing to a maximum of 250x250, not this is not on the album listing its self which is full resolution. Why does asset do this? If you browse album >> a

Then it might have 100 albums to list, and many people have are which is 200KB, which is too slow over wifi.

[Buntobox]

Does Naim wish to elaborate on how/why it is an Asset issue, so the problem can maybe be rectified?

Naim have told me that Asset must be re-sampling the artwork and displaying it at a reduced resolution. I've told them this cannot be the case as the artwork shows in full resolution at 250 x 250 one level down in the hierarchy than the one that shows it pixillated and unreadable. At this point my emails ceased to be answered. I know this appears to be an admission of guilt on their part but I wondered if you had come across this issue before and had a fix for it.