Loops accessibility in PT 11
Hi! I'm sorry if this has been discussed before and if I'm therefore double-posting but I couldn't find something specific on this topic in this group. Thing is, I'm trying to learn pro tools, and therefor I also need to know what can be done and what can't, so I know if it's me who's messing things up or if it simply can't be done with VoiceOver. So to the questions: I'm trying to use loops in PT. I've understood that it's done via the Workspace that is opened with Option+I. But once it's open, I can't figure out how the browser is organized, and I can't figure out how and if I can navigate to the location where my loop files are located. Then, if I at some point will figure that out and it can be done, will I be able to drag the loop from the browser window to a track? If yes, will I then have a chance of choosing where on the track to put this loop timewize? I'm probably wanna use loops most for percussion stuff, like for making an already existing drumtrack more massive or sound fatter in choruses etc. So it's important that I will be able to adjust the tempo of the loop too so that it will match my sessions tempo... Is there any other way of doing it than through the workspace, that didn't seem to be accessible with VO, or is there something I've missed about navigating the workspace? Is there a standard recepee for getting a loop into a session with VO that works best? I would be so happy if some of you had any help to offer, that you wouldn't believe it! :) I've struggled with this now for several days, and i'm almost out of bad language now... Lol! 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.
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: Digi 003 questions
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.
Re: Digi 003 questions
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 https://groups.google.com/d/optout.
Re: Digi 003 questions
Hi! This is nothing less than awesome! I got PT only one month ago, and I'm going to the post office tomorrow to pick up a Digi 003, so the rtf will really come in handy, Slau! Thanks a lot! One question; Will I need drivers to get the Digi 003 up and running on Mavericks with PT 10, or is it as simple as plug and play? All the best Cliff, NORWAY -- 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: Digi 003 questions
Hi and thanks both of you! Since PT 11 for some weird reason is eating up 120 % of my CPU, I'm using PT 10 as long as possible, so I'll probably just have to try and see if I can use the Digi 003 first without installing any drivers. And if that won't work, I'll have to take a look at the avid website and see if I can find it! :) I was at first thinking about something more expensive like a C24 or a D-Command as my controller, but the thing is, I really don't have enough room for it in my little home studio, so the Digi 003 seemed to be a good option for a not THAT big expense as the others, that are more on the expensive side... Well, wish me luck... Really looking forwards to laying my hands on a real controller surface now! Kind regards from Tired-of-interacting-Cliff -- 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.
