Gen 2 external

    Jul 18 2014 | 9:32 am
    Hi! compile externals in gen~? why not?

    • Jul 18 2014 | 9:39 am
      exporting in Gen was introduced in order to port code to other environments i believe . I think making externals for Max would be the same as using Gen itself anyway :) no ?
    • Jul 18 2014 | 10:01 am
      Hi "Do...While" grow older while waiting, a poly open with a gen patch inside (I guess it's because gen compile it all times..). vst´s (compiled in gen~) has problems updating parameters .. Could serve as a basic and simple system of protection (encryption) of code
    • Jul 18 2014 | 10:17 am
      ah yes ... i know what u mean .. the poly thing scared me back in the days ;
      protection-wise ... we are dealing with some sort of open source projects when dealing with Max that u agree on and benefits from . I never considered it as a goal but one way of protecting your code would be writing externals with SDK . Thats the cost i would say . Additionally u will have control of all the data flow aspects like when something is calculated in audio domain and when not ... etc For me Gen is suited for special scenarios only , not for general purpose . For example : I even got better efficiency with playing back samples (with interpolation) from within my C externals than from Gen of the same or similar logic .
      # EDIT the same im thinking that external compiled in Gen would gain similar or the same efficiency as Gen itself . but its just blind guess
    • Jul 19 2014 | 10:03 am
      Do ... While Agree on some things, and less on other thanks for replying!
    • Jul 19 2014 | 10:10 am