x.8.8 Release

The x.8.8 release is out today!

An important part of this IceLink release is compatibility with future versions of Chrome. Starting with Chrome 48, the DTLS stack in the browser is being updated to 1.2, and the BouncyCastle (DTLS) libraries included with previous versions of IceLink's .NET and Java SDKs will fail to connect when Chrome is in the answering role.

Other highlights since x.5.5:

• Especially on iOS and Mac, stability has been improved in all products by eliminating several race conditions that could emerge under certain threading scenarios.
  
  
• tvOS has received some more IceLink love with the ability to process incoming audio from WebRTC endpoints. Audio capture is still not available in tvOS, but we are ready when Apple decides to open it up.
  
  
• The Java webcam capture provider in IceLink has been significantly improved. It handles late frames far more intelligently now. If the device is having trouble keeping up with the resolution/encoding, the frame rate will drop to compensate instead of appearing to lag.
  
  
• Full iOS/tvOS/Mac bitcode support for IceLink, WebSync, and TheRest. This has once again resulted in an increase in the size of the download. Starting with the next major release, we will start packaging the SDKs by platform as well as by product so that .NET developers don't have to download the gargantuan files that are iOS static libraries.
  
  
• IceLink now has built-in functionality to let you monitor microphone volume levels using the new LocalMediaStream.OnAudioLevel event.
  
  
• The usual round of minor bug fixes and cleanups.

Head on over to the Downloads page to pick up the latest!

Development of the next major release of the product suite is well underway. We have received a lot of suggestions and ideas over the past couple years and seen many new and interesting use cases emerge. We are staying true to our roots as we go - keeping the API as consistent as possible, not over-engineering or under-engineering, simplifying the things that consistently cause confusion, expanding testability, and increasing the capabilities of the platform in powerful new ways through an innovative API. We're very excited to share this next generation with you in 2016!