From my understanding this is correct. I have tested this (on demand content) and already run into several problems, about which I will soon be making a features request post. Problem #1: it seems that only one person at a time can stream a song. I am unsure yet whether once content is requested, another user could tune in and hear it. #2: certain characters in the name will not be recognized such as a dash "-" parenthesis "(" etc. I'm not even sure spaces are recognized. Now since I have most of my MP3's named by artist - song title (and sometimes with album title as well, depending), I'd have to rename all my MP3's to get this to work. Lastly it does not support directories (according to them to make it less likely to be hacked and allow malicious access to your computer). Therefore you have to have all your Mp3's in the Content directory inside your Shoutcast directory, and not in any subdirectories, otherwise it won't work. My idea is for you to allow a playlist to be specified instead of a specific Mp3, so that you wouldn't even need the intermediate step of a web page with all mp3's listed for on demand, but rather one link that would point to a playlist on the server machine from which a user could then choose and it would select the appropriate Mp3 from wherever it was. Users could still not specify directories *directly* thus (I think) preserving some of that security they're looking out for, while at the same time giving the server much more flexibility by not having to have all Mp3's in one directory (my Mp3 archive is heavily directory dependant for sorting) and also not having to make web based listings of songs. I'm not sure how feasable that is, or what the real security risk is. Possibly a hacker could make a playlist locally that pointed to your machine and specific directories and could from there cause damage, I don't know. At any rate yes, in the current system assuming you have all your mp3's in the \content\ directory inside your shoutcast server directory and that all the names don't use special characters, you can then make an HTML list with the name of each mp3 prefaced with http://ipaddressort/content/
and users should be able to click on a link and hear the song, assuming no other user is doing so at that time. Keep in mind all this is from my own experimentation with this particular feature as it is one I am also extremely interested in. I hope this is helpful, and I'd appreciate any other comments on the subject.