Why a connection attempt to a working media server might fail: Red5, FMIS and Wowza by default only accept  rtmp connections over port 1935. This will work fine for most home Internet connections however when your user is behind a corporate firewall/network he might hit 2 major restrictions: NO traffic/connections to non standard ports like 1935 (default port for rtmp). Traffic is only allowed to standard ports like 80 (http) and 443 (https) . The solution for this is to configure the media server to accept  rtmp connections over ports 443 and 80 . NO non-http traffic allowed (or a proxy server is used). The solution for this is to configure the media server to accept  rtmpt connections. Rtmpt is[…]

2009 has been a great year for us, we’ve learned a lot and we’ve made big progress as a company and we feel 2010 is going to be even better. Everybody is back now from their NYE vacation (support should be again up to speed) and we’re deciding on directions to follow in 2010 with our business and products. Here are some of them: AVChat Instant Messenger is a new product we’re working on. We have a lot of great ideas for it, hopefully we will have something to show in March. Each product will have it’s own website. We’ve already started doing that with HDFVR and soon the Flash Audio Recorder will also be moved to its own website.[…]

Hardware accelerated playback of h.264 content in Flash Player 10.1 beta actually works! Usually when watching any HD video on the Vimeo HD Channel my CPU would  spike to about 40-50% usage. But now, after installing Flash Player 10.1 beta on my laptop, the playback process is handled by my GPU thus leaving the CPU to attend to other tasks. CPU usage with Flash Player 10.1 beta has dropped to about 10-20% (from 40-50%)! For now hardware accelerated playback is only available on the Windows version of Flash Player 10.1 beta and only for h.264 video content, but it’s a great step in the right direction.

Error 1: If, when trying to connect using AVChat 3, you are getting this error message: Connection failed, media server might be down or firewall might be blocking the connection! like this: You need to check: your rtmp connection string inserted in avc_settings.xxx the media server might not be running (you can check if Red5 is running by going to http://yourred5server.com:5080/) the media server might have not started properly (thus is not running, you can check the logs in Red5/log for any ERROR messages during startup) there is a firewall on the media server blocking TCP traffic over port 1935 (and 5080) the user trying to connect is behind a firewall that blocks the connection (either a personal one installed on[…]

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.[…]

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[…]

Adobe released last week FMS 3.5 and FMLE 3.0 which you can now download and/or purchase. There are several interesting new features which you can read about here: New features in Flash Media Live Encoder 3.0 New features in FMSS 3.5 and FMIS 3.5 Prices remain unchanged with $4500 for FMIS and $995 for FMSS. Because this is not a new major version upgrade prices are rather cheap with $349 for the FMIS 3.0 to 3.5 upgrade and $249 ofr the FMSS 3.0 to 3.5 upgrade. These prices are available in the US store. The FMLE continues to be free.

Adobe announced yesterday Flash Media Server 3.5, the next version of FMS. Just a few major changes this time: Apache is built in and can be used for delivering media files including jpeg, swf and video files. Dynamic Streaming : out of the box switching between streams of different bit rates. DVR : rewind on live streams. Kevin Towes, Product Manager for Flash Media Server, has a long blog post detailing the above 3 features and some useful links you might want to check out, including this demo website with some great example of HD flash video: http://www.streamflashhd.com/ FMS 3.5 is just announced, it is not yet available for download but hopefully it will be released soon!