Hey, Lord Tim - this just happened to me! Or a variation on it:
 
I have a set of double-tracked vocals. I decided to use VocalSynch, for kicks. Worked fine until I got to a set in which I had "bounce to clip" for whatever reason, I don't remember. But the clips had no name (that's how I know I bounced to clip at some point in the recent past).
 
Anyway, for these clips, VocalSynch refuses to "open the editor" or "create the FX Region" or whatever you want to call it. I get the progress bar; the clip flashes, then I'm left back in the Track View with no FX Region, and no editor window.
 
(By "editor window" I just mean the floating control panel with the "intensity" knob.) 
 
If I try a second time, same thing.
 
If I use the Inspector to give the clip a name, it makes no difference. Still no editor.
 
I then saved then entire project to another folder and closed and re-opened SONAR. I successfully opened a V-Vocal "region FX" and made an edit. But VocalSync refuses to open on this clip. I have no idea why.
 

I'm gonna make a wild guess that the region fx look for a clip name, thereby they won't open when they can't find the name...

I'll see if I can test that here tonight too... If this is so, good catch!

Bug it up in the Problem a Reporter as well as post the recipe and workaround in the bug forum...

Good job Tim!

Keni

FWIW I think the reason bounced clips aren't named is because if you bounce multiple clips, the program won't know which of the clip names to adopt. But I can't think of any reason why you wouldn't want an individual bounced track to retain its existing name.

The problem - or my version of it, at least - has nothing to do with the clip name. I have clips created the same way that have no name, and VocalSync works on them.
 
I've been trying to simplify my project to the smallest possible complexity to reproduce the problem, but at some point, I went too far, and the clip-under-scrutiny started allowing VocalSync to work.
 
Unfortunately I did not make interim backups, so I'm doing the process again, checking at each point and saving the project. Now Sonar has "stopped working and looking for a solution" so this may take longer than I hoped.

I've reproduced this issue by reducing the size of my project to minimum, and attaching it to newly submitted problem report, CWBRN-32387.

It's an odd bug, this one.
 
Obviously some people are able to get Melodyne to work with unnamed clips, while I can't, and I'm quite successfully using VocalSync even with unnamed clips while others aren't. There's got to be something that's triggering these different scenarios. Very weird!
 
Craig - I definitely get what you're saying about what each clip should be named, but I do think it should be named *something* rather than just being blank. Even internally, SONAR names bounced clips in the Audio folder (eg: ProjectName,TrackName,Mix-nnn kind of thing), so I think something based on the track name and what iteration of bounce you've done is a good compromise as I mentioned earlier, if you're bouncing multiple clips. If nothing else, it's just one more thing that makes it easier to identify what you've done rather than having to adjust stuff manually.

Anderton
FWIW I think the reason bounced clips aren't named is because if you bounce multiple clips, the program won't know which of the clip names to adopt. But I can't think of any reason why you wouldn't want an individual bounced track to retain its existing name.

I wouldn't want it to retain its exact name. I would like something that lets me know how/why it's different than the original clip of that name...

I've started a feature request thread about this: http://forum.cakewalk.com...r-bounce-m3202902.aspx