It'd be soul crushing to see it die simply from gaining popularity. You could trythis one though, didn't work on my phone, but might just be because I'm on my phone. This has been a pet project for two years now. Visualizers are kind of a 90's thing, so you will probably not find any good ones. It uses the music analysis data available for Spotify's whole music library via their API (structure, pitch, timbre, mood, danceability.) to produce visual experiences using the power of WebGL. Mobile users: it doesn't seem to want to size itself correctly in the Reddit mobile app's browser open it up in your default browser for a better experience. Kaleidosync is a growing collection of 20+ customizable WebGL sketches built using Vue, D3, and Three.js. Would it be within the developer terms and conditions to break up the application into multiple ones – one for each country containing a large userbase? e.g. More accurate syncing with Spotify, including automatic self-correction Play a song in your Spotify client of choice and check the visualizer out here: Kaleidosync / GitHub. Is there a formal process for requesting an application be whitelisted? The longer the delay, the less responsive the visualizer is to updating when the user selects another track.Īre there any options available to me to remedy this issue?
The application is currently configured to do so every 7500ms (it was previously more frequent, but I recently adjusted it to help with this issue), but I'm getting 429s nearly every other call. I recently had a decent influx of users and the application is beginning to hit a wall.Īt its core, the application needs to frequently ping for the user's currently playing track. I'm the author of Kaleidosync, an in-browser Spotify visualizer.
