RD already supports destructive peak level based normalisation on import, which I'd guess is commonly used by the majority of RD equipped stations. R128 is simply an alternative method (or potentially non-destructive post supplement) to Peak normalization, that in some station formats is *far* better suited to todays audio sources, some of which are hyper compressed and clipped well beyond what was done 15 years ago.

Peak normalisation may have 'cut it' once, but in 2016 it is not well suited to many modern re/mastered music files, thereby currently requiring the extra time wasteful step in RD of manually setting playback level attenuation for each track.

Yes, in an ideal world we would all listen to every bit of audio being imported and manually adjust playback level offsets, all marker points etc. We often don't have that time, *or*, automated import (and subsequent playout) is occurring while the station is unattended. Having the automation tools to 'automate' that process well, and result in the smoothest, best playout mix possible (without user intervention) is desirable. R128 is one of those tools, and it typically does a great job fully automated anyway. Another leading automation system has no less than 5 types of inbuilt 'normalisation' methods available, all non destructive. I think R128 is arguably the most useful normalisation method in a modern automation system.

When a station is time poor, a good operator will gravitate to efficient tools that reliably automate as much of the process as possible. Multiple station feeds/formats, one producer, increasingly common. Getting the best possible product delivered within the constraints of the resources you have is more the mark of a professional than an amateur.

Interesting to read the earlier post R128 is commonly used in Europe. Pleased to hear R128, as a user option, is on the road map - thank you Paravel.

_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Reply via email to