New H9000 Public Beta

[joeydego]

Looks good so far. Installation went well. Thats as far as I got. Will play with it some more tomorrow.

[chuckhague]

I installed it yesterday and spent some time exploring the new algorithms with no immediate issues. The new algos are exciting — it’s great to have a low-latency polyphonic pitch shifter that doesn’t have the usual granular artifacts. Nice work!

[stevepretty]

Agreed – new update is fantastic, and very, very welcome. Thanks Eventide! Brilliant to have that ‘system clock’ issue with the various legacy Reich loopers etc fixed as well as all the new stuff.

One quick one: on the new Polyphony algorithm, has anyone had any luck getting the MIDI bit to work? I have a keyboard plugged in which is working great with all the other MIDI algos on the box (and through MIDI monitor algo etc), but no dice with Polyphony.

Any ideas?

[tbskoglund]

The MIDI note shift is only applied once you engage the Freeze performance parameter. Let me know if that works for you. We’ll have an updated user guide with a more detailed explanation of this soon.

[stevepretty]

Thanks for the quick reply! That’s got it.

I can’t really get my head around exactly what the incoming MIDI is doing with the two voices and so on, but it’s interesting… Is there a manual that deals with this somewhere? I can’t see anything about MIDI on the H90 documentation for this algo.

Thanks again – great work all round.

[tbskoglund]

Glad to hear you are enjoying the update. The H90 manual doesn’t mention this because its a brand new feature exclusive to the H9000!

The MIDI note control will change the shift amount in increments of 100c relative to the middle C position, and the MIDI monitor will reflect these changes. So, middle C will not shift by any amount, C# will shift by +100, D +200, and B below middle will give -100. The idea is that you set the shift amount from the main voice parameters, and then offset those shifts by sending MIDI note data. I’ll post a link to the updated H9000 documentation when it is available.

[stevepretty]

Thanks – and the first MIDI note offsets the first shift, with the second offsetting the second, presumably?

[tbskoglund]

This behavior depends on both the note mode and poly mode settings.

When using mono mode, only 1 MIDI note is received and is applied to both voices.

When using poly mode:

– Normal: Voices are assigned in a round robin fashion.

– Ordered: First note played is always Voice1. Then Voice2 and so on.

– Spread1: All notes play if any keys are pressed. Voice1 is the highest,
Voice2 is the next highest and so on. The note assignment happens every time you press a key.
If you just press one note, all voices play the same note.

– Spread2: Just like spread1 except that note assignment also happens when you lift up a key.
When you lift up from a chord, you’re left with all voices playing one note.

The best way to figure out how it works is to play around and you should get the hang of it.

[alexone]

Nice, that’s really welcome!  Well done Eventide!

Not yet installed, but if I’ve understood correctly and from my perspective, there are still two things missing:
– all the algorithms at 96khz.
– audio interface mode (to make easier this mess of latencies depending on the fx chain involved).

Is Eventide still considering these additions?

 

 

[tbskoglund]

Yes, there are still many more updates and new features planned. We decided to focus on getting the new H90 algorithms out for this release plus some other bonus features and bug fixes. We are planning on 96k compatibility for all algorithms in the next update as well as some other highly requested features. We’ll see if we can fit the fixed latency mode in the next release as well.

[alexone]

Thank you for this quick answer!
I think simplifying the use of the H9000 as an interface would be a really great homage to its excellent converters (as well as making my life easier).

[joeydego]

[

[tomrandresen]

Great 🙂 Thank you 🙂

[joeydego]

tbskoglund wrote:

Yes, there are still many more updates and new features planned. We decided to focus on getting the new H90 algorithms out for this release plus some other bonus features and bug fixes. We are planning on 96k compatibility for all algorithms in the next update as well as some other highly requested features. We’ll see if we can fit the fixed latency mode in the next release as well.

 

Does this bring the H9000 current to the H90 as far as the new Algos?

[tbskoglund]

Yes, except for PrismShift which we are working on adding for the next update.

[afewster]

Would be most welcome to see the H90 presets be available to the H9000  – I’ve heard some lovely creative stuff that I would rather not have to recreate manually.

[joeydego]

afewster wrote:

Would be most welcome to see the H90 presets be available to the H9000 – I’ve heard some lovely creative stuff that I would rather not have to recreate manually.

\.

They’re in the new beta. All but 1.

[afewster]

joeydego wrote:

afewster wrote:

Would be most welcome to see the H90 presets be available to the H9000 – I’ve heard some lovely creative stuff that I would rather not have to recreate manually.

\. They’re in the new beta. All but 1.

*Presets not algo’s (so chains in H9000 nomenclature)

[tbskoglund]

It sounds like you are requesting the H90 Programs to be included. A Program on the H90 is 2 algorithm presets combined, similar to an FX Chain.

We currently do not have a way of converting H90 Programs to H9000 FX Chains easily, but we’d like to add these in a future update.

[joeydego]

I see. Didn’t realize presets were not present.

[Puppeteer]

I have a request for H9000.  Can you please make the save/export window wider (especially for exporting algorithms).  The names of most algorithms don’t fit in the window, so it’s hard to pick the correct algorithm to export when you have algorithms with similar names.

Being able to save an algorithm to disk from Emote would be a godsend if you can make that happen. This probably only affects me (though AFAIK I’m the only third party regularly developing algorithms), as I often work remotely, but having to physically move the USB stick to export algorithms slows down releasing algorithms for me.

[tbskoglund]

We can see if we can add Export Algorithm to Emote. If we add this, would you still request the front panel window UI change? Or would you just use Emote to do it?

[Puppeteer]

I would probably use emote, but the windows width would improve usability for anyone using the front panel.

Emote export would have more utility for me if I had to choose.

[Puppeteer]

Further to this, the Emote export is probably most useful for those with H9000R’s as well.

I’m not sure how feasible it is, but being able to export presets in H9 or H90 format would also be useful, as we could more easily provide additional presets for users of those products.  I don’t have either a H9 or H90, but would be happy to share presets created on supported algorithms.  I was looking at hacking the .json file to extract the preset, but the checksum is a challenge.  I direct export would simplify this a lot. Being able to import these presets somehow from H9 and H90 would also be welcome.  It would broaden preset sharing.

[Puppeteer]

Another Emote bug.

I’ve got an algorithm that will not show up on the algorithm list on Emote, though it will in the H9000.  If I load it on the H9000, then I can control it from Emote, and I can search and load the presets from Emote, just the algorithm does not appear, and doesn’t appear in searches.

[Puppeteer]

I just had Emote crash ableton when I clicked Yes to load state data.

Also, for the algorithm I’m developing SKnob3 type 0 has a different appearance in the Standalone Emote and the VST.  In the VST

In Standalone

I’ve had trouble with any type apart from type 0. Hopefully this is one of the things you guys are fixing in this version

[Puppeteer]

I’ve resolved this.  The Emote VST was an older version.  The new version 2.1.2 doesn’t show this difference any more.

[Author]

Posts