Builder InterfaceTypes

[David Healey]

@Lindon The auto-complete has it. And the connectToScript function is in the documentation.

Here's an example of creating a MIDI script processor and connecting it to a script file

local index = builder.create(builder.MidiProcessors.ScriptProcessor, "myScript", 0, builder.ChainIndexes.Midi);
builder.connectToScript(index, "{PROJECT_FOLDER}MyScript.js");

[Lindon]

@David-Healey thanks yes I know where to find the connectToScript, and my current version of auto-complete refuses to load my selection so I dont use it (much), still I guess I can read and copy..(ugly)

thanks.

[David Healey]

@Lindon The autocomplete is a bit dodgy, if you add a new object or you have a compile error it doesn't populate until you next successfully compile.

[Lindon]

@David-Healey it turns out its worse than that:

var stdscript = builder.create(
              builder.MidiProcessors.Arpeggiator, // the module type
              "Arpeggiator1",                       // the ID
              mastercontainer,                       // the parent (root)
              builder.ChainIndexes.Direct);             // the slot type

gives me:

Interface:! Line 19, column 31: Couldn't create module with ID Arpeggiator 

[Lindon]

@Lindon turns out its me being dumb...

var stdscript = builder.create(
              builder.MidiProcessors.Arpeggiator, // the module type
              "Arpeggiator1",                       // the ID
              mastercontainer,                       // the parent (root)
              builder.ChainIndexes.Midi);             // the slot type

[Lindon]

OK so now I cant get builder.connectToScript(strum, "AScript2.js"); to work its telling me

StrumProcessor:! onControl could not be parsed!

heres onControl

function onControl(number, value)
{
	
}
 

[David Healey]

@Lindon Do you see that error when you use that script manually?

[Lindon]

@David-Healey nope...

[David Healey]

@Lindon What about through the builder in a minimal test project?

[Lindon]

@David-Healey this is a minimalist test project...

[David Healey]

@Lindon Can you send it to me?

[Lindon]

@David-Healey yep hold on I will have to do some rebuilding...

[Lindon]

@David-Healey - OK how do you want it - its literally an init HISEScript and a .js file with the script in it...

[David Healey]

@Lindon If you can post it publicly just dump it here. Or a dm/email

[Lindon]

So I am back here again with the lack of documentation.

I want to create a container.... @dannytaurus kindly pointed me at part of the solution

so I have:

//holding container
builder.create(builder.SynthChain.?????,"MasterContainer",0,builder.ChainIndexes.Direct); 

I've tried reading the docs (ha ha ha ha ha..) I've tried the autocomplete....no answers

can someone point out the correct syntax, and where I can in future find it?

[Lindon]

@Lindon and of course the forum woo kicks in as soon as I post: here - for those looking ids the solution:

builder.create(builder.SoundGenerators.SynthChain ,"MasterContainer",0,builder.ChainIndexes.Direct); 

[Lindon]

@Lindon ..and then Im straight back here with this:

trying to make a script processor - the autocomplete gives me this:

	   theKeySwitchFilters[i] = builder.create(
	   				builder.MidiProcessors.ScriptProcessor,
					articulationNames[i] + "KeySwitchFilter",         // the ID
					theSamplerContainers[i],                  // the parent (root)
					builder.ChainIndexes.Direct               // the slot type		
	   				);

and the complier gives me this:

Interface:! StdBuilderElements.js (22): Couldn't create module with ID ScriptProcessor 

Anyone???

[Lindon]

@Lindon and a search thru the forum gives me this answer:

	   theKeySwitchFilters[i] = builder.create(

	   				builder.MidiProcessors.ScriptProcessor,
					articulationNames[i] + "KeySwitchFilter",         // the ID
					theSamplerContainers[i],                  // the parent (root)
					builder.ChainIndexes.Midi              // the slot type		
	   				);

[David Healey]

@Lindon
Shouldn't the chain index be Midi rather than Direct?

[Lindon]

@David-Healey yep as you see above - meanwhile where is all this documentation hidden?