Ah, so refreshing to know it's not just me that's a complete thick when it comes to the plugin parameters for that bad boy! :P
On 22/08/2012, J. R. Westmoreland <j...@jrw.org> wrote: > I thought that was the issue but wanted to make sure. I just used the > xpand2 > and default stuff for my capstone. Buying the extras right now is just a > bit > out of reach even as a student. LOL > > > -----Original Message----- > From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On > Behalf > Of Chris Norman > Sent: Wednesday, August 22, 2012 9:59 AM > To: ptaccess@googlegroups.com > Subject: Re: Pro Tools 10 and Mountain Lion > > Hiya, think I messed up the sending of this email, but if not, sorry for > the > double post. > > Firstly, Slau, it's no worries mate, I just wasn't sure if you were being > tongue in cheek or not, but I thought I'd better lay it on a plate so there > was no ambiguity. :-) > > J R, I am using Pro Tools 10 on my meager setup, and it works fine. > The only real show stopper is that the plugins have all been converted to > the AAX format, which I'm sure is lovely, but it renders the configurable > parameters completely unconfigurable LOL. > > It is worth noting that not all plugins are in AAX, XPand for example, is > still an RTAS, so it works fine, as are a few others. > > The isn't usually that much of a problem anyways, because there's a whole > plethora of presets to choose from, but for example, with the Normalise > Audio Sweet plugin, there's no presets, so I cannot normalise my stuff. > > Anyways, hope that's cleared up some stuff. > > > > On 22/08/2012, J. R. Westmoreland <j...@jrw.org> wrote: >> Slau, >> >> Can you briefly tell me why you have concerns about PT10? I used it a >> few months back for my class for recording and editing and it pretty >> much did as I expected. >> The isues I ran into were related to areas that had problems under >> both v9 and v10. >> Sorry if this is being stupid or whatever I'm just curious since I >> actually have the real versions of both and licenses for them as well. >> Thanks in advance and if it seems better go ahead and write me off list. >> >> Best, >> J. R. >> >> >> -----Original Message----- >> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On >> Behalf Of Slau Halatyn >> Sent: Wednesday, August 22, 2012 7:00 AM >> To: ptaccess@googlegroups.com >> Subject: Re: Pro Tools 10 and Mountain Lion >> >> Hi Naama, >> >> Absolutely, you'll need either Snow Leopard or Lion for now. Also, Pro >> Tools >> 9 would be recommended. Anything higher than 8.0.4 is fine but, if at >> all possible, try to stay away from version 10. If it has to be 10, >> then that's workable too. >> >> slau >> >> On Aug 22, 2012, at 12:38 AM, Naama Samantha Shang wrote: >> >>> Hi Slau, >>> So I just want to make sure I'm clear - as soon as my work machine >> arrives, do I downgrade to Lion before anything else, to avoid problems? >>> Thanks, >>> Naama >>> >>> >>> -- >>> Naama Samantha Shang >>> Audio Technician >>> Talking Book Library >>> Natanya, Israel >>> +972-9-861-7110 >>> na...@clfb.org.il >>> >>> -------------------------------------------------- >>> From: "Slau Halatyn" <slauhala...@gmail.com> >>> Sent: Tuesday, August 21, 2012 6:51 PM >>> To: <ptaccess@googlegroups.com> >>> Subject: Re: Pro Tools 10 and Mountain Lion >>> >>>> No sarcasm at all. I just didn't want to misunderstand anything >>>> since I >> currently don't use Mountain Lion. The vagaries of communication lead >> to misunderstandings and I just needed to absolutely sure that at >> least one person was categorically unable to read the start field with >> PT 10 under Mountain Lion. >>>> >>>> Cheers, >>>> >>>> Slau >>>> >>>> On Aug 21, 2012, at 11:11 AM, Chris Norman wrote: >>>> >>>>> Haha, not sure if that was sarcasm or not, but no worries anyways. >>>>> >>>>> >>>>> On 21/08/2012, Slau Halatyn <slauhala...@gmail.com> wrote: >>>>>> OK, thanks for confirming that in no uncertain terms. >>>>>> >>>>>> Cheers >>>>>> >>>>>> On Aug 20, 2012, at 10:44 PM, Chris Norman wrote: >>>>>> >>>>>>> OK, lemme try and lay this out as clearly and fully as I know it. >>>>>>> >>>>>>> I can't try pt 9 on Mountain Lion, or I would, but with PT10: >>>>>>> >>>>>>> In the edit window, when you interact with the counter display, >>>>>>> none of the values there will read. That is to say, the start, >>>>>>> current, and end selection boxes. They just say text or something >>>>>>> like >> that. >>>>>>> >>>>>>> As people have said, the same is true of the edit boxes in the >>>>>>> tempo settings, and I'd bet it's the same in the time signature >>>>>>> configuration thingy too. >>>>>>> >>>>>>> I'd be willing to put money on it being the text fields that Avid >>>>>>> use, that require you to use the numberpad to enter data. >>>>>>> >>>>>>> Other than that, everything else is working healthily, hardware, >>>>>>> etc, etc, etc. >>>>>>> >>>>>>> Cheers, and hope that clears it up a bit Slau. If you need to >>>>>>> know anything else, please let me know. >>>>>>> >>>>>>> Cheers, >>>>>>> >>>>>>> On 20/08/2012, The Oreo Monster <monkeypushe...@gmail.com> wrote: >>>>>>>> Hello, >>>>>>>> >>>>>>>> You can also try going to the events menu and tempo and >>>>>>>> constant tempo, you see it does the same thing there. Infact you >>>>>>>> will notice it does the same in all edit fields in all of the >>>>>>>> different event dialog boxes. >>>>>>>> The Oreo Monster >>>>>>>> monkeypushe...@gmail.com >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Aug 20, 2012, at 4:01 PM, "J. R. Westmoreland" <j...@jrw.org> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Interact with the counters area and there are several there. >>>>>>>>> >>>>>>>>> >>>>>>>>> -----Original Message----- >>>>>>>>> From: ptaccess@googlegroups.com >>>>>>>>> [mailto:ptaccess@googlegroups.com] On Behalf Of Nick Gawronski >>>>>>>>> Sent: Monday, August 20, 2012 1:59 PM >>>>>>>>> To: ptaccess@googlegroups.com >>>>>>>>> Subject: Re: Pro Tools 10 and Mountain Lion >>>>>>>>> >>>>>>>>> Hi, Where should I go in pro tools to see if these fields work >>>>>>>>> as I am still in the process of learning pro tools? I should >>>>>>>>> be able to let you know if the proper fields read if I am told >>>>>>>>> where to go and I will also try it on my lion installation to >>>>>>>>> see the difference. Nick Gawronski >>>>>>>>> >>>>>>>>> On 8/19/2012 6:41 PM, Slau Halatyn wrote: >>>>>>>>>> Nick, >>>>>>>>>> >>>>>>>>>> Can you read the Start field in the edit window under Mountain >>>>>>>>>> Lion in Pro >>>>>>>>> Tools 10? >>>>>>>>>> >>>>>>>>>> Slau >>>>>>>>>> >>>>>>>>>> On Aug 19, 2012, at 6:57 PM, Nick Gawronski wrote: >>>>>>>>>> >>>>>>>>>>> Hi, Some edit fields read fine like the file names to save >>>>>>>>>>> projects as and when you bounce tracks to files. I am using >>>>>>>>>>> mountain lion but do have lion still around should I need it. >>>>>>>>>>> I think it is possible to down grade to lion if you need to >>>>>>>>>>> but don't know if the newer mac books will support the down >>>>>>>>>>> grade. My digi 003 works fine under mountain lion and I did >>>>>>>>>>> not need to reinstall anything. The only thing I had to >>>>>>>>>>> reinstall was the drivers for my express card for my sata >>>>>>>>>>> drive and that was not even an upgrade I just opened the >>>>>>>>>>> folder >> where I had the pkg file and ran it and things now work great again. >>>>>>>>>>> Nick Gawronski >>>>>>>>>>> >>>>>>>>>>> On 8/18/2012 10:15 PM, Slau Halatyn wrote: >>>>>>>>>>>> So, am I understanding this correctly? With Mountain Lion, >>>>>>>>>>>> no edit >>>>>>>>> fields are being read in Pro Tools versions 9 and 10? Can >>>>>>>>> someone else confirm this? Version 10 reads fine with Snow >>>>>>>>> Leopard and Lion, from other accounts. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Aug 18, 2012, at 10:07 PM, The Oreo Monster wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hello, >>>>>>>>>>>>> >>>>>>>>>>>>> It appears to be an edit field where there would be text >>>>>>>>>>>>> you could edit >>>>>>>>> or change thats not reading in ML with PT10. This issue doesn't >>>>>>>>> happen with PT 9 or 10 on lion. And if i remember correctly PT >>>>>>>>> 9 on ML had the same issue. As i was planning to keep my air >>>>>>>>> running PT 9 in case i ran into any showstoppers in version 10. >>>>>>>>> But when i upgraded my air to ml i realiezed none of the edit >>>>>>>>> fields read at all. That was when i upgraded to version >>>>>>>>> 10 >>>>>>>>> on ML to se if it would fix the issue. So if appears for now If >>>>>>>>> pro tools is an everyday necessity at the very least you will >>>>>>>>> need to keep a lion partition around for a little bit. >>>>>>>>>>>>> The Oreo Monster >>>>>>>>>>>>> monkeypushe...@gmail.com >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Aug 16, 2012, at 8:50 PM, Slau Halatyn >>>>>>>>>>>>> <slauhala...@gmail.com> >>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> I still haven't updated my HD system to version 10 but, >>>>>>>>>>>>>> since I also >>>>>>>>> have a 003, I decided to update my regular LE version to 10. >>>>>>>>> I'd like to clear something up and I will need verification of >>>>>>>>> something: >>>>>>>>>>>>>> >>>>>>>>>>>>>> I'm running Pro Tools version 10 on Snow Leopard and there >>>>>>>>>>>>>> are no >>>>>>>>> issues with any counter displays not reading. Now, I don't have >>>>>>>>> Mountain Lion and will not run it for some time. Can someone >>>>>>>>> verify, specifically, where counters are not reading properly? >>>>>>>>> Even in Mountain Lion, that would be fairly strange, that is, >>>>>>>>> for a text display to not read correctly. >>>>>>>>> That >>>>>>>>> said, technically, Mountain Lion is not approved for Pro Tools >>>>>>>>> so I'm not concerned.yet. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Again, someone with Mountain Lion and Pro Tools 10, please >>>>>>>>>>>>>> let me know >>>>>>>>> precisely where a counter display doesn't read correctly where >>>>>>>>> it used to read correctly in Snow Leopard or Lion. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Slau >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Take care, >>>>>>> >>>>>>> Chris Norman. >>>>>>> >>>>>>> <!-- chris.norm...@googlemail.com --> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Take care, >>>>> >>>>> Chris Norman. >>>>> >>>>> <!-- chris.norm...@googlemail.com --> >> >> >> > > > -- > Take care, > > Chris Norman. > > <!-- chris.norm...@googlemail.com --> > > -- Take care, Chris Norman. <!-- chris.norm...@googlemail.com -->
