A wee LOGIC Pro Bug I didn't know about ....

[kudzu]

I've been getting familiar with the new Melodyne Plugin. Tried it on a vocal track of a song @ 68bpm, 6/8 time signature in Logic Pro 7.2.3. The Melodyne Plugin stayed @ 120pm, 4/4 ... ie. it didn't sync 2 Logic !!!!! Contacted Melodyne support ... this is what they sent ....

"Yes, in fact there seems to be an inconsistency in respect to what Logic defines to be a "beat" when transmitting the beat position to a plug-in. You would expect, for example, at tempo 100 beats per minute, that the beat position is "100" after a minute. In Logic, this is the case if the denominator of the signature is "4", but if the denominator is "8", the beat position after a minute is "200"! (In other hosts, e.g. Cubase, this behaves as you would expect.)

You have to deal with it somehow, at least until this is changed by Apple, and this is a possible workaround:

1. for transferring the audio to Melodyne via the bridge, set the signature in Logic to something with "4" in the denominator temporarily (the numerator of the signature doesn't matter for that). Don't set any tempo or signature in Melodyne. Then start playback for transfer.
2. after transferring, reset the signature in Logic to 6/8.
3. change the tempo background in Melodyne with the "Edit->Define Tempo->Double Tempo" command. (not the "Change Tempo (Autostretch)" command!) When you play back from Logic now, the audio should be audible at the right places.
4. for visible congruence of the bars, you can set the signature in Melodyne to 6/4, as 1/8 in Logic is 1/4 at double tempo in Melodyne now.

I hope that helps - no better way at the moment...

... Oh dear. It's true. I tried the fix offered ... it worked .... APPLE ? COME ON ? I kinda like how 3rd party plugins expose failings in these programs ... long may it continue

I wonder if the sync in 3rd party plugin delays doesn't work properly if u use a time signature other than ?/4 ... ?

... The more u know, the less chance of anything going wrong !!!!