Post Description

We had an idea that maybe it would be good if there was a preview button in our low-end measuring plugin
Evouyn that would cut off any excessive bass so that you could get an idea of how big the damage down there really are.
We came so far that a beta version was made and our beta testers started to do their job.
We usually deliberately refrain from telling how we meant to use the new feature since beta testers' first reaction
is invaluable when evaluating the usability of a new function. In this case, we were
horrified at how our beta testers
started to use the preview feature to actually process their masters. That was not our
intention,
the filter we used sounded terrible (we thought) and was only there to give a rough idea
of how
much bass that needed to be cut away. We ditched the feature when we realized how high the
risk of people using it improperly was.
We went on with the next project when one of our beta testers e-mailed and asked for an
adjustment.
We told him that he was using it wrong and that the feature wouldn't pass the beta stage.
Then another beta tester e-mailed and asked for an adjustment since he started to use it
on all his masters.
Then a third. Then yet another. Within 9 days all beta testers except one had requested
different functions and updates.
Ok, we get it, people liked the simplicity of an one button quick fix but we won't put it
in Evoyun.
We made Bipro, a by-product from an function in another plugin that never got implemented.

We put an unicorn and glitter on the GUI since our beta testers say its magic.
We say it's a low-end compressor or a dynamic lo-shelf EQ..[/left]

For Windows 32Bit hosts (or bridged in 64bit hosts)

nJoy!