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

[Teksonik]

Just don't use the Arp then Others might still find it useful.
Personally, I rarely use an arp. A sequence? Yes, but that what is a sequencer for.

Waiting for M1 native support as Invader2 is my to go analog synth now that I don't have Diva anymore.

Oh yes of course I could simply ignore certain functions of the synth. Just like I could ignore the synth altogether but I'd like to see Invader evolve. It sounds great so why not want it to grow?

I use Arp patches all the time but I won't ever own a Mac so don't care one bit about M1 support so you see we all have our priorities.

[briefcasemanx]

I don't have the others but can Dune3 do this without layering patches? I've barely touched it's arp.

No need to layer patches. You can think of the Voices as single Oscs: Single Osc In Voice 1 set to Arp #1, Single Osc in Voice 2 set to no Arp. Single Osc in Voice 3 set to Arp #2 and so on.

Anyway I don't want to hijack this thread. If you want to know more about D3's Arps we can go to its thread and I'll be happy to explain it further.

I was basically trying to ask the same thing as anx. Sounds like what you're describing is layering. Doesn't make sense to compare synths that layer. And some people that aren't you will find e-phonic functionality useful.

Expecting that the dev should change how the underlying engine of the synth works to make one weird option work more to your taste is unreasonable. Expecting that they should delete optional functionality because personally you don't find it useful is also unreasonable.

Saying "man it would be cool if the synth worked like X" is fine, but you are going beyond that when the dev has already given you the underlying architectural reason why it cannot work like that.

[Teksonik]

Sounds like what you're describing is layering. Doesn't make sense to compare synths that layer.

No, what I originally posted and what I stand by is that routing the Arp only to Osc2 should have no effect on Osc1. Osc 1 should not just play a single note over an over, simple as that. Adding another Env would likely solve that since the single Env is given as the reason for the behavior.

And some people that aren't you will find e-phonic functionality useful.

As I have already posted twice yes you can use it to effect on some patches. But I don't think having a single note playing over and over on one Osc while the other Osc is arpeggiating a chord is useful in a lot of patches. It's basically a half implemented feature that just by sheer happenstance provides some functionality. Not as much functionality as if it were to work properly in my opinion.

Like I asked can you think of another simple synth that has Arp Routing? I can't and there's probably a good reason for that and if there was I'd be right there bringing up the issue to the developer.

Expecting that the dev should change how the underlying engine of the synth works to make one weird option work more to your taste is unreasonable.

It's far from a "weird" option. It's something I use all the time.

I'm not suggesting change I'm suggesting growth. The fact that people push back against progress and growth is puzzling especially if they like the way the synth sounds. Stunting the growth to your taste is no less unreasonable than me suggesting that the current Arp Routing does not make sense due to a simple missing Env.

But if the idea is to keep the synth simple then why add anything? Do you only push back against features you don't want or understand or do you push back against all features?

Anyway I've done my job I've reported an issue in an attempt to improve the synth and the developer has responded. I disagree with his position but he's driving the bus.

[briefcasemanx]

Sounds like what you're describing is layering. Doesn't make sense to compare synths that layer.

No, what I originally posted and what I stand by is that routing the Arp only to Osc2 should have no effect on Osc1. Osc 1 should not just play a single note over an over, simple as that. Adding another Env would likely solve that since the single Env is given as the reason for the behavior.

And some people that aren't you will find e-phonic functionality useful.

As I have already posted twice yes you can use it to effect on some patches. But I don't think having a single note playing over and over on one Osc while the other Osc is arpeggiating a chord is useful in a lot of patches. It's basically a half implemented feature that just by sheer happenstance provides some functionality. Not as much functionality as if it were to work properly in my opinion.

Like I asked can you think of another simple synth that has Arp Routing? I can't and there's probably a good reason for that and if there was I'd be right there bringing up the issue to the developer.

Expecting that the dev should change how the underlying engine of the synth works to make one weird option work more to your taste is unreasonable.

It's far from a "weird" option. It's something I use all the time.

I'm not suggesting change I'm suggesting growth. The fact that people push back against progress and growth is puzzling especially if they like the way the synth sounds. Stunting the growth to your taste is no less unreasonable than me suggesting that the current Arp Routing does not make sense due to a simple missing Env.

But if the idea is to keep the synth simple then why add anything? Do you only push back against features you don't want or understand or do you push back against all features?

Anyway I've done my job I've reported an issue in an attempt to improve the synth and the developer has responded. I disagree with his position but he's driving the bus.

I'm not pushing back on a feature being added. I'm pushing back on a feature being *taken away*, and the expectation that the synths underlying architecture should change to support one thing that's not even close to standard on synths of this type.

[BONES]

I'd like to see Invader evolve. It sounds great so why not want it to grow?

Because it's great the way it is, it doesn't need to grow or evolve. You may only appreciate the sound but I really appreciate the whole package - the GUI, the ease-of-use and the sound.

[Musical Gym]

...

[nIGhT-SoN]

Guys, let's not forget it's a project made by a single man. I don't even think he had in mind making it a commercial thing. The pay what you want consider it a thank you for him creating this.

I don't have any expectations and every new update i consider it a gift.

[Autobot]

Forgot about Invader and never checked Invader2 now I'm wondering how I could miss this one. It starts at 5 bucks and it sounds good easy one page layout. A synth for the good quick sounds in live. Not sure if I buy it but I like to play with the demo so far.

[dellboy]

Anyway I've done my job I've reported an issue in an attempt to improve the synth and the developer has responded. I disagree with his position but he's driving the bus.

I feel safer with the dev driving the bus than you

[Autobot]

Bought Invader 2 today and loving it!!! Spent a few hours with it now and the only thing that kind of bugs me is that I can't hide the keyboard section to save screen space. Would be great if there was a switch to show/hide the keyboard section (perhaps clicking the Invader 2 logo could do this?). Many thanks E-Phonic

I would love to see this as well. It will not stop me from getting Invader 2 today but would be nice to see a "rack" version

[e-phonic]

@Autobot
I'll see what I can do. Resizing the window is always a pain in the ***. Specially to have working stable on all the DAWS I need to support.

I'm currently fixing some issues, the most important one being an occasional crash on OSX.
I've already fixed it but not yet deployed because I'm working on some more fixes at the same time.
v1.0.8 did not suffer from this crash, so if you experience this crash, please use / download v1.0.8 from the website for now.

[Autobot]

@Autobot
I'll see what I can do. Resizing the window is always a pain in the ***. Specially to have working stable on all the DAWS I need to support.

Okay. I see. As one with no idea bout coding I thought it would be easy
Thanks for giving it a try.

[e-phonic]

v1.0.10:

• Fix: occasional crash on load.
• Better unicode support for file paths and preset names.
• Preset and settings file handling rewritten. Let me know how this works!
• More explanatory drop down texts.
• Close preset browser on double click on preset name.
• Fix: registration state remembered when loading registration key for the first time.
• Version string now shows correctly.
• Updates iPlug2 framework.

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

[codec_spurt]

ee

[EnGee]

v1.0.10:

• Fix: occasional crash on load.
• Better unicode support for file paths and preset names.
• Preset and settings file handling rewritten. Let me know how this works!
• More explanatory drop down texts.
• Close preset browser on double click on preset name.
• Fix: registration state remembered when loading registration key for the first time.
• Version string now shows correctly.
• Updates iPlug2 framework.

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

Thank you