2019.12 Discussion

[Obsidian Dragon]

Originally Posted by jwilkers

I have WAY too many 3rd party plugs that the companies say are still not compatible with Catalina.

I wonder if anyone has upgraded to Protools 2019.12 and Catalina and can report on what happens to plugins that are not compatible with Catalina yet. Does only the offending plugins not load or work but the others do? Does Protools not start unless you remove the offending plugins?

Additionally, (after making backup) did you update the OS to Catalina first and then install Protools 2019.12 or did you install Protools 2019.12 first and then update the OS to Catalina? Does the order even make any difference?

[gives]

Loaded up latest film session fine.. I will run it today all day and see what I find, but so far so good! Still running Mojave 10.14.6 since I only just upgraded to that from Sierra a couple of months ago. See no need to go to Catalina yet especially with my video codec needs here.

G

[Cacov]

Originally Posted by amagras

To me this update isn't worth the trouble of restarting the computer

Quite true, again nothing for PT vanilla paying customers, not even throwing a bone at us with a miserable track count raise or something to "justify" paying the updates subscription plan. Now it could be easily 4 months before we see another update, which might again give us nothing, and there goes another year of throwing out money down the drain.

The worse part is now we can't even stop paying and reinstate when there is anything worth it.

It's becoming a really annoying situation for us. Avid can't keep stretching the rubber band any more.

[Downtown_BE]

ok - any relevant bugfixes coming from 2019.10?
thx

[TNM]

it's running well but I can't see the crosshair when i open a dedicated piano roll window.. it's so light and tiny on the 16" that i lost it 27 times in 30 minutes (yes, I counted) and could never ever find it by just looking unless I did the "shake mouse" mac os feature. Is anyone else having this issue?


I just hope there is some option I've missed or something.. maybe Avid can simply add an option for a darker easier to locate crosshair in the piano roll.. It would be a huge positive for me.. Never struggled this much before and I think cause the 16" has a higher res and puts more on screen so it's become even more tiny.. Anyway what i am asking for is arbitrary coding at it's most simple, they could do it in a couple minutes.. so.. if anyone else is suffering from this, let me know and I'll point them to this topic when i write to support.

[moshuajusic]

Originally Posted by TNM

it's running well but I can't see the crosshair when i open a dedicated piano roll window.. it's so light and tiny on the 16" that i lost it 27 times in 30 minutes (yes, I counted) and could never ever find it by just looking unless I did the "shake mouse" mac os feature. Is anyone else having this issue?


I just hope there is some option I've missed or something.. maybe Avid can simply add an option for a darker easier to locate crosshair in the piano roll.. It would be a huge positive for me.. Never struggled this much before and I think cause the 16" has a higher res and puts more on screen so it's become even more tiny.. Anyway what i am asking for is arbitrary coding at it's most simple, they could do it in a couple minutes.. so.. if anyone else is suffering from this, let me know and I'll point them to this topic when i write to support.

You're first noticing this??

http://duc.avid.com/showthread.php?t=396480

http://duc.avid.com/showthread.php?t=405925

There are also posts about this in the Avid Link "feedback requests" lounge. ("Lounge" doesn't exactly instill confidence that Avid's listening. )

It's one of the biggest, most needless time-wasters in PT. I can't even imagine a more simple thing to fix, and yet here we are. I said I'd probably wait till I get a new computer to reinstate, but I might wait even longer if this stupid MIDI smart tool cursor isn't updated. They don't need to make it bigger, just better differentiated from the background. The pencil tool is the same size and always immediately visible.

[off the wall]

2019.12 running fine on a Mac 5,1 Mojave 10.14.6.

[docric]

Mac 10.14.6... HDX... Seems solid after Day 1...

[jasonkalman]

Just my opinion, but if you are in the middle of a project and you don't have the time to mess with workarounds or plugin issues, I would stay put on Mojave PT 2019.10. No sense in doing QA work for Avid when you have work to do. I have no idea which plugs are 32 and which are 64 and quite frankly I don't care. I figure all of this will be sorted out by the middle of next year (3rd party companies should all be compatible by then) and Avid should have a more stable version for Catalina. Right now there are too many known issues. I read the release notes and it was mostly a laundry list of known issues. That doesn't give me any confidence to update at the moment. I would say, if you are running fine on Mojave, update at your own risk, good news is you can always revert back to Mojave and PT 2019.10 so in that sense, it really isn't a huge issue, just time potentially wasted.

[TNM]

Originally Posted by jscomposer

You're first noticing this??

http://duc.avid.com/showthread.php?t=396480

http://duc.avid.com/showthread.php?t=405925

There are also posts about this in the Avid Link "feedback requests" lounge. ("Lounge" doesn't exactly instill confidence that Avid's listening. )

It's one of the biggest, most needless time-wasters in PT. I can't even imagine a more simple thing to fix, and yet here we are. I said I'd probably wait till I get a new computer to reinstate, but I might wait even longer if this stupid MIDI smart tool cursor isn't updated. They don't need to make it bigger, just better differentiated from the background. The pencil tool is the same size and always immediately visible.

Thanks...

The 15" was at a much larger rez and I didn't really lose it there.. This is because it's so small on the 16", it's sort of like doing 1920x1200 aspect ration on a 15".. On the iMac Pro I am ok.. yes I just first noticed it cause this is the first time I couldn't find it, repeatedly lol! Well I'll badger them too, hopefully we'll get this and the midi connections on project reload fixed