@MrShoenel I'm using unicast -- .net receiver doesn't expect/allow ?

[SteveDevOps]

@MrShoenel can you update included c#/.net receiver to allow for unicast like the included linux receiver does?

[MrShoenel]

Hey! Can you clarify this a bit, because the receiver picks up the Scream-broadcast from its unicast-address already, cf. https://github.com/duncanthrax/scream/blob/master/Receivers/dotnet-windows/ScreamReader/ScreamReader/UdpWaveStreamPlayer.cs#L17

[SteveDevOps]

Sorry let me clarify...

I run the "sending audio" windows machine on my lan in unicast mode so that I can hardcode the ip address of the receiver in the registry along with port. I've found that on my lan, this is much more performant and doesn't have lag. The normal linux based receiver allows me to to pass an argument to force unicast mode and expect a unicast transmission. This in turn allows me to place/hard code the ip address of the receiver in my windows registry of the sending machine. I couldn't get this setup to work, didn't understand config with the .net receiver in windows for unicast mode. Are you saying that I need to just change the IPAddress line to be the private ip of the sending machine and recompile?

[SteveDevOps]

ultimately I was just confused on how to configure the .net receiver for unicast. When I run the .net receiver, I don't get any sound in this setup (sending machine with registry entry to force unicast).

https://snipboard.io/MYFaCz.jpg

[MrShoenel]

Ok, just a few questions:

• Why do you run the sending machine in unicast-mode, and do you have a way to adjust this?
• I don't understand the registry-entries you are showing, I suppose these are for your sending machine? Just to be clear, the ScreamReader does not read its options from the registry. If this registry entry controls where your sending machine is sending to, then you could just point this to 239.255.77.77:4010 and ScreamReader would pick it up.

Currently, this is not configurable, so you have two options: A) Modify the hard-coded address in the ScreamReader and re-compile, or B) make it configurable by, e.g., having it read it from the command-line or add a context-menu entry etc. You may modify the port this way, too.

ScreamReader is not bound to Multicast-mode, it just binds to any IP/port you give it, so A) should work just fine.