Control Surface question

Author
watercourse
Max Output Level: -90 dBFS
  • Total Posts : 9
  • Joined: 2014/12/20 08:09:48
  • Status: offline
2015/04/04 09:55:03 (permalink)

Control Surface question

I just installed a Presonus Faderport and noticed some unexpected behavior.  It operates in both track and bus sections (tracks work perfectly), however it's faders will not follow a mouse-selected bus in Platinum.  Also, when the Faderport scrolls through busses, its fader moves correctly with each bus change, however Sonar doesn't bring Faderport's selected bus into focus.  To troubleshoot, I tested this behavior in X3 (32 and 64 bit) and also using the software controller TouchDAW and the behavior was the same so I'm assuming it's not just an issue with the Faderport. 

Does anyone know if this is normal expected behavior, a setting I missed somewhere or a known/unknown bug?  Thanks in advance!
#1

3 Replies Related Threads

    John
    Forum Host
    • Total Posts : 30467
    • Joined: 2003/11/06 11:53:17
    • Status: offline
    Re: Control Surface question 2015/04/04 10:02:50 (permalink)
    I use a Mackie Control and it is touch sensitive. There is also a channel select button on each channel. As to the buses there is a buss switch that will let one control the buses. The master buss has its own fader.  
     
    I think the fader port will need to have some kind of selection button for selecting tracks and buses.  

    Best
    John
    #2
    azslow3
    Max Output Level: -42.5 dBFS
    • Total Posts : 3297
    • Joined: 2012/06/22 19:27:51
    • Location: Germany
    • Status: offline
    Re: Control Surface question 2015/04/04 11:26:41 (permalink)
    Selecting strip from surface (any) while really makes it current, does not always show that in SONAR. If you click on some track and then select some bus on surface, SONAR still focus the track. There is a command to switch to the bus view, but it is not reliable. So I think that is a bug. Note that different surfaces are using different API calls, so some can produce "more buggy" result as other.

    Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro
    GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB
    RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc.
    www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
    #3
    watercourse
    Max Output Level: -90 dBFS
    • Total Posts : 9
    • Joined: 2014/12/20 08:09:48
    • Status: offline
    Re: Control Surface question 2015/04/04 16:16:29 (permalink)
    Thanks for the replies. Just to clarify, the Faderport does have a bus switch and it does work to scroll and control bus volumes. Below is a rundown of the differing actions and behaviors I'm seeing between the track and bus panes using the control surface.
     
    Track Pane
    A. click on any single track in Sonar and the Faderport fader moves and now controls that track
    B. scroll through tracks using Faderport and Sonar brings focus to each track as it's passed
     
    Bus Pane (Faderport bus switch is selected)
    A. click on a single bus in Sonar and the Faderport fader doesn't move or respond
    B. scroll through buses using Faderport and Sonar's WAI moves through each bus but Sonar's selected bus never changes
     
    I guess I'm trying to find out first if the behavior I'm experiencing is normal or if Sonar is capable of mirroring the behavior of A and/or B from the Track pane within the Bus Pane.
    #4
    Jump to:
    © 2025 APG vNext Commercial Version 5.1