Is this really how SOLO should work?

Author
Post
Essentials Only Full Version
lfm
Max Output Level: -53 dBFS
  • Total Posts : 2216
  • Joined: 2005/01/24 05:35:33
  • Location: Sweden
  • Status: offline
2015/03/31 10:14:58 (permalink)

Is this really how SOLO should work?

Track #1 - audio, no sends
Track #2 - audio, pre fader send
Track #2 - audio, post fader send
ReverbBus - target for sends above
all above to master
 
Scene #1:
Solo T1 - T1 and T2 pre fader send to ReverbBus audible - not expected?
Rest normal
 
Scene #2:
Solo T2 - T2 and T2 pre fader send to ReverbBus audible - expected!
Rest normal

 
Scene #3:
Solo T3 - T3 and T2 pre fader send, and T3 post fader send to ReverbBus audible - expected!
Rest normal
 
Scene #4:
Solo override ReverbBus - T2 pre fader send send to ReverbBus audible - expected!
Rest normal
ReverbBus audio goes out to master - without Master soloed - not expected.
But not main track outs does not go out - without Master soloed - expected.
 
Scene #5:
As #4 active - Solo override
No matter what you try to Solo T1, T2 or T3 - there is no difference in sound - not expected! 
But also adding Solo override to Master - then i works as expected soloing the tracks.
 
Scene #6:
Soloing one or several tracks, leaving busses alone - this seems to have changed?
You don't have to solo busses like Master or effect bus - they are audible.
 
Scene #7:
Soloing Master bus - nothing changes in audio - this seems to have changed?
You don't have to solo busses like Master or effect bus - they are audible.
 
Scene #8:
Soloing ReverbBus bus - Mute does not work on main tracks, not even sends are muted - not expected!
You don't have to solo Master - it's are audible, just soloing ReverbBus.

 
I guess the core is that pre fader send always audible, unless T2 muted.
And Solo override seems to work system global only solo - whatever else is soloed.
 
This must be a bug, or?
Thinking both how pre-fader sends work and solo override?
And see no difference really, if using solo override or just solo - maybe there is difference if using global solo stuff.
 
Please try this at home 
Did I forget anything, please let me know.
 
Thanks.
post edited by lfm - 2015/03/31 10:59:24

Cubase Pro 9 with SA2015 as backup - W7 i7 2.8GHz 16G GeForce GT 730 - RME HDSP 9632 + AI4S
#1

8 Replies Related Threads
    Doktor Avalanche
    Max Output Level: -32.5 dBFS
    • Total Posts : 4294
    • Joined: 2015/03/26 18:02:02
    • Status: offline
    Re: Is this really how SOLO should work? 2015/03/31 12:11:50 (permalink)
    Confirm you are running Cambridge and not using drum maps...?
    #2
    bitflipper
    01100010 01101001 01110100 01100110 01101100 01101
    • Total Posts : 26036
    • Joined: 2006/09/17 11:23:23
    • Location: Everett, WA USA
    • Status: offline
    Re: Is this really how SOLO should work? 2015/03/31 12:15:57 (permalink)
    Soloing a track is equivalent to turning down the volume fader on all other tracks. Track 2's reverb send is pre-fader.


    All else is in doubt, so this is the truth I cling to. 

    My Stuff
    #3
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: Is this really how SOLO should work? 2015/03/31 12:28:29 (permalink)
    Without painstakingly addressing each one of your scenarios individually, I think the following addresses most or all of them:
     
    First, solo override works as expected on tracks, but there is a known issue with solo override on buses; it doesn't just prevent that bus from being muted by another bus being soloed; it actually solos the bus.
     
    And second, prefader sends are not muted by muting the track, either directly or by soloing some other track. And soloing a bus implicitly solos all upstream track and buses and downstream buses as well; otherwise you wouldn't ever hear a soloed bus unless it routed directly to hardware outs, and you would loose the contribution of tracks and buses that feed it as well.
     
     

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #4
    lfm
    Max Output Level: -53 dBFS
    • Total Posts : 2216
    • Joined: 2005/01/24 05:35:33
    • Location: Sweden
    • Status: offline
    Re: Is this really how SOLO should work? 2015/03/31 13:18:52 (permalink)
    bitflipper
    Soloing a track is equivalent to turning down the volume fader on all other tracks. Track 2's reverb send is pre-fader.


    I see, good explanation.
    I can just learn that thinking.
     
    But why is mute not like that then - really muting everything from that track?
    Real mess to solo what you want otherwise - having prefader sends.
     
    post edited by lfm - 2015/03/31 13:34:41
    #5
    lfm
    Max Output Level: -53 dBFS
    • Total Posts : 2216
    • Joined: 2005/01/24 05:35:33
    • Location: Sweden
    • Status: offline
    Re: Is this really how SOLO should work? 2015/03/31 13:19:28 (permalink)
    Doktor Avalanche
    Confirm you are running Cambridge and not using drum maps...?

    Yes, Cambridge and no midi stuff at all - just the three audio tracks.
    #6
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: Is this really how SOLO should work? 2015/03/31 13:28:35 (permalink)
    To get pre-fader sends to respond to soloing other tracks, I believe the LinkPFSendMute variable in AUD.ini is supposed to set that feature. See the description in http://www.cakewalk.com/D...I_Files.6.html#1134652
    #7
    lfm
    Max Output Level: -53 dBFS
    • Total Posts : 2216
    • Joined: 2005/01/24 05:35:33
    • Location: Sweden
    • Status: offline
    Re: Is this really how SOLO should work? 2015/03/31 13:29:18 (permalink)
    brundlefly
    Without painstakingly addressing each one of your scenarios individually, I think the following addresses most or all of them:
     
    First, solo override works as expected on tracks, but there is a known issue with solo override on buses; it doesn't just prevent that bus from being muted by another bus being soloed; it actually solos the bus.
     
    And second, prefader sends are not muted by muting the track, either directly or by soloing some other track. And soloing a bus implicitly solos all upstream track and buses and downstream buses as well; otherwise you wouldn't ever hear a soloed bus unless it routed directly to hardware outs, and you would loose the contribution of tracks and buses that feed it as well.
     

     
    I found doing exclusive solo - then solo override have a function staying alive - not otherwise.
    If you use solo or solo override is the same doing cumulative solo.
     
    But as you said, activating should not solo anything.
     
    Good confirmation about soloing busses. 
     
    post edited by lfm - 2015/03/31 13:37:02
    #8
    lfm
    Max Output Level: -53 dBFS
    • Total Posts : 2216
    • Joined: 2005/01/24 05:35:33
    • Location: Sweden
    • Status: offline
    Re: Is this really how SOLO should work? 2015/03/31 13:32:58 (permalink)
    scook
    To get pre-fader sends to respond to soloing other tracks, I believe the LinkPFSendMute variable in AUD.ini is supposed to set that feature. See the description in http://www.cakewalk.com/D...I_Files.6.html#1134652


    Excellent if  you can configure this - thanks.
     
    EDIT: I found that setting in the list in preferences even - and it did the trick. How lovely, now it's all intuitive to me. Fixed both mute and solo to also mute the sends from tracks that are not audible.
    post edited by lfm - 2015/04/01 02:55:19
    #9
    Jump to:
    © 2025 APG vNext Commercial Version 5.1