We are happy to announce Encoding.com’s third platform release of 2013. The release went live last night at 11:00PM PDT and includes a slew of innovative new features, performance enhancements and bug fixes. Here are the details:
Multithread FTP ingest
Get ready to tune up your source FTP servers! Encoding.com can now ingest your source media using multiple FTP threads for up to 3x faster ingest than our previous single threaded version. To give this update a test simply add ?multithread to the end of your existing FTP path. For example: ftp://user:password@server/path/movie.mp4?multithread
Multithread S3 transfer is now a default
After a few months out in the wild, we have now updated multithread S3 as the default for all jobs using S3 as a storage location. No need to add ?multithread to the end of your S3 source path anymore and no need to remove it if you already have it hardcoded into your workflow. Enjoy the overall reduction in job time when using S3 as source or destination.
We are using the WebVTT HTML5 standard to create a thumbnail format that supports time synced thumbnail previews of your video that are displayed whenever users hover over the progress bar of their player. This is great feature for quickly scanning and navigating video content. We worked closely with our good friends at LongTail Video on this feature to ensure that our VTT output works perfectly with the new JW 6 Player’s support of tooltip thumbnails. To test this feature, use <use_vtt>yes</use_vtt> parameters for the thumbnail section of your API call. This will produce a single .vtt file with a default of 4 thumbnails in a row (adjust the vtt_line_size parameters to change from default), a default width of 120px (taken from the center of the video) and a default interval of 10 seconds.
New version of our HLS segmentor
We have released a new version of our HLS segmenter for customer testing. The new version has lower overhead and produces less media stream validator errors in certain edgcases. The new version has been launched along with our existing v.1 segmentor to avoid any disruptions to production HLS workflows. Please compare this HLS output and let us know what you think. Simply add <segmenter>v2</segmenter> to the “HLS" section of your API request.
OAuth2 authentication support from YouTube destinations
We now support YouTube’s new authentication method, OAuth2, for delivering Encoding.com output files directly to your YouTube account. To authenticate your account with YouTube, go to the “My Account" tab of the client interface and click “Authenticate my account with YouTube"
Notification and API logs are now available in the web interface
To help accelerate your API integration with Encoding.com we have made a log of all job completion notifications as well as a log of all API requests – all available from the Enocding.com client interface. You can sort the requests and responses by API call, IP address, date, status, url and more.
Vid.ly usage stats
New graphical interfaces will display your live Vid.ly usage stats including: number of URLs(by type and status), data transfer and storage. View these reports on a per URL basis or globally across your entire account.
Vid.ly integration with Google Analytics
Add your GA property ID code to the “My Account" tab of the Encoding.com cleint interface and track detailed Vid.ly usage stats including time spent on each video, total visitors vs. unique visitors, geographic breakdown of your video traffic, browsers and mobile device traffic, and much more.
New Vid.ly service offerings are now available using the Encoding.com client interface
Vid.ly Lite – A slimmed down version of Vid.ly that generates 5 output formats and maps them to popular browsers, tablets, and smartphones.
Vid.ly Lite HLS – A version of Vid.ly Lite that includes dynamic framesize HLS mapped to iOS as well as OTT and Android devices that support HLS.
Vid.ly HD – Includes a 720p output for desktop browsers along with Vid.ly standard outputs.
Vid.ly + FreeWheel integration for video ad serving
Now available via the Vid.ly API and the Encoding.com web UI, existing FreeWheel customers can easily integrate video advertisements into an individual Vid.ly URL or globally across all active Vid.ly URLs associated with the account. Visit the Vid.ly --> FreeWheel section of the Encoding.com web interface to enable FreeWheel for your account and specify your FreeWheel account configuration parameters: AdServerURL, AdManager URL, Network IDs, PlayerProfiles, VideoAsset IDs, SiteSection IDs etc (provided by FreeWheel) to enable ad targeting. When a visitor views a Vid.ly URL with FreeWheel enabled, Vid.ly will pass their user information to the FreeWheel ad server and they will receive a targeted video advertisement (pre/mid/post roll or banner overlays). Vid.ly currently supports video player advertisements for both HTML5 and Flash players.
And tons of bug fixes and stability improvements…
- We can now encode videos containing speex audio and low bitrate PCM audio into Dolby HE AAC and AAC audio
- Edge case bug fixed where the audio stream still image from HLS was not created
- Watch Folder users can now choose the Encoding.com Private Cloud as a processing region
- The audio_bitrate parameter is now included in the GetMediaInfo response
- S3 destination URLs can now have more than 218 characters
- Encoding.com client interface users can now delete saved custom presets
- Number of CPU threads used during processing is displayed in the encoding queue
- Added support for closed caption time offset flag when extracting captions
- Hard CBR will now be displayed in GetStatus response
- HLS encryption bug on iOS 6