im just updated VLC to last 1.1.2
if im play this rtsp://184.72.239.149/vod/mp4:BigBuckBunny_175k.mov , it open file in 1 sec , show 0:00:00/9:56 lenght … then there is about 10-12 nothing … and after it will start playback …
richard … its same with my stream , i sended U by email … 10-12 sec nothing … after it will start buffering … and after some sec will start playback … and i was tested it with 1.0.5 … yesterday i was updated to 1.1.2 … no change … its the same …
i was set firewall to forward TCP 554 to 1935 …
now works rtsp://ip_of_wowza/live/stream_name , without specification of port 1935 … but delay is still here …
BTW: i have two NICs in server … one have WAN adress (public) , one have LAN adress (10.0.0.*) … Maybe its any network problem …
i have delay about 10-12 sec in all 3 links … VLC show length of video in 1 sec … but after it is 10 sec pause … and after it will start playback …
i had tested now WowzaMediaServer2.1.2-patch2.zip , and i have still 15 sec lag before VLC start playback rtsp stream , from FMLE … WowzaMediaServer2.1.2-patch4.zip do same lag …
Do i need something to set in Application ?
i was put key frame interval to 1 sec now … still 10 sec lag where VLC do nothing … after it will start playback much qicker , than with 5 sec key frame internal … but initial lag is still there …
try it … rtsp://80.94.54.12:1935/live/test
do U open in it in last VLC ? or what version ? how can U start it quicker than me ? im pinging 80.94.54.12 with 1msec … i heave 100mbit optical line here … i have 5 hops to this server
Výpis trasy k 80.94.54.12 s nejvýše 30 směrováními
1 < 1 ms < 1 ms < 1 ms 10.100.0.1
2 2 ms 1 ms 1 ms 217.75.85.105
3 1 ms 1 ms 1 ms six-swan-gw-fe0-0.swan.sk [217.75.72.5]
4 1 ms 1 ms 1 ms Trestel-gw1.six.sk [192.108.148.165]
5 1 ms 2 ms 1 ms 80.94.54.12
i was looking in console … there was :
INFO rtsp connect 1235096854 -
INFO stream create - -
INFO rtsp describe 1235096854 -
INFO stream play test -
INFO server comment - RTPUDPTransport.bind[live/definst]: 0.0.0.0/0.0.0.0:6978
INFO server comment - RTPUDPTransport.bind[live/definst]: 0.0.0.0/0.0.0.0:6979
INFO server comment - RTPUDPTransport.bind[live/definst]: 0.0.0.0/0.0.0.0:6976
INFO server comment - RTPUDPTransport.bind[live/definst]: 0.0.0.0/0.0.0.0:6977
INFO rtsp play 1235096854 -
INFO server comment - UDPTransport.firstPacket: 0.0.0.0/0.0.0.0:6979
INFO server comment - UDPTransport.firstPacket: 0.0.0.0/0.0.0.0:6977
10 sec wait and after that
INFO server comment - RTPUDPTransport.unbind[live/definst]: 0.0.0.0/0.0.0.0:6978
INFO server comment - RTPUDPTransport.unbind[live/definst]: 0.0.0.0/0.0.0.0:6979
INFO server comment - RTPUDPTransport.unbind[live/definst]: 0.0.0.0/0.0.0.0:6976
INFO server comment - RTPUDPTransport.unbind[live/definst]: 0.0.0.0/0.0.0.0:6977
INFO stream stop test -
INFO stream destroy test -
INFO rtsp disconnect 1235096854 -
INFO rtsp connect 1928203603 -
INFO stream create - -
INFO rtsp describe 1928203603 -
INFO stream play test -
INFO rtsp play 1928203603 -
INFO stream stop test -
INFO stream destroy test -
INFO rtsp disconnect 807043801 -
INFO stream stop test -
INFO stream destroy test -
INFO rtsp disconnect 1928203603 -
somebody was accessed my server , but there was no two lines : INFO server comment - UDPTransport.firstPacket: 0.0.0.0/0.0.0.0:6977
INFO rtsp play 1180151448 -
INFO rtsp connect 764142111 -
INFO stream create - -
INFO rtsp describe 764142111 -
INFO stream play test -
INFO rtsp play 764142111 -
INFO stream stop test -
INFO stream destroy test -
INFO rtsp disconnect 764142111 -
INFO rtsp connect 971591850 -
INFO stream create - -
INFO rtsp describe 971591850 -
INFO stream play test -
INFO server comment - RTPUDPTransport.bind[live/definst]: 0.0.0.0/0.0.0.0:6978
INFO server comment - RTPUDPTransport.bind[live/definst]: 0.0.0.0/0.0.0.0:6979
INFO server comment - RTPUDPTransport.bind[live/definst]: 0.0.0.0/0.0.0.0:6976
INFO server comment - RTPUDPTransport.bind[live/definst]: 0.0.0.0/0.0.0.0:6977
INFO rtsp play 971591850 -
INFO server comment - RTPUDPTransport.unbind[live/definst]: 0.0.0.0/0.0.0.0:6978
INFO server comment - RTPUDPTransport.unbind[live/definst]: 0.0.0.0/0.0.0.0:6979
INFO server comment - RTPUDPTransport.unbind[live/definst]: 0.0.0.0/0.0.0.0:6976
INFO server comment - RTPUDPTransport.unbind[live/definst]: 0.0.0.0/0.0.0.0:6977
INFO stream stop test -
INFO stream destroy test -
INFO rtsp disconnect 971591850 -
INFO rtsp connect 1084285438 -
INFO stream create - -
INFO rtsp describe 1084285438 -
INFO stream play test -
INFO rtsp play 1084285438 -
Richard …
Are U after NAT ? After any router ? or do U direct on internet , and your computer have public IP adress ?
no … that first log was me … i was looked in console , and start VLC to play … there was this 10 sec lag … after this two lines :
INFO server comment - UDPTransport.firstPacket: 0.0.0.0/0.0.0.0:6979
INFO server comment - UDPTransport.firstPacket: 0.0.0.0/0.0.0.0:6977
since i’m authenticating users in a custom module, using onRTPSessionCreate method, i was thinking that it was my botleneck. However, enabling debug and running tests told me that the overhead of user auth is less than one second.
the “lag” is permanent, does not depend on the client used for rtsp (vlc, mplayer, amino box), does not depend on network quality, and even on the same server than Wowza (using mplayer -vo null), there’s 10/20s of lag.
i’ve read all the docs, followed the tutorials on rtp setup/tunning. Nothing helped
i can’t lower the keyframe interval, it’s a matter of bandwidth and quality.
using mplayer, there’s no buffer. It issue the PLAY instruction and then wowza reply with a 200 code (ok), and then, it waits 10 to 20 seconds before the stream starts, when it starts (sometimes, it seams to reach a timeout. Vlc says "no data received within 10s’).
It’s strange to notice that if i use the origin server to view the stream, i takes several seconds but always works, and on the edges, it takes much more time to start and it often does not start at all.
any improvements on this topic?
we really have a problem with this, and its going to be a real bottlneck in our use of wowza.
thanks for any info
Indeed, it seems to improve latency on connection start (from 20s to almost 5 seconds). I cannot increase keyframe interval in production but i will run tests to see the effects.
Are there any drawbacks with this patch?
thanks
Well, maybe this is an issue with VLC itself and not Wowza.
I configured firewall rule to forward TCP port 554 (standard RTSP port) to Wowza’s 1935 and now I don’t see a delay of 20 seconds in VLC any more.
If I point VLC to Wowza 1935 port then I see a delay.
Maybe VLC is doing some magic tricks with ports before it starts playing video.
I tried these URLs from outside with VLC 1.1.2.
rtsp://184.72.239.149/vod/mp4:BigBuckBunny_175k.mov - No delay
rtsp://184.72.239.149:554/vod/mp4:BigBuckBunny_175k.mov - No delay
rtsp://184.72.239.149:1935/vod/mp4:BigBuckBunny_175k.mov - Delay 10-20 seconds