Sorry about the non-bugs. I've not used that cast trick to see the value as a hex number without having to drag in and use manipulators, but I should have guessed.
This one is, I believe, an actual coding error, in the area of order-of-evaluation. In the macro GET_ENCODED_VAL, in VorbisAudioRTPSink.cpp on line 129 (in the 2012.089.30 release), there's a possibly unintended evaluation of the phrase: "n = n*128 + byte&0x7F;" I think, looking at the spacing around the statement, you intended: "n = (n*128) + (byte & 0x7f);" What you're getting is: "n = (n*128 + byte)&0x7f;" // Wally _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel