Folks may or may not have noticed, but last week I made a long-wished-for technical change that hopefully has improved both the stability and functionality of the site.
The process I was using previously to update and upload the "now playing/recently played" html file was causing the program that runs the stream on my computer to crash periodically. I had been trying to figure out a fix for some time, but finally gave up and last week put a new process in place. This new method is proving to be far more stable (no crashes in about 5 days, knock on wood) but also has another advantage.
The previous process used ID3v1 tags to update the page. The problem was, these tags truncate fields (e.g. song title, artist name, album name) after 30 characters. The new process uses ID3v2 which holds longer fields. So longer album names like The Legacy of Tommy Jarrell Volume 2: Rainbow Sign now come through intact instead of being truncated to The Legacy of Tommy Jarrell Vo.
All of which makes me very happy.
John
2 comments :
John,the only thing I really notice about the playlist is that it is posting the title of the next tune to play too soon. Unless a person is familiar with the tune, you can get confused real quick.As always,this is a great site and I appreciate all the work you put into it.(And FYI,I found out if I hit the "refresh" or "Reload" button, the playlist will "unstuck" itself most of the time.)
Thanks, Christine.
This isn't something I can fix too easily. The process that updates the web page is sychronized with the process that's starting the audio stream, but there are buffers on the server and on your computer that delay the audio by up to 30 seconds or so. And there's code that makes the browser window refresh every 30 seconds, but the "what's playing now" can get ahead of what's really playing. If you're confused, the Winamp window should have the accurate title of the track you are hearing.
Post a Comment