I love this plugin. I use it for every master I got. (Also for gain matching and compensation of different tracks when mixing).
But there is one thing which so unbelievably annoys me every time I'm using it:
I use the plugin only for the meters to the left (without the histogram) and like to use it in vertical mode (that is: 'Histogram graph - OFF' in the view settings), pinning it to one side of my screen. In this way I can always look at the meteres on the fly, without wasting any space unnessary and have the place empty for my DAW and other plugins.
Now, the problem is that every f***ing time I initiate one instance of YLM2, I need to switch back over to the settings at the very top left corner, click on the switch to disable the histogram view and again close the view settings.
Why can't the plugin remember that state or have a preset with my preferred visuals?
A great plugin, but that is absolutely worth for me to take one star away from a 5/5 review.
My to-go loudness measurement tool. It is accurate, well designed, gives the best and most needed visual feedback and makes mixing fun! It even lets me export the loudness and dynamic range into a fancy PDF file - nice! I recommend it 100% - even the pro version, to at least support the dev, which would be well deserved. By the way: dev replies to feedback (any issues or FRs) quite fast. Thanks for this tool and that support!! (=.
Edit: After reading a feedback here: to me it is completely unfair to downrate this plugin, only because there might be buttons ghreyed out for the pro-version. 1. There is at least a free usable loudness meter version of it in the end (most loudness meters aren't free at all - I can just think of Meldaproduction - or are even quite expensive anyway ...) and 2. The pro-price is not even expensive at all AND includes lifetime free updates. As a professional in this area I call this small price almost "a gift to the users", like it did not cost anything at all ... (-;
... so please: especially keeping in mind that there is a free version, which just does its job (!!) and respecting that this tool is made by a single developer, I'd say it's just fair to not be bothered by greyed out buttons in a free version.
This new free version is cluttered with ghosted buttons that are unusable and making a mess of things.
I understand you maybe learnt some bad business habits from other developers you met from the winnings last time, but it's far too intrusive in this manner... ONE upgrade button would suffice, instead of leaving all the ghosted options in the way. Unfortunately it feels less about mixing, and more about avoiding buttons this time around... Big step down in usability for me.
This is a meter that does exactly what is necessary with sufficient options, is pleasing to the eye and gives accurate useable data in a wide variety of standards. I wanted to give it 10/10 but I do have one reservation, that the GUI be able to be made smaller to facilitate use on smaller screens.
The triangle right to main meter represents short term loudness. If it is moving crazy this is probably due buffer reset. Try switching "A" off. Also you can see if "Elapsed" or "Time Code" mode suits you better. The manual is in the works BTW.
Hi there. I have tried both the AU and VST2 versions in Ableton Live 9.6.2 on a Mac. The VST version does'nt show up in the list of installed plug-ins, even after a re-scan, and the AU version cannot be opened. I hope this can be resolved, I'd love to try it out! Cheers.
Unfortunately scalable interface just barely didn't make it for KVR DC16. After this competition ends, plugin will get option to become scalable and it will get option to hide distribution / histogram + it will get some cool new features.. ;)
Thank for the update, Youlean! The auto reset on transport button does not seem to work properly i v 1.1, windows 64. In FL it works until the first loop from the end of the song til the beginning. Then it stops working when I stop and start the project in the middle of the song. In Reaper it does not work at all. It is always off.
I have a similar problem, it doesn't show up in Audition (it doesn't pass the validation VST and AU), and it crashes Logic Pro right at the start. VSTs and AU aren't working. Logic Pro is 10.2.2, Audition is CC 2015.2.1 Build 126.96.36.199, on OS X Maverics.
We have tested it with our audio host GigPerformer and it works fine on our 10.10.5 machines. In fact it works so well that we've added it to our own recommended list of free plugins (and as touring musicians we are VERY discerning!)
See http://www.gigperformer.com/list-of-best-free-vst-and-au-plugins-you-should-try-out for more.
Thanks. This in known issue. It seams that plugin works only in macOS 11.11 and newer. I am looking at that, and I think that this should be solved soo.
I think your meter plugin is just about spot on. It does everything I want it too and nothing unnecessary. It works perfectly on OS X 10.10.5 with the latest version of REAPER and is a great compliment to it.
I only have one request; could you make the GUI able to be smaller? I work on a MacBook and would appreciate being able to have more plugins visible at once.
Do you have plans to charge for this or do you have a donation option somewhere?
Hi - CRASH.! The VST3 edition (v1.0.4) was not stable here with Cubase Pro v8.5.20 or v9.0.1 Any improvements/fixes made in the v1.0.5 release that might help this..? The v1.0.4 loaded into a Cubase Pro 9 project ok and you could open and use the plugin... However, after saving and closing that project, attempting to re-open it would hard crash both Cubases (v8.5.20 and v9.0.1). The project contained nothing but 13 stereo audio tracks, no other plugins at all. I uninstalled (deleted) the VST3 plugin from C:\Program Files\Common Files\VST3, I rebooted the machine and tried again to open the project... It worked..! I do not want to install/use the VST2 edition if I can help it... Win10 64-bit. Thanks, if you have any thoughts...
I am experiencing exactly the same issue, in my case with Cubase Elements 9.0.2 64-bit and Youlean Loudness Meter 1.0.5 64-bit VST3. Hope you find the solution as I really like this plugin! Thanks in advance. :)
It's giving the same message still in Pro Tools 18, sorry.
I'm a plug-in dev as well, so I have a copy of the Developer Build of Pro Tools (although this is on a different system, so it doesn't completely isolate the issue). As you know, the Developer Build does not require a valid PACE signature to load a plug-in... perhaps that is the issue? Have you tested it on a non-Dev Build of Pro Tools?