Currently the loudness track offers faster-than-realtime (“offline”) processing, but only for a point in the signal-path in the mixer.
Pull this feature out of the track and put it in a plugin. Allow us to measure, offline, a selected event.
This would be useful when we have recorded stems or mixes on tracks and punch into them. It would be easy to do a quick analysis of any of them to verify loudness, not having to deal with routing at all. This would, I’m guessing, already work with the older loudness plugin if the plugins remained opened after hitting “process”. Of course my suggestion then might imply that to carry out this request would also necessitate dealing with the other request to leave offline plugin windows open after processing. One stone - Two birds.
This would combine two things. The first is what I suspect is happening already based on new functionality and what I requested before, namely logging data. At least peaks are logged now. So, since data is being kept somewhere in memory, I’d like it if that data instead could be written to a file. The document would contain simple information - Event Name, Date, All Loudness Data.
The second which would be combined with the above is the ability to do this to more than one event (or file) at a time, and select those either in the project window or pool.
This would allow us to select X files/events, select the plugin, batch-analyze them all, and then have the results written to a document (or on-screen). I’ve had at least one occasion where QC rejected a mix I had done on the basis that loudness was off, I did a quick analysis with Dolby Media Meter and sent the resulting document off to the production company. They sent it off to QC and we never heard back from them again. Very useful.
EDIT: I know we can get an offline measurement in a ‘dialog box’ on-screen, but what I’d like to see is a list of events over time the way Dolby Media Meter does it, so one can inspect certain sections of the program material.