not very constructive suggestion: an h2 with a recursion joke, something like "YAML As Music List"
Show HN: Tired of the non-portability of my playlists, I wrote my own format
21–30 of 104 posts
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#22This is such a good idea. If nothing else, third party tools that people make to transfer playlists between platforms could standardize on this and, in doing so, would reduce duplicated efforts. After trying (and being dissatisfied with) EVERY music service, I'm currently trying to consolidate back to Apple Music. Manually. It's awful.
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#23I've never had a problem with my Winamp playlists going from one PC to another. I just double click them and the music plays.
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#24Earlier quoted context omitted.
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…
> The introduction sounds much more ambitious than your comment
It aims to be more flexible, but it doesn't specifically aim to replace them. I don't mind players using M3U, PLS, or whatever else, I just want the extra features that UPL would provide. I guess it's a fine distinction.
> I am really curious about moving from Google Play to a local library, though - can you say more about that?
Well, if Google Play allowed me to export my playlists as UPL, my local foobar2000 could easily find the tracks in my local library (I already have them all) and correlate which tracks on Google Play are which tracks locally. As it stands, I have to go into my Google Play playlist, find the thousands of songs in my playlists one by one locally, and add them to my local playlists as I find them.
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#25XKCD predicted this.
https://xkcd.com/927/
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#26I'm a little confused why '3.3.1. entries' is a sub-bullet of '3.3. id'. Perhaps it's just a typo?
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#27This is great, thanks for creating and sharing it. I've been working on my own music player of sorts [1] that uses YAML to store playlists, and I'm going to look into switching to this.
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#28This is great, thanks for creating and sharing it. I've been working on my own music player of sorts [1] that uses YAML to store playlists, and I'm going to look into switching to this. [1]: https://github.com/muzak-project/muzak
Oh, fantastic! Please let me know if you need help with anything or have any feedback. An issue in the project repo is great, or just email me directly (email in profile). Thanks!
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#29What's wrong with xspf? Couldn't you just extend that with more attributes (which legacy apps could ignore)? https://en.m.wikipedia.org/wiki/XML_Shareable_Playlist_Forma...
Yes, please!
We have enough playlists formats to support already (and most of them are half-baked/half-broken already). There is no good reason to not reuse and extend xspf.
(Last time I counted 16 major playlists formats in VLC...)
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#30What's wrong with xspf? Couldn't you just extend that with more attributes (which legacy apps could ignore)? https://en.m.wikipedia.org/wiki/XML_Shareable_Playlist_Forma...
Yes, please! We have enough playlists formats to support already (and most of them are half-baked/half-broken already). There is no good reason to not reuse and extend xspf. (Last time I counted 16 major playlists formats in VLC...)
Isn't one good reason the fact that you avoid the whole confusion of "I imported my XSPF playlist with all my IDs but my player didn't find any songs!" "Oh, that's because your player only supports XSPF 1, not 1.1"?