Open briantho opened 1 year ago
Hello. I don't have a windows PC I can easily test this on -- I might be able to procure one, but in the mean time perhaps you can get it running by running the application directly. The 'link' step is just supposed to "install" it on your machine (on Linux it links it into the location where commands are located -- I'm not sure what the Windows equivalent is).
Anyway, in the directory where you have npm install
ed it, try running node index.js
.
Let me know if that works. (It does for me, on Ubuntu.)
hmm, ok. well running "node index.js" does do something. it says "doing SSDP discovery" but nothing after that. i assume it's trying to look for dlna devices, but can't find any? I do have 2 amps that support DLNA on my network, and other DLNA apps detect them just fine. In the mean time, i'm going to try and bring up a ubuntu vm on my windows machine, and see how that goes
That's interesting. You are correct, it's trying and failing to find them. Let me know how you get on with an Ubuntu VM and I'll put this on the list of things to investigate -- though to be honest I get very little time to spend on it and a Windows problem isn't easy for me to work on and does not affect me so it's going to be low down the list :-)
I have compiled for Windows and it works although is prone to crashes. If you have more than one NIC/IP, it will get stuck at SSDP discovery.
Use cmd; Check that it has detected the correct IP with
node_modules/.bin/network_address.cmd
I just built with npm install npm audit fix --force npm link cd node_modules/.bin node ../../index.js
It crashes for a variety of reasons and is only found by YouTube in Chrome and BubbleUPnP, but it's a step in the right direction at least.
I've been trying to get this running under windows 10, and have successfully installed npm and nodejs natively. I've successfully followed the commands up to "npm link". It fails saying that "Cannot destructure property 'name' of '.for' as it is undefined."
here is the output from cmd.
2023-03-04T02_42_56_419Z-debug-0.log
is it possible to make this run under windows? I'm attaching the npm debug log. Any advice to make this work? Thanks