R/E/P Community

Please login or register.

Login with username, password and session length
Advanced search  

Pages: 1 2 3 [All]   Go Down

Author Topic: Melodyne DNA plug in - the long awaited crash machine  (Read 13139 times)

JGauthier

  • Full Member
  • ***
  • Offline Offline
  • Posts: 136
Melodyne DNA plug in - the long awaited crash machine
« on: December 02, 2009, 01:18:02 pm »

If you have ever used Melodyne, and I mean SERIOUSLY used and counted on it to work its magic, you have probably expierenced its "quirky" nature...

The program NEVER worked 100% but the results of flogging it to fruition were, IMHO, well worth it. Especially if you tried to work with multiple tracks... Boy could it get squirrely!

So Ive been waiting with baited breath for the new polyphonic melodyne. Even if it has artifacts and gets fishy, the ability to change a note in a chord is huge. Huge.

Luckily they sent us all beta versions to try which worked fine, but they weren't the plug in version.

Well the plug is out and it crashes. Hard. I mean press the button manually on the tower to restart crahses... And this room its in FLIES all day long with 200+ tracks... We have had ZERO crashes in months.

So a heads up to those who are excited or considering purchase- it still doesn't work. They pushed it back what a year, realeased beta versions and it still doesn't work.

So no review of DNA itself. No review of the interface. No review of sound quality. To review those things, it needs to not crash and actually work.

Im sure things will get better and please post in this thread ANYTHING related to Melodyne DNA. I have to buy it eventually... For now, Ill just let it crash studio A.
Logged

maarvold

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 853
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #1 on: December 04, 2009, 08:08:35 pm »

The Melodyne PlugIn has always been just about a stone's throw short of unusable on my quad core [Intel] MacPro 2.2 gHz.  It just takes over my computer and does whatever it wants, leaving me saying "wtf" a lot.  I'll grant you, it's powerful and it does do a lot without too much hassle, but--in addition to it 'hijacking' my computer every 5 minutes or so--there's a bug that makes it chase the midi map (in PT 8.x) and it varispeeds the audio clocking of the captured audio somehow and makes things sound grainy and creates zipper noise when the midi tempo map changes occur: a heartbreaker if you didn't catch the problem until all the work is done and you are ready to print the repaired track.  If you notice this happening, you can delete the midi tempo map and capture the audio again.  I never got into it deeply enough to see if the repitching already performed would still be intact, but my guess is no.  

Long-winded story short, on my computer, plain old Melodyne takes so much computing power that I can't see a polyphonic plugin version running on any but the very fastest machine, probably with Snow Leopard.  YMMV.
Logged
Michael Aarvold
Audio Engineer

J.J. Blair

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 12809
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #2 on: December 05, 2009, 09:58:44 pm »

I guess I'm sticking with AT until they fix this.  I just wish that AT had formant control, so I could avoid chipmunk effect during large interval changes.
Logged
studio info

They say the heart of Rock & Roll is still beating, which is amazing if you consider all the blow it's done over the years.

"The Internet enables pompous blowhards to interact with other pompous blowhards in a big circle jerk of pomposity." - Bill Maher

"The negative aspects of this business, not only will continue to prevail, but will continue to accelerate in madness. Conditions aren't going to get better, because the economics of rock and roll are getting closer and closer to the economics of Big Business America." - Bill Graham

Tomas Danko

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 4733
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #3 on: December 06, 2009, 07:07:20 am »

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.
Logged
http://www.danko.se/site-design/dankologo4s.gif
"T(Z)= (n1+n2*Z^-1+n2*Z^-2)/(1+d1*z^-1+d2*z^-2)" - Mr. Dan Lavry
"Shaw baa laa raaw, sidle' yaa doot in dee splaa" . Mr Shooby Taylor

JGauthier

  • Full Member
  • ***
  • Offline Offline
  • Posts: 136
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #4 on: December 06, 2009, 09:47:19 pm »

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.


Thats good to hear. Ive run it for years in Protools and its NEVER worked 100%... And I mean for anyone I know. I tried stand alone a few times and it was definitely better, but I want a plug in PT not stand alone, so Im stuck..

The Melodyne bridge was complete ass. Talk about random crap happening... But I still flogged through it. It really is way better than auto tune IMHO...

But Im about to buy auto tune again... It works, all the time.

Logged

jetbase

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 2454
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #5 on: December 06, 2009, 10:17:49 pm »

I mentioned problems I had with the regular Melodyne plugin earlier this year in this thread over in 'Whatever Works':
http://recforums.prosoundweb.com/index.php/m/428972/6028/?ms g_428972

We battled through it for that project, but I believe the producer has since purchased Autotune Evo rather than continue to deal with the Melodyne problem. I still like Melodyne as a stand alone program, but it's not as convenient as using a plugin in Pro Tools.

Has anyone used Waves Tune? Care to comment &/or compare to Autotune & Melodyne?
Logged
sleep is not an option

jwhynot: "There's a difference between thinking or acting dogmatically and drawing from experience."


Glenn Santry
http://www.myspace.com/glennsantry

maarvold

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 853
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #6 on: December 06, 2009, 10:33:43 pm »

JGauthier wrote on Sun, 06 December 2009 18:47

...But Im about to buy auto tune again... It works, all the time.




My very informal... well, guess is really the correct word at this point, is that AT might sound smoother and more 'high res'/less glitchy.  But if someone has spent some time sorting this out, I'd love to hear their take on it.  Neither one, for me, has a really great graphic mode interface, but they're both pretty good in that regard, just different methods to accomplish the same end.  
Logged
Michael Aarvold
Audio Engineer

J.J. Blair

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 12809
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #7 on: December 07, 2009, 12:39:34 am »

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.  
Logged
studio info

They say the heart of Rock & Roll is still beating, which is amazing if you consider all the blow it's done over the years.

"The Internet enables pompous blowhards to interact with other pompous blowhards in a big circle jerk of pomposity." - Bill Maher

"The negative aspects of this business, not only will continue to prevail, but will continue to accelerate in madness. Conditions aren't going to get better, because the economics of rock and roll are getting closer and closer to the economics of Big Business America." - Bill Graham

compasspnt

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 16266
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #8 on: December 07, 2009, 12:53:27 am »

J.J. Blair wrote on Mon, 07 December 2009 00:39

 Going back and forth between the two programs like that is just...




...not an option.
Logged

Tomas Danko

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 4733
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #9 on: December 07, 2009, 06:29:11 am »

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.
Logged
http://www.danko.se/site-design/dankologo4s.gif
"T(Z)= (n1+n2*Z^-1+n2*Z^-2)/(1+d1*z^-1+d2*z^-2)" - Mr. Dan Lavry
"Shaw baa laa raaw, sidle' yaa doot in dee splaa" . Mr Shooby Taylor

Tomas Danko

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 4733
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #10 on: December 07, 2009, 06:49:38 am »

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.  


Far from ideal work flow wise, but you can bounce out an instrumental of the mix and run it on one track in Melodyne while futzing about with the vocals.

I feel that the end result you get with Melodyne is totally worth the extra work.
Logged
http://www.danko.se/site-design/dankologo4s.gif
"T(Z)= (n1+n2*Z^-1+n2*Z^-2)/(1+d1*z^-1+d2*z^-2)" - Mr. Dan Lavry
"Shaw baa laa raaw, sidle' yaa doot in dee splaa" . Mr Shooby Taylor

jetbase

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 2454
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #11 on: December 07, 2009, 04:46:14 pm »

Sometimes I load in a bass or acoustic guitar track to reference the vocals to. But I must say, I don't seem to have problems if I just use the plugin to tune a line here or there.
Logged
sleep is not an option

jwhynot: "There's a difference between thinking or acting dogmatically and drawing from experience."


Glenn Santry
http://www.myspace.com/glennsantry

marcel

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1257
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #12 on: December 07, 2009, 07:28:28 pm »

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.

I have been using the RTAS plugin successfully for years, also on a G5.  Perhaps some of the problems are with Intel-based computers?  

I am, however, very strict with my workflow.  I tune a track (or a section), print it to another track, and immediately remove the plugin.  Otherwise I get CPU chokes (2x2GHz G5) pretty quickly.

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.
Logged
Best, Marcel

maarvold

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 853
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #13 on: December 08, 2009, 02:47:08 pm »

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.



The 2nd one is as I remembered: a sort of warbling/zipper type sound sometimes.  The only thing that I get with AT 5 (as an AudioSuite plugin, which is how I usually use it these days) is the very occasional chirp.  
Logged
Michael Aarvold
Audio Engineer

letemin

  • Newbie
  • *
  • Offline Offline
  • Posts: 1
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #14 on: December 15, 2009, 05:45:16 pm »

Anyone at all using the new editor plugin with success? Are problems related to OS by any chance?

As an aside, I see the new DNA stuff as more of an experimental production tool as opposed to a fix-it tool, so if manipulation yields a loss of air or if there are artifacts or, that's fine by me.  Like an instrument, it's got it's own type of sound (artifacts).
Logged

JGauthier

  • Full Member
  • ***
  • Offline Offline
  • Posts: 136
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #15 on: December 17, 2009, 11:13:46 am »

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.


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"...

Logged

Tomas Danko

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 4733
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #16 on: December 18, 2009, 11:46:30 am »

JGauthier wrote on Thu, 17 December 2009 16:13

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.


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"...




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.
Logged
http://www.danko.se/site-design/dankologo4s.gif
"T(Z)= (n1+n2*Z^-1+n2*Z^-2)/(1+d1*z^-1+d2*z^-2)" - Mr. Dan Lavry
"Shaw baa laa raaw, sidle' yaa doot in dee splaa" . Mr Shooby Taylor

jetbase

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 2454
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #17 on: March 16, 2010, 06:59:07 pm »

I've been trying Melodyne Essential RTAS with PT MPowered 8.03 (on PC) for the past couple of weeks. Sounds like the same problems as DNA in the OP (crashing PT, restarts computer). Anybody have any success with this thing?
Logged
sleep is not an option

jwhynot: "There's a difference between thinking or acting dogmatically and drawing from experience."


Glenn Santry
http://www.myspace.com/glennsantry

nob turner

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 383
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #18 on: March 27, 2010, 09:09:58 pm »

don't know about melodyne essential, but i have used melodyne editor (dna) for a bit, and while it is extremely processor hungry, it can work.  the other day i tuned single notes of violin double-stops and improved them, which isn't doable with any other software i know.  

however, it is far from perfect.  i tried to correct an out-of-tune note in an acoustic guitar chord, and there was too much chorusing to be listenable.  and it DOES crash protools periodically.  clearly it is safest to render any corrections you make with it.
Logged
Why do you think they call it the control room?
www.garymankin.com

iCombs

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 537
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #19 on: March 28, 2010, 02:07:29 pm »

Tomas Danko wrote on Fri, 18 December 2009 10:46

JGauthier wrote on Thu, 17 December 2009 16:13

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.


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"...




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.


+1.

Did 12 tracks of tuning that way just yesterday.
Logged
Ian Combs
Producer/Engineer
Lightspeed Group, Inc.
----------------------
"Mista apareeatah... can I have maar beass at all frequencies?"

JGauthier

  • Full Member
  • ***
  • Offline Offline
  • Posts: 136
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #20 on: March 28, 2010, 03:35:27 pm »

Tomas Danko wrote on Fri, 18 December 2009 08:46

JGauthier wrote on Thu, 17 December 2009 16:13

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.


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"...




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.


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...
Logged

Tomas Danko

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 4733
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #21 on: March 28, 2010, 03:54:41 pm »

JGauthier wrote on Sun, 28 March 2010 20:35

Tomas Danko wrote on Fri, 18 December 2009 08:46

JGauthier wrote on Thu, 17 December 2009 16:13

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.


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"...




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.


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...



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!
Logged
http://www.danko.se/site-design/dankologo4s.gif
"T(Z)= (n1+n2*Z^-1+n2*Z^-2)/(1+d1*z^-1+d2*z^-2)" - Mr. Dan Lavry
"Shaw baa laa raaw, sidle' yaa doot in dee splaa" . Mr Shooby Taylor

dbmusic

  • Newbie
  • *
  • Offline Offline
  • Posts: 49
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #22 on: April 07, 2010, 05:29:40 pm »

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!


+1

I've used Melodyne for years in exactly this manner and it suits my workflow just fine. Never cared much for the plugin interface. Nor do I need to import other reference tracks just to fix a few errant notes. I just split and render out a small section of the track I want to fix, use Melodyne to do it's thing, then drag and drop it back. Using this method I can't remember a single instance of it ever crashing.

Different strokes I guess.

Regards,

DB
Logged

maarvold

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 853
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #23 on: April 17, 2010, 10:52:23 am »

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.  
Logged
Michael Aarvold
Audio Engineer

bleen

  • Full Member
  • ***
  • Offline Offline
  • Posts: 118
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #24 on: April 17, 2010, 03:34:12 pm »

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.  


That's the original Melodyne plug-in, not the currently available plug-in version of Melodyne Editor.
Logged

jetbase

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 2454
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #25 on: April 18, 2010, 07:41:00 pm »

bleen wrote on Sun, 18 April 2010 05:34

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.  


That's the original Melodyne plug-in, not the currently available plug-in version of Melodyne Editor.


I got an e-mail on Saturday advising me of updates available now for Editor, Assistant & Essential RTAS.
Logged
sleep is not an option

jwhynot: "There's a difference between thinking or acting dogmatically and drawing from experience."


Glenn Santry
http://www.myspace.com/glennsantry

maarvold

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 853
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #26 on: April 23, 2010, 05:46:26 pm »

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.  
Logged
Michael Aarvold
Audio Engineer

jetbase

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 2454
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #27 on: May 03, 2010, 07:34:33 pm »

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.  


I'm still having problems running this latest version in PT8 - virtually unusable. Is anyone having any success?
Logged
sleep is not an option

jwhynot: "There's a difference between thinking or acting dogmatically and drawing from experience."


Glenn Santry
http://www.myspace.com/glennsantry

eric_hedford

  • Jr. Member
  • **
  • Offline Offline
  • Posts: 83
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #28 on: May 15, 2010, 04:40:35 pm »

Tomas Danko wrote on Sun, 28 March 2010 20:54

JGauthier wrote on Sun, 28 March 2010 20:35

Tomas Danko wrote on Fri, 18 December 2009 08:46

JGauthier wrote on Thu, 17 December 2009 16:13

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.


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"...




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.


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...



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!


Logged

J.J. Blair

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 12809
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #29 on: May 16, 2010, 01:54:54 pm »

I'm hoping that one day I can buy a working version of this plug-in, to use with PT8.
Logged
studio info

They say the heart of Rock & Roll is still beating, which is amazing if you consider all the blow it's done over the years.

"The Internet enables pompous blowhards to interact with other pompous blowhards in a big circle jerk of pomposity." - Bill Maher

"The negative aspects of this business, not only will continue to prevail, but will continue to accelerate in madness. Conditions aren't going to get better, because the economics of rock and roll are getting closer and closer to the economics of Big Business America." - Bill Graham

jetbase

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 2454
Re: Melodyne DNA plug in - the long awaited crash machine
« Reply #30 on: May 16, 2010, 07:08:21 pm »

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.


I'm wondering if some of my other older plugins may have been causing problems with PT8 & somehow making melodyne unstable. I checked plugin compatibility on the Avid website & cleaned out my plugins folder the other week. PT seems very stable now, and a quick test of melodyne (Essential RTAS) revealed no problems. I won't really know until I'm mixing in a couple of days, there are a couple of tracks I will be using melodyne on. If Essential works I might consider upgrading to Assistant or DNA.
Logged
sleep is not an option

jwhynot: "There's a difference between thinking or acting dogmatically and drawing from experience."


Glenn Santry
http://www.myspace.com/glennsantry
Pages: 1 2 3 [All]   Go Up