ProTools 2023.12 available for download on Avid site:-)

[clbraddock]

Still no support for Sonoma

[Eric Lambert]

Originally Posted by off the wall

I don't think that would ever be an Avid decision to drop Rosetta support but rather Apple at some point in the future.

Apple may beat them to the punch but this is still far off in the future. The transition to Apple Silicon has been too slow and many devs are still using Intel-only code. Rosetta is essential for most of us, and kicking it to the curb will take time.

[[email protected]]

I like the signal path coloring, but I'd be much happier with Sonoma compatibility. I can't upgrade my computers until the next scheduled upgrade? Really? what happens if I buy a new Mac?

[JFreak]

Maybe not macOS 15 yet, but macOS 16 marks 5 years of ARM development time, so at that time Apple is no longer obligated to support anything Intel and may just cut it off "to speed up development" like last time with Snow Leopard.

macOS 17 the latest, writing is on the wall. So developers have two years grace period left, then it is bye-bye Intel

EDIT:

Checked. PPC --> Intel transition took 4 years from introducing Intel to dropping PPC. We are at 3.5yr now. Best case scenario, macOS 15 may drop Intel code.

[huzzam]

Originally Posted by [email protected]

I like the signal path coloring, but I'd be much happier with Sonoma compatibility. I can't upgrade my computers until the next scheduled upgrade? Really? what happens if I buy a new Mac?

What is urgent about Sonoma? It offers nothing useful for audio work, and Ventura is stable & still receiving all security updates.

Ok, if you get an M3/M3 Pro/M3 Max machine, you'll have Sonoma, but honestly the M3 Pro is a step backwards from the M2 Pro (for PT), and the M3 is probably not the chip you'd be looking at anyway. So this is only really relevant to the M3 Max Macbook Pros, so you might want to wait for official Avid support if you're looking at that one. Meanwhile, any other newly-bought Mac will be downgradable to Ventura.

[Skwaidu]

PT 2023.12 integrated renderer seems to be a failure to those of us mixing in 7.1.4 or 9.1.6, who would like to switch back and forth between our current external renderer setups, and the new internal renderer. A big reason for myself for swapping back to the external renderer would be the beta PHRTF (when are we getting offline export from DAR of that, and/or support in PT?)

The problem is, the Extermal Renderer mappings in the IO Setup Dolby Atmos tab cannot accept Subpaths as their output. If I create a 9.1.6 Main output, I could use the integrated Renderer to monitor off that (and actually need the main output to be the full size of my monitoring setup), but then I cannot swith to the External Renderer without completely revamping the IO setup - and vice versa, if I use the External Renderer with the necessary 7.1.2 main/bed output plus 3 stereo objects, I cannot quickly switch to use the internal renderer but need to activate the IO in the Output and Bus tabs.

Also confusing, but workable is the fact that the Dolby Atmos tab in IO Setup "steals" the outputs used for objects - however this combined with the above bug means, that without having assigned object tracks in a sessions, I cannot monitor my outputs 13-16 (the static object outputs) at all! I could monitor them fine back in 2023.9, without having a renderer connected or any object assignments in a session. It would be good if the design allowed this "double routing" (i.e. outputs can be assigned in the Bus tab, while being assigned as objects in the Dolby Atmos tab), like before.

So basically, fast Internal - External Renderer switching is possible only to those who monitor in nonstandard 7.1.2 or lower monitor configurations, and that configuration is below the recommended minimum of 7.1.4, until Avid allows subpaths to be selected as External Renderer outputs (or allows "sharing" between the Bus / Mapping to Output and the Dolby Atmos tabs)


To add, there is a bug / design flaw that is present since the 2023.6 introduced expanded bus widths: 7.1.4 and 9.1.6 bus widths are missing the most important subpath, 7.1.2! That used to be the maximum and there are still some plugins that use that width, so the user now has to create that subpath manually for all wide busses. I would personally wish for 6 stereo subpaths to be added to the default set as well, so all stereo pairs, i.e. wides, sides, rears, top fronts, top mids and top backs. It's cumbersome having to create those manually everytime, as they definitely are useful to have.

[jmp72]

Originally Posted by ZoeMusic

Does anybody know if you can still use the Dolby Atmos Music Panner with ProTools 2023.12 internal renderer? I didn’t see them using it in the video.

you can't, if you use it you need to use the external renderer

[Tweakhead]

We now have an "Attribute View Filter" lane in Memory Locations, that cannot be hidden or moved to a position after the last lane that we actually find useful. (eg. after Bars|Beats, Comments, etc.)
We had only just got rid of that ridiculous "Track Marker" column in the last version, and now we're back to square one with yet another useless column.
We also cannot hide this new Filter header that now eats up yet more space at the top of Memory Locations.

All of these newly-added features/options are appreciated by many users, but Avid also need to include a preference allowing users to hide them - this includes all the tabs at the bottom of the Edit Window (MIDI Editor/Melodyne/Clips Effects). Space is limited enough without being forced to display rarely-used "information".

Please give us options. . . ability to change all column orders, hide elements (header bars), etc.

[BScout]

Originally Posted by JFreak

Maybe not macOS 15 yet, but macOS 16 marks 5 years of ARM development time, so at that time Apple is no longer obligated to support anything Intel and may just cut it off "to speed up development" like last time with Snow Leopard.

macOS 17 the latest, writing is on the wall. So developers have two years grace period left, then it is bye-bye Intel

EDIT:

Checked. PPC --> Intel transition took 4 years from introducing Intel to dropping PPC. We are at 3.5yr now. Best case scenario, macOS 15 may drop Intel code.

It'll be 5 years from the last Mac Intel sold (at least.) The last new Mac Intel sold was this year (2023) when it was discontinued. So you have a macOS in 2028 or 2029 to be the first candidate to not have Intel code.

(It's never from when they start, it's from the last product they produced that needs support)

[faraway]

Uhm is it me or did Avid neglect to put any loudness metering in the new built-in Atmos Render?