Need low latency on Wowza 2 Dev Edition
My first post and I think I will be out of my depth but here goes. I want to use the the V2 version for a "point to point" video service - the video signal will only be one way - from our location to the desired destination. Ideally, we will require "comms"to and from the destination/target point but that is in hand.
So ! Any ideas on how we can send a 1 MBPS H.264 AAC single stream to a destination under say two seconds via Wowza2. We find that the human brain finds it a bit irritating ( well mine does) when it has to wait longer than the normal human response for a reply.
Last edited by Ghengiskhan; 03-18-2010 at 12:29 PM.
Is it one way or two way? If it is just one way, what's the frame of reference to know how much latency there is? In anycase, take a look at this post on achieving lowest latency:
Sorry, what is "comms"?
Publishing with Flash client is the best for low latency 2 way applications, video chat. But it doesn't do h.264. Take a look at the VideoChat example in the Wowza examples folder.
1mbs is high for internet delivery. Some users are going to complain about stuttering and slow startup. 400kbs - 600kbs is better.
Last edited by rrlanham; 03-18-2010 at 12:50 PM.
Yes, it is one way. Only the audio will be needed for the reverse feed - for questions and answers. "Comms" is an in house jargon for communications which is usually Motorolas, break out feed from telephones etc.
Let me see if I can give you a scenario. We have a camera ( Sony DVCAM) trained on Joe Bloggs and access to a 1 MBPS upload. Annie Bloggs needs to see Joe but Joe only needs to hear Annie as she is asking all the questions and he has no need to look at her - let's assume she is ugly and we need to save bandwidth.
In short, if we can get a Q's and answers stream over a 1 MBPS stream we will get a pat on the head. One meg on H264 does look good, maybe we are pushing our luck, we will see if we can shorten the buffer on WOWZA 2 - any ideas on how to ?
So it is two way. Video and audio in one direction, audio only in the other, but it's a stream in two directions where latency matters.
Regarding the video, 1mbs will be okay for some users some of the time, but it is not optimal, and will probably be a problem for other users much of the time. 400 - 600mbs h.264 stream would be more successful for more users more of the time, for internet delivery.
You will want Joe Blog's stream to be as low latency as possible. Here is a guide on achieving the lowest latency possible:
For Annie Blog's audio stream you can use built-in Flash encoder, and that's the best choice for this scenario. If you can achieve reasonably low latency with the Video, it could work, but this system would work better if Joe Blog were also using the built-in Flash encoder. It's not worst quality option, but it's the best option for low-latency two application.