Changelog

Starting with Chrome 60, camera and microphone access on insecure origins is deprecated. More details in the blogpost.

We slightly tweaked the UI of the dashboard. Editing the current environment is now easier.

You can now record using the WebRTC client in Firefox also. Huuraay!

The billing page is now split into usage and billing for a better overview. Additional information was also added to the billing history table: vat sum, total sum, bet sum, link to invoice, etc.

Some codecs are like those pesky kids that no one wants to play with. AMR-NB audio codecs is one of those examples, but we’ve decided to be nice and convert it to standard AAC audio codec anyway.

While recording, the timer will start to, you guessed it, countdown from the maximum recording time towards 00:00.

The hiding of he Connecting message is now synchronized with the time the recording actually starts.

You wanted to only show the live feed and implement your own custom controls? Well this is your lucky day.

When the menu is not shown, you now also have the option to hide the recording counter (set st to 0 in the embed code) and the mic/cam options (set ssb to 0 in the embed code)

Users liked the way the HTML5 client showed the live feed after playback and asked for the same behavior in Flash, so here you go, live feed is now.. well live :)

Playback is no longer done through webRTC streaming as it was not optimal. Instead a simple HTML5 video tag is used which loads the freshly recorded video.

Some icky bugs still lurked around in the HTML5 client. Today we’ve fixed the issue with recording not working if trying to record while the playback was paused.

The onRecordeReady event now also returns the recorder type (flash or webrtc)

Even more improvements to the HTML5 client. Now it is smart enough to detect when only the microphone is blocked and act accordingly

Some bug squishing going around here. getPlaybackTime() now gets properly called by the HTML 5 client

You can now continue to see your beautiful self in real-time even during playback

We’ve implemented a new UI element to show the sound captured by the microphone in real time, similar to the way it is displayed in the Flash client.

Fixed issue that caused the wrong device names to be saved when a recording was made with the HTML 5 client

We’ve made updates to our HTML 5 client code, so that when a user only gets ICE candidates of type host (in which case a connection is not possible to the Internet) a appropriate error message will be displayed.

Improved documentation regarding the differences between the Flash and HTML 5 client

Updated the documentation regarding the requirement for a CORS header when using custom language files or custom video quality profiles.

We’ve added a load balancer for our 2 client delivery servers ensuring high availability if one of them ever decides to go down in flames.

We’ve moved all the client files to 2 new client delivery servers, separating the delivery from the transcoding process. This puts our platform on track to:

1. deliver the video recording clients via a CDN
2. use much faster hardware video encoding on our transcoding servers

The entire webhook data is now properly URL encoded making it easy, simple and clear for anyone to work with our awesome webhooks.

We’ve made some minor tweaks to our (beta) HTML5 video recording client:

• Disabled buttons are now less obvious => active buttons (record, stop, play) are more obvious.
• Bigger timer font makes it easier to understand

When testing using URL’s with dashes it reported the URL as invalid. We’ve updated the regular expression used for URLs to allow the “-” char.