Topic: Bounce Track Functionality

Viewing 6 posts - 1 through 6 (of 6 total)
  • April 30, 2007 at 14:18 #1276
    pernst
    Participant

    I have two questions/requests regarding Bounce tracks. Why, if a track is designated at a Bounce Track, do adjustments to the level sliders for the track have no effect on the output level of the track (containing the bounced audio)? Secondly, why, after Bouncing to a track, do the plugin’s of the Child Tracks remain active, but the tracks are muted? I am curious because I do a bit of extra work every time I freeze a group of tracks to a Bounce Track. Once the Bounce is rendered, I alter the properties of the Bounce Track to not allow bouncing (this enables the level setting for the track) and then go to each plugin in the Child Tracks and disable them. I know, I am whinning, but when the child tracks involve 6 outputs from JamStix, a instance of reverb and several eq’s, it is a bit time consuming to disable all of these each time.

    My ideal solution would be to enable level adjustments on Bounce tracks and have an option, when right clicking on a track, to enable/disable child track plugins and to Mute/Unmute child tracks.

    April 30, 2007 at 15:31 #9834
    Zynewave
    Keymaster

    Why, if a track is designated at a Bounce Track, do adjustments to the level sliders for the track have no effect on the output level of the track (containing the bounced audio)?

    Bounce recording captures the output of the track, after all processing is applied. This includes level/pan processing. Level has to be processed before the bounce capture because otherwise level/pan automation child tracks (which become muted when bounce is enabled) would not be processed. This question has come up quite often, so I may decide to change this behaviour. To adjust the gain output of a bounced group track, you can add a parent audio enabled track.

    why, after Bouncing to a track, do the plugin’s of the Child Tracks remain active, but the tracks are muted?

    If by “active” you mean loaded in memory, then you have the “unload plugin…” option in the track properties. This option is off by default, because some plugins take a lot of time loading (e.g. sample set based plugins). So if your workflow involves frequent toggling of bounce mode, you would often prefer that the plugins are always loaded.

    April 30, 2007 at 16:29 #9835
    Podianer
    Participant

    This question has come up quite often, so I may decide to change this behaviour.

    Hey Frits,

    Perhaps you could change that in the following way: When a track is bounce enabled, you could simply hide the level dials instead of dimming them. Thus people will not try to change the level and wonder why it doesn’t work..

    Max

    April 30, 2007 at 16:57 #9836
    pernst
    Participant

    Sorry about the confusion of Muting and CPU usage. I was mistaken. The muting of child tracks DOES reduce CPU usage, causing the Pluggin’s of the child tracks to effectively not utilize CPU cycles.

    Your explanation of the reason Bounce Track’s level and pan cannot be adjusted makes sense. You want to preserve the sound when you froze the track group. wrapping a parent around the bounce track is a sufficient solution.

    Thanks once again for your time.

    April 30, 2007 at 20:14 #9838
    darcyb62
    Participant

    I was one of those that was confused by this and hoped that voume and pan would work on bounced tracks, but that was a long time ago and I like the way it works now. If I want to add controls I just wrap a parent around it. Podianer’s request is a good one though and I would second it.

    April 30, 2007 at 23:38 #9839
    Zynewave
    Keymaster

    I’ll consider hiding the gain/pan dials in the mixer, instead of just dimming them. I’ve also forgotten to indicate dimmed state of the recently implemented gain faders, so hiding the faders seems like the least confusing solution.

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