]]>
I think you have to try.
Statistics: Posted by senso — 04 Apr 2012, 17:01
]]>
What kind of scripts would stop working? I guess audio would stop working and MIDI timing would get sloppy?
That seems a lot easier to debug than random crashes
Statistics: Posted by woodslanding — 03 Apr 2012, 23:22
]]>
Which is obviously faster but dangerous...
So you can call SetFastCallback(.,FALSE); It will improve the stability.
Now, I have to find a solution to set the default value to false and ensure the backward compatibility, which is not easy...
Sometime Usine is so huge that I can't remember all the settings myself.
I'm sorry for this confusion.
Statistics: Posted by senso — 03 Apr 2012, 10:27
]]>
]]>
I thought the default was TRUE. I've set fastcallback to FALSE for of all my parameters that create IML, and usine seems more stable. It's fixed a bug where 256presets was setting commatext wrong when more than one instance was in my WKP and it fixed the layout problem that started this thread. I also set it FALSE in the script that updates my combo commatext via VST program list and the one that renames busses based on track number, both of which have randomly misbehaved at times.
Is this a mistake?
Or only in the case of setVSTparameter?
Statistics: Posted by woodslanding — 02 Apr 2012, 04:34
]]>
You should leave parameters as their default callback settings (will work like in the actual VST engine of Usine).
Statistics: Posted by senso — 01 Apr 2012, 15:38
]]>
]]>
SetFastCallBack(MyIMLTriggeringInputParameter, false)
If so, where do I put this line in my script?? I can't find an example of it. The ''set vst parameter" script does not employ it, but shouldn't it?? The help file says it should be used anywhere IML is in the callback method.
thanks!
-e
Statistics: Posted by woodslanding — 31 Mar 2012, 05:17
]]>
]]>
So now my next question:
Trying to figure out how to make a script that will delay any response to a change of input after a delay whose time is a function of track#.
Unless there's an easier way, of course!
I doubt the subpatch solution will work--it would be nice if a single IML message could select the target and the action, but failing that, it seems like this will always be a problem with IML.
Statistics: Posted by woodslanding — 27 Mar 2012, 21:44
]]>
SET_TARGET_PATCH subpatchname
Statistics: Posted by nay-seven — 27 Mar 2012, 09:20
]]>
The code looks like this:
SendInternalMsg('SET_TARGET_PATCH','SENDER_PATCH');
SendInternalMsg('SET_CTRL_POS',name,IntTostr(round(GetValue(posXIN))),IntTostr(round(ypos)));
SendInternalMsg('SET_CTRL_SIZE',name,IntTostr(round(GetValue(widthIN))),height);
Do I need to be more precise about TARGET_PATCH, and not just use SENDER_PATCH? If so, what is the nomenclature? Or do I need to do something to make sure all three messages get sent at once??
This actually seems like a bug, as though the IML is getting crossed wires internally, but maybe there's a workaround?
here's a test patch:
http://www.sensomusic.com/forums/upload ... roblem.wkp
thanks,
-eric
Statistics: Posted by woodslanding — 27 Mar 2012, 06:22
]]>