As for Roon support WOL: while sending out a magic packet isn’t exactly rocket science, with all the different networks (Wifi and extenders, anyone?) / endpoints around, things could turn into a support nightmare quickly. Even a simple table containing MAC-adresses of devices to be woken would need to be cached and updated on all different remotes in use.
Would be great, plus at least one connected NAS drive would be ideal. I don’t think it’s complicated even to support multiple devices. All you need’s their MAC addresses in most simple home network environments. I use a few tools and just send two wake ups for good luck - never fails but not half as convenient. If Roon wanted to be clever it could look ahead at your playlist, and if your NAS is offline trigger the wake up based on its wake-up duration. Even that’s petty trivial IMO. Outside of Roon I script mine to wake up before backups (2 min lead time). But there are lots of priorities - do I want this over EQ/Room Correction? No. Although it’s significantly simpler to implement than either of those.
Because we like to think about solutions to the inherent problem at hand, and not a solution to a single situation.
We’ve met about this feature multiple times and spent unknown hours discussing it… WoL provides such a bad user experience, and we are trying to fix that core bad experience in a way that doesn’t have us building a complicated WoL system.
We can solve it nicely in some simple cases (the one you state), but it’s unclear to me if that is the common case.
We’ll keep on thinking about something, but in the meanwhile, use a 3rd party WoL app that solves this problem for all use cases. Sorry guys! I know it’s not the answer you want to hear, but this is what it takes to make good software.
Feature Requests don’t come with guaranteed developer response. We get to tell the devs what we want and why. They build the product. Occasionally they will poke their heads in and say that something is being picked up, less often they will say something is ruled out. More often they will take the Requests on board without ruling something in or out.
There are any number of WoL apps that can be configured to send a packet in a myriad of ways. Features to implement something in Roon that can be readily done outside Roon may not enjoy the same priority as things that only Roon can do.
If WoL arrangements are causing inconvenience, I’d suggest fixing them using existing tools external to Roon rather than continuing to suffer through any development and implementation period.
Unfortunately Roon aren’t very green (no integrated WOL) and encourage a leave-it-on 24/7 mentality.
It depends what you are using for an endpoint. It’s easy to configure a Raspberry Pi to send a WOL command to your server. For my main Trinnov system, I have an a Pi whose sole job is to send a WOL command when the system starts and then shut itself down.
Edit: there are also numerous iOS and Android Apps that can be configured to send a WOL command. It’s just less convenient and less ‘other system user’ friendly.
Is there a way for the app to wake up the server PC if it’s asleep?
I usually leave my server pc in sleep mode when not in use, it wakes up very fast, surprised the app will not do this is the core machine is sleeping. I’ve been using foobar + app for ages now and it always did this nicely.