[Glitch?] No Audio Unless Track Is Soloed!

[sjoens]

When project is played with no tracks muted or soloed, only MIDI tracks to outboard synths can be heard.

No Audio or Softsynths produce sound or meter activity unless they are soloed.

Only way to hear all tracks play together is to solo every track.

Same project that reverses Hardware Outputs mentioned in another post.

Only affects this project and any sequential projects saved after it.

 

Edited January 1 by sjoens

[Starship Krupa]

Does your Mix module indicate that there are any tracks solo'd? Was thinking maybe you have hidden tracks?

[sjoens]

No and these tracks are not hidden. Something under the hood got it's wires crossed. 

[sjoens]

Thought maybe a Take Lane was soloed but checked them all and that shouldn't affect it anyway unless it's main track is also soloed.

[David Baay]

Share the project?

[sjoens]

Weird. Today it's working so sharing may not help. The Main Outs are still crossed, but that doesn't affect performance.

[Starship Krupa]

Yeah, I think Cakewalk sometimes gets its routing....confused. I put MRhythmizer on a track last night, then stopped messing with it and put another instance on a bus (which the first track was not assigned to). I solo'd the bus and the track with MRhythmizer was also audible (and affected by MRhythmizer).

It stayed that way even after I deleted the first instance of MRhythmizer. So a track without the effect on it was being effected. I was able to clear it by deleting the second instance, quitting the project, relaunching, and then putting MRhythmizer back on the bus. It was weeeeird.

[Steven Duncan]

Just had this same problem. This is what worked for me.

Open the Console Panel.

Click on Strips.

Open the Track Manager.

Look at the list of tracks and see if any say "Solo'd" beside them. I had about 6 showing solo'd but they were NOT showing solo'd in the console or anywhere else.

On the Console Panel, go to each track that shows solo'd in the track manager. Solo it, then unsolo it.

Do this for each of the secretly solo'd tracks.

After I solo'd/unsolo'd the sixth one, my sound came back.

[David Baay]

2 hours ago, Steven Duncan said:

Just had this same problem. This is what worked for me.

If you still have a copy of the original un-fixed project, you should share a copy with the Bakers to investigate. They may not be able to get at the root cause if you can't identify the steps that got it into that state, but they might still be able to implement a fix that would make the state impossible.

[sjoens]

Good to know tho if it happens again here probably won't remember to check.  For me these are one-time-only glitches.

There's another SOLO/MUTE glitch that happens all the time in CbB:  In PRV clicking solo or mute on either of a paired synth/MIDI track results in the other one not responding "visually" to the changes until the mouse hovers over it.  Clicking one should affect both.  Not sure about new Sonar.

Edited January 1 by sjoens