stopPlaying shouldn't be being called, and no objects should be being
deleted. I'll double check this, but I am 99% certain. I'll test out the
unmodified client applications to see how they perform.
On Fri, Mar 1, 2019 at 3:06 PM Ross Finlayson wrote:
> > In any case, we can’t really help you de
My setup: my MediaSink subclass for my application (calling it RTPSink) has
a H264VideoRTPSource (gotten from the MediaSubession, determined by SDP
parsing). After calling startPlaying, it runs fine for some period of time.
However, after some random amount of time, the BasicTaskScheduler that's
us
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
xisting 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
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
> OK, thanks. This will be included in the next release of the software.
Thanks Ross - much appreciated!___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
> However, you’re running an old version of the “LIVE555 Streaming Media” code.
The same issue applies to the latest code.
> Please upgrade to the latest version, and submit a patch against that version
> instead.
The patch I already submitted is against the latest version.
__
Hello Ross
Using LIVE555 as a client to receive RTSP/RTP/MPEG2-TS streams from a 3rd party
RTSP server, I've encountered a problem which I'm hoping can be easily fixed.
Sequence for reproducing is as follows...
1. Use LIVE555 RTSP client to send a SETUP request:
SETUP rtsp://172.31.0.1:554/
Thank you very much for your prompt and helpful response Ross.
> You should definitely upgrade. Not only do we not support old versions of the
> code, but (most importantly) newer versions fix several, often-important bugs,
> including security vulnerabilities. You are putting your system at g
Hello
We rely on a now-ancient version (2009-09-04) of LIVE555 Streaming Media library
as the basis for the RTSP streaming server in our [open source] product. I'm
trying to assess how feasible it would be to upgrade to the latest version of
LIVE555 in the near future. Obviously there are challen
But why would I not want the protocol? I would stream to the server, that
server would then make the stream global for other devices to connect. The
purpose for this is I only want to view a single stream at one time, denoted
by the username of the user, which will be the name of the stream, if tha
It does not. I am going to be streaming globally and am using a global server
to direct all the traffic, creating rtsp streams for each device.
Original message
Subject: Re: [Live-devel] Question about live streaming
From: Ross Finlayson
To: LIVE555 Streaming Media - developm
Hello,
I am currently building an Android application designed to stream encoded
video (live) from each phone to a different phone, and I play to use Live555
as the server. I read that to support live streaming to edit the
OnDemandRTSPServer, as well as make a few other changes. I did said chan
13 matches
Mail list logo
