cerberus
09-16-2010, 06:24 PM
well, that is what i've found... live 6 does not have this issue but live 8 seems a mess.
for one thing, it appears to shooting back some float values where we
had doubles, leading to stuff "not exactly equaling what it is supposed to..."
and and some parameter changes being performed twice or more on a single click.
(needless to say, reaper is much better behaved for us... )
and live 8 just froze up whenever kNumParams > 32 !
any clues how to deal with these sticky wickets?
(edit -> i find i only need 31 parameters: one was actually doing nothing, it's
widget is an iBitmapContol which can always be updated from a mere variable.)
i understand there is a call which can read "what is the host daw?" from a list, which
is contained in one of the iplug files.... so perhaps one can make a plug-in which disables
certain features for certain daw hosts??? perhaps this sort of conditional test could
be helpful in getting plug-ins to not crash/fail/flail at the au validation test ? (can of worms!)
for one thing, it appears to shooting back some float values where we
had doubles, leading to stuff "not exactly equaling what it is supposed to..."
and and some parameter changes being performed twice or more on a single click.
(needless to say, reaper is much better behaved for us... )
and live 8 just froze up whenever kNumParams > 32 !
any clues how to deal with these sticky wickets?
(edit -> i find i only need 31 parameters: one was actually doing nothing, it's
widget is an iBitmapContol which can always be updated from a mere variable.)
i understand there is a call which can read "what is the host daw?" from a list, which
is contained in one of the iplug files.... so perhaps one can make a plug-in which disables
certain features for certain daw hosts??? perhaps this sort of conditional test could
be helpful in getting plug-ins to not crash/fail/flail at the au validation test ? (can of worms!)