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

Thanks, we will take a look!


1 person likes this

Any update on this?

Hi,


Unfortunately, we do not have updates! 

We plan to test and work on your case next week!




Can you please confirm you are going to be working on this problem this week? Our developer team cannot continue without this issue being addressed. 

Hi,

We will see what we can do. The reported issue is in our week plan with normal priority.

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.



Hello,


It is supposed to use webrtc and to stream video with Viblast Player.

Could you share more details for the issue? What the errors are? 

Maybe the best is to share a test page.




We are using webrtc to screenshare. We also need viblast.js to play a video on the same page. When viblast is imported it seems to be causing a conflict with webrtc.



Hello,


Somehow we have to reproduce the issue in order to see what happens.

From the given explanation this is not clear enough what is going on.

Can you share a simple test page with steps to reproduce?

It is not possible to give you a test page. I have included the log from the client page console below that shows the errors:


 

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

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

polyblob:1 Failed to load resource: net::ERR_UNKNOWN_URL_SCHEME

viblast.js:19 Uncaught TypeError: d.ua is not a function

    at RTCPeerConnection.Lf.RTCPeerConnection.addStream (viblast.js:19)

    at handleCreateOffer (vw_webrtc_peer_mgr.js:412)

    at onJoinWebinar (vw_webrtc_peer_mgr.js:312)

    at WebSocket.webSockMsgDispatcher (vw_webrtc_peer_mgr.js:190)

Lf.RTCPeerConnection.addStream @ viblast.js:19

handleCreateOffer @ vw_webrtc_peer_mgr.js:412

Hello,


The above does not help a lot. In the next days we will try to reproduce the issue.



Can you join a webex so you can see what is happening?

Login to post a comment