Topic: Feature Request: Update PlugIn Scan

Viewing 7 posts - 1 through 7 (of 7 total)
  • September 4, 2005 at 16:04 #635
    Podianer
    Participant

    Hi,

    An option in the Wizard for scanning the VST folder for only “new” Plugins would be very nice. This would safe some time, in my opinion. This feature is also implemented in Tracktion 2, where I find it quite useful.

    How’s about that?

    September 4, 2005 at 18:57 #5401
    Zynewave
    Keymaster

    Good idea. I have modified the normal ‘scan & import’ function so that it only imports a plugin if it is not already imported. Will be available in release 1.39.

    September 4, 2005 at 19:18 #5403
    Podianer
    Participant

    Fine!!! Thanks for that!! 🙂

    September 5, 2005 at 06:39 #5405
    Dandruff
    Participant

    @Zynewave wrote:

    I have modified the normal ‘scan & import’ function so that it only imports a plugin if it is not already imported.

    but please don’t forget: a “rescan all” is needed for some plugins (when changing settings in them – such as different output-config or settings which causes more latency)!

    September 5, 2005 at 17:25 #5406
    Zynewave
    Keymaster

    a “rescan all” is needed for some plugins (when changing settings in them – such as different output-config

    This requires a little more development time, so for now only filename check is implemented.

    or settings which causes more latency

    This does not require a rescan. Podium will dynamically update latency compensation whenever a plugin reports a change in latency.

    September 5, 2005 at 17:34 #5408
    Dandruff
    Participant

    @Zynewave wrote:

    a “rescan all” is needed for some plugins (when changing settings in them – such as different output-config

    This requires a little more development time, so for now only filename check is implemented.

    just add “rescan all”. should be easy to implement i think. that’s the way how it works in cubase.

    @Zynewave wrote:

    or settings which causes more latency

    This does not require a rescan. Podium will dynamically update latency compensation whenever a plugin reports a change in latency.

    really? in cubase for example that’s not possible. it needs user-interaction (rescan of all plugins).

    September 6, 2005 at 06:20 #5411
    duncanparsons
    Participant

    aahh… but this isn’t cubase!

    I hadn’t realised that dynamic latency was taken care of here – that’s pretty cool. Sometimes it can get really useful to be able to do that – if you change an FFT window, it can alter the latenecy, so normally you have to plump for the longest you can get away with, and if your window means you could use less, you’re just lumbered with it..

    cool frits!

    DSP

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