I know live555 is an event model application and thread safety must be added if
needed.
I pull and record from hundreds of cameras. Because of some OS limitaitions I
can only wait on a maximum of 64 events.
So I have threads called processors for each group of 60 sources. Each of these
has the
> I have noticed that many items are not initialized on construction.
> Mostly this shows up during incomplete usage by the programmer, me, but it is
> important to note that the checks for null that are in the code fail when in
> DEBUG on Windows.
Have you found any examples of this in our
> I'm trying to determine the NAL unit type of incoming H264 data in
> ::afterGettingFrame().
It's easy. According to the H.264 specification, the "nal_unit_type" is the
last 5 bits of the first byte of the NAL unit (i.e., of each 'frame' delivered).
Ross Finlayson
Live Networks, Inc.
http://w
Just an FYI.
I have noticed that many items are not initialized on construction.
Mostly this shows up during incomplete usage by the programmer, me, but it is
important to note that the checks for null that are in the code fail when in
DEBUG on Windows.
GCC generally zero's things, Microsof
Hello,
I'm trying to determine the NAL unit type of incoming H264 data in
::afterGettingFrame(). My goal is to send the data to ffmpeg, and I'm
basing my approach on what is described in this thread:
http://comments.gmane.org/gmane.comp.multimedia.live555.devel/7743
Can anyone point me in the ri
