Yes I did, and no luck.
gGord
-Original Message-
From: Nick Gawronski
Sent: Thursday, September 06, 2012 3:40 PM
To: ptaccess@googlegroups.com
Subject: Re: Another problem with Pro Tools and ML
Hi, Did you try reinstalling the original drivers that you installed
with lion
, September 04, 2012 9:32 PM
To: ptaccess@googlegroups.com
Subject: Re: Another problem with Pro Tools and ML
HI J. R.,
Let me say something at the outset that you should keep in mind as you
read on. I will say things that you and others will probably quarrel
with so I'm saying this up front so
realm I'd be much
appreciative of the information.
Thanks for the continued out reach to Avid on your part.
Best,
J. R.
-Original Message- From: Slau Halatyn
Sent: Tuesday, September 04, 2012 9:32 PM
To: ptaccess@googlegroups.com
Subject: Re: Another problem with Pro Tools and ML
performance, I
meant more just for beta testing P T in general.
Chris.
- Original Message - From: Slau Halatyn slauhala...@gmail.com
To: ptaccess@googlegroups.com
Sent: Thursday, August 30, 2012 10:56 PM
Subject: Re: Another problem with Pro Tools and ML
Chris,
It's
, September 04, 2012 2:18 PM
To: ptaccess@googlegroups.com
Subject: Re: Another problem with Pro Tools and ML
Pro Tools beta is like fight club. Nobody talks about pro tools beta the
same way nobody talks about fight club. And with that, I'm gonna shut up
before someone decides to take me deep see fishing
On Sep 4, 2012, at 7:09 PM, J. R. Westmoreland wrote:
Hmmm. Maybe that is why some things don't fall to the top of the list?
J. R., what specifically are you referring to that hasn't fallen to the top of
the list?
slau
Of Slau Halatyn
Sent: Tuesday, September 04, 2012 5:29 PM
To: ptaccess@googlegroups.com
Subject: Re: Another problem with Pro Tools and ML
On Sep 4, 2012, at 7:09 PM, J. R. Westmoreland wrote:
Hmmm. Maybe that is why some things don't fall to the top of the list?
J. R., what specifically are you
with the product himself.
J. R.
-Original Message-
From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf
Of Slau Halatyn
Sent: Tuesday, September 04, 2012 5:29 PM
To: ptaccess@googlegroups.com
Subject: Re: Another problem with Pro Tools and ML
On Sep 4, 2012, at 7:09 PM, J
Message-
From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf
Of Slau Halatyn
Sent: Tuesday, September 04, 2012 5:29 PM
To: ptaccess@googlegroups.com
Subject: Re: Another problem with Pro Tools and ML
On Sep 4, 2012, at 7:09 PM, J. R. Westmoreland wrote:
Hmmm
problem with Pro Tools and ML
Chris,
It's not clear yet but there's probably something about how ML is reading
the window class of the given controls. Again, until it's certified, we
don't know what changes will take place in Pro Tools that might affect how
things are read. We'll cross
Nope, afraid not, I just tried it now.
Cheers,
Take care,
Chris Norman.
chris.norm...@googlemail.com
On 30 Aug 2012, at 16:24, Scott Chesworth scottcheswo...@gmail.com wrote:
Eak, that's a biggy!
Does resetting them with Option-C make any difference? Highly doubt
it, but best to check.
I have the same problem on my machine running PT 10.01 on ML 10.8.1.
Also, VO doesn't tell me if record, solo, and mute are on or not.
Good thing to have PT with Lion partition.
I would not recommend using Mountain Lion on a recording/mixing machine.
In my experience, upgrading your OS before it is tested and certified by
every single software vendor that your studio is dependent upon has never
been a safe move.
I have many friends who are not recording engineers that
You're right, but there was a big thread on all of this. I meerly resurrected
it so Slau can make a lovely list to show our friends at Avid.
On the bright side though, when interacting with Plugin parameters, you can now
hear the correct value that you're changing too, rather than the previous
On Aug 30, 2012, at 10:49 AM, Chris Norman wrote:
Hi All,
Sorry, I couldn't find the old thread to post this in, so my bad, but I found
another problem with Pro Tools and OS X MountainLion which I thought Slau
especially should be aware of as you're talking to Avid.
The input meters
Confirmed, they defo did read in Lion.
On 8/30/12, Slau Halatyn slauhala...@gmail.com wrote:
On Aug 30, 2012, at 10:49 AM, Chris Norman wrote:
Hi All,
Sorry, I couldn't find the old thread to post this in, so my bad, but I
found another problem with Pro Tools and OS X MountainLion which I
Yeah, they do, because I got Lion on the other third of this MacBook Pro LOL.
On 31 Aug 2012, at 00:46, Scott Chesworth wrote:
Confirmed, they defo did read in Lion.
On 8/30/12, Slau Halatyn slauhala...@gmail.com wrote:
On Aug 30, 2012, at 10:49 AM, Chris Norman wrote:
Hi All,
Sorry, I
Yup? It's not just you. That's the main reason I downgraded actually. The
other issues I could tollerate, but that? was a deal breaker.
Chris.
- Original Message -
From: Chris Norman chris.norm...@googlemail.com
To: Pro Tools Access ptaccess@googlegroups.com
Sent: Thursday, August
30, 2012 11:24 AM
Subject: Re: Another problem with Pro Tools and ML
Eak, that's a biggy!
Does resetting them with Option-C make any difference? Highly doubt
it, but best to check.
Scott
On 8/30/12, Chris Norman chris.norm...@googlemail.com wrote:
Hi All,
Sorry, I couldn't find the old thread
Option C? resets the meters? I thought you just hit vo+space on 'em, or,
actually can you do either.
Chris.
- Original Message -
From: Chris Norman chris.norm...@googlemail.com
To: ptaccess@googlegroups.com
Sent: Thursday, August 30, 2012 11:26 AM
Subject: Re: Another problem
What I'd like to know is exactly what in the first place, supported or not
would cause it not to read in one O S, while it does in another. Is it how
Voiceover actually handles rendering things? I guess what I mean is, is it
most likely an issue of Voiceover not reading correctly, or is it
on the track.
HTH
Brian.
--
From: Christopher-Mark Gilland clgillan...@gmail.com
Sent: Friday, August 31, 2012 1:27 AM
To: ptaccess@googlegroups.com
Subject: Re: Another problem with Pro Tools and ML
Speaking of meters, this is gonna sound like a really
...@googlemail.com
To: ptaccess@googlegroups.com
Sent: Thursday, August 30, 2012 8:54 PM
Subject: Re: Another problem with Pro Tools and ML
I've not actually tested it, but I think you're right Bryan. If you put your
compressor on the track, it shows up a different meter to if you've nothing,
even (I believe
Chris,
It's not clear yet but there's probably something about how ML is reading the
window class of the given controls. Again, until it's certified, we don't know
what changes will take place in Pro Tools that might affect how things are
read. We'll cross that bridge soon. To answer your
Yeah, I'm really sorry I didn't do that. The state of many buttons, such as
edit mode, tools, etc. is also not spoken any more.
Gord
-Original Message-
From: Chi Kim
Sent: Thursday, August 30, 2012 4:08 PM
To: ptaccess@googlegroups.com
Subject: Re: Another problem with Pro Tools
25 matches
Mail list logo