@remarkablex said in About Steinberg VST2 License:

That would also be unfair to the other users, who have now switched to VST 3.

Well, they look are quite slow on VST3 license. I sent mine on 6 February and get this reply on 9:

***Feb 9, 12:43 CET

Thank you for contacting Steinberg Support. I have forwarded your inquiry to the right department. You will be contacted regarding the license agreement as soon as possible. Thank you for your patience!

For further questions please do not hesitate to contact us.

Best regards,

Alina Andriescu

Technical Support Steinberg***

After that, the most absolute silence. Let's wait...

@pnyboer said in Notes on my first try....:

I expected the "HISE.2.0.0.pkg" to install the 2.0 standalone - is that incorrect? I realize that best practice is to compile the standalone from source, but I'm just getting my feet wet!

You right, but it was an oversight when Christoph put the file, then we all keep on to download the source and compile it, also because Christoph is usually updating the source after bug fixes. Don't worry, mine was just an advice, not a criticism ;)

@pnyboer said in Notes on my first try....:

The Mac package currently claims that it is version 2.0, but the About window in HISE Standalone shows “version 1.6.0 (19 Nov 2018).”

That's the link of the last source that you should compile to get the standalone version https://github.com/christophhart/HISE

And here the David's tutorial about compiling HISE Standalone binary https://www.youtube.com/watch?v=0TtezP8lp24&t=5s

oppss

@Christoph-Hart said in A question to Christoph about plugins and Windows platform.:

Yeah, that's nonsense. It has literally no effect on CPU usage whether resources are embedded in the plugin binary or not.

Totally agree :)

@staiff said in A question to Christoph about plugins and Windows platform.:

I do not know if it's a security issue, but I notice that often these plugins are more "heavy" and CPU hog.

I didn't find that VST I'm working on with Hise are hungry of CPU by the way :) But what you say makes sense, with Delphi, I used to put graphics and other stuff into external dlls that were called by the program, which is a normal practice and I find it more orderly than filling a folder with many files, unless, as you say, the intent of the developer is to allow the user to customize the graphic environment.

@Christoph-Hart Thank you, well the guys who use it, told me that SynthEdit 1.1 exported a normal dll (vst2) and only from the 1.2 version the exporting on VST2 and now VST3 have the external files because Microsoft security system could block the plugins (that is Jeff's thought) but they also asking about the real possibility that 8.1 or Windows 10 can really block packed files inside the VST. Maybe you are surely right, Jeff could change from the 1.2 version using a runtime wrapper.

@Lindon said in Effect Slot cause crash:

Every time I select an "Effect Slot" FX - HISE crashes - any one else getting this

Same here

@Christoph-Hart said in A question to Christoph about plugins and Windows platform.:

Lol why would you want to extract them to disk on runtime? Looks like a funky hack.

All resources are compressed using zstd and embedded into the plugin so you don‘t need to extract anything.

Huh? I don't want extract them (maybe I explained it badly, sorry), I saw that SynthEdit do that, so I was asking you if is it true what Jeff says about Microsoft, that it's better don't put graphic elements and other stuffu inside the vst because Microsoft security prevents files being extracted from VST at runtime. I never noticed that when a vst is used the Wiondows OS extracts the stuff from the vst, I can't believe in that. Just like what d'you think about this thing Jeff McClintock said... imho I think it's a weird concept and I'm really surprided that Jeff said that :)

I was checking SynthEdit and I found that it export the vst plugins with all the graphic files and modules outside the vst. Jeff McClintock made this choice about that explaining so ""...the reason for this is Microsoft Windows increased security which prevents files being extracted from a VST at runtime.".I found that a bit weird, I mean Hise or other software have no problems about create vst with all the stuff inside, Windows behavior is normal, no prevent actions or other. @Christoph-Hart what d'you think about? Is it possible that Microsoft security system has issues with vst compiled as Hise or other software for audio developing? I never noticed that thing

@staiff said in no mono/poly filters in hise 2.0 global audio fx ???:

is there a way to have a global audio filter FX or never anymore ?

In the 2.0 there's only the Harmonic Filter Monofonic in the global section.

@Christoph-Hart It's like to see a fusion between the fisherman and the mermaid in the Frederic Leighton's painting :P

@d-healey said in HISE shop with fees for Christoph:

@ossian1961 Just had a look at the Tracktion website. The licensing system they show is a bit misleading. Nowhere on that page does it mention that Tracktion can be used under the terms of the GPL license, you have to go to the github link to find it.

I see it now :)

@staiff said in HISE shop with fees for Christoph:

like 5 or 10% on sales ...

or the licensing system used by Tracktion for Tracktion Engine (that is like JUCE's one)...

Tracktion Engine Develope

Light speed!!! Thanks !!!! :)

@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) ;)

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

Sure there are a few hiccups, but I still think it's the best way to combine a WYSIWYG editor with scripting.

I think that the few hiccups could have not a solution for the nature itself of the way or I wrong? ;)

@Christoph-Hart said in Examples of full working Hise made plugins:

but an update is overdue

I remembered you wrote something about some features you included and that weren't available on the 2.0 :P

@Stroggan said in Performance comparison Kontakt 5.8 vs HISE:

Hopefully I don't encounter any issues because this really makes me want to go 100% HISE in the future.

...and you're forgetting most important thing, Kontakt can't create a real plugin ;)

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

Frankly Im not bothered about using presets right now I just want HISE to save and recall the state of a widget.

I'd like it too. I remember, for exemple, that in the old release when you put a widget on the GUI you created, the code of that appeared on the script, that was like a "RAD" programming ide, but Christoph took off this feature in the new release we use and now I feel the widget palette a bit "weird" because when you add a widget through the script, obviously the properties used in the script are not available to modify in the palette, but only through the script, so at the moment the script-Widgets palette looks a bit "ambiguous" system. Anyway, Hise is under costant development and I have faith in Christoph skills, I'm sure he will give a more logic and stable nature to his wonderful creature :)