Quote:
Originally Posted by musicbynumbers
Reaper 5 needs this
This is the one from Nuendo.. Justin and Scwha could easily add this I reckon! I have faith in them!
|
It looks a little like the Nuendo folks may have copied the idea from the FR, but I don't think that's the case.
Plenty of engineers were asking for a timecode locked loudness history before that. In fact, a guy from RTW made a presentation here in Berlin about loudness metering, pimping their produces along the way of course, and mentioned that it was the most-requested feature.
Reaper however is not in the habit of doing anything but one type of track, which is why a dockable, arrangement-view-syncable view is proposed in the feature request.
Along with that the loudness scanning functions of source files could actually be implemented at the time the peak-files are generated.
We're talking 400ms RMS with two bands of filtering, which could easily be bolted to the end of the actual peak file for easy reference, so trimmed items could still easily have their loudness measurement calculated from the data. I am assuming of course that with a 75% overlap, the RMS scan only needs to produce data every 100 ms, so one float for eash of that and it's just 40 bytes per second of audio.
The game audio folks certainly should be clawing for this. Loudness-normalizing dialogue would give you an excellent starting point to work from.