Stretto VS tomahawk

This being native is super nice!

I maintain an open source web-based music player called Stretto[1]. It works well as a PWA on Android, but it depends on a chrome extension to bypass CORs.

Allows you to import playlists from Spotify and automatically backs them with a YouTube track (similar to this service). Also supports adding SoundCloud tracks, for those that love their remixes.

[1]https://github.com/benkaiser/stretto

GitHub: https://github.com/benkaiser/stretto Website: https://next.kaiserapps.com/

This blog post is a write-up about the open-source web-based music player I've worked on for the last 8 years. https://github.com/benkaiser/stretto

Checkout my music player, https://next.kaiserapps.com I added basic audius support (you can add audius songs to your library) and it supports offlining songs.

You can find the hosted version of Stretto here: https://next.kaiserapps.com/ (requires installing a chrome extension to make API calls work).

In a way, This reminds me of the (much more ambitious) system of resolvers [1] of the (now defunct) tomahawk player [0]

The idea was you just give it the metadata and it "resolves" it into any service. I really like this idea. it kind of lives on in "playlist converters" like tunemymusic or soundiiz. but it is not the same as it being built into the player itself (like spotube albeit with a different more straightforward aim here)

[0] https://github.com/tomahawk-player/tomahawk

[1] https://github.com/tomahawk-player/tomahawk-resolvers

Tomahawk "a free multi-source and cross-platform music player. An application that can play not only your local files, but also stream from services like Spotify, Beats, SoundCloud, Google Music, YouTube and many others... "

There is this app called Tomahawk, although I don't think it has been maintained in a while.

Just works (plays almost all formats) - FooBar2000 Minimal as fuck (CLI/Terminal) - CMUS Bloat (lots of features some you want, some you didn't know you wanted and stuff you won't use) - tomahawk

I hope eventually all of the guys muddling around this will realize the obviousness of the truth: we need a metadata-first player with Artist, Track, Album Linked Open Data entities, where the actual data are just sources for that entity, and you can have multiple providers (YouTube, Soundcloud, Bandcamp, torrents, IPFS, anything). Some tracks you listen to often you can "cache" on the SD card, so you don't hit the network AGAIN for the same data (cell towers and servers use power you know). Other times you want to make room and you blow away some of the data. But if you've got reception and a locally unavailable track shows up in a playlist it will just fetch it from one of the other sources. If some uploader decided to cripple your playlists with link rot, no problem, all of the metadata is intact and in your control, you just need to find another provider for that CreativeWork. Your metadata then becomes a monolithic single-source-of-truth database of information like "Blind Observatory is a project of David Pasternack", "this track belongs with tracks of the style called Chillrave", "this track is via Alice", "heard this in a mixtape by Bob". At which point it becomes obvious you shouldn't be handling the fabric of your digital life in anything less than a top quality FOSS graph database of sorts. You tend to that directly, then glue code deals deterministically with stuff like writes to embedded tags so the music files are portable.

Turns out Tomahawk does a lot of what I want, it's just no longer in active dev - https://github.com/tomahawk-player/tomahawk