Digital Performer 11.23 released

[James Steele]

Looks like MOTU released DP 11.23 today. It’s reported that it fixes the menu double click issue in Sonoma. Haven’t checked the release notes yet for any other fixes.

UPDATE:

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.

[hammerman]

Thanks James!

Yes, all those issues are now fixed for me.

[mikehalloran]

Not on Sonoma yet but update is smooth here.

Performer Lite has not seen this update yet but there are no surprises there; PL usually lags when DP is updated.

OTOH, I was finally able to activate PL today. iLok, TLC and one PSP license were getting in the way but this is the first time that I have seen those messages so that I could deal with them. Now that I have worked through that mess, PL finally activated. I don't know why these issues didn't get in the way of DP—but they didn't.

[bayswater]

Looks like the Sonoma fixes is all there is in the Mac version. I don't see the usual release notes anywhere.

[mikehalloran]

Looks like the Sonoma fixes is all there is in the Mac version. I don't see the usual release notes anywhere.

I see a Windows download but it may just be a re-naming to be consistent with the Mac version.

[Killahurts]

Looks like the Sonoma fixes is all there is in the Mac version. I don't see the usual release notes anywhere.

I'm still on Monterey.. if I updated to anything, it would be Ventura. Does that mean I skip this version of DP?

[Michael Canavan]

Looks like the Sonoma fixes is all there is in the Mac version. I don't see the usual release notes anywhere.

I'm still on Monterey.. if I updated to anything, it would be Ventura. Does that mean I skip this version of DP?

You want to skip Monterey, https://www.bluecataudio.com/Blog/tip-o ... e-silicon/

[HCMarkus]

Looks like the Sonoma fixes is all there is in the Mac version. I don't see the usual release notes anywhere.

I'm still on Monterey.. if I updated to anything, it would be Ventura. Does that mean I skip this version of DP?

You want to skip Monterey, https://www.bluecataudio.com/Blog/tip-o ... e-silicon/

Thinking you mean "Skip Ventura," Mike...

[mikehalloran]

I'm still on Monterey.. if I updated to anything, it would be Ventura. Does that mean I skip this version of DP?

You want to skip Monterey, https://www.bluecataudio.com/Blog/tip-o ... e-silicon/

Thinking you mean "Skip Ventura," Mike...

Ventura is pretty solid by now—the only app that has issues for me is DP* and it's minor. There are a number of apps that should not be run over Sonoma yet including Finale.

*DP still shows output track numbers instead of names in BTD over Ventura. MOTU "is aware of this" but has yet to correct it. This is not how it looked in Monterey and earlier. Had I known, I would have stayed there on my iMP. Now that I have a Studio, I'm glad I updated on the other machine or this would have freaked me out a bit:

[Rick Cornish]

If that's all they changed, I'll stand pat at 11.22 (on Monterey) until my album is finished.

[motujared]

You want to skip Monterey, https://www.bluecataudio.com/Blog/tip-o ... e-silicon/

Thinking you mean "Skip Ventura," Mike...

Ventura is pretty solid by now—the only app that has issues for me is DP* and it's minor. There are a number of apps that should not be run over Sonoma yet including Finale.

*DP still shows output track numbers instead of names in BTD over Ventura. MOTU "is aware of this" but has yet to correct it. This is not how it looked in Monterey and earlier. Had I known, I would have stayed there on my iMP. Now that I have a Studio, I'm glad I updated on the other machine or this would have freaked me out a bit:

This appears to be an issue that is specific to Apple Silicon devices where macOS returns those names when using the built-in Mac audio, which causes new bundles to default to this naming upon creation. You should be able to get around this, at least in your BTD list, by going to your Bundles window and renaming the relevant output bundle(s) (opt/alt-click on the name in the list). The actual outputs themselves will retain this name in the Bundles window (at the top of your Outputs grid), but the outputs list in the BTD window should update accordingly.

[James Steele]

Whoohoo! Thanks, Jared for sharing this. For those who aren't aware, Jared works at MOTU and is a freakin' genius. He has helped me get issues with EUCON support in DP worked out, just as one small example. Thank you for posting here, Jared!

[mikehalloran]

I'm glad I updated on the other machine or this would have freaked me out a bit:

This appears to be an issue that is specific to Apple Silicon devices where macOS returns those names when using the built-in Mac audio, which causes new bundles to default to this naming upon creation. You should be able to get around this, at least in your BTD list, by going to your Bundles window and renaming the relevant output bundle(s) (opt/alt-click on the name in the list). The actual outputs themselves will retain this name in the Bundles window (at the top of your Outputs grid), but the outputs list in the BTD window should update accordingly.

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.

Knowing about it is all I need. I am most definitely not going to rename all the bundles in all the projects that I open in Ventura.

I had a long talk with Apple about reverting to Monterey after the Ventura update and posted about it at the time. APFS Snapshots can roll back the Data Volume but not the MacOS Volume which is now sandbagged. The only way to revert the OS is to wipe the drive, reinstall the older OS and do a Time Machine Restore. On a nearly full 4TB internal NAND, takes over three days since TRIM and Garbage Collection have to prepare the cells before they can accept new data. On an empty 8TB internal drive, it's closer to 32 hours. I've done both within the last year.

[James Steele]

I'm glad I updated on the other machine or this would have freaked me out a bit:

This appears to be an issue that is specific to Apple Silicon devices where macOS returns those names when using the built-in Mac audio, which causes new bundles to default to this naming upon creation. You should be able to get around this, at least in your BTD list, by going to your Bundles window and renaming the relevant output bundle(s) (opt/alt-click on the name in the list). The actual outputs themselves will retain this name in the Bundles window (at the top of your Outputs grid), but the outputs list in the BTD window should update accordingly.

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!

[mikehalloran]

This appears to be an issue that is specific to Apple Silicon devices where macOS returns those names when using the built-in Mac audio, which causes new bundles to default to this naming upon creation. You should be able to get around this, at least in your BTD list, by going to your Bundles window and renaming the relevant output bundle(s) (opt/alt-click on the name in the list). The actual outputs themselves will retain this name in the Bundles window (at the top of your Outputs grid), but the outputs list in the BTD window should update accordingly.

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.