Topic: Bypass automation

Viewing 10 posts - 1 through 10 (of 10 total)
  • July 15, 2005 at 06:50 #591
    acousmod
    Participant

    Hi,
    Since the version 1.28 (if I remember well ?) the plugins can’t no more go to sleep when they are not used, resulting in a higher average CPU value.
    It’s a problem for me since sometimes I use a plugin only one time on a track (plugins for objects like in Tracktion or Samplitude will be great some day !…).
    So a workaround would be to be able to automate the track’s Bypass button.
    What do you think about ?

    July 15, 2005 at 09:10 #5059
    Zynewave
    Keymaster

    Since the version 1.28 (if I remember well ?) the plugins can’t no more go to sleep when they are not used

    😮 It works fine here. Please give me more details.

    July 15, 2005 at 10:38 #5063
    acousmod
    Participant

    In fact it was the 1.21 version…

    I remember that you have change something to prevent the plugins to use too much CPU, by fixing some default value (the refresh rate ?).

    The result is that for some plugins like those made with Synthedit in which the components can go to sleep mode when there is no input signal, they use since this version a fix amount of CPU.
    The difference is not wide, about 2 % average CPU for me (Podium’s indicator) in general, but on ten tracks it makes 20 % for nothing !
    Most plugins take some CPU when idle, so, if there were a way to turn a plugin completely off when it is not needed, it would be very very nice.

    July 15, 2005 at 10:47 #5065
    Zynewave
    Keymaster

    Ok, I thought you meant the audio processing. Possibly the graphics optimizations in 1.35 will improve on this. I’ve managed to improve the responsiveness of plugin editors at high CPU load. Also appearing in 1.35 is an option to unload plugins from memory when the bounce track is activated.

    July 15, 2005 at 11:12 #5066
    acousmod
    Participant

    Ok, I thought you meant the audio processing.

    Yes, I really meant audio processing.
    For example, if I insert a RoomVerb M2 on a track in my laptop, the CPU indicator can show 10 or 20 % depending on the Preset, even if there is no sound played on this track. Bypass it when not in use will preserve CPU for other tasks. (I think that Logic audio made automatically something similar, which resulted in an average lower CPU usage than other hosts).
    I think that the constant rate refresh prevents the audio processing to go to sleep mode ?

    I’ve managed to improve the responsiveness of plugin editors at high CPU load

    Very well, I’m impatient to test it !

    Also appearing in 1.35 is an option to unload plugins from memory when the bounce track is activated

    Excellent !

    July 16, 2005 at 14:57 #5070
    Zynewave
    Keymaster

    if I insert a RoomVerb M2 on a track in my laptop, the CPU indicator can show 10 or 20 % depending on the Preset, even if there is no sound played on this track

    It should be the job of the plugin to bypass its internal processing if it receives silent input. Podium cannot make the assumption that a silent input to a plugin will produce silent output, so the plugin process function has to be called. Are you feeding the M2 absolute silence? If you e.g. are monitoring analog inputs through the M2, the noise floor of the AD converters may trigger the plugin processing.

    July 16, 2005 at 16:13 #5075
    acousmod
    Participant

    Are you feeding the M2 absolute silence?

    Empty arrangement with to tracks : one for the master out, one for the plugin, with no audio file, no audio input (not activated in the setup) and not playing.
    The Roomverb M2 is an extreme case since happily most plugins take less resources, but when there are several tracks in use, it ends by a high percentage of CPU use, even when not needed most of the time.

    This is not special to Podium, the behaviour is the same in Cubase and others, but at least we can use the automation of the Mute.
    Such automation of the Track Mute or, even better in this case, the Track FX Bypass, will definetely help a lot in Podium.

    So, if you don’t know what to do during the summer (!), a new Audio Parameter “Audio Mute” will be very appreciated.

    Cheers.

    July 21, 2005 at 18:48 #5107
    stu
    Participant

    I mentioned this a while ago and I have to agree that being able to automate the track bypass switch is a good idea. Its good for when you use alot of one shot sounds in your choons and you don’t want to record them so you can still tweak them or change them a later on in the production.

    Stu

    July 21, 2005 at 21:03 #5112
    Zynewave
    Keymaster

    I’ve added ‘New ‘bypass mapping’ mixer parameter.’ to the future developments list.

    July 23, 2005 at 18:48 #5137
    stu
    Participant

    Thanks a lot this will be a massive benefit to me and Im sure alot of other people. 😀

    Stu

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