Post Fader Send Panning-Unexpected Results

Author
Post
Essentials Only Full Version
danika
Max Output Level: -88 dBFS
  • Total Posts : 127
  • Joined: 2004/10/09 01:09:20
  • Status: offline
2011/04/27 13:22:08 (permalink)

Post Fader Send Panning-Unexpected Results

I was getting some strange results with panning, so I did this simple test.

1) Created a track with a stereo sine wave
2) Created an aux bus and a post-fader send from the track to the bus
3) Panned the track left and then right (using the track pan, not the send pan).

The output of the aux bus stayed in the center.  It did not move with the track panning.  The Sonar signal flow diagram clearly shows that post-fader sends are routed post track panning.  What am I missing?


#1

7 Replies Related Threads
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Post Fader Send Panning-Unexpected Results 2011/04/27 13:50:59 (permalink)
    If there's a plug-in on the aux bus, it's probably not processing the channels indepedently, so the output is mixed. Disable the plug, and you should see the send panning reflected in the bus output.

    EDIT: Just remembered you're talking about panning the Track not the Send. I'll have to check the signal flow, but I think what you're seeing is working as designed. I've had to group the Send Pan with the Track Pan in the past to make them pan together.


    EDIT 2: I just checked the Sginal Flow diagram, and Post-fader send is shown after Pan, but it alos shows Pre-fader send before Mute and Solo buttons, yet they affect the Pre send by default.

    I noticed it said there was an AUD.INI parameter (LinkPFSendMute=0) for changing whether M/S buttons affect Pre-fader Sends, so I looked in AUD.INI, and found another parameter called LinkSendPan=0 right above it. 

    I bet if you change that to LinkSendPan=1, you'll have the behavior you want.


    EDIT 3: Hmmm... maybe not. I just tried LinkSendPan=1, and it did not have the expected effect. Not sure whether it's broken/not implemented, or I just misinterpreted the intent. I'll have to research more when I get a chance.

    post edited by brundlefly - 2011/04/27 14:17:59
    #2
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Post Fader Send Panning-Unexpected Results 2011/04/27 14:31:26 (permalink)
    Okay. Time for a new post. I found a post from way back in '04 describing the functionality of the LinkSendPan parameter. It is as I thought, but appears not to be working any longer. This post says it was implemented as far back as Cakewalk 6.01, and was originally  defaulted to 1:

     http://forum.cakewalk.com/fb.ashx?m=175342
    #3
    John
    Forum Host
    • Total Posts : 30467
    • Joined: 2003/11/06 11:53:17
    • Status: offline
    Re:Post Fader Send Panning-Unexpected Results 2011/04/27 16:44:13 (permalink)
    I wonder why sends have their own pan?

    Edit to add;
    Page 812 of the manual.

    Set the Send Pan to be the same as
    the bus that the send feeds into

    Right-click the Send Pan control and choose Follow Track Pan from
    the pop-up menu. This setting is only active when the send has the
    same interleave as the bus that the send feeds into, and is set to Post
    Fader. If enabled, the Send Pan control no longer affects the output
    post edited by John - 2011/04/27 16:58:38

    Best
    John
    #4
    bitflipper
    01100010 01101001 01110100 01100110 01101100 01101
    • Total Posts : 26036
    • Joined: 2006/09/17 11:23:23
    • Location: Everett, WA USA
    • Status: offline
    Re:Post Fader Send Panning-Unexpected Results 2011/04/27 17:41:25 (permalink)
    This setting is only active when the send has the same interleave as the bus that the send feeds into

    I was unaware that an aux send even had an interleave setting of its own. Perhaps this is a typo, and what the author meant to say was "when the track interleave is the same as the destination bus".

    This, however, would seem to make the feature pretty useless since all truly pannable tracks are mono, while most destination busses are stereo. And what, exactly, happens when you pan a send to a mono bus?



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

    My Stuff
    #5
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Post Fader Send Panning-Unexpected Results 2011/04/27 17:45:05 (permalink)
    I wonder why sends have their own pan?



    Flexibility?


    Good catch on the context menu option. I wonder how long that's been around? I was thinking it would make more sense for it to be an attribute of each individual send, rather than a global setting as it once was.




    #6
    Noel Borthwick [Cakewalk]
    Cakewalk Staff
    • Total Posts : 6475
    • Joined: 2003/11/03 17:22:50
    • Location: Boston, MA, USA
    • Status: offline
    Re:Post Fader Send Panning-Unexpected Results 2011/04/27 17:58:15 (permalink)
    Follow track pan is a per-send attribute its not global as it once was. Regarding interleave the help article is trying to say that follow track pan or send pan itself only applies if the destination for the send is pannable. i.e. if the destination has an interleave > 1 or is not mono.

    Noel Borthwick
    Senior Manager Audio Core, BandLab
    My Blog, Twitter, BandLab Profile
    #7
    bitflipper
    01100010 01101001 01110100 01100110 01101100 01101
    • Total Posts : 26036
    • Joined: 2006/09/17 11:23:23
    • Location: Everett, WA USA
    • Status: offline
    Re:Post Fader Send Panning-Unexpected Results 2011/04/27 18:19:03 (permalink)
    Thanks, Noel. It makes sense that pan has no meaning on a mono bus.


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

    My Stuff
    #8
    Jump to:
    © 2024 APG vNext Commercial Version 5.1