View Single Post
Old 16th October 2013, 22:01   #6
DrO
 
Join Date: Sep 2003
Posts: 27,873
the YP looks at a number of values to determine / maintain the stationid. but if too much changes or it cannot be certain then it can in some cases do as you saw (which was a bug) or it'll just provide a new stationid.

so if you just change the IP address or port then it should maintain it, if you change both at the same time then there's no guarantee. that is one of the scenarios v2 + authhash can cope with as you're not tied to the IP address / port of the stream, just the authhash.

with a different stream format, if everything else is the same, and it's just the format that has changed (bitrate will also be taken into account) then it'll generate a new stationid or if it had already been known (and still is known) to the YP, it then may re-use the prior stationid for that instance of the stream (which is what it's meant to do, just if it clustered incorrectly to begin with then you get into the issue you first had).

basically, most of the time it works if using a v1 DNAS but there are cases (either from you or from us) where it can break that and so the stationid changes. whereas a v2 DNAS when correctly setup will maintain the stationid as long as the listing and the authhash are in your config file(s) and in the YP system.
DrO is offline   Reply With Quote