Topic: Pre-effect level automation for "audio tracks"?

Viewing 5 posts - 1 through 5 (of 5 total)
  • April 6, 2010 at 17:12 #2183
    thcilnnahoj
    Participant

    I hope I’m missing something. šŸ™

    If I have a track playing an audio file, and some effect on it, the Automate Parameter menu for both the effect track and the actual “audio track” link to automatable parameters on the effect track. Automating pre-effect level separately is certainly possible with an instrument plug-in assigned.

    How do you set up an automation envelope for tracks that have no source mapping assigned? The only way I see is to add a dummy track before the effect, or set up level automation before adding effects, and never dare to touch it!

    April 6, 2010 at 22:03 #17829
    Zynewave
    Keymaster

    Confirmed. It seems like a bug. I’ll look at it before the 2.28 release.

    September 6, 2010 at 16:15 #19419
    thcilnnahoj
    Participant

    Don’t know when this was fixed, but thanks!

    Pre-effect level automation will only be created if the fader is set pre-effects first, though (or by creating it from the source selector right-click menu).

    Add to that, the automate parameter submenu in the right-click track menu always displays parameters for the first effect track, no matter where the fader is set… hmm. What would you think about having additional submenus for all effect tracks’ parameters in the track context menu parameter submenu?

    This way you’d have access to all parameters in the track effect chain when the individual effect selectors are not visible.

    September 7, 2010 at 01:38 #19423
    Zynewave
    Keymaster

    Hmm. I haven’t made any fixes on this issue yet. I still have this topic on my todo list.

    @thcilnnahoj wrote:

    hmm. What would you think about having additional submenus for all effect tracks’ parameters in the track context menu parameter submenu?

    This way you’d have access to all parameters in the track effect chain when the individual effect selectors are not visible.

    I think that can become a bit overwhelming. But I’ll consider it.

    September 7, 2010 at 13:17 #19427
    thcilnnahoj
    Participant

    Really? šŸ˜† Then I didn’t check it properly the first time around.

    When the fader is set post-effects, the automate parameter submenu in the track context menu will always show parameters of the first effect track, no matter on which effect it actually is. That’s why I suggested additional submenus.

    When it’s set pre-effects, and only then, you get parameters of the source track (I’m talking about tracks without source or input mappings, it always worked fine with those). If you didn’t know about it, it might even be a good-natured bug. šŸ™‚

    This answers my original question. However, if you enable pre-effects level automation first, switch the fader to post-effects, and then try to also enable level automation on the first effect track (or from the track context menu as usual), Podium thinks its the exact same parameter again and the pre-effects level parameter turns red… It works if you create post-effects level automation first.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.
Ā© 2021 Zynewave