Hello I recently installed the app on my Android TV and I'm pretty happy I can display the current playing track and album art on my big screen now. I would like to request the ability to swap the displayed album art with the track information periodically as a screen-saver. This could be beneficial when playing albums that display the same artwork throughout playback to prevent burn-in on OLED screens etc. Thank you.
Bump. I imagine that having the album art periodically change sides wouldn't be too difficult to code. @Zidoo Support-Kim
TBH I was surprised to read such a bold statement from you... Maybe it's not so difficult to code, but it requires at least some settings, and that is a different story: interface, setting-storage in the DB, backup... maybe discriminantion among local-display, app-display etc. See, maybe it is, maybe it is not. And I believe this is for sure not a priority they are going to address before other more critical and unpleasant issues. Just my 2c.
Well, I'm not a developer but I've seen implementations of moving album art (as a screen saver) on various platforms for well over twenty years now. I would assume that it's not rocket surgery. I had a rotating cube (java) with images on each face on my own website back in 1999 lol.
You are absolutely right. The problem here is we are on Android (despite a clockwork marvel Linux underneath it, still a Java resources hog...), and aiming at bitperfect audio reproduction. All this graphic rendering needs a dedicated powerful (and power-hungry...) GPU. If all the hardware is not able to sustain all the struggle, you may get not fluent graphics, and - most importan - possibly not fluent audio... which is the most important thing... So, it may be easy from an implementation POV, but... you may get the point. Cheers, Al.
Fair enough. As I understand it however, the app is running on my TV and therefore using my TV's processing power to display the image from the data provided by the stream. I could be wrong.
If it is the app, and not a screen-replication (or a ghost-screen-replication - a screen you don't see on the device, but that is being rendered there nevertheless) app, then yes, it will not draw on the devices resources... but I cannot comment.
