Re: Very important question about a long-term ProTools project I'm working on.
Hey Mark! You'll have to do your home work re publishing for the album. The truth is, you can record anything you want without permission unless it's being held for another artist wich I don't think this falls in that catigory. All they want is they're money Usuall it's $15 per song, based on 200 releases. Therefor, 13 tracks will cost you approx $200 bucks. Is that to much? Good luck man. E On 2012-08-17, at 2:21 PM, Christopher-Mark gilland wrote: OK, I am not proceeding any further with this project under any circumstances until I get some help here, as, if I mess this up, I could get in some really seriously hot water. So here's the situation. I am working on an album which is going to contain probably about 13 or 14 tracks all total of Christian treditional hymns. Granted, some of them might be done more contemporary style, but the bottom line is I am creating my own arrangements, music, vocals, and all. I'd like to have the disc ready and up on ITunes and on Amazon etc. by Christmas. Now, here is the major concern however that I face. I need to know where on the internet I can go to cross reference these hymns in a searchable database and get their current copyright status. I can't afford royalties, so, it's going to need to be things in public domain that I record. I know one could say, most of your treditional hymns will be public domain, but... don't? count on that! For example, I want to record How Great Thou Art. Someone told me that they were almost completely sure that either the Billy Graham Evangelistic Association, or George Beverly Shea himself owns the rights to that one. I know there are sites out there, for example, Brian Howerton told me about Hairy Fox, but I'm not really seeing a way up there to literally type in the song title, and see it's copyright status. I don't necessary wanna know everyone who's done the track, and their copy right. I just need to know, is it currently still considered private material, or can it freely be used. I just need the general yes or no, or if yes, what the conditions for yes would be, if there be any. Yes, I do know about copyright.gov. Are you kidding me? That's where I registered my It Takes Time track. So, yeah, I know about the copyright office, but even on that web site, maybe I'm just too impatient, but I'm even finding it really hard to track down the actual search tools that show the year, date, and if the song is copy written, and if so, for how much longer. I juszt don't wanna get into a pickle where I make the disc, release it, and then have artists contacting me going: um... excuse me? I never gave you permission to do this track, you're in big big trouble, Sir! If anyone could point me to where I need to look, I'd really be greatful. Just for example, some of the hymns I'm at least considerring, now again, this is not a track listing. These for now are just ones I know very well, that I feel very comfortable recording. Amazing Grace In the Garden How Great thou Art Because he Lives Jesus Loves Me Holy Holy Holy I Surrender All Fill my Cup, Lord Peace in the Valley What a Friend etc. I just need to know what of those are in public domain. I'm not doing any of these until I know beyond a doubt. Chris.
Re: a brief debriefing on Pro Tools
Hi, Why not point them at http://www.apple.com/accessibility for apple software and http://www.microsoft.com/enable for windows based software as I have found when talking about accessibility to other software companies if you can give them resources then you are more likely to get results? Nick Gawronski On 8/19/2012 8:50 PM, Gordon Kent wrote: It's great to know that it's not a dead issue. Frankly, I'd be willing to chip in a few bucks to bring somebody onboard if they were going to be dedicated to taking on this project and had the necessary access to source code, which could be a problem. Gord -Original Message- From: Slau Halatyn Sent: Thursday, August 16, 2012 7:52 PM To: ptaccess@googlegroups.com Subject: a brief debriefing on Pro Tools Folks, I just wanted to briefly give you a little synopsis regarding accessibility issues in Pro Tools. As most of you know, there have been some changes of late. Actually, there are the changes in Pro Tools, of course, but more importantly, there have been significant changes at Avid. If you keep up with the business section of your paper, you'll have read about the investments and divestments involving Avid, their staff, their affiliated companies, etc. This is truly a difficult period for the company. At any rate, I did speak with Bobby Lombardi and we talked about possible solutions for the future. Part of it might involve taking on an intern, not unlike the last time, and tackling the most pressing issues. There's another possibility that involves a sort of hackathon where programmers take on special projects and run with it to see how far they get and, if their work seems successful enough, they incorporate it into the application. Without delving into more details (because at this point, we know which is more likely), we're going to touch base in a few more weeks and to see where we stand. I'll be going out to San francisco at the end of October and will have some face-to-face time with Bobby and others with whom I've kept in touch. There's another development that might potentially help push things along a bit but it's too early to discuss. As soon as I have more information, I'll share it here. Best, Slau
RE: Pro Tools 10 and Mountain Lion
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
Re: Pro Tools 10 and Mountain Lion
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
Re: a brief debriefing on Pro Tools
Its not really a case of them lacking knowledge Nick. More down to a lack of finances, probably a fear of destabilising a gigantic codebase, and some serious politics. All a matter of oppinion, but for what it's worth, my oppinion is that we're best having someone poking at their internals rather than sending them links. Being the Pro Tools guru to own all gurus, Slau is the man for the job. On 8/20/12, Nick Gawronski n...@nickgawronski.com wrote: Hi, Why not point them at http://www.apple.com/accessibility for apple software and http://www.microsoft.com/enable for windows based software as I have found when talking about accessibility to other software companies if you can give them resources then you are more likely to get results? Nick Gawronski On 8/19/2012 8:50 PM, Gordon Kent wrote: It's great to know that it's not a dead issue. Frankly, I'd be willing to chip in a few bucks to bring somebody onboard if they were going to be dedicated to taking on this project and had the necessary access to source code, which could be a problem. Gord -Original Message- From: Slau Halatyn Sent: Thursday, August 16, 2012 7:52 PM To: ptaccess@googlegroups.com Subject: a brief debriefing on Pro Tools Folks, I just wanted to briefly give you a little synopsis regarding accessibility issues in Pro Tools. As most of you know, there have been some changes of late. Actually, there are the changes in Pro Tools, of course, but more importantly, there have been significant changes at Avid. If you keep up with the business section of your paper, you'll have read about the investments and divestments involving Avid, their staff, their affiliated companies, etc. This is truly a difficult period for the company. At any rate, I did speak with Bobby Lombardi and we talked about possible solutions for the future. Part of it might involve taking on an intern, not unlike the last time, and tackling the most pressing issues. There's another possibility that involves a sort of hackathon where programmers take on special projects and run with it to see how far they get and, if their work seems successful enough, they incorporate it into the application. Without delving into more details (because at this point, we know which is more likely), we're going to touch base in a few more weeks and to see where we stand. I'll be going out to San francisco at the end of October and will have some face-to-face time with Bobby and others with whom I've kept in touch. There's another development that might potentially help push things along a bit but it's too early to discuss. As soon as I have more information, I'll share it here. Best, Slau
Re: a brief debriefing on Pro Tools
If memory serves correct those very same apple docs linked to were used to get us the accessibility we have to day during the initial work. The Oreo Monster monkeypushe...@gmail.com On Aug 20, 2012, at 7:26 PM, Scott Chesworth scottcheswo...@gmail.com wrote: Its not really a case of them lacking knowledge Nick. More down to a lack of finances, probably a fear of destabilising a gigantic codebase, and some serious politics. All a matter of oppinion, but for what it's worth, my oppinion is that we're best having someone poking at their internals rather than sending them links. Being the Pro Tools guru to own all gurus, Slau is the man for the job. On 8/20/12, Nick Gawronski n...@nickgawronski.com wrote: Hi, Why not point them at http://www.apple.com/accessibility for apple software and http://www.microsoft.com/enable for windows based software as I have found when talking about accessibility to other software companies if you can give them resources then you are more likely to get results? Nick Gawronski On 8/19/2012 8:50 PM, Gordon Kent wrote: It's great to know that it's not a dead issue. Frankly, I'd be willing to chip in a few bucks to bring somebody onboard if they were going to be dedicated to taking on this project and had the necessary access to source code, which could be a problem. Gord -Original Message- From: Slau Halatyn Sent: Thursday, August 16, 2012 7:52 PM To: ptaccess@googlegroups.com Subject: a brief debriefing on Pro Tools Folks, I just wanted to briefly give you a little synopsis regarding accessibility issues in Pro Tools. As most of you know, there have been some changes of late. Actually, there are the changes in Pro Tools, of course, but more importantly, there have been significant changes at Avid. If you keep up with the business section of your paper, you'll have read about the investments and divestments involving Avid, their staff, their affiliated companies, etc. This is truly a difficult period for the company. At any rate, I did speak with Bobby Lombardi and we talked about possible solutions for the future. Part of it might involve taking on an intern, not unlike the last time, and tackling the most pressing issues. There's another possibility that involves a sort of hackathon where programmers take on special projects and run with it to see how far they get and, if their work seems successful enough, they incorporate it into the application. Without delving into more details (because at this point, we know which is more likely), we're going to touch base in a few more weeks and to see where we stand. I'll be going out to San francisco at the end of October and will have some face-to-face time with Bobby and others with whom I've kept in touch. There's another development that might potentially help push things along a bit but it's too early to discuss. As soon as I have more information, I'll share it here. Best, Slau
Reading counters
All this talk about reading counters has popped a question in m my head.. I've got the hang of reading counters in Pro Tools 8.04, which I'm using, but VO doesn't tell me what the Grid and Nudge values are. I can change the Nudge value by hitting VO space when I'm in the Nudge value, but it doesn't do the same thing for the Grid value, nor does it read either. How can I read either value, or change the Grid value?
Re: Reading counters
Press the nudge button and enter the value. You won't be able to read the value. Keep in mind that you have to enter it according to the format, that is, bars/beats, or minutes/seconds. In other words, to enter a nudge value of 1.5 seconds, you need to enter 0 decimal 1 decimal 5 and hit return. HTH, slau On Aug 20, 2012, at 9:07 PM, Jon Solitro wrote: All this talk about reading counters has popped a question in m my head.. I've got the hang of reading counters in Pro Tools 8.04, which I'm using, but VO doesn't tell me what the Grid and Nudge values are. I can change the Nudge value by hitting VO space when I'm in the Nudge value, but it doesn't do the same thing for the Grid value, nor does it read either. How can I read either value, or change the Grid value?
Re: Pro Tools 10 and Mountain Lion
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 --
Re: a brief debriefing on Pro Tools
Hi, Well I was mainly trying to refresh their memory about them as I have found that lots of companies sometimes need reminders about where to find accessibility information and kindly letting them know about them won't hurt. I am not trying to say our current method is not usable I just don't want it to go to no accessibility what so ever. Nick Gawronski On 8/20/2012 6:35 PM, The Oreo Monster wrote: If memory serves correct those very same apple docs linked to were used to get us the accessibility we have to day during the initial work. The Oreo Monster monkeypushe...@gmail.com On Aug 20, 2012, at 7:26 PM, Scott Chesworth scottcheswo...@gmail.com wrote: Its not really a case of them lacking knowledge Nick. More down to a lack of finances, probably a fear of destabilising a gigantic codebase, and some serious politics. All a matter of oppinion, but for what it's worth, my oppinion is that we're best having someone poking at their internals rather than sending them links. Being the Pro Tools guru to own all gurus, Slau is the man for the job. On 8/20/12, Nick Gawronski n...@nickgawronski.com wrote: Hi, Why not point them at http://www.apple.com/accessibility for apple software and http://www.microsoft.com/enable for windows based software as I have found when talking about accessibility to other software companies if you can give them resources then you are more likely to get results? Nick Gawronski On 8/19/2012 8:50 PM, Gordon Kent wrote: It's great to know that it's not a dead issue. Frankly, I'd be willing to chip in a few bucks to bring somebody onboard if they were going to be dedicated to taking on this project and had the necessary access to source code, which could be a problem. Gord -Original Message- From: Slau Halatyn Sent: Thursday, August 16, 2012 7:52 PM To: ptaccess@googlegroups.com Subject: a brief debriefing on Pro Tools Folks, I just wanted to briefly give you a little synopsis regarding accessibility issues in Pro Tools. As most of you know, there have been some changes of late. Actually, there are the changes in Pro Tools, of course, but more importantly, there have been significant changes at Avid. If you keep up with the business section of your paper, you'll have read about the investments and divestments involving Avid, their staff, their affiliated companies, etc. This is truly a difficult period for the company. At any rate, I did speak with Bobby Lombardi and we talked about possible solutions for the future. Part of it might involve taking on an intern, not unlike the last time, and tackling the most pressing issues. There's another possibility that involves a sort of hackathon where programmers take on special projects and run with it to see how far they get and, if their work seems successful enough, they incorporate it into the application. Without delving into more details (because at this point, we know which is more likely), we're going to touch base in a few more weeks and to see where we stand. I'll be going out to San francisco at the end of October and will have some face-to-face time with Bobby and others with whom I've kept in touch. There's another development that might potentially help push things along a bit but it's too early to discuss. As soon as I have more information, I'll share it here. Best, Slau
Re: a brief debriefing on Pro Tools
Folks, Avid have worked very closely with Apple for decades and have ready access to all kinds of resources. No need to concern ourselves with those details right now. :) Slau
Re: Pro Tools 10 and Mountain Lion
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 --
