Thanks Murray. That fix has already been built against your symptoms and is in the version assembling today, ahead of schedule. Your MU2 is one of the machines it must pass on. Give the dog my regards — he earned the walk.
Hopefully labeled 306.
Thanks Murray. That fix has already been built against your symptoms and is in the version assembling today, ahead of schedule. Your MU2 is one of the machines it must pass on. Give the dog my regards — he earned the walk.
Hopefully labeled 306.
Glad to hear topic is split. Where do I go now? This shouldn’t be so difficult to get an answer. It linked perfectly to T8 before?
The clue is that Roon and Qobuz Connect still work: they each talk to the T8 by their own private protocol, while Maestro finds it the open way, over UPnP/DLNA. Firmware updates on the EverSolo are known to switch that renderer off or reset it — which would make the T8 disappear from Maestro and nothing else, exactly what you’re seeing.
So the first stop is on the T8 itself: in the EverSolo’s own settings, find the DLNA/UPnP renderer option and make sure it’s enabled, then quit and reopen Maestro and give discovery a few seconds. If it’s already enabled, toggle it off and on once — firmware updates sometimes leave it in a half-set state.
If the T8 still doesn’t appear after that, send me a log from Maestro (Settings → Save Logs to Desktop on your Mac mini) and I’ll look at what discovery is hearing rather than guessing further. And you’re right that it shouldn’t be this hard — the answer above should have been a message in the app, and that’s worth fixing on my side too.
updated to 306 and not working for me. Constant stop starts ![]()
I wonder what the point of having a “Clear Queue” option that asks “ok” or “cancel” but clears it before the dialog box comes up
. It is a nice way to stop all music from playing though.
Just there to keep you on your toes.
At sign on I now keep getting this msg! ![]()
Could not save credentials for the background service. Please quit and reopen Maestro, then sign in again.
Same problem - Paul is there a problem with sign in ? - despite entering the correct user name and password i am not able to get into Maestro - log sent
I just sent you a note explaining. Let me know if that works.
I sent Chris instructions. Weird it’s happening to two of you maybe there’s something else amiss? Here’s what I wrote nearly musical:
Quit Maestro completely (right-click its icon in the Dock and choose Quit, or Cmd-Q with the window focused). Then open Finder, hold the Option key, click the Go menu at the top of the screen, and choose Library. In that folder open Application Support, then Maestro, and delete the file named auth.json if it’s there (it holds only the broken sign-in, nothing of your music or settings). Empty the Trash, reopen Maestro, and sign in once more — this writes a fresh, whole token.
I will try that when i get home from work today. Also when you click on maestro to open it, it first comes up with downloading your music and gold circle spins and dosnt stop while asking you to login in and that is where i get the msg.
Hi Paul
I am back in now . Followed your instructions - I tried logging in directly after emptying the trash but no joy - so I rebooted and I am back in - maybe it was the reboot maybe a combination of deleting that file auth.json and rebooting - but whichever - Maestro is back in the room. Thanks you -as always - for your super quick support
Jeff,
The banner is right, and it’s pointing at a macOS setting rather than a Maestro bug. Maestro reaches your T8 over the local network, and macOS has a per-app permission for exactly that which sometimes gets switched off after an update.
Open System Settings → Privacy & Security → Local Network, and make sure both Maestro and maestro-service are switched on. Then quit and reopen Maestro; the T8 should come back within a few seconds and the banner should clear.
Two other things I can see in your screenshot: the library scan is working through 75,000 files and will take a few hours — normal for a collection that size, and playback works while it runs. And the “Finishing sign-in” line at the top is a known bug in this version, fixed in the one building now; it’s harmless to dismiss.
Hi Paul, Maestro asked for permission for Maestro-service for access which I allowed but it does not show up. I have not seen Maestro -service for some time , but honestly never looked. Also note Maestro duplicates. Thanks,
Jeff
(Attachment maestro-diag-11.0.306-20260902-113340.zip is missing)
Rebooted Mac Pro laptop this morning and local albums appeared and have been listening for about 3 hours with no glitches and then started skipping stop starts every once and a while then got worse and now finally stopped completely. I would think Maestro would either work or not. Does anyone know why this would happen maybe Paul can chime in? I really hope at some point this all could be resolved as it does sound amazing.
That pattern — fine after a restart, then skips and stop-starts that get worse over a few hours until playback stops — isn’t random, and it isn’t your setup. It’s a class I’m actively working on where the control link between the app and the audio engine degrades over a long session on the Mac. The reboot resets it, which is why it looks like “works or doesn’t.”
What would help me most: the next time it starts skipping, before you reboot, go to Settings, Save Logs to Desktop, and email the file to me. The log from the moment it degrades is worth more than anything I can guess from here.
Thanks Paul, when I go to settings how do I save the log? I’m not to great on the computer, I only know basic stuff but with Maestro I’m learning more ![]()