[sat4all]

No - that has no relevance at all. Those delay is a constant offset, which was found by "experimenting", e.g. we asked approximately 100 users concerning their constant offset for specific samples we posted, we summed that up, removed the outliers and ended at 175 ms. It is not yet fully known where this is coming from. We know for sure that there are TVs out there that need more time when doing 24p / 23.9758 fps content - cause they do additional processing.

LipSync and stuff does not work at all on Linux. Only AMD has implemented it in their radeon drivers, but alsa does not make use of it.

Watch some samples and see if you hear sound after mouth moves or before and find your personal special value :-)

To add: this offset is only used for 24.0 / 23.9758 refreshrate.


Edit: We thought that Audio Engine (in frodo) was causing this problem and in deed Anssi found a problem in the old AE code, which is fixed in 12.3 (did not resolve all constant offsets) - when we rewrote a complete new AudioEngine for gotham, this problem was not "included" at all - so the "hw based offset" is still one that is part of the cause.

If you want to do it really write. You need drivers that use LipSync and Sound drivers that incorporate that information and application api that can use it for delay - which we don't have, none of that.

Simple Blurayplayers have that spec and use it though - which sucks in comparison.

Found it, finally!
It was my samsung tv auto motion plus setting it was set to clear which all reviews & pro calibrations recommande! switching it off solve the a/v sync case.
(wondering how fast motion scenes will look like now!!!)
edit: after all it seems impossible to keep AMP off, the picture look horrible.
my bad luck, got to decide between perfect sync and perfect picture.

thank you again, your comments was very helpful.