The Iris 2.01 update improves the modulation routing and workflow for using Iris 1 patches in Iris 2. It has been tested extensively using patches from the +8 series of Sound Libraries developed for Iris 1, as well as sound libraries developed by 3rd parties. If a patch opens in Iris 1 on your computer, it should also open in Iris 2 on the same computer with little to no interruption to your workflow.
Here are some notes to help illustrate where differences may exist when importing an Iris 1 patch into Iris 2:
Modulation amounts are translated for sound quality, not simply one-to-one value transfers. For example, translating the filter envelope from Iris 1 to Iris 2 may not bring in the exact ADSR values, but instead a translated value that represents the new envelopes in Iris 2 and uses a formula to approximate the sound of Iris 1’s envelopes.
Mod Wheel & Macros are now treated as modulators, and no longer spin knobs on the UI as they did in Iris 1. In one manifestation of this, a macro attached to coarse pitch will not snap to semitones as it did in Iris 1. To replicate this effect, you can use MIDI Assign to connect a Mod Wheel or other MIDI CC to coarse pitch (or any other parameter).
Because of this, translating Macro and Mod Wheel ranges from Iris 1 is particularly challenging. Macro and Mod Wheel assignments will be made in the translation, but their ranges will be set to a default value and need to be updated to taste. With that in mind, the values for the Macro Controls themselves will default to zero when importing an Iris 1 patch into Iris 2. For Example, an Iris 1 patch that has filter cutoff assigned to Macro 1 and set to 127 by default will come into Iris 2 at zero and need to be reset to taste after the ranges of the macro has been set. Velocity (except for master amplitude) and Aftertouch assignments are also attached by the translator but their ranges are set to a default value and will also need to be adjusted to taste.
Macros could be assigned to power buttons on the LFO & effects sections in Iris 1, but not in Iris 2. In a case like this, the translator will turn relevant LFOs & Effects “on” when the preset loads. A user may then want to assign a Macro to LFO depth or the effect amount to replicate the effect as it was intended in Iris 1.
Filter envelope amount doesn't have an analogous control which can be attached to a macro. Filter envelope amount can be adjusted manually using the modulation range adjustment at the modulation input.
Envelope release times are capped at 10 seconds in Iris 2 to give the best possible resolution in the envelope graph. This means an envelope used in an Iris 1 patch might have a release time of 13 seconds, but be truncated to 10 seconds in Iris 2.
Amplitude envelopes, Amplitude LFOs and the gain knob in each pool of Iris 1 were individual gain stages in series, whereas each pool in Iris 2 has a single gain stage with modulation and the gain knob combining mathematically. This presents a challenge when considering tremolo effects set per pool. For this case, we have added the following workaround to the translator. In any patch where say Pool 2 has LFO2 & E2 applied to it, we have also applied E2 to LFO2 depth so that that the amount of LFO applied follows the value of the envelope inline with the amplitude. However, if this patch also has Macro 4 assigned to LFO 2 depth, the combination settings in there may need to be investigated so the macro feels right with the tremolo effect. A workaround for this when designing new sounds in Iris 2 might be to use an envelope on the master amplitude control, while still retaining tremolo effects and/or macro controls over each individual sample amplitude.
In Iris 1, master filter cutoff could have up to five modulators attached. When translating to Iris 2, they will be reassigned in this order of priority:
Additional headroom will make patches in Iris 2 sound ~3 dB quieter than in Iris 1.
Iris 2.01 includes legacy LFO shapes from Iris 1, and will map Iris 1 patches to these legacy shapes. Please note that the Shape Slider is disabled because these are single shapes (not wavetables) just as they were in Iris 1. If you would like to take advantage of one of the new LFO shapes and morphing capabilities in Iris 2, simply select a different LFO wavetable from outside of the Iris 1 set.
To help prevent accidentally overwriting an Iris 1 patch, saving or updating an Iris 1 patch in Iris 2 will add a “-iris2” suffix to the patch name in the save dialog before saving or updating the patch. If you really want to overwrite your Iris 1 patch, you can remove this and overwrite, but the patch will no longer load in Iris 1.