Page 1 of 1

Posted: 13 Sep 2010, 09:54
by 23fx23
a last one and i stop asking for this month ;)

Posted: 13 Sep 2010, 10:07
by gurulogic
23fx23 wrote:a last one and i stop asking for this month ;)
haha, yeah right...sure!

btw, I want whatever 23fx23 says he wants cause he makes things I like, so +1 ;)

Posted: 13 Sep 2010, 10:10
by senso
the mouse information within a VST panel is handled by the vst itself. I don't have access directly...
So I don't know if it's possible, but at least very difficult.

Posted: 13 Sep 2010, 10:33
by 23fx23
@guru yep hehe 15days is too long.

@senso ok, that wouldn't solve the thing i got in mind anyway, and i can fake a msdwn area detection with the mouse module
if puting the vst on a cerain zone on screen as a workable solution in my case.

Posted: 13 Sep 2010, 10:40
by gurulogic
this is kind of like a mouse down...I'm sure you already thought of this though.

Image

doh! nevermind...that really doesn't help if the vst is being fed any external parameter data...

Posted: 13 Sep 2010, 10:57
by 23fx23
nope i hadn't test that nice.thanks. the only pb in my case is when automations make params change on input, it will consider a msdwn when there is not.

but i found several solutions to the problems. now i can get the 8 params from VST when changing pgm via a tiny wait
muting automations,and then they reset automations to corresponfing received values, i just need now to make the automs control only when they change so that ill also
be able to control on the vst an already assigned param if no automation is rec yet.