You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if, while playing around with songs, there was a way to share a link to an embedded song in the tracker.
Max URL length is generally ~2000 characters, which is easy to go over for a song with a few patterns, so we might need to do one or more of:
Build in an all-javascript gzip and see if you could crunch songs by gzip+base64 and put them in URL? Certainly this would just increase the max length (maybe it's closer to 4000 characters with this approach).
Nuclear option, actual backend somewhere so the url can be just /2935239 and pull the song up. Would need to have some kind of netlify or heroku app running in this case.
Alternative -- maybe you could piggyback a public upload, like a gist? If you could start the tracker with ?gist=<gist url> then users could upload a song to a public gist and make a link to it like that. No database necessary in that case.
The text was updated successfully, but these errors were encountered:
I agree. Song sharing could be easier to deal with.
I added a zip library to a recent release of the tracker for reporting compressed size, so Zip + URL encoding is an option, as is JSON crush. Constraining songs to 2K bytes after compression could cause problems though — especially if authors want to keep metadata and unused patterns.
I really don't want to add a backend to this project as it's another thing to maintain.
Ah, so probably anyone could push a song as a json file into any repo and load it with the URL option, right? If so that doesn't make it "easy" to share a song but you can make it easy for the recipient to play.
It would be nice if, while playing around with songs, there was a way to share a link to an embedded song in the tracker.
Max URL length is generally ~2000 characters, which is easy to go over for a song with a few patterns, so we might need to do one or more of:
/2935239
and pull the song up. Would need to have some kind of netlify or heroku app running in this case.?gist=<gist url>
then users could upload a song to a public gist and make a link to it like that. No database necessary in that case.The text was updated successfully, but these errors were encountered: