joshg567

I'd been wanting something to help compare and match volume levels pre/post eq/compression/etc., and then I found some guy made a VST for it: 

 I don't want to drop $150 on it, though, so figured I'd see how close I could come with M4L.

Now, through some cursory research I've discovered it is not trivial to duplicate the full functionality. However, I got started and see the obvious shortcomings, and I invite anyone interested to try to directly improve the devices as much as possible or perhaps offer guidance. I know send~ and receive~ don't work between devices so that's a huge drawback.

LevelPre goes at the front of a signal chain, LevelPost goes at the end and receives the level data from LevelPre to compute a simple difference (not something good like LU) and represent it as a variable running average on another meter, GainDiff. The Max meter~ and levelmeter~ objects are there just to try to eyeball the differences. It still requires manually tweaking gains in the signal chain (no analogous balance function), and the latency (lack of analogous sync function) is obvious. Another clear problem is that only one paired instance of the devices will work in a single live set until the sends and receives can be disambiguated.

Can improvements be made? The utility of such a device in completed state is undeniable.

I'd been wanting something to help compare and match volume levels pre/post eq/compression/etc., and then I found some guy made a VST for it: http://www.meterplugs.com/perception I don't want to drop $150 on it, though, so figured I'd see how close I could come with M4L.

Working on a Perception VST copy (Devices to help A/B), want input.