Eventide H3000 editor

Yes - cable up both the in and out to the H3000.
Also go into the MIDI menus on the 3000 and make sure sysex is enabled (might be under the Expert button in the MIDI section).

A big part of my support for the Electra One over other tools like the Peavey PC-1600, the Behringer BCR and BCF, the crazy CME thing, and the Novation Remote Zero (I tried them all) is the support for 2 way communication of sysex data and the ability to display and edit the current values of the current patch rather than blindly sending parameter changes to the hardware.

So all my presets for the Electra One require a full In and Out connection.

I have an old Behringer BCR sitting idle in the corner. Tell me pls how you intended to let interact with E1.

Sorry - a misunderstanding.

I was saying that I tried to use those other controllers in the past, but they never did 100% of what I needed.

So - I sold them all and bought Electra Ones instead.

1 Like

Sorry about the confusion.
I’m still thinking about a kind of meta-data like implementation in which any E1 preset could make advantage of the BCR knobs to add physical knobs to the E1. But so far haven’t tried anything yet.

1 Like

With some thought and the ability to query the connected device, it is possible to extend the interface in that way. I’m way overbooked with my free time and I want to spend it updating what I’ve developed to take advantage of all the new capabilities in the E1.

1 Like

How can I find your public version of the H3000 editor preset? I was only able to find the earlier private beta linked in this thread. Searching H3000 or Eventide in the main Electra presets page doesn’t bring it up.

I’ve had some fun with DC’s presets for individual algorithms. But I can’t get the H3000 to dump to the E1, so I can’t really use the H3000s presets this way. I’m pushing the top right button on the Electra and nothing happens. Any advice, or does that feature not work with this setup?

Huge thanks to both of you, this is so great!

The H3000 editor was turning into a larger headache and more convoluted coding weirdness than even the PCM 80, so I dropped it and sold off the H3000. When I get neck to my setup, I’ll see what the most recent version I have and send you a link. Very reluctant to make something public that is not exactly finished and something that I do not have the hardware around to test with anymore.

If you ask around the Eventide forums, they’re are a couple of Max/Msp versions being developed and should run in most any computer.

1 Like

Kind of sad that this won’t be happening but it totally makes sense… Not a Max/Msp User… I guess I’ll have to wait and see what eventually comes out…

It’s mostly working for all the algorithms if I recall.
It’s all the odd exception handling plus things like MIDI will increment a parameter by 2 or 4 units only, but the front panel can do it by 1’s.

1 Like

Thank you so much!!!

I would be really interested to have access to your preset even if it’s unfinished. Mainly for the String Modeler algorithm, which hasn’t been published as one of the individual presets by DC. Thank you!

And also because I can’t get the Patch Request button to work on DC’s presets. Does it work for other people? I have midi in and out plugged in correctly, and the Electra sends data to the Eventide but not the other way around.

H3000 beta is the link to the beta version. Try pulling up preset 296, 599, 648, or one of the others and see if it’ll work for you.

When I started messing with implementing the Mod Factory algorithms, it quickly became apparent (to me) that the density of controls and their ranges and interactions were more than was reasonable to represent on the Electra One surface.

Basically, I was feeling the Electra One wasn’t really making it easier to dive in and do edits. In general, I think the E1 is wonderful for a lot of things, but some of the denser presets kind of get bogged down in the sheer number of pages and parameters and how they interact. Given that the layout is by necessity kind of generic, you can’t easily develop muscle memory for quick edits like you can (for a very basic example) on a real MiniMoog. I can pretty much create a sound on that in the dark because I know where all the controls are and what they do and their ranges.

The PCM 80, Waldorf XT, Korg DL8000r and AM8000r, and the H3000 are all presets where I feel I hit the density and understanding limits. Yes, the E1 presets do give you some insights into the hardware, but when the coding gymnastics and E1 limits are constantly slowing you down, then the question becomes ‘why am I doing this?’ and ‘will I actually end up using it?’

slight apology for the rant - 3 days with no electricity while visiting my daughter and picked up a nasty cold on the plane and I’m banging my head against the persist()/recall() because likely something probably simple isn’t working for me.

3 Likes