@Christoph-Hart said in Persistence values - still cant get this to work:

But what exactly is the hiccup we‘re talking about here? As soon as you set properties with a script, you obviously can‘t change it on the interface designer anymore because it would get overwritten each time you recompile the script.

If you want to batch process widgets once via script but then keep on editing the properties, wrap the property changes into a function and call it once, then comment it out so you can access them in the interface designer again.

Christoph I don't saying you souldn't take off the old way, I'm agree with you about creating averything through code writing is better and powerful (I started in that way before the RAD Ides), but why we need, so, to get a widgets palete? I thought it's no useful (it's only my personal opinion, don't take it as a request or a criticism) ;)

@d-healey Thanks Dave.... in the meantime I will just have to get over myself... and try convince my customers that they wont really need authorisation (they already love the audio file protection in HISE)... I will create a post in the "Feature request" section...

So for those not needing the nice arrow buttons and happy enough with just getting a number field sorted this code works fine:

function onControl(myControl, myValue) { if (myControl == yourNumberLabel){ var myres = parseInt(myValue, 10); yourNumberLabel.set("text",myres); }; };

We can share our snippets in the Presets/Snippets section in order to help each other guys!

strange - I'm using the default settings and they are showing up now.

@Christoph-Hart Ahhaha, not like that much :)

-- just shut eveything down and restarted and loaded the hip all seems to work - thanks to both of you for the help.

@Christoph-Hart said in new XMLHttpRequest is not supported anymore.:

No, I am working on a little secret side project right now :)

Ok ;)

in the image folder as explained here: http://hise.audio/manual/ScriptPanel.php

section 1.1.4: fonts.

OoooooooooooooooooooKayyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy :/

Images folder + Fonts folder INSIDE images folder. Not directly inside Image folder....

@ustk We hope so :)

I think you need to manually set the value of the viewport when the preset loads. But I don't think it's possible to do the same for the preset browser. Although I could be way off and there might be a better solution.

@Christoph-Hart said in Factory Presets:

Good idea I could add a „read only“ flag to all presets embedded in the binary.

Yep, but please don't forget implementing the VST3 export in the prorities of adding pile ;)

@d-healey said in Hise Path and a couple of newbie questions.:

open your HISE project on any machine no matter what OS you made it with.

Thanks again , pretty excited to get into it .

@Stroggan said in Discord Channel:

nyway I'm rather tired of the bad developer workflow that kontakt 5 offers so I decided yesterday to make another attempt at HISE, currently porting a Fingerpicked Acoustic Guitar library over.

Great Idea...
And Done.

Here it is
https://discord.gg/hFXYra7

Everyone join :)

@pes Never mind i´ve found this: https://forum.hise.audio/topic/314/note-panning

@Jay You deleted a very important line from my presetHandler script

childSynths[id].asSampler().loadSampleMap(patchName + "_" + id); //Load the sample map

Without that line no sample map will be loaded. You can see from the parameters that the format is the patch name from the manifest + _ + the id of the sampler. So that is what the sample map name should be. But you might need to change things to work with your project, I just showed you how it works in my project as an example.

@d-healey Ok, I'm a perfect donkey! LOL
Here's the simple code to use ;)

const var Label1 = Content.addLabel("Label1", 10, 3); Content.setPropertiesFromJSON("Label1", { "width": 358, "height": 30, }); Label1.set("text", Engine.getCurrentUserPresetName());

Just to talk about companies decisions...

"Softube drops 32-bit support

In order to keep on delivering plug-ins with stellar sound quality, Softube will be focusing on 64-bit plug-ins only from here and on. This means that our future releases will only contain 64-bit plug-ins.

We do this so that we can put all our efforts into making great new products. Maintaining development tools for the 32-bit platform is becoming increasingly difficult and time-consuming.

Many software users and companies have already made the move to 64-bit, so chances are that you won’t be affected by this at all. But like any technology shift, it’s one that’s painless for some and a big headache for others."