Hello Paul
I am still not able to play local files. As I explained my files are on the same Mac Mini m2 that Maestro sits, so its not an NAS power down issue. I have seen the following message on start up
“macOS blocked maestros direct command link on this Mac. Transport commands may not reach your renderer”
I am on V11.0314. log sent
Thanks
That card does not appear. It’s either the list of network device, or the list of manufacturers on the right. Searching for “Speakers (X-SPDIF Series)” brings up nothing. Hmmmmm.
Logs sent…
Chris,
You’re right, it isn’t the NAS, and your log shows exactly what it is. Your Maestro sign-in session had silently expired — the app kept working for streaming but every request to play a local file was refused as “not signed in,” and the message you saw was the polite version of that. It’s a bug on my side that the app didn’t just sign you back in; I fixed the cause this morning, but your machine still holds the dead session.
Two steps. First: in Maestro, sign out (left sidebar, bottom) and sign back in with the same email. Then play a local file. Second, for the “direct command link” banner: System Settings → Privacy & Security → Local Network → make sure Maestro is switched on. If it was off, quit and reopen Maestro.
Tell me what happens on the first local track after that. If it still refuses, Settings → Export Logs and I’ll read it the same hour.
Hi Paul
I did as you said and - In System Settings → Privacy & Security → Local Network → there were two Maestros listed - both switched on - here is the log
Cheers
Chris
(Attachment maestro-diag-11.0.314-20260907-191558.zip is missing)
As per our recent e-mail exchange
All sorted - enjoying local files again - thanks
Best regards
Chris
Not a good day for Maestro here. 315 and 316 don’t work at all on my laptop.
Sadness. Add 311 to the list. Sigh.
280 works. I’m giving up.
So the laptop won’t run the newer versions, my desktop does. There is a change I appreciate:
Oddly though, even though I can now run through the above tests, it still displays this on playback:
Yes. I was going to post the same thing.
Yes. The newer versions will run… eventually but take ages - like 5 minutes and many crashes to install and open countless command windows in Windows. I’ve gone back to 280 now for everyday use.
What? OMG, sorry, I wonder why not. They seem to work for a few hundred other laptops. Al, can you please send me a log?
I sent it last night my friend. ooops, no I didn’t.
Sent now.
Al,
Thanks!
Windows’ embedded browser component refuses to start on your laptop with the runtime we bundle, and Maestro quits instead of falling back to the one Windows already has. 280 predates the bundled runtime, which is why it works. It’s ours, it’s the same fault a few others hit, and the fix is in the release I’m cutting today.
To get you playing now: right-click the Maestro tray icon → Exit; Settings → Installed apps → uninstall Maestro; restart Windows; then delete these two folders if they exist (paste into the File Explorer address bar): %LOCALAPPDATA%\com.psaudio.maestro-connector and %APPDATA%\Maestro. Then install https://api.maestroaudio.net/downloads/v11.0.280/Maestro_11.0.280_x64-setup.exe and decline the update offer until I post that the fix is out.
280 works fine right now. It was the 300 series that was sad. The screen would fill with endless terminal loads. And it took forever to get to the window that would let me make a log file. And that only worked once. It was a struggle. Plus, I would restart the laptop each time, use Windows to uninstall Maestro, reboot again, try another install. It was a lot of attempts. Then I reached for 280 which worked before and crossed my fingers. I was so happy when it worked.
Should I still delete those folders even though a fix is coming and 280 works?
Al, thanks for this.
The endless Terminal windows are Maestro’s own fault: on startup it probes Windows for graphics and browser-runtime details, and on the 300-series builds each probe opened a visible console window instead of a hidden one. Dozens of them.
On your laptop the embedded browser component then refused to start with the runtime we bundle, and instead of falling back to the one Windows already has, Maestro quit.
280 predates both the probes and the bundled runtime, which is why it starts on your laptop — but it’s a different Maestro. 300 was the line where Maestro left beta:
the local library was rebuilt from the scanner up (NAS shares, embedded artwork, sleeping-drive handling, the new Manage page),
Ella’s playlist builder went to v2 with the Styles, Moods and Seasons collections behind it, and every release since has carried a required set of tests for the five things that must never break — opens, signs in, plays, advances, updates.
On top of that foundation the last two weeks added the sign-in fix, the WiiM, Auralic and ECM playback fixes, album grouping that keeps a best-of together, pause that resumes where you left it, track changes in under two seconds instead of eight, local outputs on the Devices page with their own format test,
and a Qobuz link that stays linked.
None of that exists in 280. The 300 series is the one to be on; it just has to start on your machine first.
Both faults are fixed in the release I’m cutting today (11.0.317): the probes run hidden, the runtime ladder steps down instead of quitting, and the installer clears the two folders that were poisoning it — so no, don’t delete anything yourself, and don’t uninstall. When I post that 317 is out, install it straight over 280 and it should open first try. If it doesn’t, the dialog it shows has an Export Logs button; press it and send me the zip.
I have Kii 3BXTs arriving in a few minutes. I have a Maestro Playlist ready to be the first thing I listen to with them. Once it has been played I have lots if time to get current.
It is important to me that Maestro be the first source I test.
I have my Turntable and CD transport, and Roon (bah) ready as well. It’s going to be a fun day at Al’s house.
Congratulations! It will be amazing if Kii beats a $800k system. 
Don’t forget they need 1K+ hours break in, but may be they are better within the first hour already 
Crickets!
Too much fun at Al’s!
We have a lifetime subscription to Roon, but we just signed up for a yearly subscription to Maestro Music.
Good job Paul!
Thanks! I think you’re going to have fun. The interface seems a bit easier to navigate, but the sound…I still smile when I hear this.
__
Paul McGowan
CEO PS Audio
www.psaudio.com
The new Audiophiles Guide
My apologies to the Maestro folks and especially Paul! He sent me a fix for my laptop issues last night asking me to try it. I didn’t see it until this morning and the fix worked perfectly! But my delay was unfortunate. Mea Culpa!
I am also a laptop user and have been following the dialog regarding some of the issues. I also down-loaded the latest fix this morning and am happy to say that it has resolved all of the major problems that I have been experiencing. On my system, without a doubt, Maestro sounds so much better than Roon (which I’ve been using for the last few years). Thank you Paul for the latest fix!
