Are relative paths supported? Probably in this day and age it would have better chance at adoption if it would be a JSON file. It's just network effects.
[deleted]
Show HN: Tired of the non-portability of my playlists, I wrote my own format
11–20 of 104 posts
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#12Are relative paths supported? Probably in this day and age it would have better chance at adoption if it would be a JSON file. It's just network effects.
Not yet, but great idea, I've added it, thank you!
YAML is a superset of JSON, so the file can look like JSON if you want, although that's not mandatory. I don't think there are many languages that don't support YAML these days, and one of my goals was to make the format not-entirely-unreadable by humans.
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#13I'd love something like this, but I don't see any upside for iTunes or Spotify to support it. Anything that makes it easier for a customer to switch to a competitor is something they're going to resist.
They have plenty of upside to allow import through this format, as you can just upload your Winamp (yes, I'm old) playlist to Spotify and immediately migrate to their service. I'm hoping there'll be enough user demand that they'll choose not to appear evil and support export as well.
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#14This looks interesting. Do you have any plans to create converters to convert to UPL from other formats?
Yes, right now I'm collecting ideas (there have been some very good ones in this thread), and I plan to write a few small converter programs to convert from M3U/PLS, as well as some plugins (I'm thinking about beets, currently).
Any help would be appreciated!
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#15My own format = https://xkcd.com/927/
I don't see why this is being downvoted. It's fairly apropos to the subject. And it was the first thing I thought of too when I read the title.
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#16why does the example have md5 and sha1?
Good catch, I had them there initially but decided to play it safe and avoid the broken hashes, so I removed them from the list but forgot the example, thank you.
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#17My own format = https://xkcd.com/927/
I don't plan on creating a standard that will end all others, though. I just want to move from Google Play to my local library.
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#18My own format = https://xkcd.com/927/
I don't see why this is being downvoted. It's fairly apropos to the subject. And it was the first thing I thought of too when I read the title.
À format that is independent of a specific platform or player has its own merits, besides the scratch your itch part.
With a good plugin support an ecosystem to allow interoperability of playlists becomes possible.
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#19My own format = https://xkcd.com/927/
I don't plan on creating a standard that will end all others, though. I just want to move from Google Play to my local library.
The introduction sounds much more ambitious than your comment:
> The Universal Playlist Format (UPF) is a data format for music playlists. It aims to be more flexible and complete than existing formats. A Universal Playlist (UPL) will allow better description of the tracks it contains, as well as enable added functionality in music players.
I am really curious about moving from Google Play to a local library, though - can you say more about that? GP has been losing tracks, slowly but steadily, or mislabeling them horribly.
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#20Are relative paths supported? Probably in this day and age it would have better chance at adoption if it would be a JSON file. It's just network effects.
Not yet, but great idea, I've added it, thank you! YAML is a superset of JSON, so the file can look like JSON if you want, although that's not mandatory. I don't think there are many languages that don't support YAML these days, and one of my goals was to make the format not-entirely-unreadable by humans.
> I don't think there are many languages that don't support YAML these days
YAML is a big and complex format though, libyaml's header is bigger than the entirety of libtoml.
I think hand-editable playlists are a good idea, just not a fan of yaml.