FINALLY SOLVED!!!!!! :)
To get the PresetBrowser viewer loaded and so the label that shows the first preset ("Init" for exemple) everytimes the plugin is launched just add this line on the main script:
Engine.loadNextUserPreset(true);
:)
FINALLY SOLVED!!!!!! :)
To get the PresetBrowser viewer loaded and so the label that shows the first preset ("Init" for exemple) everytimes the plugin is launched just add this line on the main script:
Engine.loadNextUserPreset(true);
:)
@Jay said in Several Samplemaps at Once:
p.s. Sorry I don't know how to make a one line snippet.
@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());
Merry Christmas to you, your family and @Christoph-Hart and all guys of the Forum
Well, I read an old topic about how to create a VU meter by @mwplugs and some guy wrote about KnobMan. I use it for Kontakt libraries I make and I confirm it's perfect on HISE too. I can say that I can handle KnobMan pngs on HISE in a way more comfortable than Kontakt. That's one of the many good reasons because I'm agree with David Healey about HISE is better than Kontakt. :) Anyway here you can see some examples of Kontakt instruments made by me with all graphic stuff created with KnobMan :
https://www.kontakthub.com/product/nebulae-kontakt-instrument/
https://www.kontakthub.com/product/biosynth-kontakt/
https://www.kontakthub.com/product/profundo-kontakt-aleatoric-synth/
@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...
@Christoph-Hart It's like to see a fusion between the fisherman and the mermaid in the Frederic Leighton's painting :P
@orange said in ...Always on the PresetBrowser:
@ossian1961 If you rename your preset title
- Init
it will be on top of the presets, and you can use
Engine.loadNextUserPreset(true);
That works! Thanks!!!!!! :)
@d-healey said in BAD BAD BAD HISE!:
@ossian1961 XML is much easier to fix because we can view it in a text editor.
Anyway I hope it doesn't happen, it's a quite annoying thing ;)
@d-healey I'll do if it fails again, I mean, it happened four times on twenty and more times I opened it... it's like that sometimes the automatic preset saving gets trouble, though it's the XML that fails and return same message that it's unable to load the interface.
@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
@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