gitsummore / nile.js Goto Github PK

The website is not up.

Right now, it doesn't appear that I can run the broadcast server separately from viewer servers since it looks for the magnet endpoint on the same port.

It'd be nice to be able to specify a particular server/port to connect to for the magnet endpoint.

There is a script file reference which does not exist in the codebase.

Hello,

Could you tell me if you got the idea of Nile and the Nile's landing page from this project : https://github.com/pulsardev/netsix (and it landing https://mmorainville.github.io/netsix-gh-pages). We created an electron app using WebRTC to stream videos.

Regards

As we rack up the number WebTorrent seeds on the broadcaster side, there seems to be a client side memory leak which eventually causes the browser to crash. We’ve checked the CPU and memory usage but have found no error messages or anomalies.

Unsuccessful approaches that we have taken to solve the issue:

• Server side seeding in place of client side seeding
• Seeding in web workers
• Seeding in iframes
• Destroying WebTorrent client on each new seed
• Destroying WebTorrent file on each new seed

One solution that we have found, is browser specific. If using Chrome Canary to test the library, it seems to run indefinitely. If anyone in the open source community is able to provide some insight, please make a pull request on our GitHub repo.

To use userMedia on mobile devices you must use https/ssl server so, the broadcaster file must be on https connection, update the example and add it to the documentation for user that want to use it on mobile devices.

Hi there,

Congrats, this is a great project. It would be nice to have event handlers for the socket.io features, like emiting a broadcast notification when a broadcaster is on, so it wouldn't require a second socket.io instance.

Hi, I got my first badge from github for contributing to this repo. :)

This error occurs very frequently on the demo at https://nilejs.com/demo.html (Chrome 59.0)

It will stop playback for that video element permanently (or until playback is resumed by "Show Controls > Play". One third of the stream will then be frozen.

These errors could be handled by waiting a small amount of time and making another play request.

I understand that you can use regular WebRTC to stream video to clients without recording, but I was wondering if it would be possible to integrate that as a flag in this library as well. That way I can use one library and keep everything in one place. If that's possible, I could probably work on it, just point me in the right direction.

The example throws an error when using startLogging function

I have not tried your solution yet, but I guess since you record some chunks, you do create some latency.
Any idea on what would be the minimal latency your solution can handle ?

Regards

Still alive or no?

I started the demo-server.js, opened the client/index.html, click "start streaming", it asks for permission then nothing happens for a while and then these errors.

What sort of lag should I expect when using this with:

• 10 concurrent
• 100 concurrent
• 1000 concurrent
• 10,000 concurrent

Nested a tags in button in FF don't work.