One Synth Challenge #174: InfernalSynth by sjoerdvankreel

[sjoerdvankreel]

@doctorbob / everyone

<< I take it you can use the "effect plugin" as well as the VST3i

If anyone is having troubles using the "bundled" version (instrument + fx in 1 dll) please shout out. Already uploaded an instrument-only dll, maybe i should provide an fx-only dll, too.

[sjoerdvankreel]

@mac people

I want to do a mac version. Multiple people already offered to get me a mac (thank you so much). Have to admit i am a windows dev, never touched a mac, never seen a mac DAW, let alone programmed for a mac. This is sort of a high-risk, high-reward project. It's on the agenda, but cant make any promises.

[sjoerdvankreel]

@doctorbob

<< I don't know many (any?) VST3i's which don't implement pitchbend - all our synths have a controller for this
Well, now you know of one

<< I guess MPE should be on the to-do at some time too - but that would be another whole layer of stuff!!!
Yeah, MPE seems big. Especially with VST3 translating it to note expressions.

Anyway, you seem to know your way around this, so i hope you dont mind me firing a few questions at you. I never ever worked with midi. Never owned a midi controller, never programmed for it, nothing. Let alone the fancy stuff like aftertouch and mpe (and midi 2.0?) Plus, i have to fit that stuff into what is provided by vst3. So far i found out that some very specific midi messages are mapped by vst3 to built-in vst3 commands (pitch wheel being one (the only?) of them). What would be the best course of action here?

* Implement pitch bend + selection of low/high note or a single range control seems a no-brainer (apart from ui space, yeah
* Would it be worthwhile to assign pitchbend as a generic modulation input also (like velocity, but with a full curve instead of single value)?
* How about generic CC messages? I'd rather not deal with stuff like program change. But apparently midi also does amp/pan (why would i need that? seems superfluous, rather assign automation/modulation to parameters directly).

All in all i'm a bit struggling here, from all the stuff i've read so far. For example this: viewtopic.php?t=538083&start=15. I'm still not sure where to go. Either do pitch wheel and be done with it, or take some more overall approach to see how all of midi can fit it. And, probably, buy some basic midi controller to see how it plays out.

Any guidance?;)

[SeBaer]

Plus, i have to fit that stuff into what is provided by vst3. So far i found out that some very specific midi messages are mapped by vst3 to built-in vst3 commands (pitch wheel being one (the only?) of them). What would be the best course of action here?

You could consider CLAP, which is developed specifically to overcome VST3 shortcomings. That community seems very eager to help... And CLAP-to-VST3-converters are available

* Would it be worthwhile to assign pitchbend as a generic modulation input also (like velocity, but with a full curve instead of single value)?

That would be very nice, especially if it was possibly to detach the pitchwheel from pitch to use as an additional expressive control.

[doctorbob]

That would be very nice, especially if it was possibly to detach the pitchwheel from pitch to use as an additional expressive control.

Yes please. I already do this via parameter automation in Reaper to modulate e.g. the filter freq as well as OSC cents (why +/- 50%, not +/- 100% - ie +/- 1 semitone?). It's nice to have the tone change when bending notes in e.g. a sax, flute etc.

@sjoerdvankreel ...

I would also look into the CLAP format, gathering pace.

There are some OSC-ers who have done Mac development of vst3, maybe a shoutout to them might help you.

On hols for a few weeks now, so won't be able to respond quickly, maybe others can chime in on the MIDI things ... most people ignore midi-pan, but the expression controller (volume) is used a lot with a foot pedal to add nuance to a performance. Plenty of cheap midi controllers out there, aftertouch on the slightly more expensive ones - watch out for per note aftertouch vs full keyboard aftertouch (as in my DX-11 !!)

Also, lots of new esoteric controllers around as well as MPE ones.

Probably best to stick to the basic MIDI stuff first.

Some thoughts: Variable slopes for the HPF please? Maybe some scheme for better routing of the FM to include controlled level feedback? Lots of synths use a matrix style UI for that.

dB

[silverpants]

My entry for #174. "A Minor Deviation".

Jay suggested a minor key at 90bpm. In fact I haven't knowingly used a major chord at all!

https://soundcloud.com/slugnest/a-minor ... al_sharing

I've had to get this out early because I'm away for the rest of August inter-railing around Europe with my family

11 Instances of Infernal Synth - all designed from scratch.
DAW: Reaper
Dead Duck: Filter, Compressor, Limiter, Delay, TiltEQ
OrilRiver Reverb
Reaper: ReaEQ, ReaXComp
Limiter No6, Khs Gain. SPAN, YouLean Loudness Meter.

[doctorbob]

Hot on the heels of @silverpants, here's DoctorBob's entry. I too am away very soon so have to submit early as I don't know when I will get the call for my nephrectomy.

DAW: Reaper
Track Details: 7 * Infernal, 7 * ReaEQ, 5 * Oril River, 2 * LFX-1310, 2 * Bass Professor, 1 * STFU, 1 * Pecheneg Tremolo
Master Details: TDR VOS SlickEQ, Voxengo MSED, LoudMax 64
Metering: SPAN, Youlean Loudness Meter
Stats: LUFS: -16.5, DR: 12

Enjoy something a little different from me.

https://soundcloud.com/doctorbob/ambien ... 4-infernal

[violator_alba]

@mac people

I want to do a mac version. Multiple people already offered to get me a mac (thank you so much). Have to admit i am a windows dev, never touched a mac, never seen a mac DAW, let alone programmed for a mac. This is sort of a high-risk, high-reward project. It's on the agenda, but cant make any promises.

What IDE are you using on Windows? If by some chance you're using Visual Studio Code, it works very well on the Mac. I'm primarily a Windows developer but have done basic stuff on the Mac. I don't get on with XCode and find Visual Studio Code much more productive.

[sjoerdvankreel]

@SeBaer

<< You could consider CLAP, which is developed specifically to overcome VST3 shortcomings
It's already on the list. But, like mac and mpe, i expect this to be quite a big feature. Might not ever come around to do it.

<< That would be very nice, especially if it was possibly to detach the pitchwheel from pitch
Great, then i'll model it in the gui pretty much like velocity which can also be assigned to anything. Plus extra control for the bend range somewhere.

@doctorbob
<< why +/- 50%, not +/- 100% - ie +/- 1 semitone?
Nothing specifically, just figured that's the minimum range needed to cover every pitch. If -1/+1 is preferred then ill just go with that.

<< Probably best to stick to the basic MIDI stuff first.
Will try out pitchwheel and expression first, leave complicated stuff for later.

<< Variable slopes for the HPF please?
The math is out of my league. Current filters are a 1:1 copy from a paper from cytomic website. Might be able to find a different algorithm with adjustable slopes though, and offer an additional filter mode.

<< Maybe some scheme for better routing of the FM to include controlled level feedback
Nice one. Indeed it's very coarse now.

@violator_alba
<< What IDE are you using on Windows
Plain VS2022. I planned to look into xcode, but thanks for the vscode tip.

[MadMcMan]

Chris from airwindows as a bunch of filters that are all opensource https://github.com/airwindows/airwindow ... er/plugins , might be useful for getting some more effects and things in.

I find i'm missing global envelopes and maybe using global lfo's (future env?) on voice too.

I'd like delay and reverb on voice too if thats possible

[MorphedDreams]

@MorphedDreams

<< Random seems to repeat the same sequence or I didn't set something right?
Nope, thats the way it works for now. Resets on cycle end. I take it you want free-running random oscs/lfos? That'd be a great addition indeed.

<< And is there random on note option?
I don't understand, could you please clarify?

Yeah free-running random oscs/lfos would be great, and random on note is a random value every time a note is played and the value don't change until you press note again

[sjoerdvankreel]

@morpheddreams random-on-note: i believe a global random lfo assigned in hold-mode to a per-voice mod target does what you want?

[sjoerdvankreel]

@madmacman thanks for the filters. Global lfo on voice is already possible, its the g.lfo mod input. I never understood global envs, do they repeat or something? About per voice delay, a naive implementation uses massive amount of memory. Maybe a dedicated single delay per voice could work, but i have to figure out how to route it wrt existing fx modules.

[doctorbob]

Oh yes, before I forget an hop on a plane ... please make the MIDI expression assignable as a modulation (as per velocity) - if people have an expression pedal, ie continuous controller vs eg a sustain pedal which is just on/off, then this pedal cold be used for many extra performance expressions across all the various modules/assigns within this synth.

Good to see people coming on-board with help and suggestions for codebase.

There are Mac vst coders around, hopefully one will chime in here ...

dB

[MadMcMan]

@madmacman thanks for the filters. Global lfo on voice is already possible, its the g.lfo mod input. I never understood global envs, do they repeat or something? About per voice delay, a naive implementation uses massive amount of memory. Maybe a dedicated single delay per voice could work, but i have to figure out how to route it wrt existing fx modules.

so you can have one part of the sound controlled by an enveolpe rather than an lfo.

also on the dropdowns on the routing filtering out what doesn't apply would be great. ie you want to modulate voice fx 2 thats a distortion why do i see the options of filters etc? its confusing

If you want loads of github tickets let me know