Re: protools, midi and VoiceOver
Vincenzo, it would be so much easier if you had a real MIDI controller. You spent hundreds of dollars on Pro Tools. SPending $150 for a cheap controller is not much by comparison. You might seriously wish to spend some time with an app like GarageBand. GarageBand, particularly with VoxKeys, is an easy way to get started with recording on the Mac with a low technical barrier. Bryan On Feb 15, 2011, at 9:03 AM, Vincenzo Rubano wrote: Hi guys, finally I am beginning to understand how protools works..It's great! :-) Well, but now I need your help... I would like to record some midi events, using the virtual instruments contained into xpand, minigrand or similar plugins... But I haven't any midi keyboard, so I looked for a virtual one, and I found midikeys 1.8; it's perfectly accessible and, in the autor's opinion, it supports sending midi events to protools... So I tryed it, but I don't ear any sound from my audio interface when I play notes... I read that protools contains a mouse-virtual-midi keyboard; isn't it? Is it accessible using VoiceOver? And how can I access it? I don't know if the program doesn't work or I am wrong about the procedure; I describe what I do step-by-step below, can you tell me what you think about? In your opinion what's the problem and how can I solve it? 1. I create a new instrument track (mono or stereo); 2. In the mix' window I interact with the track, then I set up midi input to all (there aren't other choices into the pop up menu); 2. I set up midi output to out 1-2, which are the mac's built-in interface' channels; 3. I arm the track for recording into the mix' window and into the transport' window. Vincenzo.
Re: Changing track view
Hi Slau, Thanks, found it. Not too difficult after all, I was looking in the wrong place;-) friendly, Ronald Op 16 feb 2011, om 23:35 heeft Slau Halatyn het volgende geschreven: Hi Ronald, I don't recall there being a shortcut for changing the track view, although there very well may be. At any rate, to change the track view, go to the edit window and move to the track for which you'd like to change the view. This means navigating to the track's controls and not the track within the Tracks Table. Once you've interacted with the track, move past the meters and stuff until you come to the Track View Selector button. Press the button and select the view you'd like to use. Keep in mind, if you have the view selector set to volume and you select audio within the track and press Delete, what you'll be deleting is volume information not the audio itself. To edit or delete audio, you must have Waveform selected. This Track view is like a filter that displays waveforms or volume or pan or whatever parameters that have been automated. HTH, Slau On Feb 16, 2011, at 5:06 PM, RvR wrote: Hello, If I am reading it right in the reference guide you should be able to change the track view with the track view button, but I don't hear it. Found some video on the web where some guy talks that it's a triangle of some sort above the track header. the shortcuts mentioned in the reference guide are conflicting with voice over. Can anyone shed some light on the subject? thanks, Ronald
Re: on from solo mute button
Hi Herman, That simply means the mute button is on. When it's on, the track is muted. I suppose it would be clearer if the spoken text were, Mute button, on. HTH, Slau On Feb 16, 2011, at 11:40 PM, Herman Fermin wrote: What exactly does this mean? If I press on the mute button within the track, it says on mute button. I'm confused. HF
Re: automation
Hey Herman, There are 2 things to consider: 1. You need to define which parameters will be recorded for automation. Open the Automation window either from the menu bar or press Command-4 on the num pad. Choose which parameters you wish to automate. It's no accident that Volume is the first parameter in the window. Although you can automate any number of parameters at a time, it's absolutely recommended to keep it simple and deal with all volume first, then panning, if necessary, mutes, send mutes, etc. 2. When you're ready to automate, you need to put the tracks you wish to automate into Auto Write mode. This button is located within each channel strip in the Mix window. By default, after the first pass, automation will switch from Auto Write to Auto touch mode which means automation will play back as you had recorded it but, if you touch a fader, or whatever parameter you just automated, it will alter the automation to the move you just made on the second pass. Think of it like a malleable curve you can constantly change. Here's what I normally do for automation: First, I get a mix framed. Everything is ready to go with only automation left to deal with. Next, I make sure only the volume parameter is selected in the Automation window. Then I put all tracks into Auto Write. I roll the transport just for a second. This writes the current fader positions into automation. I then put everything into Auto Read. Next, I decide which track to automate with dynamic fader moves. I put only that track or tracks into Auto Touch. I go through the section and make my moves. If it's good, I keep it, put the track into Auto read and repeat with other tracks. If the move wasn't good, I press Command-z to Undo and repeat the fader move. I basically follow those steps for send Mutes or whatever parameter I need to automate. I generally don't automate panning although it does come up from time to time. HTH, Slau On Feb 16, 2011, at 11:55 PM, Herman Fermin wrote: I understand what automation is and how it works but I'm just not getting the hang of it in PT. Any tips or things I should be aware of? I can't seem to automate any plug-in parameters unless a sighted person ads the parameter to the list in the automation window in the plug-in. Everything in there is dimmed so don't understand how I can add things myself. VO doesn't see the list of available parameters at all. Or at least I don't know how to get to them if it is possible that is. HF
Re: automation
Hi What happens in pro tools when you write your first automation data at bar 32? Does it get squirrely before bar 32? If so one should make sure they're at the beginning of the track before doing their first automation write. --FC On Feb 17, 2011, at 8:29 AM, Slau Halatyn wrote: Hey Herman, There are 2 things to consider: 1. You need to define which parameters will be recorded for automation. Open the Automation window either from the menu bar or press Command-4 on the num pad. Choose which parameters you wish to automate. It's no accident that Volume is the first parameter in the window. Although you can automate any number of parameters at a time, it's absolutely recommended to keep it simple and deal with all volume first, then panning, if necessary, mutes, send mutes, etc. 2. When you're ready to automate, you need to put the tracks you wish to automate into Auto Write mode. This button is located within each channel strip in the Mix window. By default, after the first pass, automation will switch from Auto Write to Auto touch mode which means automation will play back as you had recorded it but, if you touch a fader, or whatever parameter you just automated, it will alter the automation to the move you just made on the second pass. Think of it like a malleable curve you can constantly change. Here's what I normally do for automation: First, I get a mix framed. Everything is ready to go with only automation left to deal with. Next, I make sure only the volume parameter is selected in the Automation window. Then I put all tracks into Auto Write. I roll the transport just for a second. This writes the current fader positions into automation. I then put everything into Auto Read. Next, I decide which track to automate with dynamic fader moves. I put only that track or tracks into Auto Touch. I go through the section and make my moves. If it's good, I keep it, put the track into Auto read and repeat with other tracks. If the move wasn't good, I press Command-z to Undo and repeat the fader move. I basically follow those steps for send Mutes or whatever parameter I need to automate. I generally don't automate panning although it does come up from time to time. HTH, Slau On Feb 16, 2011, at 11:55 PM, Herman Fermin wrote: I understand what automation is and how it works but I'm just not getting the hang of it in PT. Any tips or things I should be aware of? I can't seem to automate any plug-in parameters unless a sighted person ads the parameter to the list in the automation window in the plug-in. Everything in there is dimmed so don't understand how I can add things myself. VO doesn't see the list of available parameters at all. Or at least I don't know how to get to them if it is possible that is. HF
solo in place
Hi I'm trying to figure out what must be done to set this up. I'd like my sends and their verbs and delays to stay active. What must I do. Thanks --FC
Re: automation
Hey Frank, You can begin writing automation anywhere. That said, I just happen to start at the beginning. Think of the end of a song: when you finish automating, the levels will stay at that static value indefinitely unless there's a change. It's the same at the beginning of the session, only in reverse. If there are no changes, the automation value for volume, mute, pan, etc. will stay the same up until the first event. HTH, Slau On Feb 17, 2011, at 1:01 PM, Frank Carmickle wrote: Hi What happens in pro tools when you write your first automation data at bar 32? Does it get squirrely before bar 32? If so one should make sure they're at the beginning of the track before doing their first automation write. --FC On Feb 17, 2011, at 8:29 AM, Slau Halatyn wrote: Hey Herman, There are 2 things to consider: 1. You need to define which parameters will be recorded for automation. Open the Automation window either from the menu bar or press Command-4 on the num pad. Choose which parameters you wish to automate. It's no accident that Volume is the first parameter in the window. Although you can automate any number of parameters at a time, it's absolutely recommended to keep it simple and deal with all volume first, then panning, if necessary, mutes, send mutes, etc. 2. When you're ready to automate, you need to put the tracks you wish to automate into Auto Write mode. This button is located within each channel strip in the Mix window. By default, after the first pass, automation will switch from Auto Write to Auto touch mode which means automation will play back as you had recorded it but, if you touch a fader, or whatever parameter you just automated, it will alter the automation to the move you just made on the second pass. Think of it like a malleable curve you can constantly change. Here's what I normally do for automation: First, I get a mix framed. Everything is ready to go with only automation left to deal with. Next, I make sure only the volume parameter is selected in the Automation window. Then I put all tracks into Auto Write. I roll the transport just for a second. This writes the current fader positions into automation. I then put everything into Auto Read. Next, I decide which track to automate with dynamic fader moves. I put only that track or tracks into Auto Touch. I go through the section and make my moves. If it's good, I keep it, put the track into Auto read and repeat with other tracks. If the move wasn't good, I press Command-z to Undo and repeat the fader move. I basically follow those steps for send Mutes or whatever parameter I need to automate. I generally don't automate panning although it does come up from time to time. HTH, Slau On Feb 16, 2011, at 11:55 PM, Herman Fermin wrote: I understand what automation is and how it works but I'm just not getting the hang of it in PT. Any tips or things I should be aware of? I can't seem to automate any plug-in parameters unless a sighted person ads the parameter to the list in the automation window in the plug-in. Everything in there is dimmed so don't understand how I can add things myself. VO doesn't see the list of available parameters at all. Or at least I don't know how to get to them if it is possible that is. HF
Re: solo in place
Hey Frank, What you need is to solo safe the auxiliary input that's hosting the plug-in. Command-click on the solo button of any track you wish to solo safe. HTHT, Slau On Feb 17, 2011, at 1:04 PM, Frank Carmickle wrote: Hi I'm trying to figure out what must be done to set this up. I'd like my sends and their verbs and delays to stay active. What must I do. Thanks --FC
Re: solo in place
Hi Ignore that last message. I get it. Thanks --FC On Feb 17, 2011, at 3:59 PM, Frank Carmickle wrote: Hi Slau Is there a way to have this be the default behavior? Is there any reason why you would want this on all tracks? Possibly the verb and delay returns you wouldn't want it or would that still be useful? Thanks --FC On Feb 17, 2011, at 3:36 PM, Slau Halatyn wrote: Hey Frank, What you need is to solo safe the auxiliary input that's hosting the plug-in. Command-click on the solo button of any track you wish to solo safe. HTHT, Slau On Feb 17, 2011, at 1:04 PM, Frank Carmickle wrote: Hi I'm trying to figure out what must be done to set this up. I'd like my sends and their verbs and delays to stay active. What must I do. Thanks --FC
