You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm testing on something like your media-example.
Peer 1 is a webpage sending an offer and providing a videostream.
Peer 2 is node-datachannel on the backend.
The Peer 1 and 2 are connecting without a problem.
Datachannel is instanciated and periodicaly sending small text messages.
When state switches to "connected" I'm calling "onTrack".
After onMessage has received between 20 to 30 tracks, "onClosed" ist fired? There is no debug message and no error fired. On Peer 1 (Browser) too, there no error.
During my tests I only call "console.log( message.length )" inside onMessage.
After onClosed is fired, Datachannel is still working and sending text messages.
The goal should be to store the video in a file on backend.
Any idea why the videostream is interrupted?
I have this behavior in version 0.24 and 0.25
Best regards
Harry
The text was updated successfully, but these errors were encountered:
Hi!
I'm testing on something like your media-example.
Peer 1 is a webpage sending an offer and providing a videostream.
Peer 2 is node-datachannel on the backend.
The Peer 1 and 2 are connecting without a problem.
Datachannel is instanciated and periodicaly sending small text messages.
When state switches to "connected" I'm calling "onTrack".
After onMessage has received between 20 to 30 tracks, "onClosed" ist fired? There is no debug message and no error fired. On Peer 1 (Browser) too, there no error.
During my tests I only call "console.log( message.length )" inside onMessage.
After onClosed is fired, Datachannel is still working and sending text messages.
The goal should be to store the video in a file on backend.
Any idea why the videostream is interrupted?
I have this behavior in version 0.24 and 0.25
Best regards
Harry
The text was updated successfully, but these errors were encountered: