Worth every cent!
Eventide updates H3000 Factory and Band Delays
- KVRAF
- 8037 posts since 28 Dec, 2015 from Atlantis Island
https://sonograyn.bandcamp.com/music Experimental Ambient
https://martinjuenke.bandcamp.com/music Alternative Instrumental
https://martinjuenke.bandcamp.com/music Alternative Instrumental
- KVRian
- 744 posts since 15 May, 2003 from R'lyeh
Are you logging in at the Pace/iLok website? They have nothing to do with Eventide's sale prices, try the Eventide website where it actually shows you these things.EsmileZ wrote: Wed Jul 09, 2025 4:13 pm Did someone know how much is the upgrade price from h3000 mk1 to version 2 during their summer sale?
I can't login @ ilok account at the moment
- KVRAF
- 2628 posts since 16 May, 2004 from Soviet Union
I upgraded though (really liked new UI, that rare case with nowadays editions), but technically frankly expected to more. I mean, introducery was mention updated filters, so was hope that they become with true selfoscillation finally, but nope. But no regret here, as said UI it's amazing.
-
- KVRian
- 997 posts since 31 Oct, 2020
Bro, did you download the correct software
‘ Filter recreations accurately replicate the resonance and self-oscillation behavior of the hardware, faithfully capturing its magical sound. ’
What is true self oscillation in your book coz if you think you are missing something, the real H3000 is no different in this regard, ennit
‘ Filter recreations accurately replicate the resonance and self-oscillation behavior of the hardware, faithfully capturing its magical sound. ’
What is true self oscillation in your book coz if you think you are missing something, the real H3000 is no different in this regard, ennit
- KVRAF
- 2628 posts since 16 May, 2004 from Soviet Union
@audiouser720
I pretty admit that this feature of selfoscillation (when no signal is required to "driven" it - which is what I would like to see) can be deliberately limited by developer, and it will still fall under the conformity with the declared original, in the context of the nature of selfoscillation itself, as a phenomenon (changing only the method of its launch).
From the dev's side, this can be explained, for example, desire by improving control in SW over the behavior of this effect (to avoid accidental shock from a signal peak etc).
Why go far, were changes in reverb algo in the same Blackhole plugin during updates, exact with spoiling (removing) effect of increasing feedback (kind of selfoscillate) in revb tail at high resonance value. (Although i always liked this behavior in BH, but ok user's speakers condition is more important lol)
From my side, this is because I often observe in other filters emul's that selfoscillation starting up by itself (at resonance near to max resp), that is why I think this is a common/normal behavior in HW.
Sorry for bunch of words.
But, of course, if it works \ has exact the same behavior in H3000 HW (Sorry maybe did you check it at HW unit ?) - then i calm.
Added (Anticipating question of why I need this so much (and what is difference between starting from a signal or by itself) is a separate topic, I think)

I pretty admit that this feature of selfoscillation (when no signal is required to "driven" it - which is what I would like to see) can be deliberately limited by developer, and it will still fall under the conformity with the declared original, in the context of the nature of selfoscillation itself, as a phenomenon (changing only the method of its launch).
From the dev's side, this can be explained, for example, desire by improving control in SW over the behavior of this effect (to avoid accidental shock from a signal peak etc).
Why go far, were changes in reverb algo in the same Blackhole plugin during updates, exact with spoiling (removing) effect of increasing feedback (kind of selfoscillate) in revb tail at high resonance value. (Although i always liked this behavior in BH, but ok user's speakers condition is more important lol)
From my side, this is because I often observe in other filters emul's that selfoscillation starting up by itself (at resonance near to max resp), that is why I think this is a common/normal behavior in HW.
Sorry for bunch of words.
But, of course, if it works \ has exact the same behavior in H3000 HW (Sorry maybe did you check it at HW unit ?) - then i calm.
Added (Anticipating question of why I need this so much (and what is difference between starting from a signal or by itself) is a separate topic, I think)
