but then, in case of multiple NAL's, the frame or the fragmenter will
try to fragment the data buy themselves, which I donw want to happen. I
want to use the NAL size as received from my hardwre encoder.
Is there a way from within a single call to doDeliverFrame to send all
the NAL's (send more t
lets say that I do read all available data from the socket on the
first call to doDeliverFrame which was triggered by the data
arriving to the socket.
but if I feed the framer only in one NAL at the first call to the
doDeliverFrame
No, you wouldn't do that. You would need to feed *all* of the
lets say that I do read all available data from the socket on the first
call to doDeliverFrame which was triggered by the data arriving to the
socket.
but if I feed the framer only in one NAL at the first call to the
doDeliverFrame, what will trigger the call to the next doDeliverFrame
(since the s
what do you mean by "treat the data as a set of (>=1) NAL units."?
do you mean that I should read it and use the fNumOfTruncatedBytes
if needed?
No, I just meant that you should - in your socket read handler - read
*all* of the available data from the socket, rather than just one NAL
unit's w
Thanks Ross,
what do you mean by "treat the data as a set of (>=1) NAL units."? do
you mean that I should read it and use the fNumOfTruncatedBytes if
needed?
My hardware is alreay generating NAL's with the correct size.
what is the correct way if I want to work with discrete NAL? how can I
force
exit() will run functions installed with atexit(), and destructors for
C++ static objects, and so on. abort() will kill the program quickly
rather than calling these functions while the program is already in a
bad state (just like a failing assert()).
OK, FWIW (not much :-), I'll change the "ex
On Wed, Dec 30, 2009 at 2:40 PM, Ross Finlayson wrote:
>> Without this patch my VLC exists, pretending everything went fine.
>
> And why do you feel that "abort()" is better than
> "exit()"? (Because you can catch it in a signal handler?)
Because exit(0) means program exited without issue. You
On Wed, Dec 30, 2009 at 2:19 PM, Ross Finlayson wrote:
>> I failed to find a git/svn repo for live555. I think it would ease
>> development if there was one. Any reason why there is none?
>
> Because only one person (I) ever adds code directly to the code base.
That's not a valid point. Wine does
Hi everyone,
some month ago I started with h264 video enconding and decoding (Intel
Perfomance Primitives) and now I'm really interessted to transport the Frames
via the liveMedia modul.
But I have some problems with the classes (H264VideoStre... and
currentNALUnitE...), is there someone who ca
On Wed, 2009-12-30 at 05:40 -0800, Ross Finlayson wrote:
> >Without this patch my VLC exists, pretending everything went fine.
>
> As I noted in my earlier response (to someone else's question), this
> call (and other calls) to "exit()" should be getting called only if
> there's a serious proble
Without this patch my VLC exists, pretending everything went fine.
As I noted in my earlier response (to someone else's question), this
call (and other calls) to "exit()" should be getting called only if
there's a serious problem in your code. Are you actually seeing
this? If so, you should
I failed to find a git/svn repo for live555. I think it would ease
development if there was one. Any reason why there is none?
Because only one person (I) ever adds code directly to the code base.
(Also, we provide support for the latest version of the code only.)
--
Ross Finlayson
Live Netwo
1. The first one is easy. We have compiled the openRTSP
functionality to a library to be more flexible. Since a WSAStartup
call is necessary on Windows, this is correctly done in the
initializeWinsockIfNecessary call - the "f...ing lame comment" in
the source code is so true :). Well, the obvio
I see that the schedualer is launching my deliverFrame about every
1-2msec, when I got multiple descriptors in the socket.
The problem is that when I got lost of descriptors (~80) this can
take up to 160 msec which is way beyond my frame size which is 40
msec (PAL)
1. Am I doing this wrong
Hi,
Without this patch my VLC exists, pretending everything went fine.
Pierre.
exit_to_err.diff
Description: Binary data
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
Hi there,
I failed to find a git/svn repo for live555. I think it would ease
development if there was one. Any reason why there is none?
Pierre.
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-deve
Dear all,
we have compiled the live media source code on Windows and are using it to
retrieve media with RTSP/RTP. It runs very well and stable, however we have
some questions as follows.
1. The first one is easy. We have compiled the openRTSP functionality to a
library to be more flexible. Sinc
Hi All,
I am using the LIVE555 to stream h.264 bitstream
My source is making NALS with limited size so each frame may contain
more than 1 NAL.( I recived all of them together from the HW).
After I received them I am creating small descriptors describing each
NAL (pointer, size) and send ALL of th
18 matches
Mail list logo
