Analog Heat MKI/MKII 1.20

With the new Analog Heat OS 1.20, we’ve added features that will expand the usability of our powerful sound processor, enabling more sound sculpting possibilities and experimentation. With these new features, plus a few improvements and bug fixes, 1.20 is here for your fiery leisure!

Class compliant audio over USB

We’ve added support for class compliant audio over USB. This means that you will have new possibilities when using the Analog Heat together with devices that supports class compliant audio (such as computers, phones or tablets) making it an even more flexible partner in your setup. Practically this means you now may use the unit in a bunch of different scenarios - for example, as an audio interface, recording the processed sound or as a sound processor for your USB audio host. You can also use the USB audio host as a pre or post effect for the Analog Heat. The choice is yours.

Check out all the routing options in the new Audio Routing menu. Here you can setup up the audio routing in a multitude of different ways to suit your particular setup and needs.

Preset transfer

You can now export and import the Analog Heat’s presets and settings. This enables safe storage of your favorite presets and settings, and the possibility to reload them at your convenience.

For a full list of improvements and fixes, check the release notes.

Download Analog Heat OS 1.20 here

If you use the Overbridge Beta, you will need to update to the new Overbridge release, which is also released today to support the new 1.20 firmware. You can download this at Elektronauts (log-in required).

17 Likes

List of changes from OS 1.10 to 1.20

Improvements

The Analog Heat now supports class compliant audio over USB.

Added flexible routing of audio over USB.

It is now possible to send and receive presets and settings via SysEx.

Added the functionality to tap the tempo.

[MKII] Added support for the Overbridge plugin.

[MKII] The screen saver now turns off the screen after 60 minutes of inactivity.

Bug fixes

[MKI] The filter graphics were not displayed properly.

10 Likes

This doesn’t help my desire to get a heat.

11 Likes

as in hello iPad meet my Heat??

14 Likes

supports class compliant audio (such as computers, phones or tablets)

yes!! so nice

2 Likes

Holy crap, this is awesome. running to my studio to take home my AH

I don’t quite get the , enabling more sound sculpting possibilities and experimentation. piece?

5 Likes

This is marketing copy to highlight that the AH can now connect to a wider variety of devices.

6 Likes

I agree, class compliant and tap tempo is nice but it does little for me on the sound sculpting front.
Fair enough though, this is clearly a big thing for a lot of people, not every update Elektron do is for me but the blurb maybe over eggs it a little.

2 Likes

Nice upgrade. I love this unit and I will use as main soundcard now.

1 Like

You know I’ll be testing this when I get home :slight_smile:

Bring this class compliance to DT & DN and I’ll be exploding with excitement!

13 Likes

Great news. Curious to know the different ways it can work with an iPad using AUM for example.

4 Likes

Freaky Tuesday! :content:

5 Likes

That’s exactly why I want DT & DN to get this

6 Likes

On the bus home now with AH in my lap. 2 excited. Can’t remember if it’s possible to send midi thru usb though?

Like, if my keystep is connected through MIDI, will the AH echo that through USB to an iPad for example?

I reckon it will be nice to be able to use it with my ipad, especially given the lack of a physical audio output on mine.

6 Likes

I’m still waiting for a midi message to trigger envelope / lfo…
I planned to buy an IPhone to use it with AR.
Why not with AH.

It was already possible to tap tempo with a footswitch, is there a new way?
I’m surprised sysex send/receive were not working previously!

@Olle is the analog heat capable, ever, of being an audio interface that would also allow us to send midi to the host? would be nice to know if this is a limitation of the hardware or code

It becomes a bit difficult to differentiate what MIDI data is addressed to the device and what is addressed to the host. So even conceptually it’s in a gray zone. Same goes for the other way around, from the host to the device.