Loading project doesn't load faders on Control Surface

Author
Post
Essentials Only Full Version
bonesjones
Max Output Level: -90 dBFS
  • Total Posts : 6
  • Joined: 2016/03/16 20:24:31
  • Status: offline
2016/03/16 20:46:38 (permalink)

Loading project doesn't load faders on Control Surface

Hello everyone , if this is the wrong place to post this please forgive me and i'll move it. I've never posted on this forum. I'm running Sonar X2 producer. 
 
I have a Soundcraft Spirit 328 that i've been using for a couple years as my interface for track recordings. 
Well I knew that if i put work into it i could use it as a control surface as well. 
 
With several hours of tinkering with ACT learning I've been able to get the faders to work perfectly with Sonar. I'm loving it actually, my only problem that I'd like to fix if possible is that when I load a project the faders don't move to where they are on the mixer. But if i move the fader on the real mixer then it jumps right to where the slider is on my real board. 
 
In the mean time when I load a project i have to look at each slider and say, ok Track 1 is on -2.8db so i move that slider to that spot and then i have to go through each track. This gets really annoying when I have more than 16 tracks as when i move the control surface to a different set of tracks I have to repeat the process. And then back again when i wanna move back. 
 
Is there anyway to have Sonar send the right MIDI messages to my control surface to auto move the sliders to where they should be to match what the project is? 
#1

6 Replies Related Threads
    azslow3
    Max Output Level: -42.5 dBFS
    • Total Posts : 3297
    • Joined: 2012/06/22 19:27:51
    • Location: Germany
    • Status: offline
    Re: Loading project doesn't load faders on Control Surface 2016/03/17 05:59:29 (permalink)
    (My answer is based on Spirit Digital 328 Users Guide, I do not have the device)
     
    Related to Control Surface functionality (so, no automation writing, SysEx, recall, etc).
    Spirit does not support MackieControl, the only common bi-directional protocol supported by Sonar. ACT MIDI and Generic Surface are unidirectional (they are not sending values back to the controller). There is only one known way to make that work, my AZ Controller plug-in (see the signature). It is free, but it is not easy to configure. Be prepare to invest some time.
     
    There are 2 possibilities:
    1) you can try to do it yourself. Road map:
    * Spirit should be in "Read/Write Automation Mode" (I mean not in "Write only" and not in "Update").
    * Follow "Installation instructions" and "Quick start" from "Documentation" section.
    * Make "Generic Startup preset" from "Presets" section running. I am not sure, but in case encoders on Spirit send encoders messages (not continuous values like simple knobs), you will need to change "Value" Action option for them from "Direct" to "Endless". Note, you still get no feedback at that point.
    * Switch to "Feedback", select "S1 Fader :: Parameter Value Monitor", add "New" (button) action, "Move up" (button) to make it first, configure it as (change "Undefined" to) "MIDI", (change "CC" to ) "<Use Ctrl MIDI>", value (change "0" in the first box to) "Value".
    * Your first Fader should have "Feedback" now ( moved when you move the fader in Sonar, on Project load and automation). If not, recheck mode on Spirit, "Output" in Sonar preferences and parameters in the previous step.
    * "Copy" the action and "Paste" it ("Move Up" to make it first, not really required, just for aesthetic...) to all Faders feedbacks.
     
    All that sounds complicated, but it will take less time for me to complete all steps then for writing this post
     
    And so option...
    2) contact me to organize TeamViewer session for 15-30 minutes and we will make it running together.
     

    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
    #2
    bonesjones
    Max Output Level: -90 dBFS
    • Total Posts : 6
    • Joined: 2016/03/16 20:24:31
    • Status: offline
    Re: Loading project doesn't load faders on Control Surface 2016/03/18 05:29:34 (permalink)
    Dude that would be so awesome of you!!!

    I'll try my best to use your steps and figure it out. I spent hours getting it to do what it's doing right now so I think I can figure it out. if not I'll pay you for your help.
    #3
    azslow3
    Max Output Level: -42.5 dBFS
    • Total Posts : 3297
    • Joined: 2012/06/22 19:27:51
    • Location: Germany
    • Status: offline
    Re: Loading project doesn't load faders on Control Surface 2016/03/18 06:45:08 (permalink)
    If you are ready to spend hours, I can recommend to follow my "ACT MIDI Explained" tutorial. Also read the manual to imagine what is possible.
     
    Still I think it is better to have running basic setup from the beginning. You can adjust, add functionality, etc. later. So in case you are unable to follow my instructions within one (!) hour, please let me help you with that.
     
    The project is not commercial, my help will cost you nothing. As Craig has mentioned several times in the forum, music software industry is driven almost by interest, not by money.  If you multiply the time I spent to make AZ Controller by my usual salary and divide the result by number of "users"... each user could probably get MCU Pro plus 2 extenders for the sum. That does not make commercial sense at all.
    Today I am doing "yearly check" for my car (far from new, not luxury), nothing broken, just routine. And that cost more than Sonar Platinum (listed full price for new users), crazy world...

    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
    #4
    bonesjones
    Max Output Level: -90 dBFS
    • Total Posts : 6
    • Joined: 2016/03/16 20:24:31
    • Status: offline
    Re: Loading project doesn't load faders on Control Surface 2016/03/23 19:21:15 (permalink)
    I just got back from a vacation so tonight i'm going to work on this. Without anythings i've figured out how to transmit the MTC and get the play and stop buttons to work properly. As well as what i mentioned in my original post. I'm one of those "I'd rather spend 10 hours figuring it out then one hour having it done for me." I like to understand why i'm doing what i'm doing. :) 
    #5
    bonesjones
    Max Output Level: -90 dBFS
    • Total Posts : 6
    • Joined: 2016/03/16 20:24:31
    • Status: offline
    Re: Loading project doesn't load faders on Control Surface 2016/03/23 19:48:39 (permalink)
    I've gotten everything working however nothing shows up in the feedback tab. 
    I've read as carefully as I can. I think if i can just get the feed back working i'll be set. 
     
    BTW i wish i had known about this plugin before i spent hours messing with ACT. Why Sonar couldn't develop something this simple is beyond me. :) 
     
    #6
    bonesjones
    Max Output Level: -90 dBFS
    • Total Posts : 6
    • Joined: 2016/03/16 20:24:31
    • Status: offline
    Re: Loading project doesn't load faders on Control Surface 2016/03/23 23:29:41 (permalink)
    Yeah man, I give up, doesn't matter what I do I can't get any options from the feedback tab. They're all just grayed out. I've fought the good fight but I'm admitting defeat on this one. 
    #7
    Jump to:
    © 2024 APG vNext Commercial Version 5.1