Posts to the mailing list tell me there is some unspecified problem with
the MP4/QuickTime file format related to A/V synchronization, and this
is given as the reason there is no MP4FileServerMediaSubsession class in
the library yet. (Or equivalently, an MP4FileServerDemux class, so you
could
Currently live555MediaServer requires CBR or near-CBR files when
streaming from MPEG-TS. The explanation I've read on the list is that
this is because it makes determining the pacing of frame delivery
easier. As I understand it, the server has an internal model of the
video bit rate, and it c
>> This is my scenario:
>> Create a new ProxyServerMediaSession - it in turn calls
>> DESCRIBE on the backend.
>> Call RTSPServer::removeMediaSession or
>> RTSPServer::deleteMediaSession before that DESCRIBE call completes. (the
>> ProxySMS instance is deleted but
> Any idea where that handle leak originates?
No.
> Could it be Windows specific?
I suppose that's possible...
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.
To verify if the handle leak I've noticed is in my code or in liveMedia I
wrote a really simple program that just start and stops the event loop. I
took the latest testRTSPClient.cpp and just replaced main() with a loop that
initiates a thread which starts the event loop - StartEventLoop(). The mai
>> Please advise how to proceed, will there be a fix in future release?
>
> Yes, because you appear to have found a bug in the code.
>
> To help me debug this, could you please re-run the "LIVE555 Proxy Server"
> with the "-V" (upper-case V) option, to generate diagnostic output, and
> please s
> What is the best way to rewrite the code so it will cleanup any open backend
> connections and handlers or protect against this scenario?
That's for me to worry about; not you :-)
> This is my scenario:
> Create a new ProxyServerMediaSession - it in turn calls
> DESCRIBE on t
