Start a new topic

Viblast.js and WebRTC

As soon as viblast.js is imported it is blowing up our webrtc implementation since viblast is using webrtc behind the scenes (https://bloggeek.me/viblast-webrtc-interview/). Is there a way we can use webrtc and stream video?


Hi,


We found the root cause of the reported issue and will provide a fix with one of the next releases.

The issue is related to the popular adapter.js, embedded in our library. 

As a workaround, you can include the adapter.js just before viblast.js in order to eliminate the issue:

<script src="https://webrtc.github.io/adapter/adapter-latest.js"></script>

<script type="text/javascript" src="https://cdn.viblast.com/vb/stable/viblast.js"></script>  


We will let you know, once we release a version with the fix.



1 person likes this

We tried your work around and are still getting a lot of the same errors:


viblast.js:1024 Invalid asm.js: Invalid member of stdlib


viblast.js:71 URL.createObjectURL(stream) is deprecated! Use elem.srcObject = stream instead!


viblast.js:71 URL.createObjectURL(stream) is deprecated! Use elem.srcObject = stream instead!


vozzware.local.cr8content.com/:1 Mixed Content: The page at 'https://vozzware.local.cr8content.com:8443/' was loaded over HTTPS, but requested an insecure video 'polyblob:2'. This content should also be served over HTTPS.


polyblob:2:1 GET polyblob:2 net::ERR_UNKNOWN_URL_SCHEME


viblast.js:71 URL.createObjectURL(stream) is deprecated! Use elem.srcObject = stream instead!


vozzware.local.cr8content.com/:1 Mixed Content: The page at 'https://vozzware.local.cr8content.com:8443/' was loaded over HTTPS, but requested an insecure video 'polyblob:3'. This content should also be served over HTTPS.


polyblob:3:1 GET polyblob:3 net::ERR_UNKNOWN_URL_SCHEME

Hi,


Just a guess, but somewhere in your js, you are using an old deprecated WebRTC API and  you might have something like:

video.src = window.URL.createObjectURL(stream)

The code above creates "blob" video src with unsecure scheme, which causes browser to forbid it.

Instead of this you have to use the new API:

video.srcObject = stream


Did you try to run via HTTP instead of HTTPS?



It seems like the issue is not related to the player itself. 

... and without piece of your code we can not be sure where the problem might be.



Login to post a comment