Development 2.1 about chromecast-desktop-audio-streamer

[FA-Bubba]

I didn't see a link for v2.1.0

[SamDel]

The link is on the options tab, or at the releases.

[FA-Bubba]

Found it... Thanks!

[spiffamafied]

Just want to thank you for this. I've been looking for a way to cast all audio from my Windows 10 PC and so far so good. The chromecast audio stream wasn't working well for me, and this is a huge improvement. Thanks again.

[FA-Bubba]

WHAT IF...

What if I installed the ChromecastAudioStreamer on TWO PCs, and ran it concurrently, with one PC streaming only to one group of speakers, and the other PC streaming to a different group of speakers, with no overlap?

Would this work, or would it create conflicts?

[SamDel]

You're welcome @spiffamafied ! Please let it know if there are issues, or if you have ideas to improve the application.

@FA-Bubba : While testing I've been running multiple instances of Desktop Audio Streamer (on the same desktop) frequently, without issues. I didn't try on two PC's, but there shouldn't be issues.

If you have 'automatically restart when closed' checked on two instances and start the same group then they start competing 😉.

[GrahamDLL]

WHAT IF...

What if I installed the ChromecastAudioStreamer on TWO PCs, and ran it concurrently, with one PC streaming only to one group of speakers, and the other PC streaming to a different group of speakers, with no overlap?

Would this work, or would it create conflicts?

I haven't tried streaming from two computers ... I have been able to stream with DAS on one machine and use DAS on another macjhine to mute when the telephone rings.

[FA-Bubba]

I am running v2.0.23 on the PC I have been doing all of my testing so far...
I just loaded v2.1.0 on a different PC, but it is not seeing any speakers -- that is, the Device window is empty, and clicking "Scan again..." does not populate it.

Both PCs are on the same network, as the speakers are connected to.

Must the DesktopAudioStreamer be the same version to get two instances running concurrently, or is something else causing this issue?

[SamDel]

The version doesn't matter. Sometimes a reboot works to discover devices.

You can also edit the config file in the install folder, and change the value of IpAddressesDevices to
<add key="IpAddressesDevices" value="192.168.1.239,Family Room TV;192.168.1.125,PlayRoom Speaker;192.168.1.156,Basement Speaker;192.168.1.187,Office Speaker;192.168.1.178,Guest Room Speaker;192.168.1.107,Family Room Speaker" />

[FA-Bubba]

The second PC was on v2.1.0, and didn't see ANY devices, I moved the first PC up to v2.1.0 so they were on the same version, and the second PC still doesn't find ANY devices. I then dropped the second PC down to v2.0.23, and it still doesn't see ANY devices.

Both PCs have been rebooted. Both PCs are running Windows 7 Pro, with all patches/updates.

I'm not sure hard-coding the IP Addresses would be a long-term resolution, because I think the DHCP may reassign the addresses arbitrarily...

Any other ideas?

[SamDel]

When you scan for devices the application (Tmds.MDns is used for it) sends a broadcast message to the network, a device that receives the message responds to it. So either the broadcast message is blocked somewhere, or the response is blocked.

I'm not an expert on networking, to pinpoint you can try:

• Connect PC2 to exactly the same router as PC1. If it's still blocked then it's not the router settings, else you can try enabling upnp on the router.
• Turn off the firewall on PC2 temporary. If it's still blocked then it's not the firewall blocking the messages.

If you write down all changes you make we can add it to the wiki page.

[FA-Bubba]

Thank you!... it was the Firewall. I am using AVG Internet Security (on all of my PCs), and on this particular PC, it seems to allow the Windows Firewall 'suspicious' file alerts. Once I disabled the Firewall, then launched the DesktopAudioStreamer, a Windows Alert prompted me if I wanted to allow ChromeCast.Desktop.AudioStreamer.exe. I clicked OK, and it now finds ALL speakers, and 2 out of 3 Groups when AVG Firewall is running. Not sure why it isn't seeing the "ALL Speakers" Group, but I will troubleshoot later.

[SamDel]

Thanks! I've added a line in the wiki about it.

[FA-Bubba]

I observed an unusual event yesterday -- while I was away from the PC, the Mouse went 'rogue', and auto-clicked the shortcut for launching the DesktopAudioStreamer. MULTIPLE TIMES!***

This caused multiple instances of the App to be launched concurrently (see image). I think this would be undesirable -- I've noticed that some other Apps will recognize that it is already running, and will prevent additional instances from being launched; instead they will just bring the running App to the foreground.

Is there a way to get the Streamer to work that way?

*** This happened once before, and the 'auto-Mouse' launched 122 instances of "Calculator" !!!

[SamDel]

122 instances 😄!

I agree, allowing multiple instances has no use. I only used it when I was testing the 'restart when closed' option.

In Setup 2.1.3.zip Setup 2.1.4.zip :

• Run only one instance
• Make sure the encoding/streaming always uses the same thread. (before the thread could change, causing drop-outs)
• More IP4 addresses in the dropdown. @pr0t3us does this version also work for you? (I removed IP6 addresses, and the network cards that are down from the list.)

[FA-Bubba]

The Audio Streamer (v 2.1.3) ceased playing overnight. I tried re-clicking the Devices, but no result. I unloaded and restarted the Streamer App, and it opened without any Devices populating into the Window...

I force-unloaded it via Task Manager, and restarted it; again, no Devices found. I tried the "Scan Again..." button a few times, and still no Devices populated. At this point, I captured the Log (attached below).

I finally rebooted my PC, and the Streamer App worked OK. Will try v 2.1.4 tonight.

Log-2019-05-03-v2-1-3-NoDevices.zip

[SamDel]

It looks like the internet connection was completely down on your desktop.
At startup the application checks if the known devices are on, all attempts to connect to these devices timed out. Also the check for a new version on github timed out.

I can't tell what was wrong with the connection, but the application worked as expected. Maybe a notification can be added, but it's hard to do a check for an internet connection that works in all cases.

Did the 'Run only one instance' feature work for you?

[FA-Bubba]

Yes, I have been experiencing a lot of network issues over the past 3 days -- nothing caused by or related to the Streamer App -- sorry for the false alarm.

Yes, the 'Run only one instance' feature seems to be working well -- when I try to launch a second instance, the currently running instance is brought to the foreground -- THANK YOU!!

Running v 2.1.4 now.

[pr0t3us]

@SamDel Just checked 2.1.4 and is working as expected.

[SamDel]

Thanks a lot! It's not a lot of changes but I've created a 2.2 version.
Lets continue here.