[pootler]

does that make any sense ? - and is there anybody out there using Pi / live tv who recognises what I am saying?

Yes, it matches my understanding. I think if you have a perfect signal with no errors, then the audio sync will be fine (whether using official openelec or milhouse build).

If you are getting visible corruption on screen (e.g. due to a poor signal from aerial), then it is possible the timestamp of an audio packet is corrupted.

I think something in the code gets upset by the bad timestamp and results in bad audio sync for some time (possibly until that timestamp is actually reached).

It appears that the milhouse build handles the bad timestamp better than official openelec.
So, the question is, do the first or second test builds behave the same as the milhouse build (and so better than official?)

I realise that as the problem relies on random errors which come and go it may be hard to be certain if build A is better than build B.
Just keep switching between the builds and report which one you are happiest with.


Back again

So I,ve used both builds for a few days now, and the results (from the UK jury) are:

Build 2 - show drifts like build 1. Reading what you said about timestamps, rather than flip the channel to and then back again, I let things run.
Surprisingly,the drift was pulled back in again after an hour or so.
However the drifts were not large in the first place.

Build 1 - very similar I'm afraid, not a lot in it. However I couldn't use it much because it had the dreaded'' Channel change to a blank screen'' from the very very early builds?

So out of the two build 2 seemed more reliable - but it still drifted and then would pull back in again.

You have to laugh though, I am now back with Millhouse helix build ( the latest ), and Live tv today had serious audio/video drift!

Time for a coffee.

Sorry I can't be more helpful but if you'd like to throw me another build I'll try it.

Cheers

pootler