Statistics: Posted by 23fx23 — 14 Jun 2010, 18:42
]]>
Results:
* Initially it doesn't work
* If I manually modulate a parameter of the master (e.g. with a button - like nay wrote above) then it also works on my side!
* If I open the console then it stops working
* If I try to manually modulate a parameter of the master while the console is open the Usine crashes. (Beside from that Usine also crashes with a 9 out of 10 chance if I try to recompile the script after starting the audio engine, remove and readd the script module or press the "rewire" button that is connected to the script module.)
Will use the bus variant for the mean time and wait for a new Usine version where the scriptable IML is more stable.
Nonetheless very interesting and promising technology!
Thanks again to all of you (and expecially 23fx23) for your good ideas and dedication, really a nice community! And thanks to Senso for the interesting concepts of the software. This will offer so many possibilities once it's more mature!
Greetings,
NaN
Statistics: Posted by NaN — 14 Jun 2010, 18:22
]]>
for me it doesn't come from the script but from VST as nothing goes to the wire when changing... but this is another pb maybe.
yup as it can be interesting, i will make some inputs for names and nb and post as addon maybe, this can have various applications. i imagine some stuff as Nan, or progressive decrease of interactions, ducking/sidechaining, presets/automations
global apply, think their are many things even with classic modules and not vsts that could be interesting, and time saving.
In fact ive checked the input Nb thing, and it seems normal, we feel it goes to some first invisible input but it doesn't, it's the query system, can scroll the inputs on script/vst via scroller, usine display about 80 of them, (92 if well remember) but other exists and are accessibles. i was able to wire 343 wires on the go to Oatmeal, also it was a bit lagging then in wksp, the parameters still updated smootly wireless to two other instances, exept some as wavform, but ok with a fader on input.. maybe a little request to olivier
for Vst array out could higly reduce wires once more and allow to count paramnb if doable... but definitely an interesting way to explore...
Statistics: Posted by 23fx23 — 14 Jun 2010, 18:13
]]>
so maybe an initialization problem..?
but don't have the console message for the moment..,
@23fx : don't worry about input , it's not a big deal , maybe add a knob to set it manually if it's possible..?
for my part , this script give some cool ideas about auto wiring array with inlets of vsti , but i've to work more on scripting..; -)
Statistics: Posted by nay-seven — 14 Jun 2010, 17:52
]]>
nay: ill check if find a solution but im affraid the inputs nb must be well calibrated by good old manual couting sadly, didn't yet found solution for counting Vst inputs, will investigate.
Statistics: Posted by 23fx23 — 14 Jun 2010, 17:48
]]>
edit : now i reopend my patch and i got same behaviour: can't set Target patch and pots don't upd anymore here same mmmm,
will investigate
Statistics: Posted by 23fx23 — 14 Jun 2010, 17:06
]]>
The buttons of the one Helios instance are in motion (so the lfos work) but the others do nothing.
The console log is similar to my previous attempt:
...
process msg : SET_VALUE VST_0 14 0.355041712522507
Var patch not found :TARGET_PATCH
Can't Set Value : VST_0 14 0.355041712522507
process msg : SET_VALUE VST_1 14 0.355041712522507
Var patch not found :TARGET_PATCH
Can't Set Value : VST_1 14 0.355041712522507
process msg : SET_VALUE VST_2 14 0.355041712522507
Var patch not found :TARGET_PATCH
Can't Set Value : VST_2 14 0.355041712522507
process msg : SET_TARGET_PATCH SENDER_PATCH
Invalid internal message : SET_TARGET_PATCH SENDER_PATCH
etc.
My computer has an Intel Core2Duo 6700 2.66 GHz processor, 4 GB RAM and runs Windows 7 64 bit with a Juli@ audio card with ASIO drivers and several MIDI interfaces (E-MU XBoard 61 internal USB interface, UM-1 dedicated MIDI interface, Loop BE30 MIDI Loopback interface, Juli@ MIDI outs) . The Usine CPU profile is the "2cores : 12/12/12" setup, "nb threads" is 8. (These were the default values, didn't change them)
Greetings,
NaN
Statistics: Posted by NaN — 14 Jun 2010, 16:55
]]>
first test was on a 2 years dual core with windows vista sp2
new one made on my laptop seven 64 bits : a few seconds...
an other test ( if you change to 120 parameters for example ( Helios has only 81 )
82 and more connect to first outlet ( like latency and invisible one..? )
Statistics: Posted by nay-seven — 14 Jun 2010, 16:18
]]>
]]>
oatmeal (freeware )
Statistics: Posted by nay-seven — 14 Jun 2010, 15:45
]]>
anyway you got it working and no usine console log, so i wonder what's pb on nan setup...mm
are ya sure ya named the master ans slave (not caption, using right clic, maybe avoid spaces in names)
strange wiring Nay indeed, but note there is a "start input" constant on script wich is 7 by default that was working well with helios, have to adapt for VSTs, here it seems should change to 15 or 16 for input0 to start on first param...(we count in/out pins before the one we wanna start from.
Statistics: Posted by 23fx23 — 14 Jun 2010, 15:44
]]>
Statistics: Posted by nay-seven — 14 Jun 2010, 15:35
]]>
do ya get same msg even when opening the wksp on link above?
This one
Statistics: Posted by 23fx23 — 14 Jun 2010, 15:29
]]>
Here my console log:
Invalid internal message : SET_TARGET_PATCH SENDER_PATCH
process msg : SET_VALUE SLAVE_0 12 0.584999680519104
Var patch not found :TARGET_PATCH
Can't Set Value : SLAVE_0 12 0.584999680519104
process msg : SET_TARGET_PATCH SENDER_PATCH
Looks like the SET_TARGET_PATCH command is not recognized on my setup.
(The autowireing worked - it takes about 10 minutes or more though for 151 parameters, I already thought Usine has crashed)
I am using the 5.17 full version, should I use some internal beta instead? (If yes, where do I find this?)
Greetings,
NaN
Statistics: Posted by NaN — 14 Jun 2010, 14:37
]]>
Greetings,
NaN
Statistics: Posted by NaN — 14 Jun 2010, 10:35
]]>
Statistics: Posted by nay-seven — 14 Jun 2010, 08:36
]]>
i guess it can have some limits..but it seems Prgm change test will quasi instentaneous chg all clones parameters, so
seems working not bad and might be a cool technique for your stuff, one cool thing being slaves folow master but can
then be independantely tweaked, and this trigged me lot of cool ideas
copy paste the text to an empty script and compile,
then put master and clones modules/vst in same patch as the script and name them, then the Wifi link should work
//////////////////////////////////////////////////////////////////////////////////////
// IML_LINK 23fx 14.06.2K10
///////////////////////////////////////////////////////////////////////////////////////
// Allows to wireless reflect some inputs parameters of a module/vst to N slave clones.
///////////////////////////////////////////////////////////////////////////////////////
const Max_Ins= 64; // nb of input parameters (if changing ctrlX-ctrlV the script to destroy prev wires first)
const Nb_vst = 2; // nb of slave clones
const StartInput = 7; // start interesting input nb
const VstName = 'VST_'; // prefix name of slaves
const MasterName = 'MASTER'; // name of master for auto wire
const ScriptName = 'IML_LINK'; // name of actual script for auto wire
////////////////////////////////////////////////////////
var WIRE : Tparameter;
var INPUTS : array of Tparameter;
var i,j : integer;
///////////////////////////////////////////////////////////////////////////////////////
Procedure Init;
BEGIN
wire:= CreateParam('wire master',Ptbutton); SetIsOutPut(Wire,false);
setArrayLength(INPUTS,Max_Ins);
for i:=0 to Max_Ins-1 do begin
INPUTS:= CreateParam('Input'+IntToStr(i), PtDatafield); SetIsoutput(INPUTS,false);
end;
END;
//////////////////////////////////////////////////////////////////
Procedure callBack(n : integer);
BEGIN
for i:=0 to max_ins-1 do begin
if (n=INPUTS) then begin
sendInternalMsg('SET_TARGET_PATCH SENDER_PATCH');
for j:= 0 to nb_vst -1 do begin
SendInternalMsg('SET_VALUE',VstName+IntToStr(j),IntToStr(i+startInput),floatToStr(getValue(INPUTS)));
end;
end;
end;
if (n=Wire) and (getValue(Wire)=1) then begin
sendInternalMsg('SET_TARGET_PATCH SENDER_PATCH');
for i:=0 to max_ins-1 do begin
SendInternalMsg('CREATE_LINK',MasterName,IntToStr(i+startInput),ScriptName,IntToStr(i+2));
end;
end;
END;
//////////////////////////////////////////////////////////
or can get a direct exemple Wksp with Helios
Here
note it uses and requires latest 5.17 version as it uses new great iml in script improvments.
well done olivier
Statistics: Posted by 23fx23 — 14 Jun 2010, 04:37
]]>
i will have a look at your patch, there bust also be a better iml possibility maybe..
Statistics: Posted by 23fx23 — 14 Jun 2010, 01:52
]]>
Statistics: Posted by NaN — 14 Jun 2010, 01:28
]]>
Greetings,
NaN
Statistics: Posted by NaN — 13 Jun 2010, 23:30
]]>
Is there a way to disable the collecting of undo information? (Getting this faster for big schematics is imho essential, this one minute per wire delay takes out much of the fun when making patches. Only bearable while listening to really good music in the background
)* Making the slavesynth subpatches root-level patches would occupy 16 patch slots. This would make things a little bit unhandy (especially if the multichannel instrument is not the only one in the workspace) and couldn't be loaded at all with the free version. Hope a linking feature for subpatches will come one day!
Thanks again for your answers and if you could have a look at the schematic - would be really cool!
Greetings,
NaN
Statistics: Posted by NaN — 13 Jun 2010, 23:28
]]>
in other instances you get that single same bus, then demultiplex the array.
no need to reroute then outputs in serial (wich would return 2x more wires), all their inputs are wireless linked to first array out.
Statistics: Posted by 23fx23 — 13 Jun 2010, 23:15
]]>
* adding wires can become very slow when your patch is too big as all of the current patch get a copy saved for undo every time you add a wire, etc.. The best solution for this is to split your patch into sub patches or more patches in the grid.
* there is no patch linking persay but if the master sub patch "master" were loaded as a top parent patch accross multiple cells in the grid, you could use the reload patch command to load the changes saved to the master patch. ATM, this is not possible for sub patches.
* your crashes are very likely memory related. Usine memory or virtual memory use can grow during patching so if the patch is already approaching your memory limits, adding another module could cause a crash. Sometimes it can be usefull to monitor Usines memory use with Process Explorer http://technet.microsoft.com/en-us/sysi ... 96653.aspx and then restart Usine when you are nearing your limits.
* 90MB for a patch seems excessively huge ! If I get a chance I'll take a look later today...
Statistics: Posted by gurulogic — 13 Jun 2010, 21:27
]]>
Some questions to the experts:
* adding new wires is really slow in this patch (depends on the subpatch, adding a wire in MultiME80 takes nearly a minute). Is there a way to accelerate this?
* currently I have 15 copies of the SlaveSynth subpatch. Now it would be handy to link all those patches in order to be able to make changes to them without having to do the work 15 times or having to disassemble and reassemble the whole patch. (E.g. SynthMaker offers a link feature for components, is there something similar in Usine?)
* Usine crashed about 10 times when I built this schematic (mostly when I dropped a math component into the schematic). Is that memory related? (I only have 4 GB RAM but as Usine is a 32 bit app more presumably wouldn't help...)
I have uploaded the patch here if someone wants to have a look.
EDIT: sorry, forgot to compress the patch, replaced the original file with a zip archive now. (Is it normal that the uncompressed patch is about 90 MB? That seems rather big to me, the patch is not overly complex)
Statistics: Posted by NaN — 13 Jun 2010, 16:27
]]>
I'll use variant 1) for making the ME80 multichannel aware.
Zebra is also on the list of synths that I would like to use, for that I'll probably have a more in-deepth look at your suggestions 2 and 3.
Thanks a lot!
NaN
Statistics: Posted by NaN — 12 Jun 2010, 17:43
]]>