Re: Digi 003 questions
Hi Cliff, I think everybody can sympathize with wanting to get up and running as fast as possible. There are two things that come to mind based on what you've just written. If you're running on a fresh install, Spotlight will certainly spend a bunch of time indexing any drives connected to the machine including the internal drive. That might be the cause of initial CPU load if you just installed the OS and tried to run Pro Tools early on. More importantly, did you follow the Intro to Pro Tools system setup instructions including turning off Spotlight indexing for recording drives? Speaking of which, are you trying to record to an internal drive? Slau On May 12, 2014, at 5:21 PM, Cliff Isaksen cliffisak...@gmail.com wrote: Hi! Yeah, I sort of did that today... Two days ago I deleted the Machintosh HD and started fresh on MountainLion, and today I reinstalled Mavericks over a pretty fresh ML, so that's probably the next best I could do.. :) I'm on a MacBook Pro 13, mid 2012, 8 GB ram and 2,9 Ghz processor, if I remember correctly... Well, the thing about the CPU usage has baffled me too... I remember before going back to ML, the Activity Monitor in Mavericks told me that Pro tools 11 was using somewhere around 129 % CPU, and that shouldn't be possible... It's a little bit better today, but still when I checked, PT used 71 %, Kernal was doing something funky that used up over 50 % and MSD (think it's some kind of Spotlight indexing) was using over 60 %. The only explanation I can think of, is that my processor probably has multi cores and that each core might be counted as 100 % of CPU. So if I have 4 cores, I might have a total of 400 % CPU available... Or? Well, as you may correctly have gathered already, I haven't googled too much about processors and stuff yet... I really just wanna get down to business as soon as possible, and lay down some funky tracks with great music, and not have to deal with all this frustrating stuff before getting started with the real deal! :) Thanks a lot for all your help, it's highly appreciated! :) 12 May 2014 kl. 23:10 skrev Slau Halatyn slauhala...@gmail.com: Cliff, Have you tried to reinstall Mavericks from scratch and only install Pro Tools? It doesn't make sense that the program would make your system gun its fans. Which machine are you on? Also, I'm sorry, but how does a process take up 120% or was that just an exaggeration? Best, slau On May 12, 2014, at 5:28 AM, Cliff Isaksen cliffisak...@gmail.com wrote: Hi guys! I have run into some issues, and I really need some suggestions from someone who's not just as new as myself to the world of PT and controllers... :) The Problem is this: PT 11 works pretty fine together with the Digi 003 driver for 11, but PT 11 also eats up over 120 % of my Mac's CPU, so the fan starts running only after 1 minute after booting PT up, and after that, it's more or less unusable... Tried all I can think of, but nothing seems to work for fixing it. So I'll have to use PT 10, and I can't get the PT 10 driver for the Digi 003 to work in Mavericks. Can only get the driver for PT 11 to work. So I downgraded to MountainLion again, and tried installing both PT 10 and the 003 driver for PT 10. Now everything seems to work on the 003, but sound from the Mac, including VoiceOver, can't be played through the 003, and that is a huge problem... I can only playback audio from PT through the 003 and nothing more. Everything else comes out of the internal speakers, and VO also lags a lot in PT 10 now. By the way, PT 11 still rapes my processor in MountainLion... Still uses over 120 % CPU... I'm about to give up, and I think maybe I'll just have to upgrade to Mavericks again, and run PT 10 without using the 003 at all... Sorry, this got long, but I'm just out of ideas, and obviously too much of a new be to fix this myself... Any good suggestions? Thanks in advance! :) -- 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups Pro Tools Accessibility group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/ptaccess/MjpRdtYaWq4/unsubscribe. To unsubscribe from this group and all its topics, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit
Re: my post on the Avid blog
Dear Slau, Like everyone else here, I would like to congratulate you for this concise and detailed summary. For the moment, I have sold my ProTools license, I realised I was feeling comfortable with sonar and also that, being an intensive midi user, I needed a Daw that gave me full access to midi editing. I'm sorry if I ask questions that have been asked over and over on this list, but how did Midi editing's accessibility evolve with pro tools 11? I know that ProTools VS sonar is one of the recurring subjects on this list, and I was wondering if one could compile and post a little summary of what has been said about this so far . Thanks for Your continuing efforts, and not giving up. best regards, jpr http://www.jprykiel.com http://soundcloud.com/ryksounet http://twitter.com/ryksounet http://facebook.com/jeanphilipperykiel Le 11/05/2014 05:48, Gordon Kent a écrit : Hey Slau: that's a great summary of how things have evolved with PT. Frankly, the only reason I need to stick with Sonar and windows is that I have such a huge library of sampled instruments that I have done that use the SFZ format. At present, there is no aax SFZ player available for the Mac. When we wer using RTAS the garritan engine which does support SFZ worked with Pro Tools, but nobody could tell me how to refer to the Mac folder structure in an SFZ definition file. I tried putting the definitions and their associated .wav files in all kinds of folders but never got them to work, and now Garritan has pretty emphatically stated on their site that they have no plans to convert to the AAX format, which is rediculous since so many others have. If we could get access to structure, the SFZ files could be converted to sound fonts and loaded into structure. At this point, as far as instruments that are bundled with Pro tools are concerned, Structure is the real drawback for us. A good usable sampler is a very important part of the production environment, especially for those of us who want to mix and match drum kits, custom sample instruments to our taste, and process vocals through synth modulators etc. I hope they haven't forgotten about this, as I said, it's really one of the only reasons I haven't totally switched over to Pro Tools for the kind of stuff I do. But know that I sincerely apreciate what you've done, I've gone through the same thing with my many years of association with cakewalk, which has put a lot of blind folks to independent work. Gord On May 9, 2014, at 11:59 PM, Slau Halatyn slauhala...@gmail.com mailto:slauhala...@gmail.com wrote: As some of you may already know, I was asked to write something for the Avid blog regarding Pro Tools accessibility. The article was published this afternoon at: http://www.avidblogs.com/music-daw-software-for-blind-and-visually-impaired-audio-professionals/ Because of the way the story is laid out, it appears not to read entirely chronologically. So, I've pasted the contents of that post below. There were several photos in the post which are not included below. I was introduced to Pro Tools while enrolled in the audio program at Five Towns College in Dix Hills, New York, during the mid '90s. Most of my early training in college was on large format consoles and multitrack tape machines, which were de rigueur in the studios of the day. Computers had certainly found their way into the recording environment nearly a decade earlier, but more so in the role of MIDI sequencers. During the years I was in school, however, the digital audio workstation (DAW) had gotten its foot in the door of the control room and the DAW that led the way was Pro Tools, which I began to work with in my senior year. I sat there in front of the monitor, staring at a graphic representation of a waveform, wondering whether the hours I spent learning how to splice quarter-inch tape with razors had been wasted... I had the advantage of taking a one-on-one advanced digital audio class with my professor as a result of my need to use adaptive software known as inLARGE, a screen magnifying program for the Macintosh. Several years earlier, I had been diagnosed with a retinal condition that impaired my vision. When I entered college, most of the gear I used was highly tactile: mixing consoles, outboard processors, tape machine remotes, etc. By the time I was preparing for graduation, things had already begun to change. Evidence of this glowed from a VGA before me---everything, all under one roof, one box. Little did I know that this was the paradigm of the future, and little did I know that 20 years later, I'd be so closely involved with Pro Tools and its accessibility for blind audio engineers and musicians. After graduation I started a recording studio of my own, BeSharp, in New York City and for a number of years I kept one foot firmly planted in the analog multitrack world while occasionally using a computer for virtual tracks slaved to tape.
Re: my post on the Avid blog
Hi Jean-Philippe, The MIDI Event List became fully accessible as of version 11.1. As you may recall, it was always possible to create MIDI tracks, record and edit with a control surface in a cut, copy paste manner. Now that the event list is visible, one can edit all parameters, filter, etc. I'm not sure of the exact status with patch libraries and the like but things are a whole lot better than they were a few years ago. Hope that helps. Slau On May 13, 2014, at 10:37 AM, Jean-Philippe Rykiel jpryk...@gmail.com wrote: Dear Slau, Like everyone else here, I would like to congratulate you for this concise and detailed summary. For the moment, I have sold my ProTools license, I realised I was feeling comfortable with sonar and also that, being an intensive midi user, I needed a Daw that gave me full access to midi editing. I'm sorry if I ask questions that have been asked over and over on this list, but how did Midi editing's accessibility evolve with pro tools 11? I know that ProTools VS sonar is one of the recurring subjects on this list, and I was wondering if one could compile and post a little summary of what has been said about this so far . Thanks for Your continuing efforts, and not giving up. best regards, jpr http://www.jprykiel.com http://soundcloud.com/ryksounet http://twitter.com/ryksounet http://facebook.com/jeanphilipperykiel Le 11/05/2014 05:48, Gordon Kent a écrit : Hey Slau: that's a great summary of how things have evolved with PT. Frankly, the only reason I need to stick with Sonar and windows is that I have such a huge library of sampled instruments that I have done that use the SFZ format. At present, there is no aax SFZ player available for the Mac. When we wer using RTAS the garritan engine which does support SFZ worked with Pro Tools, but nobody could tell me how to refer to the Mac folder structure in an SFZ definition file. I tried putting the definitions and their associated .wav files in all kinds of folders but never got them to work, and now Garritan has pretty emphatically stated on their site that they have no plans to convert to the AAX format, which is rediculous since so many others have. If we could get access to structure, the SFZ files could be converted to sound fonts and loaded into structure. At this point, as far as instruments that are bundled with Pro tools are concerned, Structure is the real drawback for us. A good usable sampler is a very important part of the production environment, especially for those of us who want to mix and match drum kits, custom sample instruments to our taste, and process vocals through synth modulators etc. I hope they haven't forgotten about this, as I said, it's really one of the only reasons I haven't totally switched over to Pro Tools for the kind of stuff I do. But know that I sincerely apreciate what you've done, I've gone through the same thing with my many years of association with cakewalk, which has put a lot of blind folks to independent work. Gord On May 9, 2014, at 11:59 PM, Slau Halatyn slauhala...@gmail.com wrote: As some of you may already know, I was asked to write something for the Avid blog regarding Pro Tools accessibility. The article was published this afternoon at: http://www.avidblogs.com/music-daw-software-for-blind-and-visually-impaired-audio-professionals/ Because of the way the story is laid out, it appears not to read entirely chronologically. So, I've pasted the contents of that post below. There were several photos in the post which are not included below. I was introduced to Pro Tools while enrolled in the audio program at Five Towns College in Dix Hills, New York, during the mid '90s. Most of my early training in college was on large format consoles and multitrack tape machines, which were de rigueur in the studios of the day. Computers had certainly found their way into the recording environment nearly a decade earlier, but more so in the role of MIDI sequencers. During the years I was in school, however, the digital audio workstation (DAW) had gotten its foot in the door of the control room and the DAW that led the way was Pro Tools, which I began to work with in my senior year. I sat there in front of the monitor, staring at a graphic representation of a waveform, wondering whether the hours I spent learning how to splice quarter-inch tape with razors had been wasted... I had the advantage of taking a one-on-one advanced digital audio class with my professor as a result of my need to use adaptive software known as inLARGE, a screen magnifying program for the Macintosh. Several years earlier, I had been diagnosed with a retinal condition that impaired my vision. When I entered college, most of the gear I used was highly tactile: mixing consoles, outboard processors, tape machine remotes, etc. By the time I was preparing for graduation, things had
Re: Digi 003 questions
Ahhh... I was trying to record to an internal drive earlier on when the CPU usage was sky high! That might be the reason why it has gone from 120 to 70 % now, since I've formatted an old drive for exclusive pro tools use. But I don't think this drive even is the best either for PT use... Well, that might be it, even though I didn't see anything like it when trying the same in PT 10... :) Anyways, I'm making a Mavericks installer USB as we speak, and will do a completely fresh Mavericks install in a few minutes, cause I installed Digi 003 drivers for PT 10 in MountainLion, and after that didn't work out, I upgraded to Mavericks and installed PT 11 and the corresponding 003 drivers. I see that some have said that having both 003 drivers installed at the same time may cause some glitches and hick-ups, so now I'm just starting fresh on everything again! :) Lets see if that might cause things to work a little bit smoother... :) I'll rather take the work now than to get 2 tracks down tomorrow and then have to do the work anyways! :) Thank you again for all your kind help! :) 13 May 2014 kl. 16:17 skrev Slau Halatyn slauhala...@gmail.com: Hi Cliff, I think everybody can sympathize with wanting to get up and running as fast as possible. There are two things that come to mind based on what you've just written. If you're running on a fresh install, Spotlight will certainly spend a bunch of time indexing any drives connected to the machine including the internal drive. That might be the cause of initial CPU load if you just installed the OS and tried to run Pro Tools early on. More importantly, did you follow the Intro to Pro Tools system setup instructions including turning off Spotlight indexing for recording drives? Speaking of which, are you trying to record to an internal drive? Slau On May 12, 2014, at 5:21 PM, Cliff Isaksen cliffisak...@gmail.com wrote: Hi! Yeah, I sort of did that today... Two days ago I deleted the Machintosh HD and started fresh on MountainLion, and today I reinstalled Mavericks over a pretty fresh ML, so that's probably the next best I could do.. :) I'm on a MacBook Pro 13, mid 2012, 8 GB ram and 2,9 Ghz processor, if I remember correctly... Well, the thing about the CPU usage has baffled me too... I remember before going back to ML, the Activity Monitor in Mavericks told me that Pro tools 11 was using somewhere around 129 % CPU, and that shouldn't be possible... It's a little bit better today, but still when I checked, PT used 71 %, Kernal was doing something funky that used up over 50 % and MSD (think it's some kind of Spotlight indexing) was using over 60 %. The only explanation I can think of, is that my processor probably has multi cores and that each core might be counted as 100 % of CPU. So if I have 4 cores, I might have a total of 400 % CPU available... Or? Well, as you may correctly have gathered already, I haven't googled too much about processors and stuff yet... I really just wanna get down to business as soon as possible, and lay down some funky tracks with great music, and not have to deal with all this frustrating stuff before getting started with the real deal! :) Thanks a lot for all your help, it's highly appreciated! :) 12 May 2014 kl. 23:10 skrev Slau Halatyn slauhala...@gmail.com: Cliff, Have you tried to reinstall Mavericks from scratch and only install Pro Tools? It doesn't make sense that the program would make your system gun its fans. Which machine are you on? Also, I'm sorry, but how does a process take up 120% or was that just an exaggeration? Best, slau On May 12, 2014, at 5:28 AM, Cliff Isaksen cliffisak...@gmail.com wrote: Hi guys! I have run into some issues, and I really need some suggestions from someone who's not just as new as myself to the world of PT and controllers... :) The Problem is this: PT 11 works pretty fine together with the Digi 003 driver for 11, but PT 11 also eats up over 120 % of my Mac's CPU, so the fan starts running only after 1 minute after booting PT up, and after that, it's more or less unusable... Tried all I can think of, but nothing seems to work for fixing it. So I'll have to use PT 10, and I can't get the PT 10 driver for the Digi 003 to work in Mavericks. Can only get the driver for PT 11 to work. So I downgraded to MountainLion again, and tried installing both PT 10 and the 003 driver for PT 10. Now everything seems to work on the 003, but sound from the Mac, including VoiceOver, can't be played through the 003, and that is a huge problem... I can only playback audio from PT through the 003 and nothing more. Everything else comes out of the internal speakers, and VO also lags a lot in PT 10 now. By the way, PT 11 still rapes my processor in MountainLion... Still uses over 120 % CPU... I'm about to give up, and I think maybe I'll just have to upgrade to Mavericks again,
Re: ProTools11 for the blind
Hi Tim, Welcome to the list. I've never used Sonar but most people would it very accessible. Logic is somewhat accessible but not enough for serious use. Pro Tools is quite accessible in version 11.1 not 11.0. The stock plug-ins are almost entirely accessible. the thing is, there's no specific method for using it with VoiceOver. By that, I mean, you use it just like a sighted user would. This means that there's a lot of reading to do with the various manuals. If language is an issue, you might find it pretty challenging. Best, Slau On May 13, 2014, at 7:11 AM, Tim Liu timtimliu2...@gmail.com wrote: Hi everybody: I am a blind people from Hong Kong. Please forgive my English is not very good. I started making music in 2010 and use cakewalk sonar in windows OS. I feel this software is not accessible for the blind, Even with the J sonar. So I change use the mac in 2012 I use Logic pro, Nothing seems to improve my problem. yesterday, I change to ProTools11 I would like to ask what needs attention for blind people and some accessibility functions? have some plug-in is to give blind better to use protools? Because I feel not totally accessible for the blind. Also, if I want to buy some plug-ins, such as Native instrument, Waves, What is accessible? Or can Recommend some virtual instrument and effect pluging to me? Thanks -- 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: ProTools11 for the blind
Slau, By quite accessible, do you mean, 'hmmm yeah it's accessible but...', or do you mean 'yes, you can use it?' What's the best version of PT in terms of accessibility? Thanks, Ashley On 13/05/2014 19:02, Slau Halatyn wrote: Hi Tim, Welcome to the list. I've never used Sonar but most people would it very accessible. Logic is somewhat accessible but not enough for serious use. Pro Tools is quite accessible in version 11.1 not 11.0. The stock plug-ins are almost entirely accessible. the thing is, there's no specific method for using it with VoiceOver. By that, I mean, you use it just like a sighted user would. This means that there's a lot of reading to do with the various manuals. If language is an issue, you might find it pretty challenging. Best, Slau On May 13, 2014, at 7:11 AM, Tim Liu timtimliu2...@gmail.com mailto:timtimliu2...@gmail.com wrote: Hi everybody: I am a blind people from Hong Kong. Please forgive my English is not very good. I started making music in 2010 and use cakewalk sonar in windows OS. I feel this software is not accessible for the blind, Even with the J sonar. So I change use the mac in 2012 I use Logic pro, Nothing seems to improve my problem. yesterday, I change to ProTools11 I would like to ask what needs attention for blind people and some accessibility functions? have some plug-in is to give blind better to use protools? Because I feel not totally accessible for the blind. Also, if I want to buy some plug-ins, such as Native instrument, Waves, What is accessible? Or can Recommend some virtual instrument and effect pluging to me? Thanks -- 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 ptaccess+unsubscr...@googlegroups.com mailto:ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 ptaccess+unsubscr...@googlegroups.com mailto:ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: ProTools11 for the blind
Hi Ashley, Well, the definition of accessibility varies for a lot of people. Quite and very, for me, mean pretty much the same thing. In terms of MIDI, there's no question that version 11.1 is the most accessible because the MIDI Event List was not at all accessible in prior versions. Hope that helps, Slau On May 13, 2014, at 2:05 PM, Ashley ashleycox...@googlemail.com wrote: Slau, By quite accessible, do you mean, 'hmmm yeah it's accessible but...', or do you mean 'yes, you can use it?' What's the best version of PT in terms of accessibility? Thanks, Ashley On 13/05/2014 19:02, Slau Halatyn wrote: Hi Tim, Welcome to the list. I've never used Sonar but most people would it very accessible. Logic is somewhat accessible but not enough for serious use. Pro Tools is quite accessible in version 11.1 not 11.0. The stock plug-ins are almost entirely accessible. the thing is, there's no specific method for using it with VoiceOver. By that, I mean, you use it just like a sighted user would. This means that there's a lot of reading to do with the various manuals. If language is an issue, you might find it pretty challenging. Best, Slau On May 13, 2014, at 7:11 AM, Tim Liu timtimliu2...@gmail.com wrote: Hi everybody: I am a blind people from Hong Kong. Please forgive my English is not very good. I started making music in 2010 and use cakewalk sonar in windows OS. I feel this software is not accessible for the blind, Even with the J sonar. So I change use the mac in 2012 I use Logic pro, Nothing seems to improve my problem. yesterday, I change to ProTools11 I would like to ask what needs attention for blind people and some accessibility functions? have some plug-in is to give blind better to use protools? Because I feel not totally accessible for the blind. Also, if I want to buy some plug-ins, such as Native instrument, Waves, What is accessible? Or can Recommend some virtual instrument and effect pluging to me? Thanks -- 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: ProTools11 for the blind
Hi Slau, Thanks - Midi is my main use, so I'll be OK with PT11. Just waiting for apple to ship my mac; then I'll say goodbye to the trusty powermac G3, and Hi to a copy of PT11! Cheers, Ashley On 13/05/2014 19:49, Slau Halatyn wrote: Hi Ashley, Well, the definition of accessibility varies for a lot of people. Quite and very, for me, mean pretty much the same thing. In terms of MIDI, there's no question that version 11.1 is the most accessible because the MIDI Event List was not at all accessible in prior versions. Hope that helps, Slau On May 13, 2014, at 2:05 PM, Ashley ashleycox...@googlemail.com mailto:ashleycox...@googlemail.com wrote: Slau, By quite accessible, do you mean, 'hmmm yeah it's accessible but...', or do you mean 'yes, you can use it?' What's the best version of PT in terms of accessibility? Thanks, Ashley On 13/05/2014 19:02, Slau Halatyn wrote: Hi Tim, Welcome to the list. I've never used Sonar but most people would it very accessible. Logic is somewhat accessible but not enough for serious use. Pro Tools is quite accessible in version 11.1 not 11.0. The stock plug-ins are almost entirely accessible. the thing is, there's no specific method for using it with VoiceOver. By that, I mean, you use it just like a sighted user would. This means that there's a lot of reading to do with the various manuals. If language is an issue, you might find it pretty challenging. Best, Slau On May 13, 2014, at 7:11 AM, Tim Liu timtimliu2...@gmail.com mailto:timtimliu2...@gmail.com wrote: Hi everybody: I am a blind people from Hong Kong. Please forgive my English is not very good. I started making music in 2010 and use cakewalk sonar in windows OS. I feel this software is not accessible for the blind, Even with the J sonar. So I change use the mac in 2012 I use Logic pro, Nothing seems to improve my problem. yesterday, I change to ProTools11 I would like to ask what needs attention for blind people and some accessibility functions? have some plug-in is to give blind better to use protools? Because I feel not totally accessible for the blind. Also, if I want to buy some plug-ins, such as Native instrument, Waves, What is accessible? Or can Recommend some virtual instrument and effect pluging to me? Thanks -- 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 ptaccess+unsubscr...@googlegroups.com mailto:ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 ptaccess+unsubscr...@googlegroups.com mailto:ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 ptaccess+unsubscr...@googlegroups.com mailto:ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 ptaccess+unsubscr...@googlegroups.com mailto:ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
PT11.1 question
I just downloaded my free PT11.1 and I'm wondering why the installed is so small? The others have been a couple gb in size and this one is 900mb. It lists as an upgrade. Do I have to install PT11.0 first? J. R. -- 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: PT11.1 question
Hi, I think the reason the download is so small is with pro tools 11 you are just downloading the application and it does not include any pdf files as like the pro tools 10 installer did. I like this a lot better as this way you can download only what you need. If you are going to run pro tools 10 and pro tools 11 on the same system you should install both sets of drivers for your hardware and install the pro tools 10 stuff first. Just copy the pro tools application to your applications folder. The first time you launch it it will ask you to authenticate at which point voiceover if you try to move around will tell you that pro tools has no windows. Don't be bothered with that just usually around a minute later things will work it is probably installing other system files and settings. I don't think pro tools preferences stick with 10 and 11 so they are two different sets of preferences which I like a lot better. Nick Gawronski On 5/13/2014 6:50 PM, J. R. Westmoreland wrote: I just downloaded my free PT11.1 and I'm wondering why the installed is so small? The others have been a couple gb in size and this one is 900mb. It lists as an upgrade. Do I have to install PT11.0 first? J. R. -- 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 ptaccess+unsubscr...@googlegroups.com mailto:ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Protools11 shortcut problem
Hi all: Thank you for answering my last question, Your answers are very helpful to me. I have more questions. I would like to ask if I want to select one piece of music in the ProTools11.1 for edit/quantize, Which I press the shortcut keys? Thanks -- 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
