Inerthia (split from Slammer thread)

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

shamann wrote:
aliasant wrote:About this one "Man, I tried your compressor, but it didn't create all sorts of nasty, unpleasant clicks all over my audio. I think it must be broken."

Hmm. Seems to be some sort of bug then. What system, software are you using?
Sorry, please ignore that bit. I was making a joke in reference to the compressor in the other thread.
I understood that as exactly -that- joke!

Shogger

P.S. Cool how threads can be splitted these days ... :)
Top

Post

What's the 'LAH' button next to the envelope's attack? Maybe I'm in a dumb mood but the only change I can see switching it on is +10 ms on the release value...
bmanic wrote: The input knob should be much larger as it's a very important knob.
Agree 100% if not larger (gui layout problems?) at least with the notch red couloured...
Top

Post

What's the 'LAH' button next to the envelope's attack? Maybe I'm in a dumb mood but the only change I can see switching it on is +10 ms on the release value...
Well. It is a Look A Head thing.
When engaged it delays the dry signal 2 ms so that the envelope&sidechain gets some extra time to calculate the math.
It also does some other small things and one of them is that it adds 10ms to the release time. Just so that you can set the release time to its lowest position and it still sounds fine. Or atleast it should. It might depend on the audiomaterial.

Agree 100% if not larger (gui layout problems?) at least with the notch red couloured...

Hmm. Thats a nice idea. The Red color thing. Thanks. I might use that later.
Top

Post

Well. It is a Look A Head thing
Ok Martin: Clearly i was in a dumb mood because obviously it's the look a head thing :hihi:
But since i was testing it with savihost (playing wav file) there wasn't any host-latency report... and my ear didn't catch 2 ms latency!! I think you should edit-update that picture-manual because actually the 'lha' button is linked togheter with VU1 description there, and (imho) the look a head feature deserves a more relevant emphasis.

[Edit] English isn't my language but: look ahead not a-head (?) [/edit]
Thats a nice idea. The Red color thing.
Happy to help :love:

All the best
Antonio
Top

Post

tonAP wrote:
Well. It is a Look A Head thing
Ok Martin: Clearly i was in a dumb mood because obviously it's the look a head thing :hihi:
But since i was testing it with savihost (playing wav file) there wasn't any host-latency report... and my ear didn't catch 2 ms latency!! I think you should edit-update that picture-manual because actually the 'lha' button is linked togheter with VU1 description there, and (imho) the look a head feature deserves a more relevant emphasis.

[Edit] English isn't my language but: look ahead not a-head (?) [/edit]
Thats a nice idea. The Red color thing.
Happy to help :love:

All the best
Antonio



Ah. Your right of course. I forgot about the latency report. It has been my intention to use it but I forgot it.
It will be in the next release.
And again.... your right about the picture manual thing.. Im just one man with not enough time.
And.. and and.... English isnt my native tounge either... so bare with me on all the bad spelling and grammar.


I also found a stupid bug/bad programming yesterday.
The Locut filter was placed so that it was active even when the plug was switched off.. I fixed that + I have removed the "pre trim" function since it is now useless with the new routings.

This and probably more things will be in the next release.
Top

Post

This thing eats cpu-cycles like there's no tomorrow. :shock:
Top

Post

jens wrote:This thing eats cpu-cycles like there's no tomorrow. :shock:
There's jens with his 286 again! :P
Top

Post

yup, some plugins make it indeed appear as if I just had a 286 - and this is one of them - all of a sudden ten cycles only have the worth of one :-o
Top

Post

jens wrote:yup, some plugins make it indeed appear as if I just had a 286 - and this is one of them - all of a sudden ten cycles only have the worth of one :-o
Sorry bout that Jens.
Maybe you need to get a better computer?
On my mac it uses about 2% cpu. A little more if I use the exciter and Lowcut.
Top

Post

aliasant wrote: Maybe you need to get a better computer?
for sure...

however e.g. GCO-1 uses around 1,5% on my machine, while Inerthia uses ca. 10-17% (depending on what modules are enabled)
Top

Post

aliasant wrote:The Locut filter was placed so that it was active even when the plug was switched off.. I fixed that + I have removed the "pre trim"
Ah Ok: I was going to ask you exactly about Locut and pre trim :wink:

One thing I don't like at all is the 'o' of the 'Ratio' knob's label with the above-lying 'Listen' blinking led; I just find it wasting the overall neat GUI.
I guess you placed it there for the sake of simmetry (?) Well looking the left side there's the envelope section with the little knee knob centered between the two big (A R) knobs values; ok now if you place the (sidechain) little 'on' button centered as that knee knob... youll gain room for placing the blinking led between (vertically) the 'Listen' and the 'on' button. And you'd save the overall neat-simmetry... does it makes any sense? :roll:
Top

Post

tonAP wrote:
aliasant wrote:The Locut filter was placed so that it was active even when the plug was switched off.. I fixed that + I have removed the "pre trim"
Ah Ok: I was going to ask you exactly about Locut and pre trim :wink:

One thing I don't like at all is the 'o' of the 'Ratio' knob's label with the above-lying 'Listen' blinking led; I just find it wasting the overall neat GUI.
I guess you placed it there for the sake of simmetry (?) Well looking the left side there's the envelope section with the little knee knob centered between the two big (A R) knobs values; ok now if you place the (sidechain) little 'on' button centered as that knee knob... youll gain room for placing the blinking led between (vertically) the 'Listen' and the 'on' button. And you'd save the overall neat-simmetry... does it makes any sense? :roll:

Well. No ;)

It is placed above the Ratio knob because that is were your eyes are when your turning it... If your in listening mode
you should see that easily and that is why I placed the lamp in the center of the image.
I tried having it around the sidechain but that just didnt work. I found myself several times turning the ratioknob and hearing no difference.. very confusing until i glanced down to the right and saw the blinking lamp.

But I agree on the fact that it is not looking great. But that can be improved later on.
Top

Post

aliasant wrote:But I agree on the fact that it is not looking great.
But that can be improved later on.
Ok, the idea itself is not bad at all... I don't remember SMaker now: but if the 'off' state of the led could be the same grey as the GUI, that would be a neat solution? Flashing grey-yellow instead of black-yellow. So the off state would be 'almost' a perfect 'o'?
Top

Post

tonAP wrote:
aliasant wrote:But I agree on the fact that it is not looking great.
But that can be improved later on.
Ok, the idea itself is not bad at all... I don't remember SMaker now: but if the 'off' state of the led could be the same grey as the GUI, that would be a neat solution? Flashing grey-yellow instead of black-yellow. So the off state would be 'almost' a perfect 'o'?

Yes. That could work. Easy to make but.. I have another idea cooking in the back of my small head.
Since we are in "listen" mode we wont hear the processed compressed signal so I was thinking why not let the entire
gainreduction peakmeter flash... That would make more sence I think. But its for a later version.
Top

Post

[DELETED]
Top
Post Reply

Return to “Effects”