ProTools 2023.12 available for download on Avid site:-)

[BScout]

Originally Posted by Darryl Ramm

Uh color coded paths but I would want the color coding most when selecting say the bus in an IO Selector... but the colors don't show up in the menu there. Just seems like they left out a lot of the usefulness.

I am finding the colour coding helpful already (something I wanted for a long time) but they need to refine. The biggest use for me is to know if a channel is going to a direct output (hardware) or to a print channel.
This has bitten me before
But when you colour code a bus out, all sub get the same colour by default. So then you have to go through and remove the colour when you want to set most to "none" and only a few to specific colours. For instance a 5.1 out set to blue but the subpath for center to green and stereo to red. But then you have to go and remove all the other subpath colours.
It's extremely helpful for following routing.

I don't think this is meant for establishing routing where, presumably, everyone can read where they are sending things in the menu hierarchy. (Something that is truncated in the mix/edit windows when trying to trace routing.)

[Skwaidu]

Originally Posted by audiogamble

Something's really broken with backwards compatibility to external atmos renderers.

There was the thing with the subpaths that someone earlier mentioned. That right there is a no go for me and most people.

Seems like there are also these weird clashes happening between binaural settings in the io window, and those in the dolby plugin. Why did you decide that having those settings in the io window was a good idea by the way? Ask any atmos engineer, and most will tell you that they make binaural setting decisions in realtime during live playback.

Also, the IO window for external renderers is totally janky. It tries to add new outputs in the output tab and by doing so, removes existing output mappings. If you're doing anything more advanced than using Dolby Audio Bridge, you're looking at hacks and workarounds to get anything going. Didn't used to be that way.

Then when I did finally get things connected, the first old session I opened shot a feedback loop through my speakers.

Love what you've tried to do here, but you've quite severely compromised the core functionality of what used to be the best Dolby Atmos integration in the game.

Right, the subpath thing I mentioned is a big problem. I didn't even check binaural settings behaviour much yet - are the IO setup settings overriding external renderer settings? The (typo-ridden) manual section mentions "pulling" some settings from an external renderer if necessary, but it wasn't updating the bin settings to the IO Setup tab at least for me.

[Schottlandru]

Have any Windows users been able to check if 2023.12 brings the Dolby Atmos renderer in one system to us now... ???

[its2loud]

Originally Posted by Schottlandru

Have any Windows users been able to check if 2023.12 brings the Dolby Atmos renderer in one system to us now... ???

Yes, it does with the Internal Renderer.

[cmbourget]

Originally Posted by huzzam

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.

I need to buy a new Mac and I've chosen the Studio M2 Ultra. You think the M2 Max is good enough for Pro Tools (even for Dolby Atmos and big 300-track sessions). There's a big difference in price. But on the other hand, the M2 Max is limited to 96 G of RAM.

[Arionas]

It was announced that RX ARA will be part of this update.
What happened?

[Schottlandru]

Originally Posted by its2loud

Yes, it does with the Internal Renderer.

On WINDOWS !!! ???

With Spanner V4 being Win compatible now this is great news!!!

[marianna]

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?

tracy_lipp

I posted the following the other day........

" I do know that Sonoma will not be supported with the next Pro Tools release coming – the engineers are working on it but there are too many known issues which we will be publishing in a knowledge base article when that release comes out ( dont ask as I cant tell :))

While the Sonoma 14.2 update will fix some of these issues, it remains to be seen if that is enough to post-qual what's coming from us with Sonoma.

Keep focused on the Pro Tools forum for updates from Tope."

Here is the KB article that came out yesterday with the issues relating to Sonoma.

https://avidtech.my.salesforce-sites...a-Known-Issues

HTH and we are working on it.

marianna

[marianna]

Originally Posted by faraway

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

Faraway.....

The integration offers an independent re-render that can be used for loudness metering with your choice of plugin, or as an additional 5.1 or 2.0 send/print of the mix. We’ve prepared this document to help answer common questions about the current Dolby Atmos integration in Pro Tools.

https://avidtech.my.salesforce-sites...s-Renderer-FAQ

I will pass along this note to the team as it may be something they expect to improve upon but at least it gives them pause that folks want it.

Thanks
Marianna

[BarneyBarry]

Hey people, you should be mad at Apple with Sonoma, not PT devs. Apple adds constantly breaking changes. If you want to be stable, use Windows, every version works perfectly.