E-Phonic Invader 2 v1.0.11 (WIN / OSX)

[exmatproton]

Can we get a new version of Drumatic before we go all "Invader Pro?"

+1

[BONES]

If you love the core sound of any synth why wouldn't you want to expand the range of sounds it can make?

Up to a point but Invader 2 has a massively broad palette already, I don't see why it needs more than a bit of refinement. Something like GR-8 definitely needs a few more features to be properly useful but Invader 2 hits a sweet spot, the same one hardware makers in the 1980s hit upon with instruments like the Prophet V and Oberheim's OB series. For me, cross-modulation is the key. Once you can do Hard Sync, Ring Mod and/or FM, the possibilities open up by orders of magnitude.

As just one example wouldn't you like to be able to route the Oscs through their own Filters instead of both through the same filter?

No, I can't think of anything less useful and I've never understood why some synths allow that. If I want two different timbres, I'll load two instances and layer them (which I never do because I never want that).

I can already think of patches I would make if this feature were added and so on. I could easily find uses for more Oscs, more FX etc etc...

And I can think of a dozen synths in my VST folder that provide that stuff (and more) already. Why would I need another one? It's about horses for courses. If you don't need four envelopes and five LFOs to make simple bass patch, why use a synth that forces you to deal with all that stuff?

Clearly, this is a side hustle and e-phonic's synth development time is very limited...

... if doing a sequencer, I'd want options for velocity, per-lane length, multiple patterns (assignable to keys), and hit probability.

You don't see the contradiction here? You want a dev whose time is limited to waste it on things your host can already do for you, rather than on things that might actually extend the possibilities of the tool. Don't you think that's stupid? I do.

It's also a bit of a stretch to describe Invader as a side hustle when it's at version 2 and looks a lot more like a serious tool than any of e-phonic's other products.

Seems a shame to stunt a great sounding synth just to cater to simple but it is what it is.

Invader is anything but stunted or simple, as the factory presets demonstrate amply. To speak about it like that really just shows your lack of ability, your reliance on a massive feature set instead of deep know-how, more than any limitations of the instrument.

@Bones....I have you blocked. I won't read or respond to any of your posts.

Awwww, poor baby gets upset when people thrust reality in his poor, widdle face. I suppose you sleep with a light on, too.

Of course it's a very simple synth if you have the proper frame of reference. Compare it to Parawave Rapid or DUNE 3 or Zebra 2.

I reckon I could probably do more than 80% of what those things do with Invader and 100% of the things I'd want to do. It seems you look at these things in a bubble but that's not reality. They are all PLUGINS, they can only exist in an environment rich with other tools to extend their sound shaping possibilities. I can easily, for instance, mimic DUNE's layers simply by loading up multiple instances of Invader and saving the set-up in my host for instant recall whenever I might need it. I can get all of DUNE's effects from the effects that come with my host. Where I might use a second filter in DUNE as a bass-booster, I can use EQ in my host. I already have that functionality, why would I need it duplicated in a plugin? It's for one reason and one reason only - because it makes the factory presets sound better. It's pure marketing.

Ok I'm done with this thread.

That's the way, don't take any risks that reality might impinge on the fantasy world you seem to live in.

[Funkybot's Evil Twin]

Clearly, this is a side hustle and e-phonic's synth development time is very limited...

... if doing a sequencer, I'd want options for velocity, per-lane length, multiple patterns (assignable to keys), and hit probability.

You don't see the contradiction here? You want a dev whose time is limited to waste it on things your host can already do for you, rather than on things that might actually extend the possibilities of the tool. Don't you think that's stupid? I do.

No, I don't. When it comes to drum synths, the workflow can be a lot faster and it can add a lot of value to have a sequencer built in. Examples:

1. Drawing can be streamlined to focus on drums
2. Modulations can be added (at this step, do this other thing...ratchet/repeat, adjust the filter, change probability)
3. You can have an internal clock with swing
4. You can have a pattern launcher where patterns are triggered by certain keys
5. You can edit the pattern length for individual lanes

...these kinds of specialized functions/tasks make a LOT of sense in a drum VSTi, which is why so many drum VSTi's include at least some of these features. Having them, can actually improve the workflow versus trying to tediously do all that in your DAW.

I might guess by the how you tediously quote people and breakdown their posts sentence by sentence and write long replies, that similarly, you may not mind tediously going through the steps of doing similar things in your DAW. If that brings you peace or joy, by all means. But I'm just saying, if e-phonic could look to add a drum sequencer with features like that, they'd be appreciated by me and I'm sure others. Why? It can make for a nice workflow and also be fun to work with a nice sequencer like that. Did I say "you must do that or else?" No. It's not a dealbreaker. But would make for a better product IMO. If e-phonic agrees and choses to do so.

[BONES]

Doesn't your host have a drum mode for its piano roll? That takes care of point 1. The rest of your points are all things you can do easily in your host, too. It's the same non-argument as built-in arpeggiators. It's a needless duplication of functionality that is more limiting than doing it in your host's sequencer.

[Funkybot's Evil Twin]

Doesn't your host have a drum mode for its piano roll? That takes care of point 1. The rest of your points are all things you can do easily in your host, too. It's the same non-argument as built-in arpeggiators. It's a needless duplication of functionality that is more limiting than doing it in your host's sequencer.

Not if it creates a faster workflow being custom tailored, can be more deeply integrated, or just made more fun.

Why even have a synth with LFO's then BONES? You can just do that with host automation in your DAW! Why have poly synths with amp envelopes? You can just have 8 mono synths, and shape the volume envelope of each with your DAW! Filter envelopes? Just draw them in! Piano sample libraries? Just manually place the individual note samples where you want them and build up your piano track that way!

Sounds completely absurd, but it's all stuff you can just do in your DAW! Doesn't make it fun or enjoyable or even a remotely good idea. Sometimes it's nice to have specialized tools that can make these mundane things easier.

[BONES]

Orion actually had an LFO built into it's Piano Roll and it was definitely superior to using an LFO in an instrument, it gave you far more control. So I'd agree with you, synths don't really need LFOs any more...
... unless you want to actually play them. You know, with your fingers on a MIDI controller of some kind. It's a very different case to sequencing a drum machine. Because "sequencing". The same applies to polyphony and envelopes.

[AnX]

Orion actually had an LFO built into it's Piano Roll and it was definitely superior to using an LFO in an instrument, it gave you far more control.

I never found that to be true. It was much more convenient to use a synths lfo, and much more control too

You can't change the speed or depth of an lfo with MW in Orion for example...

[BONES]

Well, you can because you can add it to different patterns with different rates. You can ease in and out, can't do that with a synth's LFO. You can also add a completely different LFO to every parameter so it's like having a synth with 100 LFOs. Then, once you've added it, you can go in and edit it by hand.

[AnX]

Well, you can because you can add it to different patterns with different rates.

And how do they blend together?

You can't get the same graduation you get with moving the MW, and if you want to move the MW at different rates at different points in the song, it will take forever trying to work that out into pattern automation.

Blend in, yes, blend out, no, but never used it.

Sync and trigger is also difficult with host automation in this case.....as its a pre drawn shape running thru the pattern, regardless of how many notes are being played

[BONES]

I have never used any of it but it's all there and it all works. I honestly can't see why I would want to gradually increase the LFO rate but I can see very clearly how useful it could be to have the rate change between the verse and chorus of a song. Mostly, though, LFOs are for girls and I rarely use them at all.

[AnX]

Girls or lfos?

[BONES]

Take your pick, mate.

[steb_osc]

Isn't it great to see a thread where KVR is doing what it is supposed to do - everyone helping each other. Two lots of patches generously shared for free is the kind of thing this place should be all about but rarely is. Thanks Tek and steb_osc.

Let's get back to stuff like this!

[e-phonic]

UPDATE v1.0.8

• Parameter values now displayed in the top bar
• Adds sustain pedal support
• Oscillators that have the same pitch (or a multiple) are synced when a note is triggered to improve consistency in sound.
• The phase of the oscillators is now also updated when the volume is at zero to prevent unexpected changes when they are turned on again.
• New phase offset slider added to control the initial phase when oscillators are synced/restarted.
• Reworked MIDI note handling
• Key assign mode selection added:
  • REUSE: reuse already playing voices with the same midi note
  • NEW: assigns midi notes to new voices if available
• ARP now works correctly in polyphonic mode
• ARP now handles velocity
• SEQ now has 2 play modes, Sequencer Play (Poly) and Sequencer Play (Seq).
  • Sequencer Play (Poly) plays the (polyphonic) notes you play and applies the pitch of the sequencer to the notes
  • Sequencer Play (Seq) plays the sequence transposed to the note you play.
• Fix: clicks/pops when using oscillator restart with the triangle oscillator
• Fix: clicks/pops when switching presets
• Fix: update midi controller status after loading preset.
• Fix: song conversion from v1.0.3 working again
• Unused PW / SYNC controls are disabled when Triangle or Saw oscillator types are active.
• Minor UI improvements
• Presets are updated for the new phase controls

https://www.e-phonic.com/invader.html

[e-crooner]

Cool, the bass patch I posted 35 or so pages ago works again, must have to do with the phase rework. It sounded totally screwed-up for some time...

The value readout is very useful, and also the 0.5 percent steps of most controls, not too fine, not too gross