We’ve put a new build of AVChat 3 up today, this build (284 ) includes mostly bug fixes for the Red5 version of AVChat 3 and several small enhancements. Enhancements: new protection against spam messages (if a user sends the same message over and over again, he will be the only one seeing them, other users will only see the message once :D) the Red5 server side files are now compiled to be compatible with Java 1.5 when autostartCameras is ON, you will not start to view your webcam automatically anymore (when you publish it) the positioning algorithm for other people’s webcams has been updated the “who is typing” messages shown in the text chat can now be disabled from[…]

We have rearranged the documentation area on our website and we’ve added some new documentation for AVChat 3: Changing the background color and background image Changing the size of the video chat area Changing the join/leave/buzz/new text message sounds Overview of design options in AVChat 3 Dropping users into rooms automatically Last week we’ve also had some posts on some interesting features in AVChat 3, if you missed them here they are again: Display of streams delay Recording video streams Dynamic bandwidth usage reduction We are also preparing a big paper on security features implemented in AVChat 3 and I tell you, it doesn’t get any more secure than this! ūüôā

In the side menu for other people’s web cams, AVChat 3 now shows an estimation of how much it takes for the video and audio data to travel from the broadcaster to the viewer (trough the media server) . We call this value trip time but its also known as latency. The value is not always 100% exact but it is a really good estimation! For one to many broadcasts the trip time value¬† is not important, live TV broadcasts generally¬† have a 5-15 seconds delay to give broadcasters time to censor any audio needing censorship A low trip time is really important when the audio/video communication goes both ways, for example when 2 people are in a video conference.[…]

This article has been updated as of 30 April 2013 to add info about recording to .mp4 files and the H.264 video codec. AVChat 3 uses a media server (like Red5 and FMIS and Wowza) to stream audio and video between users. The audio and video data travels from the broadcaster user to the media server and from there to the receiver/viewer . While it passes¬† through the media server the audio and video data can be captured and stored in .flv file,¬† or, starting with build 2330, in .mp4 files.¬†The file type that will be created depends on the video codec being used (Sorenson Spark or H.264). Codecs being used… The audio data will be encoded with wither the[…]

AVChat 3 , as all the other flash video chats out there, uses a media server (like Red5 and FMIS) to stream audio and video between users. The audio and video data travels from the broadcaster user to the media server and from there to the receiver user. Even tough there is no receiver (if there is no one watching) the stream still travels from the broadcaster to the media server, thus consuming bandwidth on the media server and on the broadcaster’s Internet connection. This is where AVChat 3’s “Dynamic Bandwidth Usage Reduction” kicks in. When this feature is activated (it is by default) the broadcaster streams audio and video to the media server ONLY WHEN IT HAS VIEWERS. Here[…]

Red5 0.8 support We are glad to announce that AVChat 3 for Red5 0.8 is now available. Only Red5 0.8 is supported! We do no plan to support Red5 0.7 or earlier versions because¬† 0.8 is the most stable Red5 release yet and we encourage everyone to upgrade their Red5 installation if they have not done so already! To purchase AVChat 3 now visit the purchase page! When you purchase AVChat 3 you will now get both the FMIS and the Red5 media server files. Other Enhancements after logging in the chat, when joining the first room the welcome message is shown at the bottom of the existing text chat (history) you can now change the amount of lines of[…]