There seems to be a little confusion about what’s actually going to be offered. The title of the release states, “AudioCodes Announces WebRTC Phone.” The copy goes on to describe that the hardware will be extended to provide native support the Opus codec. This capability is projected to be deliverable in Q4-2013.
Since taking up my new gig with ZipDX and Polycom a splendid HDX-4500 has graced my home office. It’s without question the most sophisticated end-point device that I’ve encountered. It’s a real treat to use, especially since I do so many calls using video these days.
The HDX is large enough that it gets a desk of it’s own, located across the room from my primary desk, desktop PC et al. When I’m using the HDX I always have my laptop on that desk as well.
The trouble is that I’ve had some difficulty getting the lighting correct for video calls. I’ve muddled along trying different solutions with what I’ve had on-hand, and playing with moving things around the space. Recently I’ve come to think that I need to take more significant steps to provide consistently good lighting.
Not long ago Ed Tyson of Expert Shield contacted me with an offer of his companies screen protection for our Android devices. As our various phones (Nexus 4) & tablets (Nexus 7) are presently naked(!) I decided to take him up on his offer. We’re just awaiting arrival of the goods.
That said, I found that the clear protective layer for the front of the phone was a bit on the thick side. While it worked well enough as protection I found that it felt a little gummy to the touch. It subtly changed the feel of the phone in use, something that I’d like to avoid if possible.
Stella and I were initially using the Poetic Borderline Bumper case for Google Nexus 4 but we both stopped using them in recent weeks. Stella found that it made the power and volume buttons awkward to access. Mine simply tore near the power connection, then started to come apart.
Think back to the handful of new audio codecs that have been released over the past few years; CELT, SILK and Opus to name a few. Then there are the handful of proprietary codecs that have become available under more attractive licenses. Polycom’s Siren family come to mind on that front. In all of these cases I have observed that the Freeswitch development team are typically amongst the very first to implement any new codec.
In recent weeks they have added support for G.719, an ITU standard codec created by Polycom and Ericsson. With a sample rate of 48 KHz, G.719 is a full-bandwidth codec, supporting a useful audio channel of 20 Hz- 20 KHz. It does so with end-to-end delay of only 40 ms and at bit rates from 32 kbps to 128 kbps. It also supports stereo audio.
When experimenting with a new audio path I like to take measurements. Long ago, in an age of techno-pre-history known as the late 1980’s, I craved what were then an emerging class of computerized test instruments, like the Audio Precision System One. Happily, today such costs are unwarranted given the current class of programmable smart devices. I’ve been very happy with Audio Tool For Android running on my Nexus 7 tablet.
If I am to trust the measurements that Audio Tool allows me to make I need to start by confirming the validity of it’s measure using a known reference signal. I was also making use of the Zoom H2 Handy Portable Stereo Recorder, so I decided to record the output of the sweep generator in Audio Tool to the H2. Then I tool the resulting WAV file into Adobe Audition to see what resulted.
It arrived today. It took only a few minutes to come to the conclusion that it was not a solution to my problem. While I opened a trouble ticket with the company to pursue the matter, I discovered a FAQ entry claiming that the Nexus 4 always sets the HDCP copy protection flag in the video stream. Thus no downstream device will be able to record the output of the Nexus 4.