Best posts made by Levitanus

Finally, available via PackageControl:

Hi, I'm ready to sign. Ohhh. How complicated things are... It's just few lines from the JUCE repo)

Disclaimer: I don't want to hurt anybody)) Just like sublime for many little features.

So I've written some regexes, feeded scripting API headers to them and packed into ST completion buffer.
Give it try: https://github.com/Levitanus/HISEScript-Sublime

P.S. Hold my hand on heart, that Christoph will not change formatting of the headers))

@hisefilo hard to tell... I would prefer the second one)

aah! samle mod should be set) awesome!

Currently neither. However this came up a few times before so maybe I'll just add support for it - it shouldn't be too hard to implement, the hard part was getting the internal routing multichannel capable...

Thanks! It would be grate. I see, d.Healey already has huge amount of micpositions in project, I'm hardly thinking about moving orchestral library project into hise, but even for personal usage always better to get different mics though the host routing and FX, neither leave it inside the plugin...

Well, I'm going to try finish little test instrument till the morning :) thanks for the response!!!

@d-healey said in API for Interprocess communications:

LASS had a setup where you could load each divisi section up as a different patch but you had to check all the settings for each one to make sure they were correct.

as I remember there was a weird logic, that translates all midi data to every instrument, and inside it choose its part. But even if it was inside multiscript, still it was realtime midi-processor. There is no way to split parts in different plugins not connected to the shared midi-data.

in case of using open-source sampler I'm really sad because of my total incompetence in C++... And there's absolutely no time to learn it next months... Especially when just took a breath of real power of open-source in making quick hacks just for case )

While there were problems with long loops in hise i made a prototype of the same instrument within "you-know-what" and feel the memory usage problem when whole sample being included in the s.mod. So, i've made some slices to be used as "long RR" and it worked.
So i want to ask, if it possible to make several start-point positions to switch between, and use preload for them all, but not for the entire sample?

Christoph, thanks!

updated:

added:

• namespaces
• locals
• snippets:
  • callbacks mandatory
  • callback of control
  • include
• setting "hise_supress_completions": false
• Math, Array, String objects now parsed from source

changed:

• Now syntax is copy of standart Javascript with additions to native scopes, not just added scopes.

Actually, The package itself is designed to be always up to date by parsing the current HISE git folder.
But, since I didn't look to the HISE folders\API structure for a while (I just can't find any commit that compiles on my machine), It can leak some API calls.
Still, the package present in packagecontorl.io and you can try it.

Huge Thanks for You! I've got couple of very hard days, and the night should br also very busy, but tomorow I will try everything.
By the way, i tried to fix it before the first compilation:

somehow your sample references got messed up. If you copy the Main Container in the clipboard and paste it in Sublime Text or another text editor, you'll see that the file references in the samplers look like this:

But couldn't. The matter is, I think, there was wrong sample and i just deleted it from the map.

You'll need to build a new HISE

Scares only the first time, then everything just a cup of tea)