Dear Friends, Dear Marius
I have a problem with, and a suggestion for future versions of Now Playing Info plugin:
The problem I encountered after installing v2020 is as follows: A new track starts, the plugin correctly exports now plying data to a txt file, and simultaneously fails to export the correct data in the web export POST. It probably exports something, but the information is clearly uninterpretable for the web script, since the webpage is not updating. I coded my PHP script in such a way, that even if complete nonsense arrives as track info with the correct XPWD, the script will display a default track element, but it is not even doing that. This means when this happens, not even the XPWD is correct, or maybe it is the only incorrect variable in the POST, I have no idea.
This problem happens once about every 6-7 tracks played, distributed completely randomly. This issue is not caused by the info it has to send out, the exact same track's info is sometimes sent out, sometimes not, completely random. It is also not caused by the webserver, I never had this problem with the previous versions of RadioDJ.
My suggestion for future versions: A text encoding option for UTF8, without the BOM. BOM is mostly useless in UTF8, and many programs cannot interpret it, and they display it as a character in front of the text, and this is really annoying. Sometimes it can also cause crashes, a good example for this is the BUTT source client, which crashes when I try to feed it a txt file in UTF8 BOM (as the stream metadata). Unfortunately, the UTF8 encoding option in the plugin exports with a BOM, and there is no way to export without it in UTF8. If it is for some reason necessary to keep the UTF8 BOM in the plugin, please at least give us 2 options for it, like:
- UFT8 BOM
- UTF8
Thank you for your time and effort, keep up the excellent work!
David
190 Replies
27661 Views