2014-02-27, 13:13
Remember: That setting makes only sense, if it is combined with Adjust Refreshrate to match video. It's quite stupid to Sync Playback to Display, when content has 24 or 23.9758 fps and Display is running at 60hz.
Edit:
Perhaps something to add. Passthrough sucks from a sync point of view :-) If video is not encoded properly, e.g. some frames missing from time to time, wrongly converted, so that video and audio slowly get out of sync, the only chance with passthrough is to "drop" or "duplicate" packages. Those packages are mostly of 32ms time and those are "raw" packages, just a bunch of data xbmc does not touch at all.
Syncing decoded streams e.g. dts or truehd or ac3 as lpcm (this conversion is lossless(!)) is much easier, as you can do a little bit of resampling to speed up or speed down without sacrificing the sync.Sadly there is no OSS DTS-HD Master audio decoder yet and the DTS-Core is used instead.
Out of that reason some people choose "Audio Clock" for sync. There we can skip, drop, resync video output which might give "visual stutter" but not audio artifacts.
Edit:
Perhaps something to add. Passthrough sucks from a sync point of view :-) If video is not encoded properly, e.g. some frames missing from time to time, wrongly converted, so that video and audio slowly get out of sync, the only chance with passthrough is to "drop" or "duplicate" packages. Those packages are mostly of 32ms time and those are "raw" packages, just a bunch of data xbmc does not touch at all.
Syncing decoded streams e.g. dts or truehd or ac3 as lpcm (this conversion is lossless(!)) is much easier, as you can do a little bit of resampling to speed up or speed down without sacrificing the sync.Sadly there is no OSS DTS-HD Master audio decoder yet and the DTS-Core is used instead.
Out of that reason some people choose "Audio Clock" for sync. There we can skip, drop, resync video output which might give "visual stutter" but not audio artifacts.
