Pro Tools 2024.9 Thoughts

[BarneyBarry]

Originally Posted by TNM

PLEASE, never change the UI.

The UI is the Reason I MOVED to Pro Tools, as it's the best DAW GUI in the world without peer. It's the only DAW apart from Logic that never looks cluttered nor ever hurts my eyes.
And now with the custom coloring of most of the GUI - it's peerless IMO.

Just want to put a balancing opinion out there.

maybe it's not about changing UI, but changing internal code related to UI? pt have been developed for 30 years, i can't imagine technical dept

[moogboy100]

Originally Posted by Electronic1982

It's impossible,
Without Bug PT-263050 being fixed, it's not possible,
with all the routing going on in big Pro Tools sessions, it's important to know where each signal is going,
if I can't update the software, I can't update the hardware neither,
if this means the end of Pro Tools for me, then I'll end up stuck here forever

Well one of the many many new awesome features you've been missing out on is the Color Coding IO, which can easily solve a lot of the what's routed to where questions.

Aside from that, it's so dead simple to create a quick Memory snapshot of your current track view settings, to get back to they way you had it after using that Show Assignments thingy, I can't believe you're holding yourself back over that but to each their own I guess.

[Electronic1982]

Originally Posted by moogboy100

Well one of the many many new awesome features you've been missing out on is the Color Coding IO, which can easily solve a lot of the what's routed to where questions.

Aside from that, it's so dead simple to create a quick Memory snapshot of your current track view settings, to get back to they way you had it after using that Show Assignments thingy

Thanks for the suggestion, but it doesn't solve the issue because Hidden Tracks will still jump out with the colour feature, and remembering to create memory location then updating memory locations every single time a new routing is assigned and un-assigned, over and oveer again is prone to mistakes due the amount of of times updating is required, instead of a simple, single click like it should be. Bug PT-263050 needs fixing.

[moogboy100]

Originally Posted by Electronic1982

Thanks for the suggestion, but it doesn't solve the issue because Hidden Tracks will still jump out with the colour feature, and remembering to create memory location then updating memory locations every single time a new routing is assigned and un-assigned, over and oveer again is prone to mistakes due the amount of of times updating is required, instead of a simple, single click like it should be. Bug PT-263050 needs fixing.

1. The colored IO will not make hidden tracks jump out. It just means that, with a quick glance at your tracks, you can easily identify what's being routed and where.

2. Updating memory locations is not as hard as you're making it. I use soundflow. I have literally 1 button I can press on my stream deck to update the current "mix view memory location". So if I'm gonna do something that might be "destructive" to my current layout, I just hit the button, then I can do what I need to do and if I need to get back to my original view, I just recall that mem location with the keypad (. 1 .) (no, those are not ascii boobs, that's like, recall mem loc 1) Even w/o soundflow, it's still so easy to just apple-5, then ctrl-click a mem location to update it.

AVID does not think of PT-263050 as a bug, so they may never change it.

[Electronic1982]

Originally Posted by moogboy100

1. The colored IO will not make hidden tracks jump out. It just means that, with a quick glance at your tracks, you can easily identify what's being routed and where.

But I need to see hidden tracks selected that use the same routing across the entire sesssion in all time, this is why this approach won't work.

Originally Posted by moogboy100

2. Updating memory locations is not as hard as you're making it. I use soundflow. I have literally 1 button I can press on my stream deck to update the current "mix view memory location". So if I'm gonna do something that might be "destructive" to my current layout, I just hit the button, then I can do what I need to do and if I need to get back to my original view, I just recall that mem location with the keypad (. 1 .) (no, those are not ascii boobs, that's like, recall mem loc 1) Even w/o soundflow, it's still so easy to just apple-5, then ctrl-click a mem location to update it.

I can have 100+ routings going on, so this is approach is prone to mistakes, if one potential routing (or removal/ change of routing) is missed, it risk destrupting entire workflow, then I have to spend time trying to find what track jumped out and what track didn't. Selecting Tracks isn't supposed to work like this.

I can only have faith in Avid to fix Bug PT-263050

[ejinbc]

All

I have been coming to this forum for over 10 years now. The number one feature request has always been (paraphrasing) "no new features, please give us a bug free version". So far, not so much.

On the topic of Sketch, a minor mis-step perhaps. In it's current state Sketch has far fewer features than even the (almost) free Ableton Lite - recall we have Ableton Link. As far as using Sketch as an arrangement tool, a simple system of marker (or range) sequencing like Nuendo could be far more convenient and consistent with the Pro Tools interface. Or not.

Another Ableton note, I see on their website that they keep releasing bug fixes for the past major version of Ableton for those that have not updated. What a concept.

Cheers

ejinbc

[JFreak]

Video engine only NEEDS to be ARM if Avid has inside information from Apple saying macOS 16 will drop x86 code altogether. So long as Apple is playing it safe, it is only a nice to have.

[BScout]

Originally Posted by JFreak

Video engine only NEEDS to be ARM if Avid has inside information from Apple saying macOS 16 will drop x86 code altogether. So long as Apple is playing it safe, it is only a nice to have.

The AVE is still terrible.
Rosetta2 does not translate all instruction sets. The AVE isn't taking full advantage of GPU cores on the M processors. So necessary.

[JFreak]

I am hoping macOS 15 Sequoia would be the pinnacle for x86 (like OSX 10.5 Leopard was for PPC) and hoping macOS 16 would give us warm and fuzzy feelings remembering OSX 10.6 Snow Leopard which was PPC-free and super stable.

[Eric Lambert]

Originally Posted by BScout

The AVE is still terrible.
Rosetta2 does not translate all instruction sets. The AVE isn't taking full advantage of GPU cores on the M processors. So necessary.

Yes. There's no excuse for the delay of this much needed functionality. I was struggling with a video issue just today. Sloppy, old code. It's one of the few things on this machine which still uses the Rosetta crutch.