Tomas Danko wrote on Sun, 06 December 2009 04:07 |
FWIW, I've been running Melodyne Cr8 v3.2 on my Dual G5 2.7 GHz Power Mac for years and it's never ever been a problem in any way. I've used the AU plug-in as well, but prefer working separately in Melodyne. It's never hogged the CPU etiher. |
JGauthier wrote on Sun, 06 December 2009 18:47 |
...But Im about to buy auto tune again... It works, all the time. |
J.J. Blair wrote on Mon, 07 December 2009 00:39 |
Going back and forth between the two programs like that is just... |
J.J. Blair wrote on Mon, 07 December 2009 05:39 |
The problem with using it stand alone is that I really need to hear the vocal in context with the music to know if it's right or not. Going back and forth between the two programs like that is just too time consuming. |
Tomas Danko wrote on Sun, 06 December 2009 04:07 |
FWIW, I've been running Melodyne Cr8 v3.2 on my Dual G5 2.7 GHz Power Mac for years and it's never ever been a problem in any way. I've used the AU plug-in as well, but prefer working separately in Melodyne. It's never hogged the CPU etiher. |
marcel wrote on Mon, 07 December 2009 16:28 |
I do have 2 specific complaints about Melodyne: -Loss of HF image, or 'air' or whatever you want to call it. Probably an inevitable result of this type of processing, although I don't remember it being as bad with AT. -The inability to tune particular phrases without 'cycling' or 'warbling' artifacts, similar to the MIDI mapping problems Michael described above (I think), but without the MIDI events. |
Tomas Danko wrote on Mon, 07 December 2009 03:29 |
I guess the reason why I actually prefer the stand-alone version is that I never use it in automatic mode. Instead, I overhaul the vocals manually and tweak things until I think this will be the vocal tracks in the song and be done with it. So practically speaking, I put on my scrutinizer hat for a while and alter pitch and timing across all vocal tracks. From there, I just update the audio files in the song project and go back to arranging and mixing etc. I like to commit to the source material, and not deal with pitch issues or comping etc once I'm doing the final mixing. |
JGauthier wrote on Thu, 17 December 2009 16:13 | ||
See the problem with this is pitch variation. If you track to a LIVE orchestra, combined with other instruments, you get a sort of RELATIVE pitch. Theres NO WAY to use it as a stand alone if the pitch is squirrley OVERALL... And if you record mostly live players and acoustic instruments, pitch is a completely different game... Its impossible to pitch vox correctly with out relativity. I hate to poorly quote Fletchers quote but, "there are no emotions on a grid"... |
Tomas Danko wrote on Fri, 18 December 2009 10:46 | ||||
Which is why you render out the rest of the music into a separate file and put it on a track inside Melodyne for reference. |
Tomas Danko wrote on Fri, 18 December 2009 08:46 | ||||
Which is why you render out the rest of the music into a separate file and put it on a track inside Melodyne for reference. |
JGauthier wrote on Sun, 28 March 2010 20:35 | ||||||
Seriously? Yeah, thats not a crapload of extra steps... These orchestral shows are 60 minutes of music. Im supposed to bounce 60 minutes of music just for pitch reference? What world does that work in... You CAN make it work but this is not how it was intended. And your work around requires a bit more thinking than a single pitch reference when tracking orchestra sections. You would need to bounce MULTIPLE references and in protools thats all real time bouncing... Come on- for professionals remember... That means the minimum requirement is "it works"... If you have to flog it into submission thats a load... |
Tomas Danko wrote on Sun, 28 March 2010 14:54 |
Most of us here don't do 60 minute songs. Some of us here prefer to wear different hats during different periods throughout a project. I like to sit and focus on fixing small pitch- and timing anomalities and not consider anything else. I like even more to reimport the fixed audio files into the song/mixing project and get on with more important things and forget about tuning. The step to render out a song and drag the file to the Melodyne project, while dragging the other files needed, is not even a minor inconvenience or time consumer as far as I am concerned. It's easy to find a few minutes where you don't absolutely have to be near the computer, or use Pro Tools/Logic etc. To me, this works really well and I prefer this workflow to other methods. But then I do not do 60 minute songs! |
maarvold wrote on Sat, 17 April 2010 07:52 |
Got an email from Celimony this morning where they say: "We would like, however, to remind you that further development of Melodyne plugin has been discontinued." Unfortunate, imo. |
bleen wrote on Sun, 18 April 2010 05:34 | ||
That's the original Melodyne plug-in, not the currently available plug-in version of Melodyne Editor. |
maarvold wrote on Sat, 24 April 2010 07:46 |
I got an email today advising the following: "You are receiving this mail because you recently downloaded the update to Melodyne editor 1.1. The information it contains is only relevant if you use Pro Tools as host for Melodyne. If you use some other host, you can ignore this mail. Melodyne editor 1.1 contains a bug that unfortunately was only detected after the release of the update. Under certain circumstances, this bug can result in the loss of your Melodyne edits when a saved Pro Tools project is reopened. As a precaution, therefore, we recommend you to download and install a service update from which the bug has been removed." The email also contains a link to update Melodyne to a newer version with the bug fix in place. |
Tomas Danko wrote on Sun, 28 March 2010 20:54 | ||||||||
Most of us here don't do 60 minute songs. Some of us here prefer to wear different hats during different periods throughout a project. I like to sit and focus on fixing small pitch- and timing anomalities and not consider anything else. I like even more to reimport the fixed audio files into the song/mixing project and get on with more important things and forget about tuning. The step to render out a song and drag the file to the Melodyne project, while dragging the other files needed, is not even a minor inconvenience or time consumer as far as I am concerned. It's easy to find a few minutes where you don't absolutely have to be near the computer, or use Pro Tools/Logic etc. To me, this works really well and I prefer this workflow to other methods. But then I do not do 60 minute songs! |
J.J. Blair wrote on Mon, 17 May 2010 03:54 |
I'm hoping that one day I can buy a working version of this plug-in, to use with PT8. |