Hi ermina, thanks for the explanation and the links. I doubt the 0db all the time and know, that e.g. German public radio follows EBU recommendation, too. But sometimes its difficult to fight the tech myth in our college station ;) But I will try it with your explanations again.
For new files we plan to set segue and cut-points manually, but i thought to set the points automatically for the audio files i import from our current radio automation software. I could use the values from the old db, but its really unreliable, because some people in the past didn't take care, when adding new material. Would you recommend to not use segue for that material instead, because a no segue is better than a bad segue? Thanks again Keywan Am Montag, den 20.10.2014, 13:28 +0200 schrieb [email protected]: > Hello, > > personnally i use -13dB normalization on importing to rivendell for > almost everything. > For music, i then further adjust the cut gain level so that it fits the > EBU R128 recommandation. > > For our in-house productions, -13dB peak normalization on import gives > something that roughly fits the R128 (which is logical as we mix using a > K-12 meter as reference.) > > For some external programs, we have to check and adjust levels manually. > Some third-party ingest front-ends might help take care of this (ie. > keeping consistent levels between cuts), like > https://github.com/JamesHarrison/iris or > http://wiki.tryphon.eu/rivendell-import/start . > > Auto-trim is set to -29dB just in case, but start and end are always > manually adjusted for every cut, as is the segue point. > For music, setting the segue point manually (eg. on the last drum hit, > on an echo, timely with the tempo of the song,…) can result in really > tight and seemless succession of tracks, while still respecting a calm > ending or the need for a short breath at the end of particular song > (which is the thing i wanted doing that). > > Automatic segue point can be a bit harsh depending on the end of some > songs (when last word is whispered, or things) > > The most important part is to keep all levels coherent in the airplay > chain. > For example, in our installation, 0 on RDAirplay meter gives -12 on the > sound card output level: that leaves 12 dB of headroom before getting > distortion. > > > In digital audio, 0dBFS is not a desirable level to reach, whatever the > production stage. > If you need more volume, you might find (reasonable) dynamic compression > to be more effective that "0dB normalization". > > Read about the R128. It will solve all your level problems (many of > them, actually). > The core concept is that peak level is irrelevant, the important thing > is the average perceived level. > By setting this mean level around -23 LUFS, you don't have to worry > about peak levels and overcompressing anymore. > When all your content is "normalized" according to average level instead > of peak level, you have program audio that is ready to ship to the > levelling/squeezing/adjust-to-convenience step before hitting > transmitter. > > Hope it helped. > > . e > > > On 2014-10-20 12:14, Keywan Najafi Tonekaboni wrote: > > Hi > > > > what values do you recommend for "--normalization-level="? > > Some of our audio files sound overdriven, when I don't use "-12". Until > > today we normalize every report, jingle etc with Adobe Audition to 0dB. > > > > With which values for autotrim (reports/music) and segue-level/length > > do > > you have good experiences? > > > > Best, > > > > Keywan > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev -- Keywan Najafi Tonekaboni <[email protected]> http://www.prometoys.net _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
