Automation not being read [Kinda solved but still a bit freaky].

Author
Grumbleweed_
Max Output Level: -72 dBFS
  • Total Posts : 915
  • Joined: 11/1/2007
  • Location: Southampton, England
  • Status: offline
January 01, 14 3:00 PM (permalink)

Automation not being read [Kinda solved but still a bit freaky].

Happy New Year etc, now onto the problem:
 
I have a reasonably large track on the go that has gone a bit weird.
I've added a soft synth to finish off the track. That works fine. I first added a Pod Farm (Elements) Delay in the FX bin and automated the mix and feedback (using the "W") and my mouse. I could see the written automation but the dials wouldn't move to match what was happening on screen when the project was played back.
I tried the VKFX Delay and did the same thing. The dials will not move.
If I manually move the timeline indicator along the automation curve the dial will move to the correct position but playback from that point will not make the dial move away from where it last sat.
 
If I create another VKFX Delay on a track made earlier it works fine, as do any existing automations. It's just this new track.
Any ideas?
 
Grum.
 
post edited by grumbleweed4162 - January 02, 14 2:41 PM

Grumbleweed on Soundcloud
Grumbleweed on Bandcamp
Grumbleweed on Soundclick

Windows 10 Pro (64 bit), 3770K i7, 8 GB ram, Focusrite Saffire Pro 14, Cubase 9.5, Reason 10, CbB.
#1

8 Replies Related Threads

    FastBikerBoy
    Forum Host
    • Total Posts : 11326
    • Joined: 1/25/2008
    • Location: Watton, Norfolk, UK
    • Status: offline
    Re: Automation not being read. January 02, 14 2:44 AM (permalink)
    Two possibilities. "Read" is turned off, either globally (in the mix module) or on a per track basis. If the "R" widget is dull in either it is off, highlighted is on.
     
    The other possibility is that you are in "Offset" mode. There is an indicator in the mix module as well as a "+" beside the volume and pan controls.
     
    It is easy to accidentally enter offset mode by pressing "O" on the qwerty and can cause much confusion.
     
    If it is offset mode the changes should still be audible but not seen visually, if read is off changes won't be audible or visual either.
     
    HTH
    #2
    Grumbleweed_
    Max Output Level: -72 dBFS
    • Total Posts : 915
    • Joined: 11/1/2007
    • Location: Southampton, England
    • Status: offline
    Re: Automation not being read. January 02, 14 3:14 AM (permalink)
    Cheers for the reply. Unfortunately/fortunately I know about how it should work and the "normal" reasons it wouldn't work if they applied.
    At the moment my theory is it something to do with creating a synth and then replacing it as that is the only thing that is different to the problem track from those that have come before (and all work perfectly well).
    I'll experiment later but I have to take my wife to hospital very soon - there are always things that get between a man and his music!
    I'll be back.

    Grum.

    Grumbleweed on Soundcloud
    Grumbleweed on Bandcamp
    Grumbleweed on Soundclick

    Windows 10 Pro (64 bit), 3770K i7, 8 GB ram, Focusrite Saffire Pro 14, Cubase 9.5, Reason 10, CbB.
    #3
    Soft Enerji
    Max Output Level: -86 dBFS
    • Total Posts : 203
    • Joined: 11/25/2010
    • Location: Lismore, Northern Rivers, NSW, Australia
    • Status: offline
    Re: Automation not being read. January 02, 14 3:36 AM (permalink)
    grumbleweed4162
    Cheers for the reply. Unfortunately/fortunately I know about how it should work and the "normal" reasons it wouldn't work if they applied.
    At the moment my theory is it something to do with creating a synth and then replacing it as that is the only thing that is different to the problem track from those that have come before (and all work perfectly well).
    I'll experiment later but I have to take my wife to hospital very soon - there are always things that get between a man and his music!
    I'll be back.

    Grum.

    OT...........I hope she don't read this post Grum :-) And I hope all is well!

    i7-3820 3.6Ghz Processor. 32Gb DDR3 RAM. GTX660 Graphics Card. M-Audio Fast Track Pro.
    Soft Enerji Soundcloud
    Soft Enerji Bandcamp
     
    #4
    FastBikerBoy
    Forum Host
    • Total Posts : 11326
    • Joined: 1/25/2008
    • Location: Watton, Norfolk, UK
    • Status: offline
    Re: Automation not being read. January 02, 14 4:01 AM (permalink)
    You may well need to reassign the envelope if you've changed synths.
    #5
    Grumbleweed_
    Max Output Level: -72 dBFS
    • Total Posts : 915
    • Joined: 11/1/2007
    • Location: Southampton, England
    • Status: offline
    Re: Automation not being read. January 02, 14 5:07 AM (permalink)
    FastBikerBoy
    You may well need to reassign the envelope if you've changed synths.


    I changed the synth prior to adding the delay but it is the only thing I can think of that is different.
    When I'm back home I'll create a new synth and add the delay and see what happens. If it doesn't work then I'm stumped but if it does then my theory will be sound (but it's not a cool thing to happen).

    I will be using the offset mode later to drop all of my levels so this problem has at least bought the "O" shortcut to my attention. I wasn't aware of it until I started to research last night and found an old post (X1) where it was suggested it could be a part of a similar problem with automation.

    Grum.

    P.S. To Mr.Softy

    Thanks for your concern! There isn't much I can still say or do that would shock/offend my wife so I'm on reasonably safe ground. She has just been called in to the guy we are here to see and we have another appointment at a different hospital in 4 hours time for a separate problem. Great fun.

    Grumbleweed on Soundcloud
    Grumbleweed on Bandcamp
    Grumbleweed on Soundclick

    Windows 10 Pro (64 bit), 3770K i7, 8 GB ram, Focusrite Saffire Pro 14, Cubase 9.5, Reason 10, CbB.
    #6
    Grumbleweed_
    Max Output Level: -72 dBFS
    • Total Posts : 915
    • Joined: 11/1/2007
    • Location: Southampton, England
    • Status: offline
    Re: Automation not being read. January 02, 14 1:02 PM (permalink)
    Well I tried adding a new synth track and the delay but it won't automate (well, it will write but not read) yet I can add and automate the delay in any previous track (synth or audio).
    I give up

    Grum.

    Grumbleweed on Soundcloud
    Grumbleweed on Bandcamp
    Grumbleweed on Soundclick

    Windows 10 Pro (64 bit), 3770K i7, 8 GB ram, Focusrite Saffire Pro 14, Cubase 9.5, Reason 10, CbB.
    #7
    Anderton
    Max Output Level: 0 dBFS
    • Total Posts : 14070
    • Joined: 11/6/2003
    • Status: offline
    Re: Automation not being read. January 02, 14 1:54 PM (permalink)
    Just out of curiosity, which synth?

    The first 3 books in "The Musician's Guide to Home Recording" series are available from Hal Leonard and http://www.reverb.com. Listen to my music on http://www.YouTube.com/thecraiganderton, and visit http://www.craiganderton.com. Thanks!
    #8
    Grumbleweed_
    Max Output Level: -72 dBFS
    • Total Posts : 915
    • Joined: 11/1/2007
    • Location: Southampton, England
    • Status: offline
    Re: Automation not being read. January 02, 14 2:19 PM (permalink)
    Anderton
    Just out of curiosity, which synth?




    You, sir, are a clever man. I didn't think it could be the synth causing the problem as the delay I'm adding is a separate entity but, lo and behold, it is!
    The one with a problem is an Alchemy (Player) but replacing with a Dim Pro made the delay automation work again.
     
    What I'll do is create a send and automate the delay on the new bus.
    Thanks for making me look deeper into this .
     
    Grum.
     
    Edit:
    Well that was a shocker. Even adding a delay to a bus being fed by the Alchemy channel's send won't work!!!
    The solution is to freeze the Alchemy track and then the delay's automation works.
    You couldn't make this stuff up.
    post edited by grumbleweed4162 - January 02, 14 2:39 PM

    Grumbleweed on Soundcloud
    Grumbleweed on Bandcamp
    Grumbleweed on Soundclick

    Windows 10 Pro (64 bit), 3770K i7, 8 GB ram, Focusrite Saffire Pro 14, Cubase 9.5, Reason 10, CbB.
    #9
    Jump to:
    © 2025 APG vNext Commercial Version 5.1