BetabugsAudio/Yohng - W1 Limiter RELEASED
-
- AcousticHippie
- Topic Starter
- 4769 posts since 12 Mar, 2003
-
- KVRist
- 158 posts since 24 Sep, 2003 from Wales
Been using the w1 for a couple of weeks - now it looks as good as it sounds!
Thanks
Trev
Thanks
Trev
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
In my opinion, it comes down to this--
Some people simply don't like no-GUI plug-ins, no matter how good they are. They equate the appearance with the function. With a shiny new face, we're hoping that George's plug-in will get a few more users and get the respect it deserves.
You still have your choice of two flavours-- with or without GUI. Nobody's twisting any arms.
Greg
Some people simply don't like no-GUI plug-ins, no matter how good they are. They equate the appearance with the function. With a shiny new face, we're hoping that George's plug-in will get a few more users and get the respect it deserves.
You still have your choice of two flavours-- with or without GUI. Nobody's twisting any arms.
Greg
-
- AcousticHippie
- Topic Starter
- 4769 posts since 12 Mar, 2003
now that is a compliment I likeguido01 wrote:now it looks as good as it sounds!
-
- KVRist
- 46 posts since 20 Jun, 2003
GUI-less version shows indication of decibels and what you exactly do, while BegabugsGUI version has only bizarre 1...12. Some users might prefer decibels, others will prefer 1...12 (but with fancy knobs).mauseoleum wrote:gui-less version sounds better.hehe, wouldn't that also render the entire ui concept useless?
kiss steven. mmmm ... lovely.Yeah I know about the Mac VST version, but my host is AU only, and I don't have (or particularly want) FXP's adapter.
Otherwise, the algorithm is the same. Note, that in GUI version threshold is regulated 'forward', while in gui-less version, according to limiter tradition, threshold is measured as 'minus decibels'.
4Front software
http://www.yohng.com
http://www.yohng.com
-
- KVRAF
- 1651 posts since 14 May, 2002 from Earth
A cool new gui to a great limiter. Thanks alot guys 
-
- KVRAF
- 2935 posts since 14 Dec, 2003 from Edinburgh
It would be great if betabugs would make the GUI correspond to the 'proper' values that are used in the GUIless version. I know you guys make nice simple plugs but its kinda useful to know these values.gyohng wrote:GUI-less version shows indication of decibels and what you exactly do, while BegabugsGUI version has only bizarre 1...12. Some users might prefer decibels, others will prefer 1...12 (but with fancy knobs).mauseoleum wrote:gui-less version sounds better.hehe, wouldn't that also render the entire ui concept useless?
kiss steven. mmmm ... lovely.Yeah I know about the Mac VST version, but my host is AU only, and I don't have (or particularly want) FXP's adapter.
Otherwise, the algorithm is the same. Note, that in GUI version threshold is regulated 'forward', while in gui-less version, according to limiter tradition, threshold is measured as 'minus decibels'.
Top limiter, been using it for a while now, thanks George, and betabugs !!!
jim
-
- KVRAF
- 1907 posts since 29 Oct, 2003
o.k.Otherwise, the algorithm is the same. Note, that in GUI version threshold is regulated 'forward', while in gui-less version, according to limiter tradition, threshold is measured as 'minus decibels'.
how's the 'pro' version ? any progress yet?
i have couple of paywarez but for my recent projects i used exclusively arguru stardust + w1-guiless combo on master, which sounds closest to my taste. o.k.enough with freebee fiesta. when's the 'pro' version coming out ?
-
- Banned
- 22457 posts since 5 Sep, 2001
[DELETED]
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
Regarding the knobs corresponding to values--
-In concept and execution, the numbers are in many ways very arbitrary and cosmetic. Mully could have easily rendered knobs that feature no numbers whatsoever, and the functionality wouldn't be affected.
-I also think about threshold as a declining value, partly because I am already a user of George's GUI-less W1. However, we thought it would be simpler in concept if "when you turn this UP, perceived volume goes UP," so there IS a method to the madness!
-It is not feasible to put any sort of useful numbers on the release time knob. It goes from 1 ms all the way to 5000 ms, and as the manual notes, increases in release time are quadratic (is that the same as exponential?) rather than linear. Representing this numerically on the knob itself would be impossible to do with any sort of elegance.
Regarding an LED-type indicator:
-It could be handy. That's something that is pretty much up to George. For what it's worth, strictly in my opinion as a user, it's not necessary. As a musician/producer, I find I am aware of the levels of my own material and that when I bust out a limiter, it is for one of two things:
a) to tame a few stray peaks. In which case, an indicator will light up every now and then, just as I expected. I don't need an LED to tell me what I already know, which is that the occasional peak is being tamed.
b) for hard limiting and loudness maximization. In which case, the LED will almost constantly be lit up. I don't need an always-on LED to tell me that the limiting engine is engaged, when my ears are already telling me.
That's mostly a perspective as a user, though. I can certainly see why some people will feel more comfortable with numerical readouts, in which case George's original W1 is still the one for you! And while I don't personally see the need for an 'active' indicator LED, I can understand that there ARE other users besides myself who have used such things in the past and have decided that they are useful. In my personal experience, it's just a cosmetic bell/whistle.
At the end of the day, the W1 is in my opinion the best freeware limiter available, and I think people should try it out in EITHER form to see how good it really is.
Greg
-In concept and execution, the numbers are in many ways very arbitrary and cosmetic. Mully could have easily rendered knobs that feature no numbers whatsoever, and the functionality wouldn't be affected.
-I also think about threshold as a declining value, partly because I am already a user of George's GUI-less W1. However, we thought it would be simpler in concept if "when you turn this UP, perceived volume goes UP," so there IS a method to the madness!
-It is not feasible to put any sort of useful numbers on the release time knob. It goes from 1 ms all the way to 5000 ms, and as the manual notes, increases in release time are quadratic (is that the same as exponential?) rather than linear. Representing this numerically on the knob itself would be impossible to do with any sort of elegance.
Regarding an LED-type indicator:
-It could be handy. That's something that is pretty much up to George. For what it's worth, strictly in my opinion as a user, it's not necessary. As a musician/producer, I find I am aware of the levels of my own material and that when I bust out a limiter, it is for one of two things:
a) to tame a few stray peaks. In which case, an indicator will light up every now and then, just as I expected. I don't need an LED to tell me what I already know, which is that the occasional peak is being tamed.
b) for hard limiting and loudness maximization. In which case, the LED will almost constantly be lit up. I don't need an always-on LED to tell me that the limiting engine is engaged, when my ears are already telling me.
That's mostly a perspective as a user, though. I can certainly see why some people will feel more comfortable with numerical readouts, in which case George's original W1 is still the one for you! And while I don't personally see the need for an 'active' indicator LED, I can understand that there ARE other users besides myself who have used such things in the past and have decided that they are useful. In my personal experience, it's just a cosmetic bell/whistle.
At the end of the day, the W1 is in my opinion the best freeware limiter available, and I think people should try it out in EITHER form to see how good it really is.
Greg
-
- KVRist
- 82 posts since 26 Oct, 2003
-
- KVRAF
- 2935 posts since 14 Dec, 2003 from Edinburgh
But the skinless version by George already displays the number corresponding to the value the slider is set at, so the plug must be generating some kind of value that is being displayed by the Host's own GUI, so a little window under the knob displaying this value, just like in the Host's own GUI, would be very useful and surely not impossible?Lunch Money wrote:Regarding the knobs corresponding to values--
-It is not feasible to put any sort of useful numbers on the release time knob. It goes from 1 ms all the way to 5000 ms, and as the manual notes, increases in release time are quadratic (is that the same as exponential?) rather than linear. Representing this numerically on the knob itself would be impossible to do with any sort of elegance.
Don't get me wrong I'm NOT complaining in the slightest; i think anyone providing such high quality free plugins such as this is to be appluaded and thanked profusely, I'm just pointing out something that would make it more useful, and seems to exist in the original limiters code too. I'm no programmer so I may be horribly wrong, but if the skinless version shows values then it must be possible to make a skinned version show the value too.
I'm not fussed about the light meter, as I just set these things to sound the way I want them to, rather than to look 'right'. Whilst that may sound like I'm contradicting myself after what I previously said, I find it very useful to know the values of threshold, release etc, as part of the learning process. Once I learn that I like a certain setting to be at eg 60ms, I can transfer this knowledge to other plugins.
But anyway, top marks to George and to Betabugs!
jim
-
- KVRAF
- 1651 posts since 14 May, 2002 from Earth
I have a small suggestion as well:
How about naming the dll something a little less LONG. I had to rename it because it was so big it was stretching one of my hosts menus out, which was bugging me (npi). I renamed it to just "w1 limiter.dll" but since i used an installer, I dont know if it'll miss something if I forget to rename it back later and I want to uninstall.
How about naming the dll something a little less LONG. I had to rename it because it was so big it was stretching one of my hosts menus out, which was bugging me (npi). I renamed it to just "w1 limiter.dll" but since i used an installer, I dont know if it'll miss something if I forget to rename it back later and I want to uninstall.