location dependent and 3+ years old company... That's discrimination... What are they waiting for to make a "except if you pay more" rule? 👊 🤣

@d-healey ah good idea, don't use textArea at all 😆

Perfect, thanks

@dannytaurus 50mb, it includes whatever you put in the audio files folder. Loops usually go in the Samples folder I think.

@Gabor-K thanks, i dont have an intel Mac. Have no chance to test my plugin on the intel Mac. But i wonder if i recompile the HISE on the right setting to support "Standard Architectures (Apple Silicon, Intel)"...

This is a sample I recorded myself, I hope it can help you, the instrument is the Erhu from China.

Sample

@Lindon Doesn't seem to be. I've just come across some more issues today with the Viewport as well, that when attaching it to a Broadcaster it is putting out odd values for the viewPositionX and viewPositionY in an unpredictable manner. If I had more experience coding I would try to do something about it myself, but in the meantime I'll have to add another bug report on it.

@Christoph-Hart Thanks, I will email you now

@filipalex96 I guess FL MidiOut is required for your Plugin.
Midiout and your Plugin must be share the same Midi port Number.
Midi.jpg

@orange Sweet. Thanks! We'll give this a try again tomorrow! 🙏

@d-healey Awesome, thank you

@Christoph-Hart Thank you

@ustk

python, julia or matlab is your friend.
There are many scientific libraries for LUT generation, which can do curve fitting and other clever thingies.

I have an entire custom app built in python that can reverse engineer waveshapers from any linear shaper vst. I've reverse engineered many algorithms automatically using this tool.

BTW, use JuceVectorizedMath if using c++
You can do multiply add operations on a whole buffer. Efficient.

Nice, thank you @Lindon !

@d-healey Thanks for all your help. It's very much appreciated.

@AxiomCrux said in Exporting as VSTi:

No, I was trying to use the built-in export feature, does that require me to compile HISE?

When you "export" from HISE what actually happens is HISE builds a JUCE project for your plugin and runs the compiler to build it. This is the same process as compiling HISE itself.

Also you generally want to be compiling your projects using the same version as the source code that was used to build HISE, otherwise you might end up with weird conflicts.

So generally the first step is to compile HISE. That way you know everything is setup correctly for compiling. Then you export your project.

@AxiomCrux said in Exporting as VSTi:

built-in compiler script to figure out how to get a plug-in beta test installer for Mac and PC. I believe I found a video you had made for the process on Mac

I would advise in general not to run scripts (even from me) unless you understand what the script is doing. Scripts can do a lot of damage if not setup and used correctly.

All my build script does is the same manual steps you'll do when exporting your project from HISE. So start with the manual version, then you'll be able to follow along with what the script is doing.

@HISEnberg I hadn't thought of that—thanks for the idea. I actually used the saturator as an example, but I'm using a chain of dynamic effects, including the saturator and phaser, both of which have modulation. Still, I could definitely redo them using Faust or the built-in functions of Scriptnode. Thank you :)

@Sampletekk Well it does say "Processen slutförd" at the end.

@orange Thanks!

@d-healey Thanks for the help, I really appreciate it, I will check the link

@griffinboy Ok, noted. Thank you