OH NO! 8.02 and Auto-Tune EVO

Gonna bump this one - I've done some further testing - the problem is not there in V7. I can load a project with AT enabled on a track in V7 and it plays normally. In V8.02 the graphical corrections are offset a step above the correct pitch.

I will file a report with Cakewalk. Groan.

I suggest you all check your plug-ins and make sure they all function properly. I am gonna find it a little difficult to believe this bug (whatever it is they broke) only affects Antares Auto-Tune. This was not a problem in 8.01 or any previous version.

I gotta make one other comment as long as I'm on a roll. I was able to make 8.0.2 motorboat. But this was yet another unique version of it. I opened a project and once all the waveforms were done rendering, I pressed the space bar and nothing. Nada. No playback. No dropout indicator. Nothing. It just sat there. So I pressed the space bar a few more times. Nothing. Seemed hung up. So I decided to just shut down Sonar and reopen it thinking I might have inadvertently done something wrong. So I click on the X in the upper right corner and motorboating starts in. Except this was a strange muffled version of the old problem. I don't know guys. And gals. I pray this was just a fluke. I'm really losing patience with this nonsense.

ORIGINAL: MArwood

I just used AT5 and EVO and did not notice anything. I will have to test some more.
How exactly did you put EVO into the project.

Max Arwood

As a track FX insert.

It may have something to do with the fact these projects were all created with an earlier version? Install gone bad? If I have time tomorrow I might just start over with a fresh install and see what happens. If no other AT users are able to duplicate the problem then it must be me.

Yes, I've encountered that "one step off" problem from the 44.1/48 sample rate switch. After you've done it just once, you know what it sounds like. It's close to 140 cents, almost a step-and-a-half.

Yeah I probably didn't explain it very well. I'm not sure I can even now.

The fix was to make sure that Sonar is completely configured for the bit depth and sampling rate of the project (which contains any instance of Auto-Tune) before you try to load that particular project. In my case, the project I was trying to load had been recorded at 24/48 but Sonar was configured for 24/44.1. What was confusing to me at first was that even though Sonar was configured for 24/44.1, it would load the project and then switch to the correct bit depth and sampling rate. I saw this at the bottom of the screen in the task bar when Sonar was starting up. That was the clue for me.

Earlier in the day I was working on some 16 bit audio and had accidentally changed some Sonar settings to match the new audio material. I have to admit, this business of how Sonar is configured for a particular bit depth and samplig rate never made sense to me. There are at least three different places in Sonar that you have to concerne yourself with when establishing the correct settings. Why all those check-boxes can't be consolidated under a single menu heading is beyond me really. I remember a few years back having to call TS because I couldn't figure out what I was doing wrong.

Why all this has any bearing at all on Auto-Tune is also a mystery but I suspect AT synch's up with whatever setting is in the host program and apparently if the host program is set one way and the audio project was recorded another way, this is enough to confuse it. I don't know. All this business didn't seem to bother V-Vocal because I had some projects with VV in use and it didn't care. Maybe Cake just doesn't like Antares

There are at least three different places in Sonar that you have to concerne yourself with when establishing the correct settings.

Larry,

Can you elaborate, specifically?