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.
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.
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.
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?
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.
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.
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.
Thanks for the kind words and enthusiasm. Just know that working on the H3000 and PCM 80 at the same time really burned me out. I set aside the Electra Ones for a while and sold the H3000. I might be able to make some tweaks to the 3000 editor, but no promises.
Current effort is trying to learn Ctrlr and port my PCM 80 work to that platform.
I got myself the updated H3000 mk2 vst from Eventide, but I convince myself that it doesn’t sound like the H3000 hardware I tried at some point. But you kept the 81 and sold the 3000? I think I’d go the other way around, if anything
My general position is that I don’t typically just use presets with minimal/zero tweaks. If I can’t “easily” edit a box, it tends not to stay.
The H8000FW w. EVEnet remote is still here and gets a lot of use. Same with the tc 2290, Prime Time II, and other boxes. The ‘magic’ of the H3000 micro-pitch shifting and how it deals with sample playback wasn’t enough to overcome the headache of editing it so it got sold. Same with the Waldorf microWave versus the XT.
Fair enough, but I still have some questions:
-Isn´t the H3000 similar to the H8000 in the way that you load “programs”, which are separate algorithms with a set of controls made available to the user by the author of the program. In H8000´s case this could be VSig, but in the H3000 there is no environment to produce your own programs?
-From my testing with the H3000, the intrinsic sound of the unit is very attractive to me, in addition to the great programs. It sounds very different from the H8000, it has a “gritty” quality to it that works great with a lot of sources, a bit similar to sampling into certain older 12bit samplers.
H8000 oth, is going to be my new “mastering” converter, with its enormous headroom (26dBu if I remember correctly! ) and what I convince myself to think is a very “euphonic” analog input circuitry, super clear/detailed/clean but with some “sparkle” or “sheen” added to it. I haven´t delved deep into sourcing the exact facts here, so I couldn’t say if this “sparkle” is just a tad of HF gain and maybe conversely for the H3K… but comparing it to my Lexicons (PCM81/96) the eventide analog amplifier circuitry certainly has more character and “something” to it just by themselves.
I do envy your EVEnet remote; that thing certainly is such an upgrade to the H8000 and I whish I knew how to reverse engineer it so I could build myself a DIY version. I have a AtoV 16n faderbank hooked up to it though, and it works quite well with the unit in front of you with both MIDI and CV. The CV inputs are also great fun on the unit, if you have a modular (or something like VCV and a dc-coupled DA).
I´ve also extensively used the Analog Dessert remote with great success: Eventide H8000FW Remote - Analog Dessert
I´d love some more thoughts on the H8000 though; it seems pretty hard to get ahold of user experiences, patch exchange files or anything at all about it.
Sample playback on the H3K, you say… sounds like running a Tesla on a gasoline generator somehow
The H3000 is a fantastic effects unit for sure. I’ve owned 4 or 5 of them over the past 35 years.
For me though, I don’t like/don’t use any micro-pitch shifting/doubling/chorusing effects. I never liked that particular sound. I’ve even tried dedicated units like the Baloran Triko and end up not using them. Therefore what the 3000 does is covered by other effects that I have and use more frequently like the H8000, Publison units, and the various Lexicons.
The H8000 has ‘just enough’ parameters available for each effect and it’s quick and easy to create exactly what I need. I rarely use the A→B mode and tend to have it set up as 2 separate effects with their own dedicate I/O. I do agree about the analog I/O and the added presence it adds to a sound. I felt the 9000 lacked that and their pre-amp effect didn’t really get very close.
