I have been trying to run a simple shaka player test page based on the latest version from the repository using Cobalt release 11.
Using the debug version of shaka player currently I get the following console log:
[0301/112442:INFO:console.cc(52)] [console.log()] IndexedDB.install
[0301/112442:INFO:console.cc(52)] [console.log()] InputEvent.install
[0301/112442:INFO:console.cc(52)] [console.log()] mathRound.install
[0301/112442:INFO:console.cc(52)] [console.log()] MediaKeys.install
[0301/112442:INFO:console.cc(57)] [console.info()] Using native EME as-is.
[0301/112442:INFO:console.cc(52)] [console.log()] MediaSource.install
[0301/112442:INFO:console.cc(57)] [console.info()] Using native MSE as-is.
[0301/112442:INFO:console.cc(52)] [console.log()] VideoPlayPromise.install
[0301/112442:ERROR:console.cc(62)] [console.error()] VTTCue not available.
[0301/112442:INFO:browser_module.cc(534)] Loaded WebModule
[0301/112442:INFO:console.cc(52)] [console.log()] Unload latency:
[0301/112442:INFO:console.cc(52)] [console.log()] load() failed:
[0301/112442:ERROR:console.cc(62)] [console.error()] Error code
Has anyone been successful in getting shaka player work with the Cobalt Browser? If so could you please point me to the version used and what if any kind of modifications were made to get it working.
We do not expect Shaka player to be working with Cobalt well. Cobalt supports subset of HTML5, CSS, JavaScript spec on purpose, and Shaka player is not built against Cobalt specs.
I am curious why you need Shaka player to be working on Cobalt but you can refer the modified Shaka player version from our Demo Player. https://yt-media-test.appspot.com/demo-player/dash-player-2018.html
Related
When i try to open a .html file i got "WebGL 2.0 isn't available".
I'm working on MacBook Pro (late 2011)
Firefox version: 74.0
Graphic card: Intel HD Graphics 3000 512 MB
On about:support under Renderer driver WebGL 2 I got this error: WebGL creation failed:
GL error 0x500 occurred during WebGL context initialization!
Could please someone help?
As chrome some years ago it seems firefox has blacklisted the old macbookpro graphic card. Resulting we cannot use 3D in google maps anymore for example. In fact the machine is able to perfectly display 3D maps, as it did until firefox version 79.
I rollbacked to version 79 and can enjoy 3D again on my old but capable machine.
https://ftp.mozilla.org/pub/firefox/releases/79.0b9/
I found that there is a problem with the context creation of the canvas. It might depend by some incompatibilities between gpu and web browser. The solution found so far is to try and run the program on another browser that is compatible.
I am learning to build a web application for Hbbtv using the Hbbtv SDK.
So for testing a sample app, I was looking for an emulator and came across FireHbbtv Extension by firefox.
However, whatever I do, it says the extension is not compatible with the version of Firefox. can any of you help with what is happening
Firehbbtv extension is abandoned, but you can install it using an old Firefox version (<52 as far I remember). Make sure the automatic updates are disabled if you want to keep the extension available.
There is another HbbTV plugin named hybridTV (https://github.com/karl-rousseau/HybridTvViewer) It works fine, but it is in development.
There is also a third option, using the opera (now called vewd) SDK. You can find the info and the virtual machine downloads visiting
https://www.vewd.com/products-services/vewd-tv-emulator/
Is the remote debug function of Cobalt fully supported(Such as Source/Network/Timeline/Console items) as Chrome dev tool on Windows?
We can connect the Cobalt on the ARM device with chrome on Windows PC by remote debug function of Cobalt, and we have found it can only inspect the html tags in the Elements catalogue, it can NOT run the javascript in the Console(eg location.reload()), it can NOT capture a timeline in the Timeline catalogue(When reload the YT page, it will disconnect to the platform), and it also can NOT see any source files in the Sources catalogue, so is there any one who can help to point out exactly which functions are supported in the Cobalt remote debug function? If some functions are not supported yet, is there a plan to support them in the near future?
Cobalt does not fully support the developer tools.
It serves them and has support for the protocol and DOM/CSS inspection, but, as you have discovered, more work is required as of Cobalt 6 to support JS debugging, network and the other features. Yes, the plan is to support more of the developer tools, but there are no specific dates yet.
I'm trying to get web browsing working on my platform with Qt.
I'm using Qt 5.4.1, on ARM A9, running embedded linux, with qtwayland and OpenGL ES. I've successfully compiled (using yocto) QtWebEngine for the platform and I'm able to launch the example browser applications (quicknanobrowser, browser and fancybrowser) .
The issue is that the web contents are appearing as black rectangles. All other widgets/menu of the browser are working fine.
This issue has been reported and there is a fix for the EGLFS (https://github.com/qtproject/qtbase/pull/4/files?diff=split ). Since my setup is based on the wayland EGL, I'm not sure if porting this fix to wayland EGL would help.
Could someone let me know what would be going wrong? Any ideas on where to start debugging?
Any tries to stream media from https fails with TLS plugin not available error (see message log here)
Whereas, trying the same stream using Win32 VLC version (also 2.1.5) succeeds (see message log here.
Is there a reason why x64 VLC version does not support encrypted connections?
Windows 8.1, VLC 2.1.5
It's due to a bug. In VLC 3.0.0, the latest nightly build, there appears to be no problems streaming videos that require TLS. You can find it here if interested: http://nightlies.videolan.org/build/win64/vlc-3.0.0-20150203-0441/
Note that because it's an unstable build there may be other issues.