Choice of network adapter about scream HOT 3 OPEN

Hi Mads (@madsbuvi),

in Windows 10, you can set the default adapter for multicast (or other traffic that can go either way) by using interface metric. See "The interface method" in this article: https://www.ghacks.net/2016/12/02/change-network-adapter-priorities-in-windows-10/

In Windows 7, you can also set interface order in an easier way: https://serverfault.com/questions/205648/how-do-i-add-a-multicast-route-in-windows-7

cheers,
/tom

PS: If the above fails, it should also be possible to set a static route for multicast traffic pointing to the correct interface: https://sites.google.com/site/embeddedsystesting/home/how-to-modify-or-delete-windows-default-multicast-routes

from scream.

Just took an hour troubleshooting why I couldn't get ScreamReader to work even though I could see the multicast packets in Wireshark on the receiver PC (and even though it worked on a different PC). Eventually I came to the conclusion that it must be listening on the wrong interface, disabled the Virtual Box adapter and it suddenly started working. Like a charm.
This is a great project!
Too bad the driver signature requirements limit it so much, but I guess I'm lucky my old laptop doesn't know a thing about Secure Boot and was upgraded from Win7 so the limitations don't apply :-) .

Guess I'll have to try specifying some metric for the adapter at some point...

from scream.

I spent a couple of hours yesterday troubleshooting my linux container before throwing up Wireshark, noticing a 169.-address and coming to the same conclusion as the previous posters.
Is it possible to have and option to bind to an IP/interface or maybe just a FAQ about interface order?

I'm very happy with the results nonetheless. I'm using my workstation to stream sound to my Media server/NAS which is plugged directly into my living room stereo.

from scream.