Very important question about a long-term ProTools project I'm working on.
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: Pro Tools 10 and Mountain Lion
But the question is, was it different in Pro Tools 9? On Aug 17, 2012, at 1:48 PM, Christopher-Mark gilland wrote: > Slau, if you go to the events menu, under tempo operations, then go to > constant, for example, you'll see that the tempo value bpm field doesn't read > for example. It tells you it's a numerical value text box, but try as you > may, it won't tell you what it's set to. > > Chris. > > - Original Message - From: "Slau Halatyn" > To: > Sent: Thursday, August 16, 2012 8:50 PM > Subject: Re: Pro Tools 10 and Mountain Lion > > > 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
Slau, if you go to the events menu, under tempo operations, then go to constant, for example, you'll see that the tempo value bpm field doesn't read for example. It tells you it's a numerical value text box, but try as you may, it won't tell you what it's set to. Chris. - Original Message - From: "Slau Halatyn" To: Sent: Thursday, August 16, 2012 8:50 PM Subject: Re: Pro Tools 10 and Mountain Lion 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
I have a couple of rooms in my basement with locks that would work for that one. LOL Most glad I have the space and machinery to run two versions of the OS. J. R. -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of David Eagle Sent: Friday, August 17, 2012 6:38 AM To: ptaccess@googlegroups.com Subject: Re: a brief debriefing on Pro Tools I've not got much room in my flat for storing hostages, but anything other than that, I'd be happy to help. Thanks so much slau. On 17/08/2012, Kevin Reeves wrote: > Awesome. Thanks so much for all of this man. You rock. > > Kevin > On Aug 16, 2012, at 7:52 PM, Slau Halatyn wrote: > >> 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 >> > > -- http://www.davideagle.co.uk
Re: a brief debriefing on Pro Tools
I've not got much room in my flat for storing hostages, but anything other than that, I'd be happy to help. Thanks so much slau. On 17/08/2012, Kevin Reeves wrote: > Awesome. Thanks so much for all of this man. You rock. > > Kevin > On Aug 16, 2012, at 7:52 PM, Slau Halatyn wrote: > >> 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 >> > > -- http://www.davideagle.co.uk
Re: a brief debriefing on Pro Tools
Awesome. Thanks so much for all of this man. You rock. Kevin On Aug 16, 2012, at 7:52 PM, Slau Halatyn wrote: > 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 >
