[Announcement] Cobalt 9 Release

[Daniel Juyung Seo]

Hello everyone,

 

The Cobalt team is thrilled to announce the Cobalt 9 release!  This is a feature complete and stable release of Cobalt.

 

Cobalt 9 includes Starboard API version 4 for porters and it supports all features required for 2017 YouTube certification. The Cobalt 9 release code is available on Cobalt open source "RELEASE_9" branch. (Read branching/versioning documents for more information)

 

Although not all the features for 2018 YouTube certification have been implemented yet, porting Cobalt 9 with Starboard API version 4 on your system will allow you to easily rebase up-coming Cobalt releases for 2018 YouTube certification.

 

There are newly implemented features, improvements, and simplified code. We have roughly summarized the change list below, and hope this will give you a brief idea about Cobalt 9 changes.

 

Features

• Fully compliant for 2017 YouTube certification.

• Starboard API version 4 is frozen and is 2017/2018 YouTube certification compatible.

• 2017 Certification Requirements

• HDR (High Dynamic Range) support

• Animated WebP

• 2018 Certification Requirements

• MSE (Media Source Extensions): W3C Candidate Recommendation 05 July 2016

• EME (Encrypted Media Extensions): W3C Proposed Recommendation 16 March 2017

• Spherical video support with CSS Spherical Filter Extension

• WebSockets

• Opus Audio codec without Ambisonics specifications

• Accessibility (Screen Reading)

• Better font configuration options

• CSP (Content Security Policy) local mixed content support for DIAL 2.0 smooth pairing.

• Hooks for hardware-accelerated AES to use in SSL transport

• Support for the application exit strategy by 'cobalt_user_on_exit_strategy' in gyp_configuration.gypi

• Suspend on SIGUSR1 and restore on SIGCONT reference implementation to Starboard Linux port.

• Tizen Platform Port: Wayland window system based Tizen platform port is introduced. Special thanks to Samsung Electronics engineers for the contribution. (Contributors: YoungJoon Ahn, Jaeyoung Myo, Sungho Kim) (Tizen code, Wayland code)

 

Certification Tools

Major certification tools(Conformance, MSE, EME, Progressive) are ready for 2017 certification using Cobalt. Please visit Qual-E website(https://qual-e.appspot.com) with the following command:

$ ./cobalt --url=https://qual-e.appspot.com --csp_mode=disable

 

Git Branch

If you have a local git branch tracking RC_9, you have to reset the upstream branch to RELEASE_9 like this:

$ git fetch

$ git checkout <local-branch-tracking-RC_9>

$ git branch -u remotes/origin/RELEASE_9

 

Contact Points

Please contact our support channels if you have any kinds of problems or questions.

1. Stack Overflow: For programming related technical questions with Starboard or Cobalt.

2. Issue Tracker: For bug reports or feature requests.

3. Mailing List: For feature discussions, schedules, and roadmaps.

 

Thank you,

On behalf of the Cobalt team

[Wu Jefferson]

hi Cobalt Team,

  We are also thrilled to hear about Cobalt 9 official release! Thanks for all hardwork put in!

  For the certification tool, how about "Adaptive Bit Rate", "DRM", "SSL", and "Web Audio" sections?

It seems that these pages are still not functioning as expected (UI incorrectly drawn, video not playing).

Can we use this version for certification? Or are there still some more patches to come?

thank you.

/Jefferson

Daniel Juyung Seo於 2017年6月8日星期四 UTC+8上午9時32分00秒寫道：

[Daniel Juyung Seo]

Hello Wu Jefferson,

- "Adaptive Bit Rate", "DRM": These test cases use open source Shaka Player so we don't expect it to be fully compatible with Cobalt. Please use youtube.com/tv instead for Cobalt.

- "SSL", "Web Audio": I will update you after more investigation.

Thanks,

Daniel

[Kwangrim Ahn]

Hi Daniel

I got below error while opening CSS Spherical Filter Extension page

"You need permission to access this published document."

Could you check permission?

[Daniel Juyung Seo]

Hi Kwangrim Ahn,

You need to get a permission to our partner site to access to that document and sign in with that account.

Please reach out to your partner manager.

Thanks,

Daniel

•  Daniel Juyung Seo 서주영     •  Partner Technology Manager (APAC) / 차장   •  Partner Engineering, YouTube in the Living Room, Google   •  Learn more about Cobalt application runtime for YouTube in the Living Room

You received this message because you are subscribed to the Google Groups "cobalt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cobalt-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Wu Jefferson]

hi Daniel,

  Thanks for the reply!

  Please let us know how we can use Cobalt 9 to pass youtube 2017 certification. For example:

- 2018 tests should be used instead (from stack overflow)?

- what we should do with the  "Adaptive Bit Rate", "DRM", "SSL", "Web Audio"?

- other misc things we should know for cert.

PS: An official announcement on this would be nice :)

thank you.

/Jefferson

Daniel Juyung Seo於 2017年6月15日星期四 UTC+8下午1時36分38秒寫道：

[Daniel Juyung Seo]

Hi wu Jefferson,

- 2018 tests should be used instead (from stack overflow)?

Use https://qual-e.appspot.com. It will redirect you to the right MSE/EME/Progressive conformance tests when you run Qual-E on Cobalt.

 

- what we should do with the  "Adaptive Bit Rate", "DRM", "SSL", "Web Audio"?

My answer is still the same as my previous answer.

- "Adaptive Bit Rate", "DRM": These test cases use open source Shaka Player so we don't expect it to be fully compatible with Cobalt. Please use youtube.com/tv instead for Cobalt.

- "SSL", "Web Audio": I will update you after more investigation.

 

- other misc things we should know for cert.

There are a lot of things you should know for. I recommend you to go through all the document in our partner site under "testing" and "certification" tabs, and perform the pre-certification on your end. 

Please work with your partner manager closely for the further discussion.

Thanks,

Daniel

[ecf...@realtek.com]

hi Daniel Juyung Seo,

could you specify which build flag we should use to pass Qual-e certificate, qa or gold ?

currently, we build cobalt RELEASE_9 with gold but it can render Conformance   only, other not.

if qa, it can render Conformance ,MSE, EME and Progressive.

thanks.

Daniel Juyung Seo於 2017年6月8日星期四 UTC+8上午9時32分00秒寫道：

Hello everyone,

[Daniel Juyung Seo]

Hi,

The build types shouldn't matter for rendering the test pages while you are expected to use Gold build for the certification and product for the best performance.

If you face any issue with Cobalt or Qual-E, please report it to the issue tracker. https://issuetracker.google.com/issues?q=componentid:181120

Thanks,

Daniel