Anyone have Odd AutoTune Problems?

Click just before the region you are about to work on (graphical mode), hit play...POP occurs on the first syllable of the vocal. A nasty, digital POP. Try a different start point. POP! again. Try a different start point. No pop. Ahhhh...good. Hit record to bounce the corrected section to another track. POP ...there it is again. What the hell is this? Capture a section to be tuned. Look at the graphic window. Some notes, that should appear higher, are no where to be seen. Just for kicks, scroll down to WAY below the melody line. Wow..there they are ...the notes that should have been higher. Correct them. Fine. Works. Why did they appear here? Tune a section. Play it back to make sure. Sounds good. Hit record. Section plays back...hmmm, now it doesn't sound in tune. Stop recording. Open the graphic window. hit play. Now it's in tune again. Hit record. This time it's fine. Anyone experience any of this kind of stuff?

It does the glitching lots of the time. Just keep your finger on command+. to quickly abort the recording. Also, make sure you have the correct "input type" selected...soprano, alto, tenor, low, instrument, bass. It'll cause octave jumps when tracking if you don't have the right one selected. It's trying to track pitch...it's not perfect.

Hmmmmmmm often if your getting repeated problems like this try working on a smaller regions ... generally is more reliable ...

Don't get me started about Autotune... Analyze a selection five time and you'll likely get five different pitch representations on screen for that selection. This alone drives me nuts. After analyzing a section, many time Autotune behaves as if it's working off a different analysis than the one displayed on screen. That is, it's shifting octaves, or not correcting where it should be. Analyze again, and you'll see the octave jumps it was doing, or that a note that once was there is no longer there, etc. Generally there is too much random behavior in Autotune. It should always analyze and playback the same. I don't see why it should work one way one time and another way the next. Draw a line exactly on a gridline. Scroll down. Scroll back up. Now your line is probably no longer on the grid. (pre-Autotune 3 you had a display of where the cursor was at any given time. This eleviated the problem somewhat. Thanks, Antares, for taking that away ;-) Octave shifts are a problem regardless of the input type selected. In fact, the whole input type doesn't seem to do as much as one would expect. Autotune should be smarter than this. The slightest bit of grit on vocals causes Autotune problems. Shouldn't there be some sort of filter applied to the analysis chain to filter that stuff out? I think it's sort of silly that you have to go to the Auto mode panel to change the grid for the Graphical mode. The scroller bars and zoom buttons are oddly placed and not very mac like. Pre-Autotune 3 the zoom buttons were all together which was very handy. That's it off the top of my head, but I think I just scratched the surface... Autotune, IMHO, has slowly grown worse with each new version Antares has released. AT3, while pretty to look at, is the worst yet.

I agree with all of the above...I think I have a post either here or on ProSoundWeb's recpit about the same types of problems. Autotune is VERY buggy. It makes me wonder what others use. I've heard some really good things about PitchDoctor but I haven't tried it yet. I went to a talk at the AES show that had Tal Hertzberg and Ron Fair and they were talking about how they used pitch correction on Vanessa Carlton's "Ordinary Day". Listening to it the correction is pretty smooth, I'd like to find out what they were using. I didn't hear any of the problems that are normally associated with Autotune. Does anyone know for sure what they used?

I Agree I almost always use RTAS. Bedsides who wants to use up DSP using autotune? Steve

Same problems always. I did a thread sometime ago about all this..... After switching computers last week, I finally got AT3 back running. It still has the problem of the fields going blue text over a dark green background which you can't read. It flashes white when it first pops on then goes blue. They will not respond to that. Otherwise, it still pops and glitches like it always did. I hate to solo a track with a client nearby. They ask what all that spitting is. I have tried all the range changes etc. That does not seem to help. You can't slow it down enough like you could in 2.X versions... So, same story as always