My apologies for taking so long to reply, OSCON has been taking up all my
time this week.
> I *might* be able to modify the "readSocket()" function to better handle
> this case, but I don't want to risk inadvertently messing up higher-level
> code that uses this function by mishandling cases when
I am troubleshooting an issue similar to Dirk Dugger when receiving RTP
over TCP via the RTSPClient class. If the server closes the connection mid
stream, the client gets no notification.
I have traced the problem to the readSocket() function in
GroupsockHelper.cpp where recvfrom() is used to get
I have a similar issue to that reported by Philippe Clavel in April where
RTSPClient receives a SIGPIPE from closed socket and terminates the
process. In my case, I am not using the RTSPServer class, so the fix
implemented in that class does not help me. Instead, I have adapted that
fix for the R
>
> Correct me if I am wrong, but currently testRTSPClient receives RTP
> packets. Is there a way to receive the individual h264 frames, Ie. parse
> the incoming packets and provide each individual h264 frame (each i frame
> and p frames).
>
>
In your MediaSink derived class (called "DummySink" in
>
> I am just starting to evaluate live555 and would like to know if there is
> a way to access the list archives so I can check if my questions have
> already been answered before I ask here.
>
The archives are available here:
http://lists.live555.com/pipermail/live-devel/
The easiest way to sea
> OK, the "typedef" has been removed in the latest version of the code (just
> installed).
>
>
Thanks Ross. I'm finally seeing zero warnings when compiling Live555.
-Barry
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com
I'm getting compiler typedef warnings for liveMedia/include/Locale.hh, line
52 (Live555 version 2012.04.21) which looks like this:
typedef enum LocaleCategory { All, Numeric };
Shouldn't the LocaleCategory type name come at the end, like this?
typedef enum { All, Numeric } LocaleCategory;
-Bar
This patch resolves a typedef conflict for Boolean between
UsageEnvironment/include/Boolean.hh and the system provided MacTypes.h on
OS X when using Xcode to compile Live555.
osx_boolean.patch
Description: Binary data
___
live-devel mailing list
live-de
At a minimum, you will probably need to add the MPEG start code 0x0001
to each frame before passing it to your decoder. See
H264VideoFileSink::afterGettingFrame1() for an example of this.
You may or may not need to deal with parsing the SProp string depending on
whether your H.264 stream cont
For H.264, the payload delivered in the afterGettingFrame() method is a NAL
unit. The big ones are (usually) the coded video frames (there are various
types depending on your encoder settings) and the small ones are (usually)
SPS and PPS NAL units which contain various settings needed by your
deco
, Feb 27, 2012 at 2:39 PM, Barry Stump wrote:
> I am working on an iOS project similar to what you describe: H.264 video +
> AAC audio with Live555 and FFmpeg handling RTSP and video decoding
> (respectively). I recommend basing your work on testRTSPClient.cpp, with
> an Objective-C++ wrapp
11 matches
Mail list logo
