Hey guys,
 
Here's an odd one for me. If I do a Region FX edit (say tuning something with Melodyne), it works as intended. If I bounce down the clip, and then think "ah, I need to do a bit more work on it" then I can no longer get the Region FX to activate. I've noticed that they'll work fine on anything that says "Record nnn" as in tracks that haven't previously been bounced that have filenames, but after a bounce, the name is blank and I can't get anything to work on them.
 
Just throwing it out there on here first before I head to problem reporting to see if it's just me or not. It seems like something more people would have mentioned if it was widespread. Cheers!

Hi Tim...

Unless I'm mistaken, once you bounce a clip, it creates a new clip replacing the old...

If you want to be able to go back that simply, you need to use Freeze for the track instead though I'm told it's not supposed to be done, it works fine for me when I've done this....

What I more often do is clone the track with all the Melodyne edits and archive/hide the original. Then I apply the processing via bounce to clip on the cloned track. This way I can go back to the archived track to redo any portions, then copy the new data to the cloned track an process it there... Again archiving and hiding the original...

A bit tedious, but I've gotten so used to working this way it's become automatic...

Keni

That's a good workaround
 
I don't understand what could be so different about bounced clips, which are just WAVs at the end of the day, that's not letting Region FX activate. I do suspect this is all on my end though, so it might be time to bite the bullet and do that system upgrade / clean out I've been meaning to do for ages.

This shouldn't need a work-around. Bounce to clip should create a new WAV file that you can then re-apply the RegionFX to.
 
I mean, obviously you can't open the Editor with the previous clip in it, once you've bounced... but nothing should prevent you from applying the RegionFX over and over again, bouncing in-between.
 
(Not that I'd recommend this - you'd get accumulated artifacts pretty quickly)
 
But it should be possible. If you're not able to do this, I'd call it a bug.
 
 

I'm thinking that the problem here is that you're expecting the region fx to still be in place.

When you bounce to clip it renders the region fx and removes it...

Unless you're trying to create a new region fx of the processed clip and it is failing to do so...? This would be an issue...

Can you talk a bit more about what you're trying to do and expecting?

Keni

...or you could just "Undo" the region fx and go back to the original clip and re-do your edits plus the new edits that you want to make. That way you would only have to do one bounce after all the edits are done, keeping any artifacts to a minimum. Of course, this wouldn't be helpful if you made many edits and would be difficult to repeat them all.

Hey guys,
 
Let me explain more of what I'm doing, and I'll use Melodyne and a vocal track as the example.
 
I get my vocal track recorded. On the track, I can clearly see "Record nnn" for each take in the clip header. Nothing on there has been bounced to new clips or anything, just regular recording/edits.
 
I go through the clip and find certain phrases that might need some pitch correction, so I select that portion and do CTRL+M to load up Melodyne. Adjust as needed. You can clearly see that each one of those clips have Region FX in the clip header.
 
My machine is getting on a bit (this is being polite to it) so after about 4 or 5 edits, I prefer to go back in and bounce each Region FX clip to a new clip. If I don't do this then SONAR starts to become unstable for me. It's an acceptable workaround for me considering the low specs of the machine.
 
So I'll have a track which has the named "Record nnn" untouched takes with the bounced sections in there which no longer have any filename in the clip header.
 
I finish what I'm doing, listen back to the track as a whole and I think "You know, that first clip I adjusted could have been better" so I go to the bounced clip, do CTRL+M to activate Melodyne so that I can do some more work on it.
 
Things that I'm aware of at this point:
 
Since it was bounced, this is a NEW clip, so therefore it's got no Region FX on there that are editable (as you would have if you went to re-edit an existing Region FX clip) - I'm treating this as if this is just a regular clip that I want to adjust.
 
I'm also aware that each edit done like this is a destructive process that will introduce more artefacts and ideally I would still have the un-bounced Region FX clip that I could just re-adjust. I'm not really debating the sound quality of the clip after doing multiple generations of editing like this on it - it's subjective - but more so that I *should be able* to do this stuff if I feel I want to.
 
If I CTRL+M this clip, Melodyne will attempt to start up, it'll show in the Undo history that I've added Melodyne but nothing actually activates.
 
How I see it is that if you bounce any clip down to a new clip (either to commit any effects, edits or Region FX to it), that clip should actually be seen by SONAR as just another WAV that you can do further editing to, as if it was a recorded WAV rather than a bounced one.
 
But what I'm experiencing is that any bounced clip that no longer has a "Record nnn" name will fail to activate any new instances of Region FX when you try to add them.
 
As I mentioned, I really do suspect this is isolated to my machine, so if someone would like to give this a go to see if it works as intended for you, that'd be awesome 

yeah, I here you. I do this all the time, the exact process you just described. I always bounce down my melodyne clips to a new wav, and then later, if needed, I go back and open Melodyne again to do further edits on the same clip, with no problems. You should be able to do that without a problem. I do remember that happening once or twice in Sonar X3e. I don't remember what I did to work around it. I think I wasn't too much farther along in my editing, so I could go back and undo the region fx and open Melodyne and redo the original edits, plus the new ones I needed to do.  Sorry, not sure what advice to give you at this point.

Lord Tim
Hey guys,
 
Let me explain more of what I'm doing, and I'll use Melodyne and a vocal track as the example.
 
I get my vocal track recorded. On the track, I can clearly see "Record nnn" for each take in the clip header. Nothing on there has been bounced to new clips or anything, just regular recording/edits.
 
I go through the clip and find certain phrases that might need some pitch correction, so I select that portion and do CTRL+M to load up Melodyne. Adjust as needed. You can clearly see that each one of those clips have Region FX in the clip header.
 
My machine is getting on a bit (this is being polite to it) so after about 4 or 5 edits, I prefer to go back in and bounce each Region FX clip to a new clip. If I don't do this then SONAR starts to become unstable for me. It's an acceptable workaround for me considering the low specs of the machine.
 
So I'll have a track which has the named "Record nnn" untouched takes with the bounced sections in there which no longer have any filename in the clip header.
 
I finish what I'm doing, listen back to the track as a whole and I think "You know, that first clip I adjusted could have been better" so I go to the bounced clip, do CTRL+M to activate Melodyne so that I can do some more work on it.
 
Things that I'm aware of at this point:
 
Since it was bounced, this is a NEW clip, so therefore it's got no Region FX on there that are editable (as you would have if you went to re-edit an existing Region FX clip) - I'm treating this as if this is just a regular clip that I want to adjust.
 
I'm also aware that each edit done like this is a destructive process that will introduce more artefacts and ideally I would still have the un-bounced Region FX clip that I could just re-adjust. I'm not really debating the sound quality of the clip after doing multiple generations of editing like this on it - it's subjective - but more so that I *should be able* to do this stuff if I feel I want to.
 
If I CTRL+M this clip, Melodyne will attempt to start up, it'll show in the Undo history that I've added Melodyne but nothing actually activates.
 
How I see it is that if you bounce any clip down to a new clip (either to commit any effects, edits or Region FX to it), that clip should actually be seen by SONAR as just another WAV that you can do further editing to, as if it was a recorded WAV rather than a bounced one.
 
But what I'm experiencing is that any bounced clip that no longer has a "Record nnn" name will fail to activate any new instances of Region FX when you try to add them.
 
As I mentioned, I really do suspect this is isolated to my machine, so if someone would like to give this a go to see if it works as intended for you, that'd be awesome 

Ok... I'll try to do this tonight when I have access... Yes, it should be able to open the new clip as a Melodyne region... Though it would not have your old Melodyne edits available...

I think I would opt to freeze the track instead of bouncing the clips at this point, then bounce the clips after I'm happy with them all... Freeze dies work for this (afaik) though people have told me I'm not supposed to do this... At least that way your edits are still available and you don't have to repeat them... Or as I mentioned earlier, i clone the melodyned track then archive and hide it so I can return to the edits.... My preference these days...

Keni

You mentioned that the new clip has no name? I'm just wondering if this is part of the problem, perhaps causing ARA to fail. If you give the clip a name, will it work?
Still don't know why it ends up nameless in the first place, I haven't checked if it does for me...