Helm: new cross platform synth beta release

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

Hooray, it passes AU validation again. Nice job, Matt! :tu:

Post

Nice ! Thank you, Matt :D

Post

I haven't had a chance to check the synth out yet, but on your blog, the -evolution- of your new logo was pretty fun to see. Am I getting the *joke* that it's now called Helm, and the logo sort of looks like an alien head with a helmet on ? :hihi:
Image

Post

Does this thing come packaged with presets yet? I want to hear what it's capable of in the right hands.

Xenos and The Unfinished, get in here! :phones:

Post

Great! Now the 32 bit vst works fine in Mulab. I'm really digging it. Diverse and so tweakable, easy to get nutty. You're on the way sir!

Post

Very cool synth! So far it's very impressive. Is there any way no to have osc phase retriggered each note?
AJYoung wrote:Also, feature question:
Maybe I'm just missing it, but is there any way to change oscillator phase? Or more specifically, to make the unison free-running. Can't get those juicy supersaws without it! :ud:
Would be a very nice feature to have the ability to create nice lush pads with no synced phase on osc multiple voices.
mtytel wrote:Also, feature question:
List of 0.6 changes:
...
- Fixed unison phasing at beginning of note
...
- Better starting phases for unison voices
...


Does this have to do with phase triggering?

Have a nice day!

Post

So I'm trying to compile this thing in Linux with the makefile but I get to; Compiling juce_VST_Wrapper.cpp
../../../JUCE/modules/juce_audio_plugin_client/VST/juce_VST_Wrapper.cpp:69:51: fatal error: public.sdk/source/vst2.x/audioeffectx.h: No such file or directory
#include <public.sdk/source/vst2.x/audioeffectx.h>

Where in the dick I'm I suppose to put the sdk folder? I can't find any reference to it's path in any file and I'm about ready to smash my own head in with a hammer. This is the first time trying to compile a vst on Ubuntu so any help would be greatly appreciated. It's been three days stuck on this.

Post

Is there any specific reason to compile helm? Ready made deb files are available on the website and in the KX Studio repo's.

Post

Bigtea wrote: This is the first time trying to compile a vst on Ubuntu so any help would be greatly appreciated. .
Helm is available as both windows, and native linux vsts.
No need to compile anything.

Scroll down this page to a list of 5 commands to enable the kx-studio
repositories in your ubuntu.

https://linuxmusicians.com/viewtopic.php?t=9666

Copy/paste and run each command.
Then start synaptic package manager, as sudo,
and use it's reload button to refresh your now expanded collection of software.
(There are great youtube videos of synaptic gui, if it is new to you.)
Helm native linux vst, and many others will be in your synaptic listing,
which has several handy ways to list and find your choices.

Linux has it's own native vsts,
different builds than their windows counterparts, as well as instruments and plugins
in LV2, dssi, and ladspa formats.

There are so many well-maintained audio packages these days, that compiling
is an option, but far from a necessity, and there is a topic at the link to request
that software of interest, be compiled, turned into debian packages,
and added to the repositories.
Cheers

Post

https://github.com/mtytel/helm/blob/master/helm.jucer has this line:

<LINUX_MAKE targetFolder="builds/linux/VST" vstFolder="~/srcs/VST3 SDK" vst3Folder="~/srcs/VST3 SDK" extraCompilerFlags="-ffast-math -msse2" extraLinkerFlags="-ffast-math -msse2">

so put the public.sdk in ~/srcs/VST3 SDK ?


But like said already, there are binaries available ..

Post

ras.s wrote: But like said already, there are binaries available ..
I'm not actually distributing the linux vst binary because of some license issues.. I will in the future, probably the next release.

Post

Bigtea wrote:So I'm trying to compile this thing in Linux with the makefile but I get to; Compiling juce_VST_Wrapper.cpp
../../../JUCE/modules/juce_audio_plugin_client/VST/juce_VST_Wrapper.cpp:69:51: fatal error: public.sdk/source/vst2.x/audioeffectx.h: No such file or directory
#include <public.sdk/source/vst2.x/audioeffectx.h>

Where in the dick I'm I suppose to put the sdk folder? I can't find any reference to it's path in any file and I'm about ready to smash my own head in with a hammer. This is the first time trying to compile a vst on Ubuntu so any help would be greatly appreciated. It's been three days stuck on this.
You need to put the vst3 sdk in "~/srcs/VST3 SDK"
You have to download it from steinbergs site because I can't distribute it.

http://www.steinberg.net/en/company/developers.html

Post

Yea I figured it out. Thanks for the replies. I actually feel really dumb taking multiple days to figure it out.

Post

Can somebody help clear up a question for me: How do I assign a modulation source to a destination?

Pretty sure I click the helmet part of the logo in the source (and make it turn blue) and then click any of the green destinations? I was messing with this last night and none of my clicks in the destination zones seemed to be registering. At least I didn't see any modulations afterwards when I pressed a key.

And then afterwards do I have to click the helmet again to make it not be blue anymore? And what does it mean when the bottom part of the logo under the helmet is green? That it's assigned to a destination?

Post

You have to click and drag ! to give the amount of modulation you want that parameter to have and the direction.

Then click the helmet again when your done :)

You can also right click a source to see what destination(s) is/are linked to it. Or the other way around, rightclick a destination to see what source is etc...

Lava wrote:Can somebody help clear up a question for me: How do I assign a modulation source to a destination?

Pretty sure I click the helmet part of the logo in the source (and make it turn blue) and then click any of the green destinations? I was messing with this last night and none of my clicks in the destination zones seemed to be registering. At least I didn't see any modulations afterwards when I pressed a key.

And then afterwards do I have to click the helmet again to make it not be blue anymore? And what does it mean when the bottom part of the logo under the helmet is green? That it's assigned to a destination?

Post Reply

Return to “Instruments”