On Sun, 2007-06-24 at 00:12 +0100, Sjoerd Simons wrote: > > I'm not simply guessing, the rtsp log shows that the stream transports > gstreamer tries to setup aren't supported by the server. Whether the > transports > the server support is RDT or some other doesn't matter.
No. What it shows is that the code which prints output printed that a "we can't support that" was returned. Perhaps there is a bug in presenting transports to the server, or perhaps the server's reply is being decoded incorrectly. Perhaps there is some entirely other problem. How do you know? You're *guessing* that the problem is the absence of RDT support. So does that mean that you're promising that adding RDT support will fix the problem entirely? I doubt it. Which means that you're guessing. And, worse, guessing as a strategy, apparently, to avoid any actual debugging. > My changed title was and still is the real bug. gstreamer needs support for > real servers and the transports their using. You're not even paying attention. The server is not a Real Server (which is a particular product); it's a Helix Server. Thomas
signature.asc
Description: This is a digitally signed message part
