Layers - Mute Previous Takes is "Ghosting" Waveform

Greetings all,
X1 Layers seems a tad buggy compared to 8.5.3, eh?

We tried "auto punch" mode on entire tracks with Layers turned on, and "mute previous takes" selected.

When the takes were done, all previous takes were "ghosted" - outlined waveforms as if the Mute tool had been used.

This did not happen on 8.5.3, and it was easy enough to un-mute or solo layers on a track with the tiny "M" or "S" buttons next to each layer - directly after recording.

Now you have to change tools, grab the Mute tool, and "un-mute" the layer before you can listen to it.

Using the clip menu Mute/UnMute", "K" hot-key, or mini Mute/Solo in each track layer does not work on the ghosted waveform.

I've looked through the X1 Reference Guide, Scott's wonderful "Sonar X1 Power" as well as searched this forum and have found nothing on this.

Anyone know how to "un-ghost" all previous layers in a track without going layer-by-layer with the Mute tool?

OR BETTER YET - 
Is there a way to "mute previous takes" that only mutes during record, but leaves the waves in each previous layer un-ghosted, yet muted - LIKE IN 8.5.3 ??!!

Thank you for your time and input,
MG

Thanks for the reply FastBikerBoy.

My apologies for not being clear in my original post -

"Using the clip menu "Mute/UnMute", "K" hot-key, or mini Mute/Solo in each track layer does not work on the ghosted waveform. "


By "ghosting", I mean that the previous takes' waveforms show the dotted outline of the waveform.


You see this "ghosting" when you comp layers in a track with the Mute tool.
The tracks you don't want are ghosted/muted when you press the control key and drag the Mute tool under the section of layer that you DO want.


Examples of this are in the references guide and Sonar X1 Power "Layers" sections.


The solid waveforms were retained in Sonar 8.5.3 with "mute previous takes" selected.


But the layer Mute buttons on previous takes were all engaged. To hear previous takes you simply clicked the layer Solo or Mute buttons to change the take you heard. Easy enough, right?


This is different.


It's as though I comp'ed the last take and ghosted all of the other previous takes...

The only way to now listen to previous takes is to go grab the Mute tool from the toolbox, unmute each and every previous take, THEN use the layer Mute and Solo buttons to then listen to each take.


It's added several extra steps over the workflow in 8.5.3!


Also, in 8.5.3, I did not have to select the entire track as a "punch-in/punch-out" points.
We simply turned layers on, selected "mute previous takes", and hit record. It worked flawlessly.


This hiccup in X1 Producer is all taking place in the x64 Sonar X1 Producer (X1c) running on Vista Ultimate (x64).


I hope to try opening the project in XP Pro (x86) Sonar Producer X1c (x86) later this evening to see if I get the same response.


Thanks again for any and all ideas.


Regards,
MG

Thank you for the verification dke!

I just submitted this to Cakewalk.

Hopefully I don't get the dreaded "we can't verify this" reply and we actually see a fix in the next rev of X1 Producer...

...After last night with a client watching X1's bugs in their full glory, I'm considering moving back to 8.5.3... 

At least there it was an occasional OS seizure (Vista white screen) and easily fixed with a reboot of the system...

Cheers,
MG

O.K. Kids, for those who are interested -

Here's a response from Cakewalk's Tech Support on this topic: "In our tests, the only way we were able to have the notes become "ghosted" (partially muted) is if the Clip Boundaries extend beyond the Punch Boundaries. In other words, if the clip in a layer went from measure 1 to measure 10, but the Punch Region only went from measure 1 to measure 5, when recording a new take measure 1 to measure 5 of the original clip would be muted (or "ghosted"). Likewise, if the Punch Boundary only lasted from measure 4 to measure 5, only this measure of the original clip would become muted. This duration of the partial mute of the clips present is determined by the Punch Boundaries.

This behavior is the same in SONAR X1 and SONAR 8.5.

If you try extending your Punch Region beyond the start & end points of your clips in the track, then it should "mute" the entirety of the clips in the layer as opposed to a selected portion of the clip. So, if you extend the punch region you should be able to speed up your workflow without having to use the Mute tool over portions of audio clips. Instead you should be able to just select clips and use "K" to mute or unmute them."

Though...if the clip extends beyond the punch...isn't that how it usually works when doing a punch in of just a section in a song?

What about subsequent loops?  Would they be ghosted?

...AH-HAH!
That's it -

We started a new punch each time - we did not loop.

By starting a new punch, and not over-lapping the clip, we ghosted each previous take.
(dke - I'm assuming that your punch did not fully overlap your clip too?)

I'll be if we had LOOPED instead, it would have ghosted the first take, but muted previous takes...

I hope to try this tonight.
Now I need to go back to older projects to see why we did not see the ghosting in 8.5.
...I'll be it was looped and not re-started on each pass...ghosting only the original take, but not successive takes.

Whew!
Ain't technology great - when ya' know how to USE IT??!!

Thanks to FastBikerBoy and dke for taking the time to respond.
(And to you dke for taking the time to verify what I was seeing.)

MG

I'll have to check on 8.5 as well, but I sure don't remember ever having to grab the mute tool to unmute portions of takes while I was punching-in and I have used both looping & starting each take manually.  I hadn't actually done any punching-in with X1 until testing the other night after reading your problem.

Dan