Does the latest code of 'drm.h' in master branch meet the EME part of 2018 YouTube TV HTML5 Technical Requirements?
Widevine CE CDM stongly recommands to use the certificate from servers, and we met with some problems using the old method with latest CDM library.
How can we always get certificate from Youtube with Cobalt?
Can you report this to the Cobalt issue tracker?
https://issuetracker.google.com/issues?q=componentid:181120
Related
I would like to use the newest version 1.1 of AdaptiveCards in the BotBulder Node.js SDK 4 to use the new features such as vertical alignment. However, the CardFactory.adaptiveCard only allows version 1.0.
Is it possible to use the AdaptiveCards SDK itself to render AdaptiveCards for use in chat? I am using AdaptiveCards in Telegram, hence they need to be rendered into an image. I tried using the AdaptiveCards method .render but failed due to the issue described here.
If not, is this planned for the future?
The BotFramework SDK does not currently support the most recent release of AdaptiveCards - v1.1; however, someone has just submitted a feature request to the development team on GitHub to incorporate the updated version into the SDK. Hopefully, the newest release will be developed into the framework and will work with the CardFactory soon.
In the meantime, the user who submitted the feature request also suggested a possible workaround. They recommend creating a DOM object which will allow you to render the JSON card into HTML using the AdaptiveCards Library. Then, you can use Puppeteer - a high-level API to control Chrome - to render the HTML and convert it into an image. The image can then be sent to the user in the chat in place of a card. Unfortunately, you do lose a lot of the card's functionality such as actions, but you will be able to use some of the new formatting features in the new release of AdaptiveCards. I would recommend looking at this post and the Puppeteer Repository if you think this solution may work for you.
We found why we can playback the purchased videos of YTTV, but cannot test EME website. Because SourceBuffer::appendBuffer is used in 2017 EME test website, but YTTV home page can automatically select the old API if SourceBuffer::appendBuffer does not be implemented.
EME 2017 test website:
http://yt-dash-mse-test.commondatastorage.googleapis.com/unit-tests/2017.html?test_type=encryptedmedia-test
Cobalt team is aware of the need to upgrade the supported EME version, see https://stackoverflow.com/a/41070502/1318869.
In the meanwhile, for the purpose of testing of Starboard player implementation, try running youtube.com/tv in Cobalt and play any purchased video.
Did some search but didn't find the reason for this.
When using the Azure media player (http://amp.azure.net/libs/amp/latest/docs/), and when I switch to version 1.5.0, suddenly, for a regular mp4 file (not adaptive streaming), my Firefox (version 43.0.4) has a bar saying "The audio or video on this page requires DRM software this FireFox does not support".
Anyone has idea about this? I didn't use any DRM on my page (it is a most basic un-protected mp4 playback).
Thanks!
PS: I tried the official azure media player demo page (http://amsplayer.azurewebsites.net/azuremediaplayer.html), and it has the same issue as well.
This is a known issue that's been fixed in AMP version 1.6.0 (set for release soon). It’s a Firefox bug that pops up when AMP queries APIs to detect browser capabilities. This happens even if the content isn’t using DRM. The message is inaccurate and it’s a little annoying but fortunately it doesn’t affect playback and will be fixed when you upgrade to v1.6.0.
I just come across about ibeacons technology which introduced by Apple but haven't got any API/framework from Microsoft.
Is there any API or framework available from Microsoft which gives support for Ibeacons implementation?
Thanks
Unfortunately, this is not possible with Windows Phone 8, because it only supports Bluetooth 3.1 iBeacons require Bluetooth 4.0, also known as BluetoothLE.
In October 2013, Nokia announced that upcoming phones would have Bluetooth LE support. Unfortunately, these only allow OS-level pairing with Bluetooth LE devices. There is no public api.
This makes it impossible to develop a third-party iBeacon Library for the Windows Phone similar to the Android iBeacon Library.
Unfortunately, Windows Phone users will have to wait for a later release with either native iBeacon support or a public BluetoothLE API that allows a third party to develop a Windows iBeacon Library.
Update: this appears to remain impossible with Windows Phone 8.1. See my comment on the answer from #keni
Update:
Windows 10 will support Bluetooth LE Advertisements. Current status as of today (4/23/2015) is that the preview build of Windows 10 still has an incomplete SDK implementation and a few bugs. However, next week a new build will be introduced and it can be safely assumed that we'll get a good glimpse on how this will actually work.
Sending and receiving pure Advertisements works already. Have a look at the Sample that you can download from github here:https://github.com/Microsoft/Windows-universal-samples/tree/master/bluetoothadvertisement
Update
a public BluetoothLE API will come in Window Phone 8.1
http://allaboutwindowsphone.com/flow/item/19234_Windows_Phone_81_receives_Blue.php
Please read the following blog post for BLE for developers in Windows 8.1
http://sviluppomobile.blogspot.com/2014/02/ble-for-windows-81-part-i.html
I'm excited about desktop Google Docs client. I found a project using Adobe AIR which imitates Mozilla Prism. That didn't impress me at all. Do you have any pointer to a FOSS project building desktop Google Docs client?
If there are none, if you were to build, how would you do?
“Exciting” things like clipboard/dnd integration, offline, upload integration would mostly come from quality html5 support + some userscripts if google docs doesn't make use of non-portable features yet. Pick a browser with good html5 support, write userscripts, bundle it.