Digital Performer 11.23 released

[SMS]

Fixed all the issues I noticed.

Thanks, Motu for a quick and apparently well implemented fix.

[apanacci]

Hey guys where are the update notes ?

[Phil O]

...There are a number of apps that should not be run over Sonoma yet including Finale...

I haven't had any problems with Finale (yet). What issues are you seeing?

Your friendly neighborhood Phil

[motujared]

Nope. That screen shot could have been from my iMac Pro—the 'other machine' where I saw it first.

Whereas MOTU fixed the Core Audio issue with 11.2x, they acknowledged that this is still a thing and that they were aware of it. As I have not updated to Sonoma, I was hoping for a fix. I have no doubt that MOTU is still aware of it.

You don't have to say "they," Mike. You can say "you." Jared is a developer at MOTU and he tends to be pretty much on top of these things and is drawing from multiple reports at this point, most likely.

But way to make the MOTU rep feel welcome here!

A) I don't know that — sorry Jared.

b) I was quoting MOTU release notes from an earlier update about being "aware of it."

c) the screen shots were identical on my Intel Mac that I decommissioned yesterday and the M2 Studio I received a few days ago.

No worries. I'm admittedly not sure what you're referring to in regard to release notes; if you can point me to the specific update note I might have a better idea of whether we were previously aware of this issue, or if it just sounds similar to a different issue.

Upon further investigation, I'm not seeing this issue on Ventura with Intel, so I'm not sure exactly how it's happening for you. Correct me if I'm wrong, but my best guess is this: the projects you're seeing this in may have been created on Apple Silicon (with built-in audio selected) and as a result, the bundle names defaulted to the odd names that the built-in audio driver is returning on Apple Silicon. Once these bundles were created, those names would have been saved into the project (and the output bundle names are what shows up in the Bounce to Disk window). If this theory is correct, a few things would also be true:

- You wouldn't see this behavior in new projects created while connected to an interface other than the built-in audio.
- If you were to correct any bundle name once, it should persist (and not get reverted back).
- If you create a project on an Intel Mac and bring it over to Apple Silicon, existing bundle names should stay correct.

Hopefully some of that is helpful. I know you mentioned it's a minor/cosmetic issue, but I was surprised to hear that it "changed" for you, as my understanding is this should not occur.

[mikehalloran]

Upon further investigation, I'm not seeing this issue on Ventura with Intel, so I'm not sure exactly how it's happening for you. Correct me if I'm wrong, but my best guess is this: the projects you're seeing this in may have been created on Apple Silicon (with built-in audio selected) and as a result, the bundle names defaulted to the odd names that the built-in audio driver is returning on Apple Silicon. Once these bundles were created, those names would have been saved into the project (and the output bundle names are what shows up in the Bounce to Disk window).

My M2 Studio arrive last week. I have yet to begin a project on the Studio or any other Apple Silicon Mac.

I've had an Intel iMac Pro since 2017. The change happened the moment I updated to Ventura in January and I opened a project I was working on. I posted about it here at the time and the inability to roll back the MacOS with APFS Snapshots in another thread after having had a long talk with Apple on this and other Ventura issues.
https://www.motunation.com/forum/viewtopic.php?t=64689

I can open any old project ever created going back to those begun in DP 2.7 and get the same result.

Although I have de-commissioned the iMP, I can load an old project on my 2012 MBP running Mojave or Catalina, then load it onto my wife's 2020 iMac running Ventura and get screen shots from all. Not today, I have a project with a steep deadline. Tomorrow, I'll be in Cupertino with Apple Engineering trying to suss out a problem regarding the Studio and multiple displays—not the only one complaining about it but I may be the only person who knows enough to have found a workaround till they fix the problem. I have consulted to Apple on and off since 1986.

[cuttime]

Hey guys where are the update notes ?

The release notes are always in the installer these days.

Enhancements introduced in version 11.23

Fixes
• Fixed a bug causing the Mac menu bar to not activate without double-clicking on macOS Sonoma.
• Fixed a bug causing the titlebar height to appear incorrect on certain windows in macOS Sonoma.
• Fixed a menu bar text alignment bug in macOS Sonoma.

[motujared]

Upon further investigation, I'm not seeing this issue on Ventura with Intel, so I'm not sure exactly how it's happening for you. Correct me if I'm wrong, but my best guess is this: the projects you're seeing this in may have been created on Apple Silicon (with built-in audio selected) and as a result, the bundle names defaulted to the odd names that the built-in audio driver is returning on Apple Silicon. Once these bundles were created, those names would have been saved into the project (and the output bundle names are what shows up in the Bounce to Disk window).

My M2 Studio arrive last week. I have yet to begin a project on the Studio or any other Apple Silicon Mac.

I've had an Intel iMac Pro since 2017. The change happened the moment I updated to Ventura in January and I opened a project I was working on. I posted about it here at the time and the inability to roll back the MacOS with APFS Snapshots in another thread after having had a long talk with Apple on this and other Ventura issues.
https://www.motunation.com/forum/viewtopic.php?t=64689

I can open any old project ever created going back to those begun in DP 2.7 and get the same result.

Although I have de-commissioned the iMP, I can load an old project on my 2012 MBP running Mojave or Catalina, then load it onto my wife's 2020 iMac running Ventura and get screen shots from all. Not today, I have a project with a steep deadline. Tomorrow, I'll be in Cupertino with Apple Engineering trying to suss out a problem regarding the Studio and multiple displays—not the only one complaining about it but I may be the only person who knows enough to have found a workaround till they fix the problem. I have consulted to Apple on and off since 1986.

This all sounds somewhat odd to me, and I would certainly be interested to know the results of this if/when you get a chance to try it. If you're up for a bit of troubleshooting and can PM me the project file (both versions, before and after having opened it on Ventura), that would be helpful for us to see what might be going on.

[sayatnova]

Odd, 11.22, says it is the most current and when I look for an update it says it is the most current?.... Did something change?

[HCMarkus]

Odd, 11.22, says it is the most current and when I look for an update it says it is the most current?.... Did something change?

MOTU.com:

Digital Performer 11
Mac v11.23+94219 | Oct. 12, 2023

[mikehalloran]

Odd, 11.22, says it is the most current and when I look for an update it says it is the most current?.... Did something change?

Updating from within DP 11.22 showed none available. The downloads page does as mr. Marcus pointed out.

[James Steele]

Updating from within DP 11.22 showed none available. The downloads page does as mr. Marcus pointed out.

I reported this directly to a contact at MOTU. Seems like MOTU would want to make sure this feature works as it's much more convenient than having to go check their website.

Personally, I'm eager for an update to their audio drivers now that I'm on Sonoma. My gut feeling tells me there *must* be some tweaking they could do to improve them since I *think* they pre-date Ventura. Perhaps even Monterey?

[sayatnova]

Thanks James and Mike,

Will go to the website to update. However, if I did not see the info here, I would not have know to have done so...

[James Steele]

I heard back from a source at MOTU that since the 11.23 release was so specific and only applied to a relatively small number of users that are running Sonoma, that they elected not to trigger the built in update notification in DP. They have the capability, but chose not to "ding, ding" thousands and thousands of users around the world for a fix that wouldn't apply to over 90% of them I guess.

[daniel.sneed]

[...]They have the capability, but chose not to "ding, ding" thousands and thousands of users around the world for a fix that wouldn't apply to over 90% of them I guess.

I took the plunge. So Far so good on Monterey. I didn't notice any sort of *snappier* behaviour, though

[mikehalloran]

[...]They have the capability, but chose not to "ding, ding" thousands and thousands of users around the world for a fix that wouldn't apply to over 90% of them I guess.

I took the plunge. So Far so good on Monterey. I didn't notice any sort of *snappier* behaviour, though

I know. What's up with that?

OTOH, Performer Lite was updated to 11.23 yesterday and I'm not noticing anything different. I'm pretty certain that none of my people are running Sonoma — not getting any "Mike, why doesn't : work now?" calls so I'm safe for the moment.