Pro Tools 2019.10 Discussion

[JFreak]

Originally Posted by Sardi

They do not listen.

Or, even more frightening idea, they do not know how. Avid has confirmed the rumor that they have been working on HDX voice upgrade for a year already witn no release (because certain percentage of cards would fail on firmware update) so maybe this sidechain compensation on native mixer is one of the neverending stories they are trying to do but so far have no solution..?

[JingleDjango]

If that were the case, they must have really coded themselves into a corner with their audio engine. And i thought it got a significant overhaul in the last few years, when they moved to 64 bit? Every other DAW I've used had implemented the feature competently. When i began using Pro Tools a few years ago i was stunned to find that mix techniques I'd taken for granted in Logic and Ableton were totally impractical in PT.

Obviously i still see enough value in PT to continue using it (for now), but what gives? My guess is they're paralyzed by so much legacy code but will never have the resources needed to address the problem.

[Nish]

Just noticed the zip file of PT2019.10 changed to Pro Tools 2019_10_Win_RevA in our accounts, but don't see any mention anywhere or changelog either.

[TOM@METRO]

I see this as well. And the file is a little larger. I'll ask.

[Nish]

Originally Posted by TOM@METRO

I see this as well. And the file is a little larger. I'll ask.

Installing on Win7 worked again but once I open a session the HUI is still screwed up so had to revert back to 2019.6 again. It looks like I won't have another choice than upgrade to Win 10.

[ChuckS]

Originally Posted by Nish

Just noticed the zip file of PT2019.10 changed to Pro Tools 2019_10_Win_RevA in our accounts, but don't see any mention anywhere or changelog either.

It probably has the updated iLok installer.

[TOM@METRO]

^^^ Yes ^^^

[gnprice]

Originally Posted by dmontron

Installed 2019.10 (Mac) a couple of days ago from 2018.6 (which I’ve been using as Ultimate with minimal issues) and I had to revert back.

I was getting irregular delay compensation readings but worse I was not able to use video at all!

Every previous session I opened with video I’d get an error and the video engine would crash and endlessly restart until I canceled. When I tried to import a video I’d get an error that the codec was not supported and the video engine would crash and go into a restart loop.

I lost a days work (I know, I know... shouldn’t have even tried the update-but as I’m paying for it, liked the idea of some of the features and I lost better judgement) trying to figure it out before just reverting back; I don’t have time right now to start a case with Avid but I will.



Sent from my iPhone using Tapatalk

After upgrading to 2019.10 (on top of 2019.6 running Sierra) I also encountered video engine crashes and endless restarts. The "codec was not supported" was also seen when trying to import a known-good h.264 mp4 file. Thanks to CCC, I quickly reverted back to 2019.6 and all is well. This is the first major issue I've run into along the way since updating from 11 -> 12 -> 2018 -> 2019. I'd be academically curious to know if a clean install would work? However, being a lazy degenerate, I think I'll just ride it out with what works. I will consider this exercise an example of: 1.) Newer isn't always better, and 2.) If it ain't broke then don't fix it.

[john1192]

Originally Posted by JingleDjango

My guess is they're paralyzed by so much legacy code but will never have the resources needed to address the problem.

yes .. sad state of affairs .. i love the coded themselves into a Corner Line ...

[amagras]

Originally Posted by ChuckS

It probably has the updated iLok installer.

Now pay $200