Re:DRM’s Dead Canary: How We Lost the Web, What We Learned, ...
by StavrosK on Tuesday November 28, 2017 @07:51AM
(#15796736)
I designed a playlist format to solve your exact problem, but unfortunately there hasn't been much uptake so far: http://universalplaylist.stavros.io/
[ Parent
| on HN ]
Re:DRM’s Dead Canary: How We Lost the Web, What We Learned, ...
by feeboo on Tuesday November 28, 2017 @11:05AM
(#15798428)
I also thougth about this problem. Current playlist implementations are seriously lacking when you move your library. I have some shell scripts here that just replace parts of the path in the playlists.
I looked at your playlist format specs, why do you use floats? I'm currently coding on a GO audioserver and save time intervals as Nanoseconds (time.Duration). This makes more sense to me, as floats may behave badly in some contexts.
Re:DRM’s Dead Canary: How We Lost the Web, What We Learned, ...
by StavrosK on Tuesday November 28, 2017 @11:12AM
(#15798496)
I use floats because it's most natural to represent duration in time. Nanoseconds are going to be about as lossy as floats too, I guess (although for a different reason). If you're going for maximum accuracy, you'd need to represent the duration as the number of samples.
I wonder if floats are going to be a significant problem, hmm.