e555.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson
Sent: 5 octobre 2012 01:56
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Suggestions
Thanks. These two changes will be included in the next release of the software.
Ross Finlayson
L
Thanks. These two changes will be included in the next release of the software.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
Hi,
I have two suggestions of modification to the code. Well, it is at least
things I've added to the library I'm using.
The first modification is to avoid compilation warnings under windows. It is
just to add the file "errno.h" in "Netcommon.h". This way the redefinition
warnings do not app
I'm not sure I totally understand what you're asking/suggesting (but since you
use a non-professional email address, I really don't care :-). But it sounds
like you want to perform RTSP client operations in a 'synchronous' way, whereby
you block - waiting for the response to each RTSP request -
As a user of your library, i have some problems with your RTSPClient
while integrating it to my app.
So i decide to write my "pains" and my "ideal" client example for testRTSPClient
-- What i need to create client? Do i have to know "env" or "task scheduler?
string rtspUrl = "rtsp:///video.h
No, the right solution is to properly implement the RTP payload
format described in RFC 4175. This will require implementing:
1/ a new subclass of "MultiFramedRTPSink" - e.g., called
"UncompressedVideoRTPSink" - for transmitting RTP packets of this
payload format, and
2/ a new subclass of "Mult
Hi,
I'm using liveMedia library for streaming from a Flir thermocamera (A320) that
can stream MPEG4 format, uncompressed video and a proprietary format (FCAM).
For MPEG4 streaming, I used liveMedia with ffmepg libraries, without any
problems.
I needed also to stream the uncompressed video (Y1
That's pretty much what I thought, you seem pretty knowledgeable in this
area and I wanted to see if anything popped out at you.
I haven't got much of a response from the FFMPEG list so I think I
pretty much on my own.
Thanks
Matt S.
Ross Finlayson wrote:
8. Here is where the 80% comes in. Mos
8. Here is where the 80% comes in. Most of the time it the FFMPEG
decoder sees the new frame size and correctly handles it and
everything is good but about 20% the time it doesn't and FFMPEG
crashes.
Therefore, there's a bug in FFMPEG. That's what you need to address
first (on some other mai
I'm looking for suggestions on the proper way to signal to the client
that the frame size has changed in an H264 stream.
What I have actually works about %80 of the time.
Here is what I have.
1. Server is encoding camera data in real time using X264 and serving
the data via Live555 RTSP server
10 matches
Mail list logo
