m3u extended playlist comments useful?

[simoncn]

(24-05-2016 16:04)adrian Wrote:  It seems like it shouldn't, but I have read that encoders and/or decoders add some silence at both ends, something having to do with frame lengths of the mp3 encoding algorithm. I encountered this as an explanation for why gapless playback may be difficult with mp3. I assume in the end these length values are just used to tell the user how long the play list will last, so errors that are small don't matter.

Any padding needed to fill an MP3 frame would be so short that it's extremely unlikely to affect the duration in seconds. As you say, this value is purely informative.

Quote: I did start wondering about how play lists are titled when browsing and how they show up in the interface---presumably based on file name since there is no metadata to give a name or any organization. Or is it recommended to create one master playlist that lists all the other playlists and use the #EXTINF to give titles for them?

When viewing playlists from the # playlists container, the file name is used. If the playlist is referenced from another playlist, the reference will have the name from #EXTINF if present. It is your choice whether the extra level of indirection when browsing is worth the benefit of having a friendlier name.