Digital Performer 11.23 released

[labman]

I didn't notice any sort of *snappier* behaviour, though

[James Steele]

I didn't notice any sort of *snappier* behaviour, though

“MOTU must face!”

[jlaudon]

[...]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 updated to 11.23, I'm still on Monterey mid-project so I won't upgrade my OS yet. I did find a couple issues... once in a while if I drag a soundbite, DP will just crash instantly. Another issue is that in my current music project, I have to constantly import WAV files and mp3s, now the importing time and conversion time is about 3-4 times slower than in 11.22.

[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). 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.

I don't know why you believe this is an Apple Silicon vs Intel issue. It's not. Nothing I can find on motu.com or in the release notes indicates that it's anything other than Ventura (and now Sonoma). I have yet to begin a project on either of my Apple Silicon Macs.

This is a file I created on my 2017 iMac in 2022 over Monterey. I no longer have a Mac on Monterey but pulled this from the archive and loaded it onto three Macs. All three Macs are running DP 11.23 and I created these screenshots this afternoon.

Before I went to Ventura in January 2023, my BTD window looked like this:

2012 MacBook Pro Catalina 10-19-2023.png (67.02 KiB) Viewed 2720 times

After rebooting and firing up DP, they look like this.

2020 iMac Ventura 10-19-2023.png (129.55 KiB) Viewed 2720 times

This is the same file on my M2 Studio:

2023 M2 Mac Studio Ventura 10-19-2023.png (163.81 KiB) Viewed 2720 times

I could load the same project on my wife's M1 MacBook Air but we all know how it would look.

[mikehalloran]

These are the only mentions of Ventura and macOS 13 in the DP Release Notes. Nothing about Intel vs Apple Silicon:

Screenshot 2023-10-19 at 3.05.05 PM.png (111.97 KiB) Viewed 2711 times

Screenshot 2023-10-19 at 8.24.46 PM.png (228.48 KiB) Viewed 2705 times

Screenshot 2023-10-19 at 8.28.34 PM.png (136.72 KiB) Viewed 2705 times

[motujared]

These are the only mentions of Ventura and macOS 13 in the DP Release Notes. Nothing about Intel vs Apple Silicon:




Screenshot 2023-10-19 at 3.05.05 PM.png

Screenshot 2023-10-19 at 8.24.46 PM.png

Screenshot 2023-10-19 at 8.28.34 PM.png

Thanks for the additional info - after a bit of further digging on our side I can shed a bit more light on the situation but unfortunately I don't have a way of fixing it directly. However, I can at least try to explain what leads to this behavior.

The names of the outputs in the BTD windows are pulled from the Bundles window. Each of the bundles in the Bundles window will default to naming itself based on the outputs it is assigned to, unless a custom name is set. It looks to me like your project contains two bundles, neither of which has a name set, which causes it to pull from the assigned outputs.

In the built-in empty document template, there is one named bundle ("Main Out L-R"). I'm assuming based on your screenshots that you've modified this by changing the document(s) in question and/or using a custom new document template with un-named bundles. What this means is that your bundles are now pulling from what the audio driver is returning.

The reason I had initially mentioned Apple Silicon was because I was primarily seeing this issue with the built-in audio driver on Apple Silicon devices, and found it to be working fine when I quickly checked this on an Intel Mac running Ventura. I've since managed to identify at least one Intel Mac running Monterey which also exhibits this issue, which means it's not isolated to Apple Silicon nor is it a Ventura-specific issue. The bug really is just that certain Macs do not return the correct metadata when using the built-in audio. If you have another audio output, you could confirm this by choosing that (from Configure Hardware Driver) and checking that those output names change - for example, when I tried connecting to my HDMI monitor's audio out, that description changed to the name of my monitor.

If you're using a custom template, you should be able to assign a name to those bundles in your template once + save that new template as your default, and then make new projects from that template. Subsequent projects made from that template should be named correctly, and that name should persist regardless of the audio interface as the bundle name will be what shows up in the BTD window. This won't work for your existing projects, but renaming the bundles as I mentioned before should also stick. (I know you mentioned it's not a big deal, just wanted to offer that possibility in case you wish to try it).

Hope that helps/clarifies things!

Edit to add: The changelog entries you had pointed out are unrelated to this - only speaking for myself, of course, but I was not aware of this issue previously.

[mikehalloran]

If you have another audio output, you could confirm this by choosing that (from Configure Hardware Driver) and checking that those output names change -

I have 11 audio outputs including 6 physical and 5 more virtual. Some do change the name; others do not but none of those I use do.

Knowing the issue makes it relatively unimportant but it does confuse people. There are other problems that should have higher priority.

[greg328]

So-if we’re running OS 13.6 Ventura- is there any compelling reason to update to DP 11.23?
Greg


Sent from my iPhone using Tapatalk

[James Steele]

So-if we’re running OS 13.6 Ventura- is there any compelling reason to update to DP 11.23?
Greg


Sent from my iPhone using Tapatalk

My understanding is DP 11.23 is a maintenance release to fix some issues specific to Sonoma. I’d say probably not.

[greg328]

Thanks James---I'll wait---I'm going to update to Sonoma as soon as most of my plug-in vendors give the OK!
Right now, almost none of them are ready

Greg

[cuttime]

There's a new build of 11.23 (94363) available today, but nothing seems to be noted in the changelog.

[Luke]

There's a new build of 11.23 (94363) available today, but nothing seems to be noted in the changelog.

Thanks for the heads up brother.

[Michael Canavan]

There's a new build of 11.23 (94363) available today, but nothing seems to be noted in the changelog.

Awesome catch, There's some issues with plugins here, I'm on Sonoma though, so hopefully that's part of it.

[funkyfreddy]

I just upgraded to MacOS Monterey and then to this latest version of DP. All seems well so far....