No, the network is clean. It appears that there is a problem in
timestamp conversion from RTP packets to PES packets.
I had to modify MPEG2TransportStreamFromESSource.cpp, exclude PTS
from the PES header by assigning
fInputBuffer[7] = 0x00; // instead of 0x80
fInputBuff
hello
can i use morgan rtp filter on the pda
think you
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
In my case, almost all NAT will not allow the RTP packet pass-through. I do
believe that the NAT(router) actually don’t know where the packet should send
to.
Before the server(S) sent the RTP packet to the client(C) , S-C only have a TCP
connection for RTSP. The NAT (router) can’t read the R
No, the network is clean. It appears that there is a problem in timestamp
conversion from RTP packets to PES packets.
I had to modify MPEG2TransportStreamFromESSource.cpp, exclude PTS from the
PES header by assigning
fInputBuffer[7] = 0x00; // instead of 0x80
fInputBuff
I tried this and the result file stutters a lot in VLC.
I also tried to stream this TS using BasicUDPSink and it also
stutters in VLC and if played on Amino set-top box.
What can be a reason for this?
Packet loss, perhaps? (You can check for packet loss using the "-Q"
option to "openRTSP".)
Ralf,
2008/2/22 Ralf Buhlrich <[EMAIL PROTECTED]>:
> Hi Aravind,
>
> I just enhanced the MPEG2TransportStreamFromESSource and the
> MPEG2TransportStreamMultiplexor to embedded H.264 in a MPEG2TS
> to stream stream it via RTP.
>
Are you able to share this modification with us / live555?
Regards
Hi,
we use live555 as a client receiving videos from RTSP servers. The
servers are MPG4 encoding boxes that are rather unstable and can crash
abruptly terminating the network connection.
As a workaround I plan to close RTSPSource if it has not received any
data within the given timeframe. The que
Cristiano Belloni wrote:
> [EMAIL PROTECTED] wrote:
>
>> 1. Are you inheriting from FramedSource, from DeviceSource, or
>> modifying DeviceSource?
>>
> Inheriting from FramedSource.
>
>> 2. Is "isAwaitingData()" function an abbreviation for
>> "isCurrentlyAwaitingData()", or are these
[EMAIL PROTECTED] wrote:
> 1. Are you inheriting from FramedSource, from DeviceSource, or
> modifying DeviceSource?
Inheriting from FramedSource.
> 2. Is "isAwaitingData()" function an abbreviation for
> "isCurrentlyAwaitingData()", or are these separate functions?
It's a separate function. Retur
