Web push notifications are a great way of re-engaging and retaining users after they leave a website: They are an effective, light-weight, real-time complement to e-mail marketing campaigns. Let’s see how to set up web push notifications for your web app in a few simple steps!
-
Quickstart: Web Push Notifications
-
How Bundler changes your ENV, and how to change it back
-
Headless Chrome on EC2
-
Wowza powered by M3 and G2 instances on AWS
This blogpost is continuation of ffmpeg/ffserver network latency benchmark
Today, I will focus on delay introduced by Wowza. As the previous blogpost showed the source of the delivery delay which is not the network latency but rather the computation itself I will try to explain how to reduce that waste of the time.
Research
At he beginning we have to find what exactly does cause the delay. After deeper research I have found what follow:
- transcoding to multiple video/audio formats
- synchronising for KEYFRAME inserts
-
Video streaming benchmark with ffmpeg, ffserver, wowza
I had a chance for deep research and test of video/audio streaming techniques. My testing stack is based on Wowza which worked good enough for simple solutions. I have decided to extend that model so there was a need to research much deeper for techniques and find out the cutting-edge technology of this days…
-
Simple OSX bi-directional video chat using ffmpeg, ffplay and wowza
In this blogpost I will try to present how to set up a very simple video chat application for 2 users. I will call them Chris and John for simplicity. In short, each of them will publish the video and audio. The other side will subscribe to video and audio of the publisher. For instance, Chris will publish video/audio and John will subscribe for it. If both John and Chris will publish/subscribe we achieve “video chat” connection.
For simplicity I will describe the LAN (local network) solution. However it is fully scalable on the entire web.