I confirm that suggestion works.
Respectfully and without meaning to nag: please do continue to consider the
patch for future inclusion. I note this isn't the first time I've encountered
issues with LIVE555 streaming media and trailing slashes. If I recall correctly,
it wasn't possible for a clien
> 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&
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=d
Right now I’m not planning on changing the existing code in our software. This
code is already complex, and there’s a huge installed base of RTSP servers out
there that work with the existing code; some of these servers might be affected
by any change.
Instead, I suggest modifying your ‘synthe
Hello
We've built an RTSP client based on the LIVE555 streaming media library. The
client is fairly basic, so the only command/response sequence currently
supported is:
options -> describe -> setup -> play ... -> teardown
All has worked fine until now when we've encountered an RTSP server (actu
