Goodness, Slau. I'm sorry! Not to be rude/overdramatic here, but I
thought I was doing a good thing, helping. I guess not though. Jesus
Christ! Thank you for the link though.
Chris.
---
Chris Gilland
Youtube:http://www.youtube.com/c/chrisgilland
On 10/24/2022 4:06 PM, Slau Halatyn wrote:
Chris,
Once your shock (beyond belief) wears off, you should consider the
fact that Avid posts compatibility data on their website and Pro Tools
users are used to the fact that upgrading an OS before Pro Tools
supports it is not recommended, not to mention somewhat risky. People
do, however, try things out on a separate machine or partition just to
experiment. Brace yourself (so that you're not shocked) when the
question of whether or not to upgrade to Ventura comes up for months
to come and users will repeatedly be pointed toward the compatibility
chart on the Avid site. When the question inevitably comes up, steel
yourself and share the following link:
https://avid.secure.force.com/pkb/articles/en_US/compatibility/Pro-Tools-Operating-System-Compatibility-Chart
On Oct 24, 2022, at 2:56 PM, Christopher Gilland
<[email protected]> wrote:
I'm absolutely shocked beyond belief that not a single person, not
even Slau, has written in on the list about this. as of yet. At
least, not that I've seen.
Remember that today for us Mac users is mager upgrade time. This
means OS Monterrey is getting an upgrade officially to OS 13 Ventura.
Along with this, we may even be getting the official iPadOS 16,
though I'm more here to focus on the mac.
It's important to note that the update today for Ventura is *not* a
beta... Not even a public beta. It's the official release.
That being said, however, doesn't mean that just because the update
is out, you immediately should jump for joy with excitement, "it's
here, it's here,
it's here, finally!"
Let me say this: During the beta cicle, neither myself nor others
could say much due to nondisclosure NDA agreements. There are
probably still things privately
being tested which people are on NDA regarding; they most likely
probably can't even disclose they are! testing in the first place, so
it's most likely
probably a waist of your time to ask around.
What I'd say is, check, check, check, and oh did I mention, check!
And by the way, check! OK, you get my point.
The bottom line is, will things work with Ventura? Prr'rrobbably,
yes. You should! key word, should! be fine as far as DAW's like
Logic, Reaper, ProTools,
etc. But! that being said, be careful. The bigger concern is plugins
and such.
For new users just getting on the bandwaggon with all this stuff, let
me be very black and white crystal clear and maybe even a bit direct
with you. Even
though this would be an official release, you still do this at your
own risk. A lot of developers haven't yet officially, and that's the
key word here,
officially, declared and certified that their software is fully
compatible. I definitely don't think Avid has with ProTools.
Also note that just because a DAW launches and works in Ventura for
the most part doesn't mean it's fully compatible. Depending on your
current software,
and current hardware setup, you might luck out. Things for you may
work flawlessly. But then, the next Joe Bird from down the street may
have a totally
different setup configuration. He/She/They try installing Ventura,
and it wind up being an absolute utter dreadful nightmare.
If you have another secondary mac you can try things with, it would
be very advisable to try Ventura there before putting it on your main
production machine.
Once you know that it works OK for your environment, then you could
migrate things over slowly little by little to your main machine. The
reason
I say slowly little by little is that if, hypothetically something
does break, you'll remember the last thing in steps you did, and
either can undo it,
or can say, whoops, that's where things broke. Then you can evaluate,
how important is it really that this thing that broke really is. Is
it something
though completely broken you can tollerate, or is it a total
dealbreaker. And hopefully if you're smart, because it broke first on
your test machine/environment,
it's not like you brought your main machine to a halt, sota speak.
If you, like me, don't have a separate system, then you really only
have 3 options: 1, best choice, don't do it at all, just wait until
things are fully
certified to be compatible, 2. Do it, but be darn sure you have
either a Time Machine backup of Monterrey, or wherever you were
previously, or 3, use an
external hard disk, or find a way to partition your current disk
without wiping it and dule boot between the 2 OS's until you know
things totally are safe.
In conclusion, I'm simply just saying, be really really really
careful today! Just because the update is there doesn't mean you just
have to have it right
away. If it means making or breaking your job, then make it.
My mamma always told me, if it ain't broken, don't fix it. LOL!
Chris.
--
You received this message because you are subscribed to the Google
Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ptaccess/7998edf8-669d-880d-76bc-59785883f760%40gmail.com.
--
You received this message because you are subscribed to the Google
Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ptaccess/2812F868-3D34-4AC5-A4CF-9C28DCC34AA7%40gmail.com
<https://groups.google.com/d/msgid/ptaccess/2812F868-3D34-4AC5-A4CF-9C28DCC34AA7%40gmail.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups "Pro Tools
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ptaccess/449b7122-97c8-4214-4e20-9a9bbce02464%40gmail.com.
