FIRST FREE VST INDEX BUGGY

[kamder]

hello !!! i have found (i think ) a problem with the get first free vst index command : if i add a new modulator , or if i copy an existed modulator the vst index gived is the same off some existing modulators !!!!!!
to temporarely resolve the issue for my stuff i have do this :

int CtrlrManagerVst::getFirstFree()
{
///KAMDERFREEVST KAMDERFIRSTFREE///
//return ((int)map.size());///removed/////
return (vsti.getLast()+1); /// VST INDEX MAX and add 1 …///
}

i think if you have a best solution (giving the REAL FIRST FREE VST INDEX) it can be good

THANKS
KAMDER .

[atom]

i’ll have a look asap.

[GunniKonn]

Giving the first free VST index is a great idea, I remember this causing me headaches for a while until I found out that the copy got the same VST index as the original.

[human fly]

copying groups containing modulators causes a lot of same VST Index.
i don’tknow if this is a problem, if you can re-number afterwards.
but how do you determine #s to use?

a shared # is handy if you want synced response from 2 modulators.
apparently if you try that with more than 2, it doesn’t work
(?must ‘use Lua’?)

[Author]

Posts