Thanks for the suggestion Ross. Unfortunately it doesn't work. When I add that attribute, LIVE555 streaming library constructs the following URL: rtsp://192.168.2.102:554/?src=1&freq=11538&sr=22000&pol=v&msys=dvbs&fec=45&mtype=qpsk&pids=0,654,604,624,16,17,18/?src=1&freq=11538&sr=22000&pol=v&msys=dvbs&fec=45&mtype=qpsk&pids=0,654,604,624,16,17,18
The server doesn't accept this. What is required is simply the input I originally supply: rtsp://192.168.2.102:554/?src=1&freq=11538&sr=22000&pol=v&msys=dvbs&fec=45&mtype=qpsk&pids=0,654,604,624,16,17,18 I can understand that you'd want to exercise extreme caution when modifying the RTSPClient code. However... 1. The required patch is not complex: (replace RTSPClient.cpp line 1438) unsigned suffixLen = strlen(suffix); separator = (prefixLen == 0 || prefix[prefixLen-1] == '/' || suffixLen == 0 || suffix[0] == '/') ? "" : "/"; 2. You're weighting a concrete example of an incompatible server (Triax TSS400) against a hypothetical [and in my opinion highly unlikely] compatibility break with existing servers. 3. Iff the patch broke compatibility with other servers, the people interacting with those servers could simply add a trailing slash to the URL they pass in. That's trivial. I strongly urge you to reconsider your decision. Regards, Nathan _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
