Anyone using Paul's Maestro Music management system?

V90, same issue I last reported

while playing a track, clicked on a different track in album, does not play, and displays…

then tried another album

even though AirLens shown on bottom of window, play came over computer speaker

switched on the bottom from Airlens to System Audio and back to Airlens…plays both on computer speaker and Airlens

same as reported the last few weeks

quit Maestro…play continued

started Maestro up again, play continued for several seconds and stopped

SQ so nice

update: played another Qobuz album all the way through, when got to end did not stop, kept repeating the last track

trying to go from a favorite track to another track, Maestro goes on autopilot and stars playing tracks

I think there is a buffer of some sort that stores bits. When I stop or change tracks, I get sound from computer and AirLens for a while, then one of them alone

I spend half my time opening and closing and re-opening Maestro

Only starting an album and let it play sees to play as intended, though last track keeps repeating

so tedious remains; never had any of this with any other music app

I have been having the same issues for some time on my iMac/Intel. How long did it take for all of your albums to load? I have never been able to get that far before the program times out.

On v. 90. Macbook?silicone. Grimm MU2.

Playback issues continue.

Play an album from local files, stop it, go to Qobuz and click Play Now on a new album and instead of playing the first track, the last track in the previous album resumes playing. Had to click on a couple of different tracks in the new album to get the “old track” to stop playing; and then click on the first track of the new album to start. Same thing when stopping and going to a different album in Qobuz.

Played a couple of tracks without issue but then half-way through a track it jumps to the next track. This happens infrequently.

If you go through Qobuz favourites, click on an album and then click Back to back to the favourites list, you go to the top of the favourites list instead of the location of the location of the album that you were just looking at. This was fixed for local files but still happening in Qobuz.

Qobuz favourites issue. While saving a new album as a Qobuz favourite saves it as favourite in Maestro, it doesn’t appear as favourite in either Roon or in Qobuz. If I save an album as a favourite in Roon, it will show in Qobuz as a favourite (and vice-versa), it doesn’t appear as a favourite in Maestro automatically. I eventually figured out that you have to go into Setting settings and click on the Refresh Favourites button to import new favourites. Would be nice if this happened automatically.

Here’s a strange one. Maestro is playing. I’m browsing on my iPad (Safari or Chrome), click on a link to a YouTube video and Maestro stops playing. Have to go back to my MacBook and close and restart Maestro in order to get it play. Doesn’t happen if I click on a YouTube video link in the browser on my MacBook; only when I’m using my iPad.

I haven’t tried Maestro yet but I have a suggestion if using Jriver as a model. The issue I have using JRemote is that for large libraries, when browsing artist names for example, some letters get extremely long. I’d love to see some way of navigating via a second letter or way to get to the second half of the artists that start with letter S, if that makes sense.

Also hoping there is a way to navigate the different folders I have made on my hard drive. I Would also love to be able to sort by file type or sample /bit rate. I have several albums t where I purchased one sample rate the tAnother higher sample rate.

Another thing I use a lot in Jriver is convert from flac to WAV, and also the feature to locate the file on hard drive

Hi Paul,

I fired up Maestro to get the log file you requested and a new version auto-downloaded and installed.
The app quit (crashed?) and restarted automatically showing this error:

Went to the Support menu and tried to drag and drop the log .zip file here:

but that didn’t work. Browsing to the file worked and the logs should be winging their way to you now :slight_smile:

The “Maestro could not start its window” error persists after each launch of the app.

My CPU is:

The “play/not-play on-add” behaviour should be an option in Settings.
Regards
Mark

V190 - same issue with Ella - only 1 track generated…

Hi Paul,

App was showing Local library → Artist view.
Went for a 45min walk and came back to this:

The app appears to be a heavy user of CPU and memory resources. I wonder if this explains the less than responsive behaviour I experience when browsing/searching my local library?
Upon selecting Local library → Artist view (or any view for that matter) and then do nothing - just leave it alone, the fan on my CPU kicks in and I notice this:

Now trying to see if I can get Maestro to play tunes from my local library without crashing.
Navigate to an album. Select a track. Click on the RHS … (more options) menu. Select ‘Add to Queue’. Get a popup message saying the song has been added to the queue.
But there is nothing in the queue! As I was typing this message it started playing. I guess that was after a delay of ~20 seconds, so I guess it’s not all bad news :slight_smile:
Paul - I am sorry, but I am going to leave Maestro for now.

Regards
Mark

Yeah, I am having even more fun with Ella than that. Sigh. Working on it.

No Maestro, no Roon, no music yet. World Cup is getting interesting so I will watch that. I will try Maestro after v200. :grin:

Wish I could help - only 65 and I have no clue about programming….lol. Good luck PauL

@Paul
Can you please help with my previous request?
I’m stuck with progressing the setup of Maestro.
Thanks,
Phil

I’ve set up the free 30 day demo and come to a window requesting local network access.
I click on “show macOS Permission Dialog’ and it comes up with “Requesting” transiently then nothing more. What next?

Thanks

Hi Philip, glad to see you’re giving Maestro a go.

This is a macOS quirk rather than anything you’ve done wrong, and it’s fixable in a minute or two.

Background: macOS only shows that Local Network permission dialog once per app. If it thinks it has already asked (or if its prompting system gets stuck, which is a known macOS issue), clicking our button fires the request but the dialog never appears — exactly the “Requesting…” flash you’re seeing.

Please try these in order:

  1. Open MAC System Settings → Privacy & Security → Local Network. If Maestro is in the list, switch it ON, then go back to Maestro and click “I’ve allowed it — continue.” That’s usually the whole fix.

  2. If Maestro isn’t in that list: quit Maestro completely (Cmd-Q), relaunch it, and try the permission button again.

  3. If the dialog still won’t appear: restart your Mac, then launch Maestro and try once more. A restart clears the stuck state in macOS’s permission system — this resolves nearly all remaining cases.

  4. One more possibility: if your Mac is running macOS 14 (Sonoma) or earlier, this permission doesn’t exist on your system at all — Apple added it in macOS 15. In that case there’s no dialog to grant, and you can simply click “I’ve allowed it — continue” and carry on with setup.

You’ll know it worked when setup proceeds and Maestro can see your other devices.

If none of that gets you moving, tell me which macOS version you’re on (Apple menu → About This Mac) and I’ll dig deeper — and thanks for giving Maestro a try. You caught us on setup’s one awkward handshake with macOS; the listening is better than the paperwork, I promise.

Hi Mark,

The Task Manager capture shows the app burning a quarter of a CPU core while sitting idle on the Artist view — that should be zero, and it’s the same engine that slowly eats memory until the Out of Memory crash you came back to after your walk.

It also explains the sluggish browsing you’ve felt all along: your clicks were competing with a busy loop that shouldn’t exist. You’ve handed us the exact recipe to reproduce it — open Artist view, touch nothing, watch the fan — and that’s the hard part of any bug like this.

The 20-second Add to Queue delay is logged as its own defect too.

One small favor, only if you’re willing before you set it aside. As you try again for a bit: Maestro Help → Export Diagnostics and send me the file. It captures what the app was doing during that idle burn and would shortcut the fix considerably. If you’d rather just be done for now, that’s fine too.

Separately — the Windows startup bug from this week’s update (the flash-and-error-dialog on launch) is fixed in v11.0.193, rolling out in another hour or so, and the fix for bit-perfect exclusive playback to your Singxer is built and close behind it.

V193 is close to shipping so try that please.

Hi Paul, first I want to tell you how impressed I am with how hard you’re working on this. I’m not sure I’ve ever met anyone more dedicated to making things work right - whether hardware or software - in the service of good music listening in high-end audio. I know this must be frustrating as hell, and it might seem like all people are doing is yelling at you, but I think I speak for a lot of people contributing to this topic that you are doing something few of us would attempt, especially when you SHOULD BE RETIRED, dammit!

That being said, I would like to jump in and give this a shot, but in order to effectively compare it to Roon, the roonfeature I like most, that seems to have the biggest effect on my sound, is the application of convolution filters for room-correction. I’m not sure whether Maestro has enabled that feature yet. What’s the status?

Thanks again for your dedication to this project.

Hi @Paul - I’m one of the folks watching from the sidelines anxiously anticipating the release of the iPad version of Maestro. I understand you have been using it for some time already. My question is how you would characterize its current stability and feature maturity? In other words, is it your expectation that it will be subject to the same amount of user interaction in its early months as has been the experience of PC/Mac users? My hope is that the limited variability in the target iPad platform will present less of a challenge than the seemingly endless combinations of hardware and software variables in the PC/Mac world.

Thank you for your dedication to this project. It will be well worth waiting for.

You’re very kind and BTW, if I retired I’d go crazy. I have no intention of retiring when I am having this much fun, despite the frustrations. :blush:

Remaster, the DSP suite, is not yet active. Final touches on Maestro’s stability and speed, then iPad release, then Remaster DSP suite.

The good news is that with a few exceptions, like one or two unique bugs to iPad, there will be identical performance as you have with the desktop version and that will be true from day one.

I designed Maestro for the very beginning to be like that, where the iPad is more of a remote than a brain—and in this way, Roon and the others are the same. You can’t use the Roon iPad version without the Roon server running and what’s really happening is the iPad is simply a remote control for the Roon server that’s doing the work.

I modeled Maestro in the same way except, instead of the desktop server doing the work, Maestro does most of the work in the Cloud. So, whether desktop remote is controlling Maestro cloud server, or iPad is controlling cloud server, doesn’t really matter much.

So, hopefully that makes sense.

Lastly, this should also help folks understand why in a number of cases with problems you send to me they are fixed within a few minutes and fixed for all users. That’s because I am able to fix the cloud server.

Lastly, I am using the iPad app daily.

Good morning Paul, just tried V193 and tried Ella again. She threw the following error:

API 503: {“success”:false,“error”:“Ella couldn’t start this station — try again”,“reasonCode”:“no_pool_candidates”,“stage”:“stage1_opener”,“openerPick”:{“poolCandidates”:0,“eligible”:0,“excludedByHistory”:0,“resolveFailed”:0,“relaxationRung”:null}}