Hey graemeh,

Does this happen on any piece of audio you try and process by the same amount? Are you able to upload the audio at all so I can try reproduce this here on my end?

Sam.

Or possibly upload a recording or clip of this?

Hi Sam,
I've attached the Original and the 6%Faster files for you. I just did another test today and the result is the same. Any help much appreciated.
No answer to part B of my post re the 4% time discrepancy?
Cheers
Graeme

And yes, I could make it happen on a different track as well - the vocal almost sounded double-tracked in spots.

Hi graemeh,

I can reproduce this same effect here on my end. Unfortunately I can't seem to reproduce it on other tracks with vocals that I have though. Is there any special processing you have done on this vocal track at all? I will have to ask one of the developers if there is a reason this could be happening.

In terms of the 4% time discrepancy, i'm not actually aware of this bug myself but it sounds like something Logic will need to fix. If you can let me know the steps to reproduce/see the issue i'll be happy to take a look though and see if there is anything we can do on our end.

Cheers,

Sam.

That vocal has been processed through Melodyne Studio 3.2.2.2.
I'll do some experiments on my end, but I suspect that's the answer - whether Melodyne Editor (which I also use) also creates the same effect, I don't know.
The other vocal that I tested had also been Melodyned (as are pretty much all of the vocals that leave my studio).

To reproduce the 4% error, load a stereo file into Logic Pro's Arrange window and check the length in the time line bar ie 4:00. Then double click the file and the Sample Editor will open. In the Sample Editor, select "Factory" from the Menu Bar and open Time and Pitch Machine. If Serato is selected as the algorithm you'll notice that the time is 4% faster ie: 3:50.
I started a thread in Logic Discussions 18 0r so months ago about this and it was verified by a number of people - it was subsequently fixed in one version but then reverted to the buggy version again. I can't remember which versions off the top of my head...
This Apple bug however, renders the superior time shifting algorithm of P'n T essentially useless for me in Logic Pro 9 (still ok in Logic 7) - as I do a lot of precise time editing for Ballet and Calisthenic Groups who rely on me to make sure their musical item is under 3:00 or some other specific time limit. Hope this helps.
Cheers
Graeme

I would say that it's likely that there is some kind of issue that Pitch 'n Time is having when processing audio that has been adjusted in Melodyne. Unfortunately we don't have a copy of this here to test with though. Are you able to test a vocal that you have not run through Melodyne and let me know if the same thing happens?

In terms of the other issue, it looks like this is a bug on Apple's end as it seems to happen when any algorithm is selected which they will need to fix. I would recommend getting in touch with them and reporting this as there isn't much we can do to fix this on our end. You can find Apple's support details here:

www.apple.com

Cheers,

Sam.

I've just done an avalanche of tests and discovered that when my Amek CIB is bypassed (I have that and an Orban DeEsser permanently patched into the return vocal chain to the desk) the problem disappears and audio pitch shifts properly. So I guess my problem is solved. Thanks Sam! I'll let Apple know of the bug - again...thanks.