2021.3.1

[innesireinar]

Is out

[PhiBee]

Just installed, now testing :)

[Emi]

But it's April, wouldn't be 2021.4?!?

[JFreak]

Originally Posted by Emi

But it's April, wouldn't be 2021.4?!?

If it is a bugfix for 2021.3 it makes more sense to use 2021.3.1 version number. Otherwise why bother calling it 2021.3.0 to begin with?

[Sardi]

Originally Posted by JFreak

If it is a bugfix for 2021.3 it makes more sense to use 2021.3.1 version number. Otherwise why bother calling it 2021.3.0 to begin with?

Yeah, except that’s not the naming convention they outlined when they switched to this new version numbering system in 2018.

‘The plan is that version numbers will now reflect the year and month of the release. The first release, 2018.1 - corresponds to January 2018. A February release would be 2018.2, March would be 2018.3, and so on. If the software requires more than one release in a month (an urgent patch is needed, for example), the extra release will be identified by a third number in the format 2018.1.1. Product splash screens, about boxes, Avid Master Accounts, and Application Manager will display the full version number – for example 2018.1.1’

We’re in April, so going by the above, it should be 2021.4.

Incorrect version numbering aside, I’m quite surprised they didn’t fix the import audio dialog bug. That’s not gonna go down well.

[BScout]

There are only 2 fixes.

Pro Tools 2021.3.1 resolves the following critical bugs:
The Parallel Task Optimizations preference is no longer missing from Pro Tools Software (PT-271772)
Knife-edge automation will once again follow the edge of the clip boundary (PT-271659)

The HD Driver changed with 2021.3. Nothing new in the latest HD Driver (they just recompile it with any release.)

Don't know why anyone is surprised other bugs aren't fixed. They've specified the "critical" ones they fixed in the notes.

[off the wall]

Originally Posted by Sardi

Yeah, except that’s not the naming convention they outlined when they switched to this new version numbering system in 2018.

‘The plan is that version numbers will now reflect the year and month of the release. The first release, 2018.1 - corresponds to January 2018. A February release would be 2018.2, March would be 2018.3, and so on. If the software requires more than one release in a month (an urgent patch is needed, for example), the extra release will be identified by a third number in the format 2018.1.1. Product splash screens, about boxes, Avid Master Accounts, and Application Manager will display the full version number – for example 2018.1.1’

We’re in April, so going by the above, it should be 2021.4.

Incorrect version numbering aside, I’m quite surprised they didn’t fix the import audio dialog bug. That’s not gonna go down well.

Yeah, I was surprised that the import dialog is still messed up. and I agree, the version # violates their own rules. Looking backwards, one will assume this update came out in March.

[JFreak]

Originally Posted by off the wall

I agree, the version # violates their own rules. Looking backwards, one will assume this update came out in March.

The so called "their own rules" do not mention dot-zero or dot-one, it just states that major version number is year.month -- they just carry the dot-zero in there, hoping it will never change.

So.. if we need a bugfix for a 2019.12 it would be called 2019.12.1 even if it was released in 2021 hottest summer month. This is called software version tree and so long as there are only dot-zero versions we just drop it and talk about 2019.12 or 2021.3 as per "their own rules" say, year and month when that was released.

Nobody would know what it was if this imaginary example of 2019.12.1 would be called 2021.4 as it would clearly be 2019.12 features with a bugfix but released in april of 2021. Can you understand it with this example?

Who wants to go back interpreting what PT6.4.1cs2 really meant? Gosh... And besides, this is not the first time either. But who would remember 2020.9.1 as it is so ancient history.

[PhiBee]

Chuuuuuut ! Don't complain, we have an update

UPDATE
Ok, everything works, pfiou ! Never mind the version

[off the wall]

Installed. It did NOT address the audio import dialog bugs in Mojave. Still the same, no double clicking of folders to navigate and must hit Open button twice to complete the process. Ugh.