iZotope Iris 2

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS
Annual Subscription for Iris Presets Iris 2

Post

I did a quick check on some of Simon's patches (the first 20 of the subscription). Please note that I did not try the modwheel effects.

Most of the ones I listened too sounded the same, with some exceptions, such as:
- Ambient Guitar Scape Split
- Autumn chimes
- Backstage Textures

I general, I find that the Iris 1 original patches had more details... It is like if the Iris 2 translated patches sound a bit duller, with more emphasis on the bass and less on the high end. It is tricky to compare the two, since I also have the impression that the default volume is a bit less in Iris 2 (I had to boost it by around 2 dB for it to sound about the same volume). But hey, I am an old guy, so it could be a problem with my ears :D

Post

As announced in the release notes, the overall level in Iris 2 is 3 dB less. The spectral content sounds the same to me, due to controller assignment workarounds there will be some audible differences in some patches.

Post

Hi Simon,

Tx for the 3 dB value.
Listen to Ambient Guitar Split, key c4 as an example.
In Iris 1, it sounds like if there was some shimmering on it. This is not as present on Iris 2.

Eric

Post

I'll check later, maybe the Macro formerly assigned to LP cutoff needs to be reassigned, so the filter is now more closed and the shimmering gets lost. If you really want to check this, open the text file with all patch descriptions and see if the controllers do what they're supposed to.

Post

Working my way through the conversion of patches with the letter A this morning, more findings are: The LFO depth assignments still don't translate, so if in a v1-patch the Modwheel was assigned to 3 LFOs each one modulating pitch in it's dedicated oscillator with small depth amounts of e.f. 3%, 3% and 5%, in Iris 2 these values all default to 0.50 = 50%. To accurately adjust/repair those settings, edit the value for modulation depth amount numerically, as the graphical assignment in the GUI is only very approximate. So enter a 0,03 value for 3% and a 0,05 value for 5%.

Also when re-saving the edited patch in Iris 2 will not embed the sample in the patch, in order to do that, first save the patch, then use the export function to embed the samples and overwrite the formerly saved version (which has the -iris2 tag in it' name).

I am simplifying all patches which had an envelope and a Macro assigned to oscillator volumes, as that combination does not work anymore in the new architecture (as the Macro adds it value to the amp envelope which causes cut off notes when the envelope reaches the end of the release time.) So I am using master envelope 5 for the overall volume instead, which unfortunately does not allow for different release times and envelope settings per oscillator anymore, but at least it gets the job done in those cases.

What a splendid way to start the day :)

Post

It seems like a new bug has been introduced with this release:
Assign a sample+hold LFO to pitch and set it to "Restart" - it will not modulate pitch but only set a random pitch value with each new note played. Workaround: disable Restart to actually modulate things. (I found this while converting the patch "Alien City", so you can try for yourself).

Post

Sampleconstruct wrote:It seems like a new bug has been introduced with this release:
Assign a sample+hold LFO to pitch and set it to "Restart" - it will not modulate pitch but only set a random pitch value with each new note played. Workaround: disable Restart to actually modulate things. (I found this while converting the patch "Alien City", so you can try for yourself).
And the problem also is that assigning a Macro to LFO speed does nothing, speed is not modulated/changed when turning the Macro (also in the patch Alien City).
Last edited by Sampleconstruct on Thu Dec 18, 2014 10:25 am, edited 1 time in total.

Post

One more info:
During the conversion, Iris 2 patches will not have the former minimum value of a knob set to the new minimum, but the controller value saved with a patch in Iris 1. So if e.g. Macro 1 was assigned to delay mix ranging from 0 - 50%, and the patch was saved in iris with with a value for Macro 1 of 20%, the new minimum knob value will be 20% and the Macro assigned will add it's value to that basic value. This will cause wrong sounding levels when a controller is fully dialed in.

I am stopping this Sisyphean work for now, until Brad has acknowledged and hopefully fixed that new LFO bug.

Post

Spitfire31 wrote:It's great that iZotope listened and tried to make nice! Kudos for that.

But until much requested spectral improvements and time stretch features are implemented (v 2.5? v 3.0? v ➰?), I'm not going to bite.

/Joachim
Agreed on both points. Kudos for the patch.

And I'm not jumping on this or another version until Izotope goes back to what made Iris so special -- spectral tools.

Post

Happy xmas Brad, but can you tell us what's going on? Are we going to see another update before the price reduction expires?

Post

swartzfeger wrote:
Spitfire31 wrote:It's great that iZotope listened and tried to make nice! Kudos for that.

But until much requested spectral improvements and time stretch features are implemented (v 2.5? v 3.0? v ➰?), I'm not going to bite.

/Joachim
Agreed on both points. Kudos for the patch.

And I'm not jumping on this or another version until Izotope goes back to what made Iris so special -- spectral tools.

+2

Not only that, but the poor handling of the patch progression from 1 - > 2 and the issues that Sampleconstruct describes seem to make 2 a step backwards in terms of smart or creative patch creation. What a poor update. I would consider buying the update if promises were made that address some issues, though I never buy something for what it might be. But if iZotope made the promises I may consider the update. I don't know. Anyway, iris 2 has seemed like a very disappointing let-down of an update to me. Poor show iZotope, poor show.

Post

I just opened a patch with the broken Sample&Hold LFO in Iris 2 and a miracle occurred, it is now working, I mean actually modulating, only the speed control via the assigned Macro is not working. So this must be some telepathic update iZotope were sending out, all subscribers try e.g. my patch Alien Noise 01, turn up the Modwheel and please check if it is also working on your end.

How strange, so the extra hold-LFO-bug was only coded for 2014 but not for 2015? LOLZ…
Last edited by Sampleconstruct on Thu Jan 08, 2015 9:22 am, edited 1 time in total.

Post

Sampleconstruct wrote:I just opened a patch with the broken Sample%Hold LFO in Iris 2 and a miracle occurred, it is now working, I mean actually modulating, only the speed control via the assigned Macro is not working. So this must be some telepathic update iZotope were sending out, all subscribers try e.g. my patch Alien Noise 01, turn up the Modwheel and please check if it is also working on your end.

How strange, so the extra hold-LFO-bug was only coded for 2014 but not for 2015? LOLZ…
But strangely in other patches the Sample&Hold LFO is not modulating as it should and it just produces the extra hold and not the sample part. Another weird Iris 2 phenomena this is.

Post

Sampleconstruct wrote:
Sampleconstruct wrote:I just opened a patch with the broken Sample%Hold LFO in Iris 2 and a miracle occurred, it is now working, I mean actually modulating, only the speed control via the assigned Macro is not working. So this must be some telepathic update iZotope were sending out, all subscribers try e.g. my patch Alien Noise 01, turn up the Modwheel and please check if it is also working on your end.

How strange, so the extra hold-LFO-bug was only coded for 2014 but not for 2015? LOLZ…
But strangely in other patches the Sample&Hold LFO is not modulating as it should and it just produces the extra hold and not the sample part. Another weird Iris 2 phenomena this is.
So it stopped working again, after reloading a patch in which the S&H LFO worked a few minutes ago (Alien Noise 01) it is now broken again - sigh.

Post

Can this be true: Are the envelopes when assigned to volume and the FX section is running in Send mode, post-send? Because even when I have sustain turned to 0%, audio signal is still reaching the effects, this can’t be right…and it was not like this in Iris 1.

Post Reply

Return to “Instruments”