Talking clock - timestamp problem?

[David Holroyd]

Hi,

On 18/08/14 22:11, David Holroyd wrote:
> I am trying to build a pipeline something like a 'talking clock', 
> continually
> announcing the current date and time as test input to another system.
>
> The pipeline I've built in Ruby (bindings via gir_ffi) looks like:
>
>   appsrc ! festival ! wavparse ! audioconvert ! audioresample
>     ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! rtpL24pay
>     ! udpsink

> If timestamps coming out of wavparse are the problem, is there a way 
> to alter
> the pipeline to fix this?

I inserted an identity element and used it's 'handoff' signal to add an 
offset buffer.pts to account for the elapsed time between each utterance.

That does seem to smooth-out the sending of RTP packets, although it 
feels a bit hacky.  Is there a better way?