On 11/1/18, Fred Gleason <fr...@paravelsystems.com> wrote:
> On Oct 31, 2018, at 15:43, Gregory Avedissian <avedis...@gmail.com> wrote:
>
>> Is it safe to do something as simple as having the script go to /var/snd
>> and run:
>> for i in *.wav ; do sox --norm=-5 "$i" /tmp/"$i" && cp /tmp/"$i" "$i" ;
>> done
>>
>> Oh yeah, there will be rm /tmp/"$i" in there, too. Just noticed that.
>>
>> I ran a quick test, and it seems to work. Seems too easy. Am I missing
>> something?
>
> Reprocessing already-imported audio this way will likely kill waveform
> display in rdlibrary(1). This is because (last I looked) sox(1) does not
> output fully BWF-compliant WAV files (in particular, the LEVL chunk needed
> for generation of the visual waveform). You should however be able to
> achieve a similar result with full BWF compatibility by using rdconvert(1).
> (Do ‘man 1 rdconvert’ to get documentation).
>
> That said however, I’d strongly second Robert Jeffrares’s recommendation
> that this be handled as part of the broadcast chain rather than by changing
> the gain structure of Rivendell. -5 dBFS leaves very little headroom to work
> with, and rewriting audio can cause quality degradation (especially if MPEG
> Layer II format is involved).
>

Thanks. We're re-examining the setup in light of Robert's suggestion.
Whatever we do, I will have to renormalize a bunch of carts, because
some are at -5 and some at -13 now. We're using rivendell-2.10.3-1
installed from deb packages, and rdconvert does not exist there.

I do have a new rivendell 2.19.x on centos that I installed a few
weeks ago, and it looks like I can convert the files on that system
and copy them back to /var/snd. Are there any problems with doing it
that way? Is it possible just to copy rdconvert to the server and run
it in the older version of rivendell? (I can try that last one when I
get home.)

Greg
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Reply via email to