Doesnt start?
bedeho opened this issue · comments
Awesome project!
Tried to stream and consume across a few different peers, both on the same and different networks, but I was never able to get an actual video feed on the consumer end, it was just grey?
@bedeho thanks so much for logging this ^__^
There was a bug that came up over the weekend in one of the dependencies for hypercore, which hypervision is built on top of. This was apparently fixed overnight.
Are you able to delete hypervision, re-clone it, and follow the installation instructions again? This should work now.
Let me know if there are still issues!
Thanks for the prompt reply.
I tried this literally a few minutes in advance of posting the issue, so if a fix was posted over the weekend, then I will not have missed it. This is the commit I am using, which is still what master points to as of now.
commit b269b94dca955fc14630f691f78e93d5d4983759
Author: Louis Center <git@louis.center>
Date: Tue Mar 21 17:28:25 2017 +1100
Removed underline from "settings" button
@bedeho Apologies! I shouldn't have assumed it was to do with that, I just wanted to be sure it wasn't related because viewing was broken for me as well up until about 24 hours ago (by the weekend I should have said Monday evening Europe time).
If you cloned the repo fresh and did an npm install just before you posted the issue, then it shouldn't be related.
I'm doing a fresh install and test right now and have viewing working a-ok on my end.
What operating system and version of Node are you running hypervision on?
Does viewing work across two instances of hypervision on the same computer, or does it only break across different computers/networks?
I have tried on a bunch of different combinations of Ubuntu and OSX, all running pretty recent versions of node. I just now tried it locally on OSX, and that worked great, so perhaps this has something to do with NAT? do you have hole punching implemented?
A colleague of mine whom I tried this with also suspected it might be due to broken peer discovery on a p2p network with low peer liquidity, but from what we could tell, you are actually using the BitTorrent DHT as the peer discovery layer?
@bedeho yea we are using the dht and are doing hole punching. could you perhaps try installing p2p-test on the machines you are testing on and share the results? https://github.com/mafintosh/p2p-test
That will definitely help us debug.
@mafintosh hey, ok, will try that now.
@mafintosh
This is what I tried and got
./bin.js oslo-LAN
Network tested. Thank you for participating.
{ time: '2017-03-21T12:05:52.935Z',
description: 'oslo-LAN',
holePunchable: true,
pings:
[ { port: 45075, host: '195.159.234.190' },
{ port: 45075, host: '195.159.234.190' } ] }