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

Sampleconstruct wrote: -> on the list of bugs never to be fixed... *sigh*
They already have your money, so they don't care.
My main tools: Kontakt, Omnisphere, Samplemodeling + Audio Modeling. Unify = godsend. Tari's libraries also rock.

Post

Ben H wrote:
Sampleconstruct wrote: -> on the list of bugs never to be fixed... *sigh*
They already have your money, so they don't care.
Only for Iris 1 though, they gave me an NFR for Iris 2, LOL and I worked hard for it. :dog:

Post

Ben H wrote:
Sampleconstruct wrote: -> on the list of bugs never to be fixed... *sigh*
They already have your money, so they don't care.
They should if they want more of it though. If they keep breaking trust with their existing user base just to gain short term profits from new customers eventually that will bite them in the ass.

Post

Sampleconstruct wrote:
Ben H wrote:
Sampleconstruct wrote: -> on the list of bugs never to be fixed... *sigh*
They already have your money, so they don't care.
Only for Iris 1 though, they gave me an NFR for Iris 2, LOL and I worked hard for it. :dog:
Yeah I decided not to buy Iris 2 either, after I saw how bug-riddled it was/still is. :roll:
My main tools: Kontakt, Omnisphere, Samplemodeling + Audio Modeling. Unify = godsend. Tari's libraries also rock.

Post

Ben H wrote:
Sampleconstruct wrote: -> on the list of bugs never to be fixed... *sigh*
They already have your money, so they don't care.
They don't have my money yet, though :hihi:

Bad support for promising products ruins the market :(
Blog ------------- YouTube channel
Tricky-Loops wrote: (...)someone like Armin van Buuren who claims to make a track in half an hour and all his songs sound somewhat boring(...)

Post

Actually the last time I gave them my money was for the update to RX4 Advanced, that still works like a charm.

Post

Ben H wrote:
Sampleconstruct wrote:
Ben H wrote:
Sampleconstruct wrote: -> on the list of bugs never to be fixed... *sigh*
They already have your money, so they don't care.
Only for Iris 1 though, they gave me an NFR for Iris 2, LOL and I worked hard for it. :dog:
Yeah I decided not to buy Iris 2 either, after I saw how bug-riddled it was/still is. :roll:
Other than the v1 preset import, is there any major bug?
Zerocrossing Media

4th Law of Robotics: When turning evil, display a red indicator light. ~[ ●_● ]~

Post

zerocrossing wrote:
Ben H wrote:
Sampleconstruct wrote:
Ben H wrote:
Sampleconstruct wrote: -> on the list of bugs never to be fixed... *sigh*
They already have your money, so they don't care.
Only for Iris 1 though, they gave me an NFR for Iris 2, LOL and I worked hard for it. :dog:
Yeah I decided not to buy Iris 2 either, after I saw how bug-riddled it was/still is. :roll:
Other than the v1 preset import, is there any major bug?
Depends on your definition of “major bugs“, but yes, i would call some of the issues below major bugs.

*The Sample&Hold (random) LFO is still broken in version 2.01, in most cases it decides not to modulate, sometimes it modulates, so it’s behavior is very erratic. Also the speed of the random LFO can currently not be modulated with any controller. So all patches using a random LFO are affected by that. iZotope is still working on a fix for this issue (they said in March 2015).

*When you assign the modulation wheel to the main output gain using negative values, e.g. something like -20% to compensate for the gain boost introduced by the distortion FX (also assigned to the wheel), the next time you open the preset the wheel will totally mute the output when fully engaged, as the master output knob at the top of the UI can't be assigned to any controller anymore, the only workaround is to individually assign negative values to the individual outputs of each oscillator.

*Trying to modulate Chorus depth (not mix) with a Macro doesn't work, the knob modulation indicator is actually moving when tuning the Macro but the sound doesn't change.

*Since Iris 2 the Send-levels to the FX modules are routed pre-envelope, so when a patch is using the FX-Send-mode, a sound will reach the FX section although it’s sustain level might be turned to zero. They are thinking of adding a pre/post-switch to fix this issue, the workaround is, to also assign the amplitude envelope of an oscillator the the respective send level.

*The feature to change LFO waveforms via Macros has been removed in Iris 2

*As the minimum/maximum modulation amount was removed in Iris 2, some modulation values can not be assigned accurately anymore, like e.g. delay times, cutoff levels etc, so some modulation levels might slightly differ in the converted Iris 2 patches.

*The new architecture of Iris 2 renders some former assignments useless/impossible, so I used many workarounds in the Iris 2 patches, sometimes I also added a few modulations here and there, taking advantage of the new modulation system. But the new patches sound just as good :)

*The zipper noises in Iris 2 when moving/automating Macros and other controllers like the Modwheel have increased significantly in comparison with version 1, if you move them slow enough, you will be able to avoid those artifacts.

*CPU usage has significantly increased in Iris 2.

*The master output knob at the top of the GUI can't be modulated anymore.

*Limiter amount can't be modulated anymore.

*Modulating delay time with an LFO does not produce usable results.

Post

Sampleconstruct wrote:
zerocrossing wrote:
Ben H wrote:
Sampleconstruct wrote:
Ben H wrote:
Sampleconstruct wrote: -> on the list of bugs never to be fixed... *sigh*
They already have your money, so they don't care.
Only for Iris 1 though, they gave me an NFR for Iris 2, LOL and I worked hard for it. :dog:
Yeah I decided not to buy Iris 2 either, after I saw how bug-riddled it was/still is. :roll:
Other than the v1 preset import, is there any major bug?
Depends on your definition of “major bugs“, but yes, i would call some of the issues below major bugs.

*The Sample&Hold (random) LFO is still broken in version 2.01, in most cases it decides not to modulate, sometimes it modulates, so it’s behavior is very erratic. Also the speed of the random LFO can currently not be modulated with any controller. So all patches using a random LFO are affected by that. iZotope is still working on a fix for this issue (they said in March 2015).

*When you assign the modulation wheel to the main output gain using negative values, e.g. something like -20% to compensate for the gain boost introduced by the distortion FX (also assigned to the wheel), the next time you open the preset the wheel will totally mute the output when fully engaged, as the master output knob at the top of the UI can't be assigned to any controller anymore, the only workaround is to individually assign negative values to the individual outputs of each oscillator.

*Trying to modulate Chorus depth (not mix) with a Macro doesn't work, the knob modulation indicator is actually moving when tuning the Macro but the sound doesn't change.

*Since Iris 2 the Send-levels to the FX modules are routed pre-envelope, so when a patch is using the FX-Send-mode, a sound will reach the FX section although it’s sustain level might be turned to zero. They are thinking of adding a pre/post-switch to fix this issue, the workaround is, to also assign the amplitude envelope of an oscillator the the respective send level.

*The feature to change LFO waveforms via Macros has been removed in Iris 2

*As the minimum/maximum modulation amount was removed in Iris 2, some modulation values can not be assigned accurately anymore, like e.g. delay times, cutoff levels etc, so some modulation levels might slightly differ in the converted Iris 2 patches.

*The new architecture of Iris 2 renders some former assignments useless/impossible, so I used many workarounds in the Iris 2 patches, sometimes I also added a few modulations here and there, taking advantage of the new modulation system. But the new patches sound just as good :)

*The zipper noises in Iris 2 when moving/automating Macros and other controllers like the Modwheel have increased significantly in comparison with version 1, if you move them slow enough, you will be able to avoid those artifacts.

*CPU usage has significantly increased in Iris 2.

*The master output knob at the top of the GUI can't be modulated anymore.

*Limiter amount can't be modulated anymore.

*Modulating delay time with an LFO does not produce usable results.
Yeah, but other than those, it works flawlessly! :tu:

Post

menthol wrote:
Sampleconstruct wrote:
zerocrossing wrote:Other than the v1 preset import, is there any major bug?
Depends on your definition of “major bugs“, but yes, i would call some of the issues below major bugs.

*The Sample&Hold (random) LFO is still broken in version 2.01, in most cases it decides not to modulate, sometimes it modulates, so it’s behavior is very erratic. Also the speed of the random LFO can currently not be modulated with any controller. So all patches using a random LFO are affected by that. iZotope is still working on a fix for this issue (they said in March 2015).

*When you assign the modulation wheel to the main output gain using negative values, e.g. something like -20% to compensate for the gain boost introduced by the distortion FX (also assigned to the wheel), the next time you open the preset the wheel will totally mute the output when fully engaged, as the master output knob at the top of the UI can't be assigned to any controller anymore, the only workaround is to individually assign negative values to the individual outputs of each oscillator.

*Trying to modulate Chorus depth (not mix) with a Macro doesn't work, the knob modulation indicator is actually moving when tuning the Macro but the sound doesn't change.

*Since Iris 2 the Send-levels to the FX modules are routed pre-envelope, so when a patch is using the FX-Send-mode, a sound will reach the FX section although it’s sustain level might be turned to zero. They are thinking of adding a pre/post-switch to fix this issue, the workaround is, to also assign the amplitude envelope of an oscillator the the respective send level.

*The feature to change LFO waveforms via Macros has been removed in Iris 2

*As the minimum/maximum modulation amount was removed in Iris 2, some modulation values can not be assigned accurately anymore, like e.g. delay times, cutoff levels etc, so some modulation levels might slightly differ in the converted Iris 2 patches.

*The new architecture of Iris 2 renders some former assignments useless/impossible, so I used many workarounds in the Iris 2 patches, sometimes I also added a few modulations here and there, taking advantage of the new modulation system. But the new patches sound just as good :)

*The zipper noises in Iris 2 when moving/automating Macros and other controllers like the Modwheel have increased significantly in comparison with version 1, if you move them slow enough, you will be able to avoid those artifacts.

*CPU usage has significantly increased in Iris 2.

*The master output knob at the top of the GUI can't be modulated anymore.

*Limiter amount can't be modulated anymore.

*Modulating delay time with an LFO does not produce usable results.
Yeah, but other than those, it works flawlessly! :tu:
lol. :lol: :hihi:
My main tools: Kontakt, Omnisphere, Samplemodeling + Audio Modeling. Unify = godsend. Tari's libraries also rock.

Post

Yea,
I am always right
accept when I am wrong!

Post

Kalamata Kid wrote: accept when I am wrong!
We do, KK, we do :hihi:

Post

Fleer wrote:
Kalamata Kid wrote: accept when I am wrong!
We do, KK, we do :hihi:
The Terminator pissed off that the did not get the part in a play about Bach
on the way out said "I'll be Bach". :D

Not so funny, lately been a fan of Sibelius.

Edit: Sorry for the dumb stupid humor. :oops:
It was 4 AM here. :? That's my excuse. :roll:
Fleer is a fan of Bach and so am I. :D

Second edit: As it turns out there is already such
humor: https://www.google.com/webhp?sourceid=c ... %22bach%22
I promise I will not be back to do any more Bach humor edits.

Post

LOL! :hug:

Post

"*The master output knob at the top of the GUI can't be modulated anymore.

*Limiter amount can't be modulated anymore.

*Modulating delay time with an LFO does not produce usable results."
- sampleconstruct

These are really the only ones that annoy me. But really not enough to complain about it.


I went into the purchase of Iris 2 and many sound packs fully expecting nothing, or, if I expected anything it would have been that iZotope would drop all support for Iris and stop further development right after purchase.

So, I can report back that I have not been disappointed in any way by iZotope and really love Iris 2 and very much enjoy using it.

I've been a regular critic of iZotope's stunts over time about as much as anyone else. I never forgave them for removing the reverb after Ozone 5, just for example. I knew what I was getting into going with Iris 2. Make informed purchases and then you don't have to waste your creative time complaining on some forum. I hate wasting time -- I have far better things to do and lots of money to make. Complaining gives too much acknowledgement that you even recognize the company's existence, er, maybe give some false importance to them. Negative criticism, as in attempting to dissuade others from using, serves no purpose to me really, since I couldn't care less what others use. If I did care, I might complain about Iris loudly, pushing more and more of you here toward using those same dozen or so instruments you do use here, sounding all alike and not very interesting either. That's why, btw, I use instruments such as Iris and others, bugs and all.

Post Reply

Return to “Instruments”