Re: Introduction and a few questions.
Yeah, I think that's the one. slau On Jun 3, 2011, at 12:29 AM, Scott Chesworth wrote: From memory, F12 was another one that Avid recommend you disable. It's originally assigned to bring up Dashboard so I can't say I've missed it, but I also can't say I use it in PT either. It's an alternative to using Command+Space to start recording. Likely not a deal breaker, just adding it to the list. Hth Scott On 6/3/11, Abdul D Kamara abduldkam...@googlemail.com wrote: Yeah, I think you are right about the play button. I'm going to bed now, and I will be taking with me the 36 page document on Pro Tools short cuts. Oh, and if you happen to remember the other shortcuts that need to be disabled, please let me know, I have already disabled the one for spotlight... I am not using an external drive right now, though I will. I get the sense that this is critical, Beyond the issue of space, why is it so? Thanks again, Abdul On 3 Jun 2011, at 01:09, Slau Halatyn wrote: Hey Abdul, Glad it worked. I'm thinking that you probably armed the Record button in the transport but never actually engaged the transport by pressing the Play button. Well, the Command-space bar shortcut will solve that. There's also another couple of options for engaging the transport. One is with a particular f-key (I don't recall which one because I never use it) and num pad 3 and then space bar. Again, I never use that but it's just another option. Glad you're rolling, so to speak ;) Slau On Jun 2, 2011, at 7:00 PM, Abdul D Kamara wrote: Hey Folks, thanks to Slau, the recording problem is fixed. It appears that using the key commands work better than trying to directly manipulate controls in the transport cluster. On 3 Jun 2011, at 00:26, Slau Halatyn wrote: I don't think so. In step 4 Abdul says he armed the track and then in the Transport cluster he engaged the record function. I take that as he took the right steps. bTW, Abdul, you needn't use the transport window or cluster for engaging the transport. Command-space bar is the keyboard shortcut for putting the transport into record. HTH, slau On Jun 2, 2011, at 6:21 PM, Monkey Pusher wrote: It seems he may haver not armed, or record enabled the mono track he wants to record on. He only mention pressing the arm button in the transport cluster, but not the one on the track. You have have to record enable the track as well so Protools knows which track you want the recorded audio placed on. Hope this helps. Steve On 6/2/11, Slau Halatyn slauhala...@gmail.com wrote: Hey Abdul, OK, one thing I forgot to mention is the issue of input monitoring. Now, I'm not sure what the case is with LE systems but, with HD systems, one can switch between monitoring the input or the playback of a given record-enabled track. Option-k toggles between these two modes. It's under the Tracks menu. Again, I'm not sure what the case is with LE so you'll have to check. Now, if I remember correctly, with MBoxes, there was a particular knob that, when turned to the left, sent the input to the stereo out and when turned to the right, sent the recorded signal to the output. So, essentially, if it's somewhere in the middle, you'd get both. I would make sure that the knob is at least in the middle so you can hear playback. During recording, it would be perhaps better to use only the input signal as there would otherwise be a slight delay between the live signal and the playback signal. Using a small playback buffer or using low latency monitoring would help this situation considerably. HTH, slau On Jun 2, 2011, at 2:22 PM, Abdul D Kamara wrote: Hey Slau, So the idea is that some of these clips, which include sections of music and/or voice recording, would be at times overlapping the voice from the primary audio track. I will be following a pretty tight script, doing it live most of the way, so I think I might want to give the instrument track with the launchpad a go. Of course, I understand some of these explanations can be quite involved, so in advance, you have my gratitude. I have been able to set up the baby grand piano to work with my controller. I think I get how a fraction of this works. Expanding my library to accommodate my clips is the trick. On to the audio: 1. By signal feeding you mean that I am able to hear my voice via the microphone? If so, yes. 2. Link Timeline Edit Selection is checked. I don't think that I have manipulated any other defaults. So thus far, no luck. On 2 Jun 2011, at 19:13, Slau Halatyn wrote: Hey Abdul, OK, I have some time now to address your questions. First, let me say that you might only possibly need a trigger for specific audio clips if you're planning to do it in real time. I would bet that you're not planning to do the whole of each podcast episode live, without any edits. So, triggering sounds, per se,
Introduction and a few questions.
Hey All, I'm new to the list. ...thought it would be good to introduce myself, as I already have a kabillion questions for you all. I'm trying to set up a Podcast. I'm running Pro Tools 8.0.5 with an MBox 2 as my interface. The basic template I need has a audio and instrument track, the former will be for voice recording via mic and the latter will be for for triggering various audio clips, which will be done through a MIDI controller. To do so, I will need to have the clips made into virtual instruments. At least, this is the conceptual explanation I got from an expert from my nearby audio equipment reseller. So here are some of the questions I have. 1. How do I create a virtual instrument in Pro Tools, and can I access them? 2. How do I direct the controller to use the instrument? I should say that the device is a LaunchPad Live Controller I'm told that it should integrate seamlessly with Pro Tools. I am also having a little trouble with understanding the steps for recording an audio track. I have done the following. 1. Created a session and specified recording parameters. 2. Created an mono Audio Track. 3. Checked the physical layer: gain/volume levels, connections, etc... 4. Armed the track. 5. In the Transport Cluster, I hit Record Enabled. I stopped after 10 seconds of recording, went back to the beginning, tried to play, but no sound. What is up with that? But more reasonably, what am I missing? I appreciate that some of these questions are super simple for some, so please bare with me. Also, if any of you know of a down to basics tutorial that I can refer to, please let me know. Many Thanks, Abdul
Re: Introduction and a few questions.
Hi Abdul, Welcome to the list. If nobody else tackles your questions, I'll be happy to get you started. I'm about to start a session and don't yet have the time to properly reply. I'll have some time in about 4 hours and will post then. cheers, Slau On Jun 2, 2011, at 6:46 AM, Abdul D Kamara wrote: Hey All, I'm new to the list. ...thought it would be good to introduce myself, as I already have a kabillion questions for you all. I'm trying to set up a Podcast. I'm running Pro Tools 8.0.5 with an MBox 2 as my interface. The basic template I need has a audio and instrument track, the former will be for voice recording via mic and the latter will be for for triggering various audio clips, which will be done through a MIDI controller. To do so, I will need to have the clips made into virtual instruments. At least, this is the conceptual explanation I got from an expert from my nearby audio equipment reseller. So here are some of the questions I have. 1. How do I create a virtual instrument in Pro Tools, and can I access them? 2. How do I direct the controller to use the instrument? I should say that the device is a LaunchPad Live Controller I'm told that it should integrate seamlessly with Pro Tools. I am also having a little trouble with understanding the steps for recording an audio track. I have done the following. 1. Created a session and specified recording parameters. 2. Created an mono Audio Track. 3. Checked the physical layer: gain/volume levels, connections, etc... 4. Armed the track. 5. In the Transport Cluster, I hit Record Enabled. I stopped after 10 seconds of recording, went back to the beginning, tried to play, but no sound. What is up with that? But more reasonably, what am I missing? I appreciate that some of these questions are super simple for some, so please bare with me. Also, if any of you know of a down to basics tutorial that I can refer to, please let me know. Many Thanks, Abdul
Re: Introduction and a few questions.
Hey Abdul, OK, I have some time now to address your questions. First, let me say that you might only possibly need a trigger for specific audio clips if you're planning to do it in real time. I would bet that you're not planning to do the whole of each podcast episode live, without any edits. So, triggering sounds, per se, is probably completely unnecessary. If it's a live radio-style show then, yes, that would be appropriate. The overwhelming majority of podcasts are put together in pieces with segments recorded, edited and then output as a single mixed file. Normally, any kind of music or sound effects would be copied and pasted into a dedicated track and mixed along with the other material or sometimes even put into the same track as a stand-alone audio region in the midst of other audio regions—essentially as a link in a chain of various pieces of audio. So, I wouldn't worry about the virtual instrument track at this time. To address the audio questions, you seem to have followed the right steps in general. Let me ask a few other questions: 1. When you created the mono track and checked the routing, were you able to hear the signal feeding the microphone? 2. Make sure that link Timeline Edit Selection is checked under the Options menu. Did you change any other defaults? 3. When you stopped the transport, did you press Return to get back to the beginning of the session? BTW, there are two types of playback behavior as it pertains to the insertion point. With the insertion following the playback cursor, if you stop the playback by pressing the space bar, the insertion will stay at the stopped playback position. If insertion is not following playback, the insertion point will stay at the initial position and remain there while the playback cursor continues on playing the material. If you press the space bar in this mode, the transport main counter will instantly reset back to it's original position where you started playback. This is a matter of personal preference and is coincidentally found in the Preferences dialog under the Setups menu. Let's start with that for now. Let me know. Slau On Jun 2, 2011, at 6:46 AM, Abdul D Kamara wrote: Hey All, I'm new to the list. ...thought it would be good to introduce myself, as I already have a kabillion questions for you all. I'm trying to set up a Podcast. I'm running Pro Tools 8.0.5 with an MBox 2 as my interface. The basic template I need has a audio and instrument track, the former will be for voice recording via mic and the latter will be for for triggering various audio clips, which will be done through a MIDI controller. To do so, I will need to have the clips made into virtual instruments. At least, this is the conceptual explanation I got from an expert from my nearby audio equipment reseller. So here are some of the questions I have. 1. How do I create a virtual instrument in Pro Tools, and can I access them? 2. How do I direct the controller to use the instrument? I should say that the device is a LaunchPad Live Controller I'm told that it should integrate seamlessly with Pro Tools. I am also having a little trouble with understanding the steps for recording an audio track. I have done the following. 1. Created a session and specified recording parameters. 2. Created an mono Audio Track. 3. Checked the physical layer: gain/volume levels, connections, etc... 4. Armed the track. 5. In the Transport Cluster, I hit Record Enabled. I stopped after 10 seconds of recording, went back to the beginning, tried to play, but no sound. What is up with that? But more reasonably, what am I missing? I appreciate that some of these questions are super simple for some, so please bare with me. Also, if any of you know of a down to basics tutorial that I can refer to, please let me know. Many Thanks, Abdul
Re: Introduction and a few questions.
Hey Abdul, OK, one thing I forgot to mention is the issue of input monitoring. Now, I'm not sure what the case is with LE systems but, with HD systems, one can switch between monitoring the input or the playback of a given record-enabled track. Option-k toggles between these two modes. It's under the Tracks menu. Again, I'm not sure what the case is with LE so you'll have to check. Now, if I remember correctly, with MBoxes, there was a particular knob that, when turned to the left, sent the input to the stereo out and when turned to the right, sent the recorded signal to the output. So, essentially, if it's somewhere in the middle, you'd get both. I would make sure that the knob is at least in the middle so you can hear playback. During recording, it would be perhaps better to use only the input signal as there would otherwise be a slight delay between the live signal and the playback signal. Using a small playback buffer or using low latency monitoring would help this situation considerably. HTH, slau On Jun 2, 2011, at 2:22 PM, Abdul D Kamara wrote: Hey Slau, So the idea is that some of these clips, which include sections of music and/or voice recording, would be at times overlapping the voice from the primary audio track. I will be following a pretty tight script, doing it live most of the way, so I think I might want to give the instrument track with the launchpad a go. Of course, I understand some of these explanations can be quite involved, so in advance, you have my gratitude. I have been able to set up the baby grand piano to work with my controller. I think I get how a fraction of this works. Expanding my library to accommodate my clips is the trick. On to the audio: 1. By signal feeding you mean that I am able to hear my voice via the microphone? If so, yes. 2. Link Timeline Edit Selection is checked. I don't think that I have manipulated any other defaults. So thus far, no luck. On 2 Jun 2011, at 19:13, Slau Halatyn wrote: Hey Abdul, OK, I have some time now to address your questions. First, let me say that you might only possibly need a trigger for specific audio clips if you're planning to do it in real time. I would bet that you're not planning to do the whole of each podcast episode live, without any edits. So, triggering sounds, per se, is probably completely unnecessary. If it's a live radio-style show then, yes, that would be appropriate. The overwhelming majority of podcasts are put together in pieces with segments recorded, edited and then output as a single mixed file. Normally, any kind of music or sound effects would be copied and pasted into a dedicated track and mixed along with the other material or sometimes even put into the same track as a stand-alone audio region in the midst of other audio regions—essentially as a link in a chain of various pieces of audio. So, I wouldn't worry about the virtual instrument track at this time. To address the audio questions, you seem to have followed the right steps in general. Let me ask a few other questions: 1. When you created the mono track and checked the routing, were you able to hear the signal feeding the microphone? 2. Make sure that link Timeline Edit Selection is checked under the Options menu. Did you change any other defaults? 3. When you stopped the transport, did you press Return to get back to the beginning of the session? BTW, there are two types of playback behavior as it pertains to the insertion point. With the insertion following the playback cursor, if you stop the playback by pressing the space bar, the insertion will stay at the stopped playback position. If insertion is not following playback, the insertion point will stay at the initial position and remain there while the playback cursor continues on playing the material. If you press the space bar in this mode, the transport main counter will instantly reset back to it's original position where you started playback. This is a matter of personal preference and is coincidentally found in the Preferences dialog under the Setups menu. Let's start with that for now. Let me know. Slau On Jun 2, 2011, at 6:46 AM, Abdul D Kamara wrote: Hey All, I'm new to the list. ...thought it would be good to introduce myself, as I already have a kabillion questions for you all. I'm trying to set up a Podcast. I'm running Pro Tools 8.0.5 with an MBox 2 as my interface. The basic template I need has a audio and instrument track, the former will be for voice recording via mic and the latter will be for for triggering various audio clips, which will be done through a MIDI controller. To do so, I will need to have the clips made into virtual instruments. At least, this is the conceptual explanation I got from an expert from my nearby audio equipment reseller. So here are some of the questions I have. 1. How do I
Re: Introduction and a few questions.
It seems he may haver not armed, or record enabled the mono track he wants to record on. He only mention pressing the arm button in the transport cluster, but not the one on the track. You have have to record enable the track as well so Protools knows which track you want the recorded audio placed on. Hope this helps. Steve On 6/2/11, Slau Halatyn slauhala...@gmail.com wrote: Hey Abdul, OK, one thing I forgot to mention is the issue of input monitoring. Now, I'm not sure what the case is with LE systems but, with HD systems, one can switch between monitoring the input or the playback of a given record-enabled track. Option-k toggles between these two modes. It's under the Tracks menu. Again, I'm not sure what the case is with LE so you'll have to check. Now, if I remember correctly, with MBoxes, there was a particular knob that, when turned to the left, sent the input to the stereo out and when turned to the right, sent the recorded signal to the output. So, essentially, if it's somewhere in the middle, you'd get both. I would make sure that the knob is at least in the middle so you can hear playback. During recording, it would be perhaps better to use only the input signal as there would otherwise be a slight delay between the live signal and the playback signal. Using a small playback buffer or using low latency monitoring would help this situation considerably. HTH, slau On Jun 2, 2011, at 2:22 PM, Abdul D Kamara wrote: Hey Slau, So the idea is that some of these clips, which include sections of music and/or voice recording, would be at times overlapping the voice from the primary audio track. I will be following a pretty tight script, doing it live most of the way, so I think I might want to give the instrument track with the launchpad a go. Of course, I understand some of these explanations can be quite involved, so in advance, you have my gratitude. I have been able to set up the baby grand piano to work with my controller. I think I get how a fraction of this works. Expanding my library to accommodate my clips is the trick. On to the audio: 1. By signal feeding you mean that I am able to hear my voice via the microphone? If so, yes. 2. Link Timeline Edit Selection is checked. I don't think that I have manipulated any other defaults. So thus far, no luck. On 2 Jun 2011, at 19:13, Slau Halatyn wrote: Hey Abdul, OK, I have some time now to address your questions. First, let me say that you might only possibly need a trigger for specific audio clips if you're planning to do it in real time. I would bet that you're not planning to do the whole of each podcast episode live, without any edits. So, triggering sounds, per se, is probably completely unnecessary. If it's a live radio-style show then, yes, that would be appropriate. The overwhelming majority of podcasts are put together in pieces with segments recorded, edited and then output as a single mixed file. Normally, any kind of music or sound effects would be copied and pasted into a dedicated track and mixed along with the other material or sometimes even put into the same track as a stand-alone audio region in the midst of other audio regions—essentially as a link in a chain of various pieces of audio. So, I wouldn't worry about the virtual instrument track at this time. To address the audio questions, you seem to have followed the right steps in general. Let me ask a few other questions: 1. When you created the mono track and checked the routing, were you able to hear the signal feeding the microphone? 2. Make sure that link Timeline Edit Selection is checked under the Options menu. Did you change any other defaults? 3. When you stopped the transport, did you press Return to get back to the beginning of the session? BTW, there are two types of playback behavior as it pertains to the insertion point. With the insertion following the playback cursor, if you stop the playback by pressing the space bar, the insertion will stay at the stopped playback position. If insertion is not following playback, the insertion point will stay at the initial position and remain there while the playback cursor continues on playing the material. If you press the space bar in this mode, the transport main counter will instantly reset back to it's original position where you started playback. This is a matter of personal preference and is coincidentally found in the Preferences dialog under the Setups menu. Let's start with that for now. Let me know. Slau On Jun 2, 2011, at 6:46 AM, Abdul D Kamara wrote: Hey All, I'm new to the list. ...thought it would be good to introduce myself, as I already have a kabillion questions for you all. I'm trying to set up a Podcast. I'm running Pro Tools 8.0.5 with an MBox 2 as my interface. The basic template I need has a audio and instrument track, the former will be for voice recording via mic and the latter will be for
Re: Introduction and a few questions.
I don't think so. In step 4 Abdul says he armed the track and then in the Transport cluster he engaged the record function. I take that as he took the right steps. bTW, Abdul, you needn't use the transport window or cluster for engaging the transport. Command-space bar is the keyboard shortcut for putting the transport into record. HTH, slau On Jun 2, 2011, at 6:21 PM, Monkey Pusher wrote: It seems he may haver not armed, or record enabled the mono track he wants to record on. He only mention pressing the arm button in the transport cluster, but not the one on the track. You have have to record enable the track as well so Protools knows which track you want the recorded audio placed on. Hope this helps. Steve On 6/2/11, Slau Halatyn slauhala...@gmail.com wrote: Hey Abdul, OK, one thing I forgot to mention is the issue of input monitoring. Now, I'm not sure what the case is with LE systems but, with HD systems, one can switch between monitoring the input or the playback of a given record-enabled track. Option-k toggles between these two modes. It's under the Tracks menu. Again, I'm not sure what the case is with LE so you'll have to check. Now, if I remember correctly, with MBoxes, there was a particular knob that, when turned to the left, sent the input to the stereo out and when turned to the right, sent the recorded signal to the output. So, essentially, if it's somewhere in the middle, you'd get both. I would make sure that the knob is at least in the middle so you can hear playback. During recording, it would be perhaps better to use only the input signal as there would otherwise be a slight delay between the live signal and the playback signal. Using a small playback buffer or using low latency monitoring would help this situation considerably. HTH, slau On Jun 2, 2011, at 2:22 PM, Abdul D Kamara wrote: Hey Slau, So the idea is that some of these clips, which include sections of music and/or voice recording, would be at times overlapping the voice from the primary audio track. I will be following a pretty tight script, doing it live most of the way, so I think I might want to give the instrument track with the launchpad a go. Of course, I understand some of these explanations can be quite involved, so in advance, you have my gratitude. I have been able to set up the baby grand piano to work with my controller. I think I get how a fraction of this works. Expanding my library to accommodate my clips is the trick. On to the audio: 1. By signal feeding you mean that I am able to hear my voice via the microphone? If so, yes. 2. Link Timeline Edit Selection is checked. I don't think that I have manipulated any other defaults. So thus far, no luck. On 2 Jun 2011, at 19:13, Slau Halatyn wrote: Hey Abdul, OK, I have some time now to address your questions. First, let me say that you might only possibly need a trigger for specific audio clips if you're planning to do it in real time. I would bet that you're not planning to do the whole of each podcast episode live, without any edits. So, triggering sounds, per se, is probably completely unnecessary. If it's a live radio-style show then, yes, that would be appropriate. The overwhelming majority of podcasts are put together in pieces with segments recorded, edited and then output as a single mixed file. Normally, any kind of music or sound effects would be copied and pasted into a dedicated track and mixed along with the other material or sometimes even put into the same track as a stand-alone audio region in the midst of other audio regions—essentially as a link in a chain of various pieces of audio. So, I wouldn't worry about the virtual instrument track at this time. To address the audio questions, you seem to have followed the right steps in general. Let me ask a few other questions: 1. When you created the mono track and checked the routing, were you able to hear the signal feeding the microphone? 2. Make sure that link Timeline Edit Selection is checked under the Options menu. Did you change any other defaults? 3. When you stopped the transport, did you press Return to get back to the beginning of the session? BTW, there are two types of playback behavior as it pertains to the insertion point. With the insertion following the playback cursor, if you stop the playback by pressing the space bar, the insertion will stay at the stopped playback position. If insertion is not following playback, the insertion point will stay at the initial position and remain there while the playback cursor continues on playing the material. If you press the space bar in this mode, the transport main counter will instantly reset back to it's original position where you started playback. This is a matter of personal preference and is coincidentally found in the Preferences dialog under the Setups menu. Let's start with that for now. Let me know.
Re: Introduction and a few questions.
Hi Steve, I'm sorry if it wasn't clear, but I have done exactly that. No cigars. Any other suggestions? Push comes to shove, tomorrow I will pay a visit to some people who might be able to help me. Perhaps there some details I'm overlooking. Best, On 3 Jun 2011, at 00:21, Monkey Pusher wrote: It seems he may haver not armed, or record enabled the mono track he wants to record on. He only mention pressing the arm button in the transport cluster, but not the one on the track. You have have to record enable the track as well so Protools knows which track you want the recorded audio placed on. Hope this helps. Steve On 6/2/11, Slau Halatyn slauhala...@gmail.com wrote: Hey Abdul, OK, one thing I forgot to mention is the issue of input monitoring. Now, I'm not sure what the case is with LE systems but, with HD systems, one can switch between monitoring the input or the playback of a given record-enabled track. Option-k toggles between these two modes. It's under the Tracks menu. Again, I'm not sure what the case is with LE so you'll have to check. Now, if I remember correctly, with MBoxes, there was a particular knob that, when turned to the left, sent the input to the stereo out and when turned to the right, sent the recorded signal to the output. So, essentially, if it's somewhere in the middle, you'd get both. I would make sure that the knob is at least in the middle so you can hear playback. During recording, it would be perhaps better to use only the input signal as there would otherwise be a slight delay between the live signal and the playback signal. Using a small playback buffer or using low latency monitoring would help this situation considerably. HTH, slau On Jun 2, 2011, at 2:22 PM, Abdul D Kamara wrote: Hey Slau, So the idea is that some of these clips, which include sections of music and/or voice recording, would be at times overlapping the voice from the primary audio track. I will be following a pretty tight script, doing it live most of the way, so I think I might want to give the instrument track with the launchpad a go. Of course, I understand some of these explanations can be quite involved, so in advance, you have my gratitude. I have been able to set up the baby grand piano to work with my controller. I think I get how a fraction of this works. Expanding my library to accommodate my clips is the trick. On to the audio: 1. By signal feeding you mean that I am able to hear my voice via the microphone? If so, yes. 2. Link Timeline Edit Selection is checked. I don't think that I have manipulated any other defaults. So thus far, no luck. On 2 Jun 2011, at 19:13, Slau Halatyn wrote: Hey Abdul, OK, I have some time now to address your questions. First, let me say that you might only possibly need a trigger for specific audio clips if you're planning to do it in real time. I would bet that you're not planning to do the whole of each podcast episode live, without any edits. So, triggering sounds, per se, is probably completely unnecessary. If it's a live radio-style show then, yes, that would be appropriate. The overwhelming majority of podcasts are put together in pieces with segments recorded, edited and then output as a single mixed file. Normally, any kind of music or sound effects would be copied and pasted into a dedicated track and mixed along with the other material or sometimes even put into the same track as a stand-alone audio region in the midst of other audio regions—essentially as a link in a chain of various pieces of audio. So, I wouldn't worry about the virtual instrument track at this time. To address the audio questions, you seem to have followed the right steps in general. Let me ask a few other questions: 1. When you created the mono track and checked the routing, were you able to hear the signal feeding the microphone? 2. Make sure that link Timeline Edit Selection is checked under the Options menu. Did you change any other defaults? 3. When you stopped the transport, did you press Return to get back to the beginning of the session? BTW, there are two types of playback behavior as it pertains to the insertion point. With the insertion following the playback cursor, if you stop the playback by pressing the space bar, the insertion will stay at the stopped playback position. If insertion is not following playback, the insertion point will stay at the initial position and remain there while the playback cursor continues on playing the material. If you press the space bar in this mode, the transport main counter will instantly reset back to it's original position where you started playback. This is a matter of personal preference and is coincidentally found in the Preferences dialog under the Setups menu. Let's start with that for now. Let me know. Slau On Jun 2, 2011, at 6:46 AM, Abdul D Kamara wrote: Hey All, I'm new to the list.
Re: Introduction and a few questions.
Slau, thanks, this is really good to know. On 3 Jun 2011, at 00:26, Slau Halatyn wrote: I don't think so. In step 4 Abdul says he armed the track and then in the Transport cluster he engaged the record function. I take that as he took the right steps. bTW, Abdul, you needn't use the transport window or cluster for engaging the transport. Command-space bar is the keyboard shortcut for putting the transport into record. HTH, slau On Jun 2, 2011, at 6:21 PM, Monkey Pusher wrote: It seems he may haver not armed, or record enabled the mono track he wants to record on. He only mention pressing the arm button in the transport cluster, but not the one on the track. You have have to record enable the track as well so Protools knows which track you want the recorded audio placed on. Hope this helps. Steve On 6/2/11, Slau Halatyn slauhala...@gmail.com wrote: Hey Abdul, OK, one thing I forgot to mention is the issue of input monitoring. Now, I'm not sure what the case is with LE systems but, with HD systems, one can switch between monitoring the input or the playback of a given record-enabled track. Option-k toggles between these two modes. It's under the Tracks menu. Again, I'm not sure what the case is with LE so you'll have to check. Now, if I remember correctly, with MBoxes, there was a particular knob that, when turned to the left, sent the input to the stereo out and when turned to the right, sent the recorded signal to the output. So, essentially, if it's somewhere in the middle, you'd get both. I would make sure that the knob is at least in the middle so you can hear playback. During recording, it would be perhaps better to use only the input signal as there would otherwise be a slight delay between the live signal and the playback signal. Using a small playback buffer or using low latency monitoring would help this situation considerably. HTH, slau On Jun 2, 2011, at 2:22 PM, Abdul D Kamara wrote: Hey Slau, So the idea is that some of these clips, which include sections of music and/or voice recording, would be at times overlapping the voice from the primary audio track. I will be following a pretty tight script, doing it live most of the way, so I think I might want to give the instrument track with the launchpad a go. Of course, I understand some of these explanations can be quite involved, so in advance, you have my gratitude. I have been able to set up the baby grand piano to work with my controller. I think I get how a fraction of this works. Expanding my library to accommodate my clips is the trick. On to the audio: 1. By signal feeding you mean that I am able to hear my voice via the microphone? If so, yes. 2. Link Timeline Edit Selection is checked. I don't think that I have manipulated any other defaults. So thus far, no luck. On 2 Jun 2011, at 19:13, Slau Halatyn wrote: Hey Abdul, OK, I have some time now to address your questions. First, let me say that you might only possibly need a trigger for specific audio clips if you're planning to do it in real time. I would bet that you're not planning to do the whole of each podcast episode live, without any edits. So, triggering sounds, per se, is probably completely unnecessary. If it's a live radio-style show then, yes, that would be appropriate. The overwhelming majority of podcasts are put together in pieces with segments recorded, edited and then output as a single mixed file. Normally, any kind of music or sound effects would be copied and pasted into a dedicated track and mixed along with the other material or sometimes even put into the same track as a stand-alone audio region in the midst of other audio regions—essentially as a link in a chain of various pieces of audio. So, I wouldn't worry about the virtual instrument track at this time. To address the audio questions, you seem to have followed the right steps in general. Let me ask a few other questions: 1. When you created the mono track and checked the routing, were you able to hear the signal feeding the microphone? 2. Make sure that link Timeline Edit Selection is checked under the Options menu. Did you change any other defaults? 3. When you stopped the transport, did you press Return to get back to the beginning of the session? BTW, there are two types of playback behavior as it pertains to the insertion point. With the insertion following the playback cursor, if you stop the playback by pressing the space bar, the insertion will stay at the stopped playback position. If insertion is not following playback, the insertion point will stay at the initial position and remain there while the playback cursor continues on playing the material. If you press the space bar in this mode, the transport main counter will instantly reset back to it's original position where you started playback. This is a matter of personal preference and is coincidentally
Re: Introduction and a few questions.
Arg, I should have included this in the previous email as I also hate posting a whole lot of short messages in succession on a list. Slau, upon installing Pro Tools, I came across a dialog of which I cannot remember the full detail. The crux of it is that there are certain keyboard command conflicts with Pro Tools and the Finder and that I had to do something to turn off the shortcuts on the finder end. Does this sound familiar to you? e.g., As you may know, Command + Space normally gets you to spotlight. On 3 Jun 2011, at 00:26, Slau Halatyn wrote: I don't think so. In step 4 Abdul says he armed the track and then in the Transport cluster he engaged the record function. I take that as he took the right steps. bTW, Abdul, you needn't use the transport window or cluster for engaging the transport. Command-space bar is the keyboard shortcut for putting the transport into record. HTH, slau On Jun 2, 2011, at 6:21 PM, Monkey Pusher wrote: It seems he may haver not armed, or record enabled the mono track he wants to record on. He only mention pressing the arm button in the transport cluster, but not the one on the track. You have have to record enable the track as well so Protools knows which track you want the recorded audio placed on. Hope this helps. Steve On 6/2/11, Slau Halatyn slauhala...@gmail.com wrote: Hey Abdul, OK, one thing I forgot to mention is the issue of input monitoring. Now, I'm not sure what the case is with LE systems but, with HD systems, one can switch between monitoring the input or the playback of a given record-enabled track. Option-k toggles between these two modes. It's under the Tracks menu. Again, I'm not sure what the case is with LE so you'll have to check. Now, if I remember correctly, with MBoxes, there was a particular knob that, when turned to the left, sent the input to the stereo out and when turned to the right, sent the recorded signal to the output. So, essentially, if it's somewhere in the middle, you'd get both. I would make sure that the knob is at least in the middle so you can hear playback. During recording, it would be perhaps better to use only the input signal as there would otherwise be a slight delay between the live signal and the playback signal. Using a small playback buffer or using low latency monitoring would help this situation considerably. HTH, slau On Jun 2, 2011, at 2:22 PM, Abdul D Kamara wrote: Hey Slau, So the idea is that some of these clips, which include sections of music and/or voice recording, would be at times overlapping the voice from the primary audio track. I will be following a pretty tight script, doing it live most of the way, so I think I might want to give the instrument track with the launchpad a go. Of course, I understand some of these explanations can be quite involved, so in advance, you have my gratitude. I have been able to set up the baby grand piano to work with my controller. I think I get how a fraction of this works. Expanding my library to accommodate my clips is the trick. On to the audio: 1. By signal feeding you mean that I am able to hear my voice via the microphone? If so, yes. 2. Link Timeline Edit Selection is checked. I don't think that I have manipulated any other defaults. So thus far, no luck. On 2 Jun 2011, at 19:13, Slau Halatyn wrote: Hey Abdul, OK, I have some time now to address your questions. First, let me say that you might only possibly need a trigger for specific audio clips if you're planning to do it in real time. I would bet that you're not planning to do the whole of each podcast episode live, without any edits. So, triggering sounds, per se, is probably completely unnecessary. If it's a live radio-style show then, yes, that would be appropriate. The overwhelming majority of podcasts are put together in pieces with segments recorded, edited and then output as a single mixed file. Normally, any kind of music or sound effects would be copied and pasted into a dedicated track and mixed along with the other material or sometimes even put into the same track as a stand-alone audio region in the midst of other audio regions—essentially as a link in a chain of various pieces of audio. So, I wouldn't worry about the virtual instrument track at this time. To address the audio questions, you seem to have followed the right steps in general. Let me ask a few other questions: 1. When you created the mono track and checked the routing, were you able to hear the signal feeding the microphone? 2. Make sure that link Timeline Edit Selection is checked under the Options menu. Did you change any other defaults? 3. When you stopped the transport, did you press Return to get back to the beginning of the session? BTW, there are two types of playback behavior as it pertains to the insertion point. With the insertion following the playback cursor, if you stop the
Re: Introduction and a few questions.
Hey Folks, thanks to Slau, the recording problem is fixed. It appears that using the key commands work better than trying to directly manipulate controls in the transport cluster. On 3 Jun 2011, at 00:26, Slau Halatyn wrote: I don't think so. In step 4 Abdul says he armed the track and then in the Transport cluster he engaged the record function. I take that as he took the right steps. bTW, Abdul, you needn't use the transport window or cluster for engaging the transport. Command-space bar is the keyboard shortcut for putting the transport into record. HTH, slau On Jun 2, 2011, at 6:21 PM, Monkey Pusher wrote: It seems he may haver not armed, or record enabled the mono track he wants to record on. He only mention pressing the arm button in the transport cluster, but not the one on the track. You have have to record enable the track as well so Protools knows which track you want the recorded audio placed on. Hope this helps. Steve On 6/2/11, Slau Halatyn slauhala...@gmail.com wrote: Hey Abdul, OK, one thing I forgot to mention is the issue of input monitoring. Now, I'm not sure what the case is with LE systems but, with HD systems, one can switch between monitoring the input or the playback of a given record-enabled track. Option-k toggles between these two modes. It's under the Tracks menu. Again, I'm not sure what the case is with LE so you'll have to check. Now, if I remember correctly, with MBoxes, there was a particular knob that, when turned to the left, sent the input to the stereo out and when turned to the right, sent the recorded signal to the output. So, essentially, if it's somewhere in the middle, you'd get both. I would make sure that the knob is at least in the middle so you can hear playback. During recording, it would be perhaps better to use only the input signal as there would otherwise be a slight delay between the live signal and the playback signal. Using a small playback buffer or using low latency monitoring would help this situation considerably. HTH, slau On Jun 2, 2011, at 2:22 PM, Abdul D Kamara wrote: Hey Slau, So the idea is that some of these clips, which include sections of music and/or voice recording, would be at times overlapping the voice from the primary audio track. I will be following a pretty tight script, doing it live most of the way, so I think I might want to give the instrument track with the launchpad a go. Of course, I understand some of these explanations can be quite involved, so in advance, you have my gratitude. I have been able to set up the baby grand piano to work with my controller. I think I get how a fraction of this works. Expanding my library to accommodate my clips is the trick. On to the audio: 1. By signal feeding you mean that I am able to hear my voice via the microphone? If so, yes. 2. Link Timeline Edit Selection is checked. I don't think that I have manipulated any other defaults. So thus far, no luck. On 2 Jun 2011, at 19:13, Slau Halatyn wrote: Hey Abdul, OK, I have some time now to address your questions. First, let me say that you might only possibly need a trigger for specific audio clips if you're planning to do it in real time. I would bet that you're not planning to do the whole of each podcast episode live, without any edits. So, triggering sounds, per se, is probably completely unnecessary. If it's a live radio-style show then, yes, that would be appropriate. The overwhelming majority of podcasts are put together in pieces with segments recorded, edited and then output as a single mixed file. Normally, any kind of music or sound effects would be copied and pasted into a dedicated track and mixed along with the other material or sometimes even put into the same track as a stand-alone audio region in the midst of other audio regions—essentially as a link in a chain of various pieces of audio. So, I wouldn't worry about the virtual instrument track at this time. To address the audio questions, you seem to have followed the right steps in general. Let me ask a few other questions: 1. When you created the mono track and checked the routing, were you able to hear the signal feeding the microphone? 2. Make sure that link Timeline Edit Selection is checked under the Options menu. Did you change any other defaults? 3. When you stopped the transport, did you press Return to get back to the beginning of the session? BTW, there are two types of playback behavior as it pertains to the insertion point. With the insertion following the playback cursor, if you stop the playback by pressing the space bar, the insertion will stay at the stopped playback position. If insertion is not following playback, the insertion point will stay at the initial position and remain there while the playback cursor continues on playing the material. If you press the space bar in this mode, the transport main counter
Re: Introduction and a few questions.
Hey Abdul, Yes, that's one of the things you need to turn off in the spotlight preference pane. I don't recall what the other one is but, another important one is, make sure to turn off Spotlight indexing for your external drive to which you are recording. You are recording to an external drive, yes? Anyway, that's important. Slau On Jun 2, 2011, at 6:47 PM, Abdul D Kamara wrote: Arg, I should have included this in the previous email as I also hate posting a whole lot of short messages in succession on a list. Slau, upon installing Pro Tools, I came across a dialog of which I cannot remember the full detail. The crux of it is that there are certain keyboard command conflicts with Pro Tools and the Finder and that I had to do something to turn off the shortcuts on the finder end. Does this sound familiar to you? e.g., As you may know, Command + Space normally gets you to spotlight. On 3 Jun 2011, at 00:26, Slau Halatyn wrote: I don't think so. In step 4 Abdul says he armed the track and then in the Transport cluster he engaged the record function. I take that as he took the right steps. bTW, Abdul, you needn't use the transport window or cluster for engaging the transport. Command-space bar is the keyboard shortcut for putting the transport into record. HTH, slau On Jun 2, 2011, at 6:21 PM, Monkey Pusher wrote: It seems he may haver not armed, or record enabled the mono track he wants to record on. He only mention pressing the arm button in the transport cluster, but not the one on the track. You have have to record enable the track as well so Protools knows which track you want the recorded audio placed on. Hope this helps. Steve On 6/2/11, Slau Halatyn slauhala...@gmail.com wrote: Hey Abdul, OK, one thing I forgot to mention is the issue of input monitoring. Now, I'm not sure what the case is with LE systems but, with HD systems, one can switch between monitoring the input or the playback of a given record-enabled track. Option-k toggles between these two modes. It's under the Tracks menu. Again, I'm not sure what the case is with LE so you'll have to check. Now, if I remember correctly, with MBoxes, there was a particular knob that, when turned to the left, sent the input to the stereo out and when turned to the right, sent the recorded signal to the output. So, essentially, if it's somewhere in the middle, you'd get both. I would make sure that the knob is at least in the middle so you can hear playback. During recording, it would be perhaps better to use only the input signal as there would otherwise be a slight delay between the live signal and the playback signal. Using a small playback buffer or using low latency monitoring would help this situation considerably. HTH, slau On Jun 2, 2011, at 2:22 PM, Abdul D Kamara wrote: Hey Slau, So the idea is that some of these clips, which include sections of music and/or voice recording, would be at times overlapping the voice from the primary audio track. I will be following a pretty tight script, doing it live most of the way, so I think I might want to give the instrument track with the launchpad a go. Of course, I understand some of these explanations can be quite involved, so in advance, you have my gratitude. I have been able to set up the baby grand piano to work with my controller. I think I get how a fraction of this works. Expanding my library to accommodate my clips is the trick. On to the audio: 1. By signal feeding you mean that I am able to hear my voice via the microphone? If so, yes. 2. Link Timeline Edit Selection is checked. I don't think that I have manipulated any other defaults. So thus far, no luck. On 2 Jun 2011, at 19:13, Slau Halatyn wrote: Hey Abdul, OK, I have some time now to address your questions. First, let me say that you might only possibly need a trigger for specific audio clips if you're planning to do it in real time. I would bet that you're not planning to do the whole of each podcast episode live, without any edits. So, triggering sounds, per se, is probably completely unnecessary. If it's a live radio-style show then, yes, that would be appropriate. The overwhelming majority of podcasts are put together in pieces with segments recorded, edited and then output as a single mixed file. Normally, any kind of music or sound effects would be copied and pasted into a dedicated track and mixed along with the other material or sometimes even put into the same track as a stand-alone audio region in the midst of other audio regions—essentially as a link in a chain of various pieces of audio. So, I wouldn't worry about the virtual instrument track at this time. To address the audio questions, you seem to have followed the right steps in general. Let me ask a few other questions: 1. When you created the mono track and checked the routing, were you able to hear the signal
Re: Introduction and a few questions.
Hey Abdul, Glad it worked. I'm thinking that you probably armed the Record button in the transport but never actually engaged the transport by pressing the Play button. Well, the Command-space bar shortcut will solve that. There's also another couple of options for engaging the transport. One is with a particular f-key (I don't recall which one because I never use it) and num pad 3 and then space bar. Again, I never use that but it's just another option. Glad you're rolling, so to speak ;) Slau On Jun 2, 2011, at 7:00 PM, Abdul D Kamara wrote: Hey Folks, thanks to Slau, the recording problem is fixed. It appears that using the key commands work better than trying to directly manipulate controls in the transport cluster. On 3 Jun 2011, at 00:26, Slau Halatyn wrote: I don't think so. In step 4 Abdul says he armed the track and then in the Transport cluster he engaged the record function. I take that as he took the right steps. bTW, Abdul, you needn't use the transport window or cluster for engaging the transport. Command-space bar is the keyboard shortcut for putting the transport into record. HTH, slau On Jun 2, 2011, at 6:21 PM, Monkey Pusher wrote: It seems he may haver not armed, or record enabled the mono track he wants to record on. He only mention pressing the arm button in the transport cluster, but not the one on the track. You have have to record enable the track as well so Protools knows which track you want the recorded audio placed on. Hope this helps. Steve On 6/2/11, Slau Halatyn slauhala...@gmail.com wrote: Hey Abdul, OK, one thing I forgot to mention is the issue of input monitoring. Now, I'm not sure what the case is with LE systems but, with HD systems, one can switch between monitoring the input or the playback of a given record-enabled track. Option-k toggles between these two modes. It's under the Tracks menu. Again, I'm not sure what the case is with LE so you'll have to check. Now, if I remember correctly, with MBoxes, there was a particular knob that, when turned to the left, sent the input to the stereo out and when turned to the right, sent the recorded signal to the output. So, essentially, if it's somewhere in the middle, you'd get both. I would make sure that the knob is at least in the middle so you can hear playback. During recording, it would be perhaps better to use only the input signal as there would otherwise be a slight delay between the live signal and the playback signal. Using a small playback buffer or using low latency monitoring would help this situation considerably. HTH, slau On Jun 2, 2011, at 2:22 PM, Abdul D Kamara wrote: Hey Slau, So the idea is that some of these clips, which include sections of music and/or voice recording, would be at times overlapping the voice from the primary audio track. I will be following a pretty tight script, doing it live most of the way, so I think I might want to give the instrument track with the launchpad a go. Of course, I understand some of these explanations can be quite involved, so in advance, you have my gratitude. I have been able to set up the baby grand piano to work with my controller. I think I get how a fraction of this works. Expanding my library to accommodate my clips is the trick. On to the audio: 1. By signal feeding you mean that I am able to hear my voice via the microphone? If so, yes. 2. Link Timeline Edit Selection is checked. I don't think that I have manipulated any other defaults. So thus far, no luck. On 2 Jun 2011, at 19:13, Slau Halatyn wrote: Hey Abdul, OK, I have some time now to address your questions. First, let me say that you might only possibly need a trigger for specific audio clips if you're planning to do it in real time. I would bet that you're not planning to do the whole of each podcast episode live, without any edits. So, triggering sounds, per se, is probably completely unnecessary. If it's a live radio-style show then, yes, that would be appropriate. The overwhelming majority of podcasts are put together in pieces with segments recorded, edited and then output as a single mixed file. Normally, any kind of music or sound effects would be copied and pasted into a dedicated track and mixed along with the other material or sometimes even put into the same track as a stand-alone audio region in the midst of other audio regions—essentially as a link in a chain of various pieces of audio. So, I wouldn't worry about the virtual instrument track at this time. To address the audio questions, you seem to have followed the right steps in general. Let me ask a few other questions: 1. When you created the mono track and checked the routing, were you able to hear the signal feeding the microphone? 2. Make sure that link Timeline Edit Selection is checked under the Options menu. Did you change any other defaults? 3. When you stopped the
Re: Introduction and a few questions.
Yeah, I think you are right about the play button. I'm going to bed now, and I will be taking with me the 36 page document on Pro Tools short cuts. Oh, and if you happen to remember the other shortcuts that need to be disabled, please let me know, I have already disabled the one for spotlight... I am not using an external drive right now, though I will. I get the sense that this is critical, Beyond the issue of space, why is it so? Thanks again, Abdul On 3 Jun 2011, at 01:09, Slau Halatyn wrote: Hey Abdul, Glad it worked. I'm thinking that you probably armed the Record button in the transport but never actually engaged the transport by pressing the Play button. Well, the Command-space bar shortcut will solve that. There's also another couple of options for engaging the transport. One is with a particular f-key (I don't recall which one because I never use it) and num pad 3 and then space bar. Again, I never use that but it's just another option. Glad you're rolling, so to speak ;) Slau On Jun 2, 2011, at 7:00 PM, Abdul D Kamara wrote: Hey Folks, thanks to Slau, the recording problem is fixed. It appears that using the key commands work better than trying to directly manipulate controls in the transport cluster. On 3 Jun 2011, at 00:26, Slau Halatyn wrote: I don't think so. In step 4 Abdul says he armed the track and then in the Transport cluster he engaged the record function. I take that as he took the right steps. bTW, Abdul, you needn't use the transport window or cluster for engaging the transport. Command-space bar is the keyboard shortcut for putting the transport into record. HTH, slau On Jun 2, 2011, at 6:21 PM, Monkey Pusher wrote: It seems he may haver not armed, or record enabled the mono track he wants to record on. He only mention pressing the arm button in the transport cluster, but not the one on the track. You have have to record enable the track as well so Protools knows which track you want the recorded audio placed on. Hope this helps. Steve On 6/2/11, Slau Halatyn slauhala...@gmail.com wrote: Hey Abdul, OK, one thing I forgot to mention is the issue of input monitoring. Now, I'm not sure what the case is with LE systems but, with HD systems, one can switch between monitoring the input or the playback of a given record-enabled track. Option-k toggles between these two modes. It's under the Tracks menu. Again, I'm not sure what the case is with LE so you'll have to check. Now, if I remember correctly, with MBoxes, there was a particular knob that, when turned to the left, sent the input to the stereo out and when turned to the right, sent the recorded signal to the output. So, essentially, if it's somewhere in the middle, you'd get both. I would make sure that the knob is at least in the middle so you can hear playback. During recording, it would be perhaps better to use only the input signal as there would otherwise be a slight delay between the live signal and the playback signal. Using a small playback buffer or using low latency monitoring would help this situation considerably. HTH, slau On Jun 2, 2011, at 2:22 PM, Abdul D Kamara wrote: Hey Slau, So the idea is that some of these clips, which include sections of music and/or voice recording, would be at times overlapping the voice from the primary audio track. I will be following a pretty tight script, doing it live most of the way, so I think I might want to give the instrument track with the launchpad a go. Of course, I understand some of these explanations can be quite involved, so in advance, you have my gratitude. I have been able to set up the baby grand piano to work with my controller. I think I get how a fraction of this works. Expanding my library to accommodate my clips is the trick. On to the audio: 1. By signal feeding you mean that I am able to hear my voice via the microphone? If so, yes. 2. Link Timeline Edit Selection is checked. I don't think that I have manipulated any other defaults. So thus far, no luck. On 2 Jun 2011, at 19:13, Slau Halatyn wrote: Hey Abdul, OK, I have some time now to address your questions. First, let me say that you might only possibly need a trigger for specific audio clips if you're planning to do it in real time. I would bet that you're not planning to do the whole of each podcast episode live, without any edits. So, triggering sounds, per se, is probably completely unnecessary. If it's a live radio-style show then, yes, that would be appropriate. The overwhelming majority of podcasts are put together in pieces with segments recorded, edited and then output as a single mixed file. Normally, any kind of music or sound effects would be copied and pasted into a dedicated track and mixed along with the other material or sometimes even put into the same track as a stand-alone audio region in the midst of other audio
Re: Introduction and a few questions.
Hi Abdul, The first thing you'll probably want to read is your Introduction to MBox or Getting Started with MBox—whatever they call it these days. That'll explain the exact steps you need to take in terms of setting up your system correctly. Regarding drives, in short, that's just how it is. All serious workstations, be it audio or video, most often require the use of a dedicated drive that is separate from the boot drive. You can probably get away with recording one or two tracks for short periods of time but it's absolutely highly recommended to use a dedicated external FireWire drive. bTW, OWC makes a nice bus-powered fireWire drive that is 7200 rpm and costs around $159. Come to think of it, I recall you're overseas but, still, it might be nice to find something bus powered but, more importantly, 7200 rpm for sure. Cheers, Slau On Jun 2, 2011, at 7:22 PM, Abdul D Kamara wrote: Yeah, I think you are right about the play button. I'm going to bed now, and I will be taking with me the 36 page document on Pro Tools short cuts. Oh, and if you happen to remember the other shortcuts that need to be disabled, please let me know, I have already disabled the one for spotlight... I am not using an external drive right now, though I will. I get the sense that this is critical, Beyond the issue of space, why is it so? Thanks again, Abdul On 3 Jun 2011, at 01:09, Slau Halatyn wrote: Hey Abdul, Glad it worked. I'm thinking that you probably armed the Record button in the transport but never actually engaged the transport by pressing the Play button. Well, the Command-space bar shortcut will solve that. There's also another couple of options for engaging the transport. One is with a particular f-key (I don't recall which one because I never use it) and num pad 3 and then space bar. Again, I never use that but it's just another option. Glad you're rolling, so to speak ;) Slau On Jun 2, 2011, at 7:00 PM, Abdul D Kamara wrote: Hey Folks, thanks to Slau, the recording problem is fixed. It appears that using the key commands work better than trying to directly manipulate controls in the transport cluster. On 3 Jun 2011, at 00:26, Slau Halatyn wrote: I don't think so. In step 4 Abdul says he armed the track and then in the Transport cluster he engaged the record function. I take that as he took the right steps. bTW, Abdul, you needn't use the transport window or cluster for engaging the transport. Command-space bar is the keyboard shortcut for putting the transport into record. HTH, slau On Jun 2, 2011, at 6:21 PM, Monkey Pusher wrote: It seems he may haver not armed, or record enabled the mono track he wants to record on. He only mention pressing the arm button in the transport cluster, but not the one on the track. You have have to record enable the track as well so Protools knows which track you want the recorded audio placed on. Hope this helps. Steve On 6/2/11, Slau Halatyn slauhala...@gmail.com wrote: Hey Abdul, OK, one thing I forgot to mention is the issue of input monitoring. Now, I'm not sure what the case is with LE systems but, with HD systems, one can switch between monitoring the input or the playback of a given record-enabled track. Option-k toggles between these two modes. It's under the Tracks menu. Again, I'm not sure what the case is with LE so you'll have to check. Now, if I remember correctly, with MBoxes, there was a particular knob that, when turned to the left, sent the input to the stereo out and when turned to the right, sent the recorded signal to the output. So, essentially, if it's somewhere in the middle, you'd get both. I would make sure that the knob is at least in the middle so you can hear playback. During recording, it would be perhaps better to use only the input signal as there would otherwise be a slight delay between the live signal and the playback signal. Using a small playback buffer or using low latency monitoring would help this situation considerably. HTH, slau On Jun 2, 2011, at 2:22 PM, Abdul D Kamara wrote: Hey Slau, So the idea is that some of these clips, which include sections of music and/or voice recording, would be at times overlapping the voice from the primary audio track. I will be following a pretty tight script, doing it live most of the way, so I think I might want to give the instrument track with the launchpad a go. Of course, I understand some of these explanations can be quite involved, so in advance, you have my gratitude. I have been able to set up the baby grand piano to work with my controller. I think I get how a fraction of this works. Expanding my library to accommodate my clips is the trick. On to the audio: 1. By signal feeding you mean that I am able to hear my voice via the microphone? If so, yes. 2. Link Timeline Edit Selection is checked. I don't think that I
Re: Introduction and a few questions.
Sorry for my mistake earlier, not sure how i missed that he did mentione that he armed the track. If i may throw another suggestion out there, OWC i believe or is it nu tech or some other company, makes an internal drive caddy for mac books. U can take out your cd rom drive and slide an a second internal HD in the slot with this caddy. Great so you can have a second drive for Pro Tools, and all you will have to bring is your laptop and iLock and some headphones, if mixing or editing. Just another thought. However you may want to keep your power adapter handy as running two intanal HD's will shorten battery life noticeably. On 6/2/11, Slau Halatyn slauhala...@gmail.com wrote: Hi Abdul, The first thing you'll probably want to read is your Introduction to MBox or Getting Started with MBox—whatever they call it these days. That'll explain the exact steps you need to take in terms of setting up your system correctly. Regarding drives, in short, that's just how it is. All serious workstations, be it audio or video, most often require the use of a dedicated drive that is separate from the boot drive. You can probably get away with recording one or two tracks for short periods of time but it's absolutely highly recommended to use a dedicated external FireWire drive. bTW, OWC makes a nice bus-powered fireWire drive that is 7200 rpm and costs around $159. Come to think of it, I recall you're overseas but, still, it might be nice to find something bus powered but, more importantly, 7200 rpm for sure. Cheers, Slau On Jun 2, 2011, at 7:22 PM, Abdul D Kamara wrote: Yeah, I think you are right about the play button. I'm going to bed now, and I will be taking with me the 36 page document on Pro Tools short cuts. Oh, and if you happen to remember the other shortcuts that need to be disabled, please let me know, I have already disabled the one for spotlight... I am not using an external drive right now, though I will. I get the sense that this is critical, Beyond the issue of space, why is it so? Thanks again, Abdul On 3 Jun 2011, at 01:09, Slau Halatyn wrote: Hey Abdul, Glad it worked. I'm thinking that you probably armed the Record button in the transport but never actually engaged the transport by pressing the Play button. Well, the Command-space bar shortcut will solve that. There's also another couple of options for engaging the transport. One is with a particular f-key (I don't recall which one because I never use it) and num pad 3 and then space bar. Again, I never use that but it's just another option. Glad you're rolling, so to speak ;) Slau On Jun 2, 2011, at 7:00 PM, Abdul D Kamara wrote: Hey Folks, thanks to Slau, the recording problem is fixed. It appears that using the key commands work better than trying to directly manipulate controls in the transport cluster. On 3 Jun 2011, at 00:26, Slau Halatyn wrote: I don't think so. In step 4 Abdul says he armed the track and then in the Transport cluster he engaged the record function. I take that as he took the right steps. bTW, Abdul, you needn't use the transport window or cluster for engaging the transport. Command-space bar is the keyboard shortcut for putting the transport into record. HTH, slau On Jun 2, 2011, at 6:21 PM, Monkey Pusher wrote: It seems he may haver not armed, or record enabled the mono track he wants to record on. He only mention pressing the arm button in the transport cluster, but not the one on the track. You have have to record enable the track as well so Protools knows which track you want the recorded audio placed on. Hope this helps. Steve On 6/2/11, Slau Halatyn slauhala...@gmail.com wrote: Hey Abdul, OK, one thing I forgot to mention is the issue of input monitoring. Now, I'm not sure what the case is with LE systems but, with HD systems, one can switch between monitoring the input or the playback of a given record-enabled track. Option-k toggles between these two modes. It's under the Tracks menu. Again, I'm not sure what the case is with LE so you'll have to check. Now, if I remember correctly, with MBoxes, there was a particular knob that, when turned to the left, sent the input to the stereo out and when turned to the right, sent the recorded signal to the output. So, essentially, if it's somewhere in the middle, you'd get both. I would make sure that the knob is at least in the middle so you can hear playback. During recording, it would be perhaps better to use only the input signal as there would otherwise be a slight delay between the live signal and the playback signal. Using a small playback buffer or using low latency monitoring would help this situation considerably. HTH, slau On Jun 2, 2011, at 2:22 PM, Abdul D Kamara wrote: Hey Slau, So the idea is that some of these clips, which include sections of music and/or voice recording, would be at times overlapping the voice from the primary audio track.
Re: Introduction and a few questions.
Hey all On Jun 2, 2011, at 7:09 PM, Slau Halatyn wrote: Hey Abdul, Glad it worked. I'm thinking that you probably armed the Record button in the transport but never actually engaged the transport by pressing the Play button. Well, the Command-space bar shortcut will solve that. There's also another couple of options for engaging the transport. One is with a particular f-key (I don't recall which one because I never use it) and num pad 3 and then space bar. Again, I never use that but it's just another option. Just to clarify the number 3 on the numpad starts the transport in record mode so you don't need to hit the space bar. At least it does over here. --FC
Re: Introduction and a few questions.
Hello Abdul On Jun 2, 2011, at 7:22 PM, Abdul D Kamara wrote: Yeah, I think you are right about the play button. I'm going to bed now, and I will be taking with me the 36 page document on Pro Tools short cuts. Oh, and if you happen to remember the other shortcuts that need to be disabled, please let me know, I have already disabled the one for spotlight... Command shift question for help should also be disabled. There may be a few more. HTH --FC
Re: Introduction and a few questions.
I've heard of folks doing that modification and it does sound convenient for the sake of traveling light for remote stuff. Slau On Jun 2, 2011, at 9:08 PM, Monkey Pusher wrote: Sorry for my mistake earlier, not sure how i missed that he did mentione that he armed the track. If i may throw another suggestion out there, OWC i believe or is it nu tech or some other company, makes an internal drive caddy for mac books. U can take out your cd rom drive and slide an a second internal HD in the slot with this caddy. Great so you can have a second drive for Pro Tools, and all you will have to bring is your laptop and iLock and some headphones, if mixing or editing. Just another thought. However you may want to keep your power adapter handy as running two intanal HD's will shorten battery life noticeably. On 6/2/11, Slau Halatyn slauhala...@gmail.com wrote: Hi Abdul, The first thing you'll probably want to read is your Introduction to MBox or Getting Started with MBox—whatever they call it these days. That'll explain the exact steps you need to take in terms of setting up your system correctly. Regarding drives, in short, that's just how it is. All serious workstations, be it audio or video, most often require the use of a dedicated drive that is separate from the boot drive. You can probably get away with recording one or two tracks for short periods of time but it's absolutely highly recommended to use a dedicated external FireWire drive. bTW, OWC makes a nice bus-powered fireWire drive that is 7200 rpm and costs around $159. Come to think of it, I recall you're overseas but, still, it might be nice to find something bus powered but, more importantly, 7200 rpm for sure. Cheers, Slau On Jun 2, 2011, at 7:22 PM, Abdul D Kamara wrote: Yeah, I think you are right about the play button. I'm going to bed now, and I will be taking with me the 36 page document on Pro Tools short cuts. Oh, and if you happen to remember the other shortcuts that need to be disabled, please let me know, I have already disabled the one for spotlight... I am not using an external drive right now, though I will. I get the sense that this is critical, Beyond the issue of space, why is it so? Thanks again, Abdul On 3 Jun 2011, at 01:09, Slau Halatyn wrote: Hey Abdul, Glad it worked. I'm thinking that you probably armed the Record button in the transport but never actually engaged the transport by pressing the Play button. Well, the Command-space bar shortcut will solve that. There's also another couple of options for engaging the transport. One is with a particular f-key (I don't recall which one because I never use it) and num pad 3 and then space bar. Again, I never use that but it's just another option. Glad you're rolling, so to speak ;) Slau On Jun 2, 2011, at 7:00 PM, Abdul D Kamara wrote: Hey Folks, thanks to Slau, the recording problem is fixed. It appears that using the key commands work better than trying to directly manipulate controls in the transport cluster. On 3 Jun 2011, at 00:26, Slau Halatyn wrote: I don't think so. In step 4 Abdul says he armed the track and then in the Transport cluster he engaged the record function. I take that as he took the right steps. bTW, Abdul, you needn't use the transport window or cluster for engaging the transport. Command-space bar is the keyboard shortcut for putting the transport into record. HTH, slau On Jun 2, 2011, at 6:21 PM, Monkey Pusher wrote: It seems he may haver not armed, or record enabled the mono track he wants to record on. He only mention pressing the arm button in the transport cluster, but not the one on the track. You have have to record enable the track as well so Protools knows which track you want the recorded audio placed on. Hope this helps. Steve On 6/2/11, Slau Halatyn slauhala...@gmail.com wrote: Hey Abdul, OK, one thing I forgot to mention is the issue of input monitoring. Now, I'm not sure what the case is with LE systems but, with HD systems, one can switch between monitoring the input or the playback of a given record-enabled track. Option-k toggles between these two modes. It's under the Tracks menu. Again, I'm not sure what the case is with LE so you'll have to check. Now, if I remember correctly, with MBoxes, there was a particular knob that, when turned to the left, sent the input to the stereo out and when turned to the right, sent the recorded signal to the output. So, essentially, if it's somewhere in the middle, you'd get both. I would make sure that the knob is at least in the middle so you can hear playback. During recording, it would be perhaps better to use only the input signal as there would otherwise be a slight delay between the live signal and the playback signal. Using a small playback buffer or using low latency monitoring would help this situation considerably. HTH, slau On Jun 2,
Re: Introduction and a few questions.
From memory, F12 was another one that Avid recommend you disable. It's originally assigned to bring up Dashboard so I can't say I've missed it, but I also can't say I use it in PT either. It's an alternative to using Command+Space to start recording. Likely not a deal breaker, just adding it to the list. Hth Scott On 6/3/11, Abdul D Kamara abduldkam...@googlemail.com wrote: Yeah, I think you are right about the play button. I'm going to bed now, and I will be taking with me the 36 page document on Pro Tools short cuts. Oh, and if you happen to remember the other shortcuts that need to be disabled, please let me know, I have already disabled the one for spotlight... I am not using an external drive right now, though I will. I get the sense that this is critical, Beyond the issue of space, why is it so? Thanks again, Abdul On 3 Jun 2011, at 01:09, Slau Halatyn wrote: Hey Abdul, Glad it worked. I'm thinking that you probably armed the Record button in the transport but never actually engaged the transport by pressing the Play button. Well, the Command-space bar shortcut will solve that. There's also another couple of options for engaging the transport. One is with a particular f-key (I don't recall which one because I never use it) and num pad 3 and then space bar. Again, I never use that but it's just another option. Glad you're rolling, so to speak ;) Slau On Jun 2, 2011, at 7:00 PM, Abdul D Kamara wrote: Hey Folks, thanks to Slau, the recording problem is fixed. It appears that using the key commands work better than trying to directly manipulate controls in the transport cluster. On 3 Jun 2011, at 00:26, Slau Halatyn wrote: I don't think so. In step 4 Abdul says he armed the track and then in the Transport cluster he engaged the record function. I take that as he took the right steps. bTW, Abdul, you needn't use the transport window or cluster for engaging the transport. Command-space bar is the keyboard shortcut for putting the transport into record. HTH, slau On Jun 2, 2011, at 6:21 PM, Monkey Pusher wrote: It seems he may haver not armed, or record enabled the mono track he wants to record on. He only mention pressing the arm button in the transport cluster, but not the one on the track. You have have to record enable the track as well so Protools knows which track you want the recorded audio placed on. Hope this helps. Steve On 6/2/11, Slau Halatyn slauhala...@gmail.com wrote: Hey Abdul, OK, one thing I forgot to mention is the issue of input monitoring. Now, I'm not sure what the case is with LE systems but, with HD systems, one can switch between monitoring the input or the playback of a given record-enabled track. Option-k toggles between these two modes. It's under the Tracks menu. Again, I'm not sure what the case is with LE so you'll have to check. Now, if I remember correctly, with MBoxes, there was a particular knob that, when turned to the left, sent the input to the stereo out and when turned to the right, sent the recorded signal to the output. So, essentially, if it's somewhere in the middle, you'd get both. I would make sure that the knob is at least in the middle so you can hear playback. During recording, it would be perhaps better to use only the input signal as there would otherwise be a slight delay between the live signal and the playback signal. Using a small playback buffer or using low latency monitoring would help this situation considerably. HTH, slau On Jun 2, 2011, at 2:22 PM, Abdul D Kamara wrote: Hey Slau, So the idea is that some of these clips, which include sections of music and/or voice recording, would be at times overlapping the voice from the primary audio track. I will be following a pretty tight script, doing it live most of the way, so I think I might want to give the instrument track with the launchpad a go. Of course, I understand some of these explanations can be quite involved, so in advance, you have my gratitude. I have been able to set up the baby grand piano to work with my controller. I think I get how a fraction of this works. Expanding my library to accommodate my clips is the trick. On to the audio: 1. By signal feeding you mean that I am able to hear my voice via the microphone? If so, yes. 2. Link Timeline Edit Selection is checked. I don't think that I have manipulated any other defaults. So thus far, no luck. On 2 Jun 2011, at 19:13, Slau Halatyn wrote: Hey Abdul, OK, I have some time now to address your questions. First, let me say that you might only possibly need a trigger for specific audio clips if you're planning to do it in real time. I would bet that you're not planning to do the whole of each podcast episode live, without any edits. So, triggering sounds, per se, is probably completely unnecessary. If it's a live radio-style show then, yes, that would be appropriate. The overwhelming
