Hi Geoff, On 11/13/2014 07:59 AM, Geoff Shang wrote:> On Thu, 13 Nov 2014, Roger H?gensen wrote: > >> Shoutcast v1, Shoutcast v2, Icecast-KH are all "compatible" with the >> way info is collected by StreamLicensing. > > It's not really clear to me what you're looking for in terms of > specific stats.There's an earlier thread, this message somehow detached from threading, at least for me.> You should be able to get any of the stats you want, in any format you > want, by using XSL templates. This is a bit technical but can be done. > I once came up with a template to mimic Shoutcast 1's 7.html which > worked quite nicely (I don't have access to this right now).There are a couple of things that this particular licensing broker wants that are not in the general /admin/stats XML document, which is used for XSLT files in the web directory. IMHO it would already now be possible to gather the data, it's just that the licensing broker doesn't bother to figure it out and demands an easily digestible one URL solution. For other reasons we might humor this, but unless someone wants to throw some money at it, it will happen in the regular development cycle at free time pace.> I also understand that it's meant to be possible to secure these > things with Icecast's authentication mechanisms, but I've never > managed to figure out how to do it and asking has not had any responses.If it's just xslt files you can wrap them in the config by a <mount><mount-name>/custom.xsl</mount-name><authentication>?</authentication></mount>. It's a bit counter intuitive to define a mount for a XSLT, but that's how icecast mechanics work. We'll be working on those things, but right now getting 2.4.1 out the door with some important bug fixes is priority 1. I will be replying to the original thread once the release has happened. Cheers Thomas
On 2014-11-13 09:16, "Thomas B. R?cker" wrote:> Hi Geoff, > > On 11/13/2014 07:59 AM, Geoff Shang wrote: >> On Thu, 13 Nov 2014, Roger H?gensen wrote: >> >>> Shoutcast v1, Shoutcast v2, Icecast-KH are all "compatible" with the >>> way info is collected by StreamLicensing. >> It's not really clear to me what you're looking for in terms of >> specific stats. > There's an earlier thread, this message somehow detached from threading, > at least for me. >I forwarded this mail to Marvin at StreamLicensing, and I told him that he might want to join the mailinglist to pursue this matter further. Me acting as a middleman is impractical in the long run (like forgetting to forward a mail and letting it collect dust for example). So hopefully he or another direct representative will pop up in the future. Personally I still think it's important that Icecast 2 can provide the same stats as Shoutcast v1, Shoutcast v2 and Icecast-KH does "out of the box". (maybe add it for Icecast 2.4.x or 2.5.0?) And in the long run a proper low load stats API/login for royalty collector purposes could be implemented (Icecast 2.5? 2.6? 2.7? 3.0 ?) for the long run as suggested earlier by whomever it was (sorry I forgot). Todays "hammering" once every minute or so is not the best design (being a programmer I'm well aware of that). I'm sure even SoundExchange and the acronyms out there would not mind standardizing some of the info presented (to allow accurate geographical stats that still respect privacy) if it means they'll get even more accurate data than currently. -- Roger "Rescator" H?gensen. Freelancer - http://www.EmSai.net/
Hi Roger,> And in the long run a proper low load stats API/login for royalty > collector purposes could be implemented (Icecast 2.5? 2.6? 2.7? 3.0 ?) > for the long runIt's also useful for public service and non-profit broadcasters to have detailed analytics about their audience.> I'm sure even SoundExchange and the acronyms out there would not mind > standardizing some of the info presented (to allow accurate geographical > stats that still respect privacy) if it means they'll get even more > accurate data than currently.Right, there is no standard world-wide API for submitting this kind of data at the moment, so there's a lot of manual reporting going on. Live365 does automated reporting but only to SoundExchange as far as I know, which is not useful for anyone with listeners outside the USA. Online music retailers do have an XML reporting standard, called DDEX: http://ddex.net/node/44 but the last time I asked it had not been extended to cover broadcast reporting. I think this is because in online music sales there are a few dominant players which all have to be tech-savvy, whereas both radio and royalty collection have been analogue businesses for a long time. Plus there are multiple collection agencies in most countries, covering different aspects of copyright licensing. A handful of the bigger societies are DDEX members. Cheers! Daniel