
Posts
-
RE: Simple gain vst3: interface does not work
@Aueh post a snippet of your project
-
RE: Generate RSA activation code for machine code on the web page?
@CatABC this looks about right....
-
RE: Win 10 / VS 2017 HISE Build Error
@Dadang you still have ipp on somewhere..
-
RE: FrontEndMacro: Display Parameter Text Instead of Parameter ID
@bendurso said in FrontEndMacro: Display Parameter Text Instead of Parameter ID:
@Lindon Or you could disable isPluginParameter checkbox, and insert a name for pluginParameterName anyway
I think you are missing the point, this is about QoL is it not?
-
RE: FrontEndMacro: Display Parameter Text Instead of Parameter ID
@bendurso hmm, is this handling the case where I dont set a pluginParameterName name? In that case it should fall back to the param name....
-
RE: Paid 3rd party DSP licensing? (Eventide, Sinevibes, Audio Damage etc.)
@Straticah said in Paid 3rd party DSP licensing? (Eventide, Sinevibes, Audio Damage etc.):
@Lindon I did that a while ago for Reverbs and have not found anything better than freeverb or ZitaLight unfortunately...
I guess like the rest of us its just a matter of coding up your own then...
-
RE: Paid 3rd party DSP licensing? (Eventide, Sinevibes, Audio Damage etc.)
@Straticah you would have to check the license in each case Im afraid...
-
RE: Paid 3rd party DSP licensing? (Eventide, Sinevibes, Audio Damage etc.)
@Straticah the faust based FX are actually very good have you tried them?
-
RE: Polyphonic Aftertouch?
@Morphoice said in Polyphonic Aftertouch?:
@Lindon given you've been trying to get polyphonic aftertouch to run too, here's a working solution from @ulrik . I'm trying to get it running on my side, maybe you want to give it a try too and let us know how it goes.
you mistake me for that person I'm afraid - all I've been trying to do is get channel aftertouch working correctly and consistently across HISE modulators...
-
RE: How do I load a midi script programmatically?
@d-healey said in How do I load a midi script programmatically?:
@Lindon said in How do I load a midi script programmatically?:
{PROJECTS}\mysub\yoursub\afile.ext
You don't need a slash after the wildcard, and if you use forward slashes only it will work on all systems. Don't know about the lopp player though.
yeah that might work for you but as I say its at the very least unreliable for me, it might be cases of paths without {PROJECT_FOLDER} in them
-
RE: How do I load a midi script programmatically?
@d-healey I do what i've always done and put the font in the images folder and call this:
Engine.loadFontAs("{PROJECT_FOLDER}DIN Alternate Bold.otf", "DIN Alternate");
works everywhere.
Where it doesnt work is if you want to declare some sub-folder path i.e.
{PROJECTS}\mysub\yoursub\afile.ext
so its simple to work around:
// on init const var WINDOWS = "WIN"; const var MAC = "OSX"; const var OS = Engine.getOS(); //elsewhere... if(OS == WINDOWS) { theLoopPlayers[pos].setFile(LP_LoopFileFolder + "\\"+ component.get("text") + ".wav"); }else{ theLoopPlayers[pos].setFile(LP_LoopFileFolder + "/"+ component.get("text") + ".wav"); };
You of course will also want to check for Linux...
-
RE: How do I load a midi script programmatically?
@d-healey said in How do I load a midi script programmatically?:
@Lindon said in How do I load a midi script programmatically?:
you are going to have to use different separators based on the OS in question
fwd slash for mac os backslash for windows:You should be able to use the same on all OS and HISE will handle it. I think the issue here is you don't need to put a slash of any kind after
{PROJECT_FOLDER}
because that wildcard includes a slash.You should, but my experience is you cant...
-
RE: How do I load a midi script programmatically?
@Orvillain you are going to have to use different separators based on the OS in question
fwd slash for mac os backslash for windows: -
RE: Simple gain vst3: interface does not work
@Aueh read the forum. Thus very problem was posted and solved this week.
Hint you will need to use a hardcoded fx
-
RE: Compiling Just an Empty Clone Container Fails
@d-healey said in Compiling Just an Empty Clone Container Fails:
@Lindon said in Compiling Just an Empty Clone Container Fails:
form a completely fresh, new and empty project...
But you're using the snippet Bill posted?
Yes
-
RE: Compiling Just an Empty Clone Container Fails
@d-healey
Im usingc808118776c8f41f5f718faa4f9af3ea5313ba72
from 17th feb.
Im also doing this form a completely fresh, new and empty project...
-
RE: Compiling Just an Empty Clone Container Fails
The project builds fine here, windows - latest HISE build:
include_juce_audio_devices.cpp include_juce_audio_formats.cpp include_juce_audio_plugin_client_utils.cpp include_juce_audio_processors.cpp include_juce_audio_utils.cpp include_juce_core.cpp include_juce_cryptography.cpp include_juce_data_structures.cpp include_juce_dsp.cpp include_juce_events.cpp include_juce_graphics.cpp include_juce_gui_extra.cpp include_juce_opengl.cpp include_juce_osc.cpp include_juce_product_unlocking.cpp include_melatonin_blur.cpp C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.38.33130\include\bit(11): warning STL4038: The contents of <bit> are available only with C++20 or later. [D:\Hise_Work\test4TheDoc\Binaries\Builds\VisualStudio2022\t est4TheDoc_SharedCode.vcxproj] include_hi_snex_60.c include_hi_snex_61.c include_juce_gui_basics.cpp test4TheDoc_SharedCode.vcxproj -> D:\Hise_Work\test4TheDoc\Binaries\Compiled\Shared Code\test4TheDoc.lib include_juce_audio_plugin_client_VST2.cpp Creating library .\..\..\Compiled\VST\test4TheDoc.lib and object .\..\..\Compiled\VST\test4TheDoc.exp Generating code Finished generating code test4TheDoc_VST.vcxproj -> D:\Hise_Work\test4TheDoc\Binaries\Compiled\VST\test4TheDoc.dll Press any key to continue . . .
and the DLL build fine too: