OK, I figured out the problem - it was caused by the nonstandard 'metadata' track in the back-end stream. Because this track is non-standard, we can't proxy it, but that should not have prevented the other, standard 'video' track from being proxied.
I've now installed a new version "2012.07.06" of the "LIVE555 Streaming Media" software that should fix this problem. Now, your front-end client should be able to receive the 'video' track OK. Thanks for bringing this issue to our attention. Ross Finlayson Live Networks, Inc. http://www.live555.com/
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel