ADMIN: Testing a New Music Player (Part 2: Some Notes (So Far))

Some observations about the new music/audio player thing I experimented with yesterday…

1. It’s not as customizable as I’d like it to be — yet.
   • I wish I could arrange things so it doesn’t span the entire width of the blog post; I suspect that I can, with some artfully applied style-sheet changes.
   • The colors need to be tinkered with, as well. (Again, though, I suspect I just need to… well, to tinker some more.)
2. There doesn’t seem to be any way to change the name of a track as it appears in the playlist. By default — maybe unchangeably? — the player uses the filename. Personally, I try never to use spaces, punctuation, or other special characters in my filenames, and I don’t make the names, y’know, Mixed Upper- and Lowercase — plain all lowercase for me. Which didn’t matter before, because I could specify how I want each track labeled. Now? A filename like songtitle_artistname.mp3 shows up exactly as such in the playlist, not as Song Title, by Artist Name (or whatever). Ugly. (I got the “user-friendly” names in yesterday’s post to appear that way by renaming their files that way, against my tech-guy better-or-otherwise judgment.)
3. I haven’t yet figured out how to replicate the functionality of what I used to call the “RAMH right-bracket secret decoder ring” trick for playlists of more than one song. On the other hand, even with the old audio player I didn’t really have a solution — I’d just hoped otherwise.
4. Most, well, troublingly: I couldn’t use the new audio player with my (Android) smartphone’s Firefox browser. It showed up beautifully on the screen, and went through the motions of playing each song — showing the little progress meter, advancing to the next track, and so on. But… no sound. (It worked okay in the Chrome Android browser.)

Will see how things progress as we move along here…