Thanks James, I never used r128gain but it sounds awesome. I'll test it shortly. Thanks a lot !
I found this: https://github.com/3M3RY/repositories I'm still testing those tools with no success so far. 2012/2/2 James Harrison <[email protected]> > I'm pretty certain that if you're just normalizing (no topping/tailing) > with a tool like r128gain, you'll be fine. So long as the duration doesn't > change, it ought to be alright. > > I'd recommend making a copy of /var/snd (to /var/prenorm), do in-place > normalization to everything in there, mv /var/snd to /var/oldsnd, mv > /var/prenorm to /var/snd, and test. If it goes horribly wrong, move things > around again. > > Cheers, > James Harrison > > > On 02/02/2012 18:31, Pierre-Luc Gauthier wrote: > > Hello there, > > I've been told a while back on the #rivendell-dev IRC never to manually > edit the cuts in /var/snd. > That seems about right thinking of the database notion of "cut length" in > milliseconds and all the markers that relate to it. > > But what about the audio itself? > Could we edit cut 000001_001.wav with, lets say, audacity making sure to > leave it at the exact same length? > > I've imported LOTS of music rebuilding a brand new installation. And > forgot to normalize it... I'm about to batch the entire content of > /var/snd/ with audacity. > > So far, Rivendell doesn't seems to mind. > Do anyone advises against this practice? > > Thanks > -- > *Pierre-Luc Gauthier* > * > * > > > > > > _______________________________________________ > Rivendell-dev mailing > [email protected]http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > > -- *Pierre-Luc Gauthier* * *
_______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
