I still have not heard back from Celemony about getting my trial functional, but in searching for other info I found that Celemony's forum was abolished with the release of Melodyne 4 (I read into such differently than what is claimed on that page). Has anyone come across a FAQ page from Celemony for the points in this thread?

mettelus
I still have not heard back from Celemony about getting my trial functional, but in searching for other info I found that Celemony's forum was abolished with the release of Melodyne 4 (I read into such differently than what is claimed on that page). Has anyone come across a FAQ page from Celemony for the points in this thread?

I copied this from my manual:
The tempo functions are only relevant in the stand-alone implementation of Melodyne and only found there. The plug-in implementation takes its tempo information from the DAW and is therefore tied to its tempo progressions. To share with your DAW the fruits of Melodyne’s tempo detection, you can export a MIDI file from the stand-alone implementation containing the tempo progressions detected by Melodyne and import it into the DAW as a tempo map.
 
Brian

That seems reasonable enough, and functional. What, if anything, does Studio One do that provides greater functionality than that? Just out of interest... 

subtlearts
That seems reasonable enough, and functional. What, if anything, does Studio One do that provides greater functionality than that? Just out of interest... 

In Studio One it is a whole different story. Check out the video from a studio one user https://forums.presonus.c...pic.php?p=83426#p83426
I made a correction, Melodynes tempo detection works in Studio One version 2 as well as version 3.

Did Studio One v3 release a patch when Melodyne 4 hit the streets? I am dismayed that bringing tempo data into SONAR (from a plugin) wasn't the first reaction to this "new information."
 
As many projects require the mating of audio/MIDI data, the number one thorn in my side has been the tempo map. Even when Drum Replacer hit the streets, my first reaction was to "audio microscope" AudioSnap (essentially what Melodyne 4 is doing), yet that comment seemed to spin off into oblivion. Now a plugin can do it, but there remains no "on the fly" mating of that plugin. As Melodyne 4 seems to have elegant methods to adjust this "at will," it may be time to consider making SONAR slave to a plugin for tempo mapping - the utter segregation of MIDI vs. audio in SONAR can finally be "abolished" and made significantly less painful than it is today.
 
AudioSnap "could" have beaten Melodyne to the punch here, but has never ventured down the path of "audio microscope" although Drum Replacer did (saving users forced micromanagement of the pool), or an elegant graphical solution for adjustment.

What is the latest on this? I never used melodyne for tempo detection.  I just wanted meloydyne to match my current snap or tempo when I opened it?  is there a workflow I don't understand that requires the analysis of melodyne audio to dictate the tempo of the parent project??
 
If melodyne 4 opens with the current snap or "granularity" of my session...whats the problem?  my current melodyne editor 2 gets randomly messed up and does not follow the granularity of the current session.   So if I am 1/8 I still have to fart with melodyne and set the X and Y to a useable scale then make sure that one setting is 1/8 inside the melodyne plugin.  
 
Smooth snap or edit granularity back and forth and back again would be great. I have not upgraded yet, but I have always had to "set" the tempo in melodyne before.  Just FYI

subtlearts
That sounds like a reasonable workaround, but it would be even more brilliant if it could all be done internally with Studio running as a plugin. Hmm. I'm going to install the demo and play around a bit... 

We have plans of improving this part of the ARA integration in a future release. It shouldn't be very difficult.

Noel Borthwick [Cakewalk]

subtlearts
That sounds like a reasonable workaround, but it would be even more brilliant if it could all be done internally with Studio running as a plugin. Hmm. I'm going to install the demo and play around a bit... 

We have plans of improving this part of the ARA integration in a future release. It shouldn't be very difficult.

Well that's a happy bit of news... 

Noel Borthwick [Cakewalk]

subtlearts
That sounds like a reasonable workaround, but it would be even more brilliant if it could all be done internally with Studio running as a plugin. Hmm. I'm going to install the demo and play around a bit... 

We have plans of improving this part of the ARA integration in a future release. It shouldn't be very difficult.

Yes thankyou Noel. While it is possible to save the detected tempo to a MIDI file from the plugin, we need a way to save the tempo map into the current project without having to create a new project from a MIDI file.

Noel Borthwick [Cakewalk]
 
We have plans of improving this part of the ARA integration in a future release. It shouldn't be very difficult.

Noel, that is just the news I have been hoping for! :)
 
The day this comes out is the day I will finally feel I can begin recording the versions of my own songs that I have always longed to be able to record - first, the most important main vocal and playing (simultaneously) track, recorded with no click so that the performance can be as heartfelt and spontaneous as possible. 
 
Then, adding the other instruments and voices, using the tempo map to make everything nice and tight.
 
And all from within Sonar, so that very little time is spent "engineering" (I have to use this word in very large mocking quotation marks in my case :)) and the great majority of the time is spent concentrating on coming up with the best performance I can dredge up.
 
All this to say, I can't wait. Thanks again!
LJ