How do I load a midi script programmatically?

[Orvillain]

@d-healey Riiiiight. That seems very odd to me. HISE could at least draw in the scripts and make it read only, or otherwise indicate success. Because it looks broken to me, and is the same "symptom" as what I see when trying to connect a script in code.

The only difference being when I try to connect a script in code, I get an error that says "onControl could not be parsed!"

Hmmmmm. I guess I need to dig into this some more. Your tip about removing the "Scripts" folder from the path was a good one, but does not seem to have made any difference.

But now that you've said what you've said... I'm wondering, how do I even confirm the script has been attached successfully? It looks exactly the same in the actual project:

And alllllll this time, I've been assuming it didn't work properly because of how empty it looks, and also because of the parse error in the log.

[d.healey]

@Orvillain If you add controls to your scripts interface they will show up in that blank area.

[Orvillain]

Okay. I've gotten it to work by replacing the forward slash with a backslash. This is on Windows. I don't know if MacOS will cope with that???

I was reasonably sure that even on Windows this should work?? It works for a bunch of other things, iirc.

[Lindon]

@Orvillain you are going to have to use different separators based on the OS in question
fwd slash for mac os backslash for windows:

HISE | Docs

(docs.hise.dev)

[Orvillain]

@Lindon Thanks!

Really sorry for the n00b question here. It was just boggling my mind, and I was making it a lot more complicated than it needed to be.

[d.healey]

@Lindon said in How do I load a midi script programmatically?:

you are going to have to use different separators based on the OS in question
fwd slash for mac os backslash for windows:

You should be able to use the same on all OS and HISE will handle it. I think the issue here is you don't need to put a slash of any kind after {PROJECT_FOLDER} because that wildcard includes a slash.

[Lindon]

@d-healey said in How do I load a midi script programmatically?:

@Lindon said in How do I load a midi script programmatically?:

you are going to have to use different separators based on the OS in question
fwd slash for mac os backslash for windows:

You should be able to use the same on all OS and HISE will handle it. I think the issue here is you don't need to put a slash of any kind after {PROJECT_FOLDER} because that wildcard includes a slash.

You should, but my experience is you cant...

[d.healey]

@Lindon How do you include files or fonts?

I do this and it works on all systems

Engine.loadFontAs("{PROJECT_FOLDER}Fonts/Text/Inter-Regular.ttf", "regular");

[Lindon]

@d-healey I do what i've always done and put the font in the images folder and call this:

Engine.loadFontAs("{PROJECT_FOLDER}DIN Alternate Bold.otf", "DIN Alternate");

works everywhere.

Where it doesnt work is if you want to declare some sub-folder path i.e.

{PROJECTS}\mysub\yoursub\afile.ext

so its simple to work around:

// on init
const var WINDOWS = "WIN";
const var MAC = "OSX";
const var OS = Engine.getOS();


//elsewhere...

	if(OS == WINDOWS)
	{
		theLoopPlayers[pos].setFile(LP_LoopFileFolder + "\\"+ component.get("text") + ".wav");
	}else{
		theLoopPlayers[pos].setFile(LP_LoopFileFolder + "/"+ component.get("text") + ".wav");			
	};	

You of course will also want to check for Linux...

[d.healey]

@Lindon said in How do I load a midi script programmatically?:

{PROJECTS}\mysub\yoursub\afile.ext

You don't need a slash after the wildcard, and if you use forward slashes only it will work on all systems. Don't know about the lopp player though.

[Lindon]

@d-healey said in How do I load a midi script programmatically?:

@Lindon said in How do I load a midi script programmatically?:

{PROJECTS}\mysub\yoursub\afile.ext

You don't need a slash after the wildcard, and if you use forward slashes only it will work on all systems. Don't know about the lopp player though.

yeah that might work for you but as I say its at the very least unreliable for me, it might be cases of paths without {PROJECT_FOLDER} in them