I'm stuck in the new Melodyne 4 Studio and feel really stupid. It must be a simple solution to this:
 
I'm trying to use multiple files in Melodyne 4 and so far I opened a separate Melodyne in each effect bin of my 6 audio tracks. Now that I am ready with syncing all files to each other, the 6 Melodynes is really CPU heavy. How do I render the change into the audio file and remove Melodyne from effect bin? Or have I done it the wrong way? I tried to mark every track and created them as Region FX but I couldn't open more than one track at the time that way.
 
Can you help?

You can apply audio effects.  I'd be careful because that will also apply any eq or other effect from the Pro Channel.  It's how I used to do it before using the region effects feature.

I also use Region FX. if you bounce what is in your bins, just remember, like sacaliat said. be careful.
its destructive.

Use Region FX then once you have finish editing right click on the tracks and Render Region FX.

Effects just interfere with Melodyne, so add them afterwards (rendering that is). All my issues with Melodyne have been from not rendering as soon as I'm done with a clip or track. Now I'm in that habit and life is good! LOL
 

Thanks everybody!
 
I will try applying audio effects tomorrow. I haven't begun mixing yet so no EQ or other effects should interfere.

Sort of a dumb question:  When you speak of rendering a track with Melodyne applied to it (either the whole track or a region effect) is that the same as "freezing" the track?

There are no dumb questions, really, just impatient people. LOL
No    Freezing turns midi data into an audio track. It's temporary not like bouncing it down to audio. See this
https://www.cakewalk.com/Documentation?product=SONAR%20X2&language=3&help=Mixing.23.html
 
When you use Melodyne you have to create a Region Effects version of it, whether it's a clip or whole track. When you get done editing (and certainly before closing the project) in Melodyne, you have to Render the Region Effects "back" into "regular clip-ness" (LOL I like to amuse myself). So, freezing and rendering a Region Effect are not really similar at all.
 
When I started editing tracks in Melodyne (without watching any videos... duh), I would close the project leaving my Melodyne Regions "open" (ie not rendering them) and that caused problems. Now I've learned my lesson and render each clip before even moving on to the next one, or closing the project.
 
Michael
 

Having to render the regions before closing the project to avoid issues is a bug if I've ever heard of one. Melodyne adds artifacts to my tracks that I sometimes don't hear till I listen a day later with fresh ears. Fresh ears also allows me to judge if the correction is acceptable or not. Sometimes the original sounds better than the corrected version. Having to render before closing kills this going back option.

Was this an issue with previous versions of Melodyne? I don't recall having issues with open fx regions with Melodyne editor 2. I never rendered my regions before.

I certainly do now that I've upgraded to studio 4. My old projects with open regions have bizarre things going on.

I always make a copy and Melodyne that.