Youlean Loudness Meter has an average user rating of 4.40 from 5 reviews
Latest 5 reviews from a total of 5
Nothing but the AU shows up in reaper, and when I try to load that it crashes. Anyone else?
THIS POST HAS BEEN REMOVED
I have update the zip file for MacOS. This is a quick fix, I am working on a proper solution.
Awesome, am excited to try this one... Will try as soon as I get a chance. Cheers.
Hi! Very nice plugin! But what means letter A and Triangle? I didnt manage to find some manual.
And one more: sometimes arrow starts to move randomly up and down very fast when i'm trying to measure some music loop.
A automatically resets the measurement every time the loop starts I guess.
Yes... But the movement is very strange. And there is no possibility for static measurement (when playing synth, for example) without cursor movement.
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 youlean, Thanks for this. Its a tool I needed! I can see you perfecting this in later updates. Well done.
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.
Try version 1.0.1. This version should fix most critical bugs. If you encounter any other bugs, please let me know. Regards.
Hey youlean, as I wrote on your thread, the Windows link actually downloads the MacOS version. Windows v. still available?
Thanks Youlean, this is great, but I was hoping for something scalable (for high dpi screens) when I see "resizable" mentionned :)
Measurement is reset when loop restarts in daw (shouldnt happen imho), at least in Reaper.
Would be nice to have an option to hide graph...
I think the A-button (which I guess stands for auto reset on transport) is supposed to switch on and off the reset when loop restarts. However, I don't think this works properly in version 1.1.
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.. ;)
I am investigating auto reset bug.
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 am investigating auto reset bug! Hopefully there will be fix soon...
Just one question, what is the purpose of the play-button? LUFS integrated is measured after measurement is reset or do I have to press play in addition?
When pause is activated integrated loudness and LRA should be paused. Now I see that this also doesn't work properly. I will fix that.
Just want to say that true peak detection is not accurate, so don't rely on it util I fix this. Sorry for that.
Unfortunately crashes Ableton live when it is installed. Shame, it looked really promising.
Well, it is not end of the world, it will be fixed. :D It is known bug AU crashing Ableton. Try VST version.
Still can't get any of the versions to work. VST2 and VST3 don't even show up in the last of Ableton plugins and AU still crashes Ableton.
Hi! I've found that Youlean Meter 32-bit doesn't remember last settings (Split, True peak, GUI size) in reaper 5 and nuendo 6.
OK. What plugin format ans OS are you using? I will check this out.
Sorry that i didn't mention that earlier. VST2 32-bit, widnows 7.
Can you tell me what Logic version do you use and what is your OS version? Here it validates just fine...
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 18.104.22.168, on OS X Maverics.
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 soon.
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.
Thanks for the review. Plugin does indeed have some bugs that are going to be resolved in the next update.
There will be released a new version in a couple of days that will fix that.
Congratulations on your well deserved win.
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?
Thanks. There is no option for donation. If you want to support me, just tell your friends about my plugin. :)
GUI scaling is coming after NAMM Show (I don't have time to implement it before NAMM).
THIS POST HAS BEEN REMOVED
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. :)
OK, I will check this out. Thanks for the detail report, it really makes debugging much easier for me.
Hey, does anyone know where I can download previous versions of this. I was looking for a version that was supported my Mac OS 10.6. Thanks.
Hi Youlean. Can you please help me? Every time I use my DAW (REAPER on Windows), I get a file on my desktop called "꺈똋翹" whose contents is:
Available Plugin Version=20002
News Title=New version available V2.0.2
News Button Text=GO TO WEBSITE
News Skip Button Text=LATER
News Button URL=https://youlean.co/youlean-loudness-meter/?utm_source=YLM%20Plugin&utm_medium=UPDATE&utm_campaign=update%20notification%20v2.0.2.
Hey, sorry for the trouble. This is plugin checking for the news.
Disable checking for updates and it won't go to the desktop anymore.
This is a bug BTW, so what OS are you using? Also, what is your system language?
Just tried to use the AAX latest free version (v 2.3.0) and Pro Tools doesn't like it when it scans it on launch. Getting this error:
"The following plug-ins failed to load because they are not valid 64-bit AAX plug-ins:
Youlean Loudness Meter 2.aaxplugin"
Thanks for the reply. That is on a macOS 10.11.6 system, with Pro Tools Ultimate 2018.7.
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?
I think that coping is probably the issue. Did you try to use the installer?