FIRST FREE VST INDEX BUGGY

Home Forums General Programming FIRST FREE VST INDEX BUGGY

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #29873
    kamder
    Participant
    • Topics: 9
    • Replies: 13
    • Total: 22

    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 .

    #29874
    atom
    Keymaster
    • Topics: 159
    • Replies: 2945
    • Total: 3104
    • ★★★★★

    i’ll have a look asap.

    #29903
    GunniKonn
    Participant
    • Topics: 5
    • Replies: 27
    • Total: 32

    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.

    #62565
    human fly
    Participant
    • Topics: 124
    • Replies: 1070
    • Total: 1194
    • ★★★★

    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’?)

Viewing 4 posts - 1 through 4 (of 4 total)
  • The forum ‘Programming’ is closed to new topics and replies.
There is currently 0 users and 54 guests online
No users are currently active
Forum Statistics
Threads: 2,495, Posts: 17,374, Members: 77,605
Most users ever online was 12 on January 22, 2019 3:47 pm
Ctrlr