

And checked that they are all built.Ĭonfusion about individual tracks. And while you can do this album by album (rather than track by track), it's still pretty slow and pernickety. So far the only way I can see to fix this problem is to find the image on the web somewhere, cut and paste within JRiver via 'cover art/paste from clipboard' then to do the right thing by everybody else, 'cover art/submit to internet' and finally 'cover art/get from internet' to see that it got there successfully. It also appears that the resolution that JRiver offers depends very much on what's already been put there - and if the 225 x 225 image is what I have, and it's the best that anybody else has, then that's what JRiver offers when you apply Cover Art/Get from internet - even if I've already put a much larger image there via Jaikoz (or any other metadata editor). It's not that png is the issue, as I have other situations with hi-rez (ie >1000px x 1000px jpgs) cover art, that still don't show in JRiver.Ĭlearly JRiver puts its cover art somewhere different within the metadata than most other metadata editors.
