ed end of the track is at least 1.5 seconds away from the end
>> of the segue. If these conditions are not met, the segues won't hit
>> correctly on the air. We wasted an extra 2 weeks learning that lesson the
>> hard way.
>> · Even if you have a piece of imagin
n is less than a second, you're still going to need
> that second of silence in front and that 4 seconds of silence in back, or
> its segue will be nasty. You won't like it.
> TC
>
>
>
> *From:* rivendell-dev-boun...@lists.rivendellaudio.org [mailto:
> rivendell-dev-boun...
Even if you have a piece of imaging or a sound effect or
> > something whose duration is less than a second, you're still
> > going to need that second of silence in front and that 4
> > seconds of silence in back, or its segue will be nasty. You
> &g
air. We wasted an extra 2 weeks learning that lesson the hard way.
>> ·Even if you have a piece of imaging or a sound effect or
>> something whose duration is less than a second, you're still
>> going to need that second of silence in front
gt; going to need that second of silence in front and that 4
> seconds of silence in back, or its segue will be nasty. You
> won't like it.
> TC
> *From:*rivendell-dev-boun...@lists.rivendellaudio.org
> <mailto:rivendell-dev-boun...@lists.riven
ront and that 4 seconds of silence in back, or
> its segue will be nasty. You won't like it.
> TC
>
>
>
> *From:* rivendell-dev-boun...@lists.rivendellaudio.org [mailto:
> rivendell-dev-boun...@lists.rivendellaudio.org] *On Behalf Of *Pedro
> Picoto
> *Sent:* T
in back, or
> its segue will be nasty. You won't like it.
> TC
>
>
>
> *From:* rivendell-dev-boun...@lists.rivendellaudio.org [mailto:
> rivendell-dev-boun...@lists.rivendellaudio.org] *On Behalf Of *Pedro
> Picoto
> *Sent:* Thursday, June 26, 2014 1:39 PM
> *To
;t like it.
TC
From: rivendell-dev-boun...@lists.rivendellaudio.org
[mailto:rivendell-dev-boun...@lists.rivendellaudio.org] On Behalf Of Pedro
Picoto
Sent: Thursday, June 26, 2014 1:39 PM
To: rivendell-dev@lists.rivendellaudio.org
Subject: [RDD] Segue start failing
I've noticed that randomly
I've noticed that randomly the segue start point isn't respected. Each time
I listen to one failing I check it on the RDLibrary and it's correctly
marked.
Running version 2.8.1. and never had this problem before. I've been
using/testing/learning this
version for quite a while.
_
