Topic: Vsti scanning problem(s)

Viewing 3 posts - 1 through 3 (of 3 total)
  • February 2, 2006 at 21:13 #724
    swayzak
    Participant

    hi

    I attempted to get the device definitions + assoc parameters with a total scan of my vsti folder (around 300 plugs in total !)

    Podium freezes (requiring a 3 finger shuffle to close it) with:

    jamstix
    Algo’s M42
    Waldorf Attack

    Not a bad strike rate I suppose !

    One thing I’ve noticed though. All parameter properties for all the VSTi’s I’ve looked at (randomly selected around 10) list the value definitions as 0 in all the boxes.

    Not much use I guess – presumably I’d have to set them ALL to 0 min, 127 max ?!!?

    swayzak

    February 2, 2006 at 21:17 #6079
    Zynewave
    Keymaster

    One thing I’ve noticed though. All parameter properties for all the VSTi’s I’ve looked at (randomly selected around 10) list the value definitions as 0 in all the boxes.

    Not much use I guess – presumably I’d have to set them ALL to 0 min, 127 max ?!!?

    No, just leave them with min/max as 0/0. For plugin parameters this means that they will use the full floating point range of the parameters. If you enter values for the min/max range, Podium will use that to quantize the values when editing and displaying parameter values in the curve editor and on the sliders in the mixer.

    February 2, 2006 at 21:36 #6080
    swayzak
    Participant

    thanks

    Actually the “rogue” plugins imported fine separately.

    jamstix hadn’t been launched following installation of extra sample packs (which is required for completion of their installation)…I guess Podium didn’t like this in a whole folder scan. Worked OK with an individual import.

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