Topten Software

TiUser · Post by **TiUser** » Mon May 25, 2009 7:16 am

"Subsession Behaviour - Entire Bank" is a useful feature for plugins that do not support selection via standard patch lists...

However I've noticed that during a subsession change in plugins with entire bank option active transitioning to the same entire bank also forces reloading the same bank again and a short break in sound occurs.

Can this be optimized so that only true new "entire banks" force reload while supressing reloading the same bank again, resulting in no interrupt of the the plugins sound output in that case?

bradr · Post by **bradr** » Fri May 29, 2009 2:04 am

I've been thinking about this, the question is what constitutes a changed bank?

If two sub-sessions have the same saved bank state is that enough to determine that the bank doesn't need to be reapplied?

Or should it compare to the current state of the plugin so that if parameters have been tweaked since the first session was loaded they're restored to the state saved in the second sub-session.

Certainly the second approach would speed up things when no parameters have been changed and save having to reapply the bank again. But I think tweaked parameters between sub-session is a common enough scenario to warrant further thought.

Comments?

TiUser · Post by **TiUser** » Fri May 29, 2009 7:02 am

...well... I have to be honest, some plugins produce pops or more strange noise when just exposing a new bank... maybe there are other possibilities to keep plugins silent before applying a new bank?... of course, you could say this is a problem with the plugins but that does not better the situation and transition...

TiUser · Post by **TiUser** » Fri Jun 12, 2009 6:35 pm

...were there any changes with Build 2041 in subsession behaviour - entire bank?

I've a session were a plugin jumps back to an initial sound or something, but not the bank saced with the subsession before...

bradr · Post by **bradr** » Sat Jun 13, 2009 12:07 am

Nothing to do with sub-sessions changed between build 2040 and 2041. Any chance this could be related to MIDI routings or triggers - thats where the most significant changes were in this build. Particularly routings which can now send program changes - maybe that's causing a preset change?

TiUser · Post by **TiUser** » Sat Jun 13, 2009 5:32 am

bradr wrote:...now send program changes - maybe that's causing a preset change?

I'll try to check that - sounds plausible for a reason

edit: I guess you're right, I deleted the midi routing and the effect has gone... I just wonder what's the news that creates these program changes...