The server broadcasts live source frames (PAL or NTSC) and the client side
receives these frames and put them on a small display. We are looking for a
way to write the FPS (Or maybe PAL, NTSC) data to the SDP on the server side
I suggest subclassing each "RTPSink" class that you use, and redefin
For calculating the duration of a frame in h263, the temporal
reference (TR) of the current and next frame has been used.
My query is why is it being used for determining the duration of the frame?
Because it seems to work.
Is there any way to determine the frame duration or the frame rate
Hi Ross,
We are writing the server and the client sides with Live555 library.
The server broadcasts live source frames (PAL or NTSC) and the client side
receives these frames and put them on a small display. We are looking for a
way to write the FPS (Or maybe PAL, NTSC) data to the SDP on the ser
Hi,
For calculating the duration of a frame in h263, the temporal reference (TR) of
the current and next frame has been used.
My query is why is it being used for determining the duration of the frame?
Is there any way to determine the frame duration or the frame rate of a h263
video?
Thanks
Does Live555 support setting maximum connection number? If we
set 5, the 6th connection request will be refused.
No; however, you could easily implement this yourself by subclassing
"RTSPServer" to include a connection counter, and then managing this
by reimplementing the virtual functi