Unclear which build to use for CE varients (CPM, avdvplus, P3i) + possible audio sync setting bug

[avrignaud]

Been exploring different CPM varients, and recently am using the new P3i CE T1 version. Installed v1.5 of Audio Offset Manager, and I seem to be able to set audio delay in increments of .5 (which is fantastic), but it never sticks. Only seems to automatically stick if I do a varient of .250. So, am not sure if this is a bug with 1.5, whether 1.6b3 is appropriate and fixes, and in general, what version of AOM to use? Apologies if this isn't the best place for bugs/discussion - I don't see anywhere else here on Github, and the Kodi thread of AOM appears to be dead. Thank you!

[matthane]

Hello, the audio increment mismatch is unfortunately something that I can't account for on the addon side, exclusively. It requires both the addon and the Kodi build to support the same smaller increment steps. For example, if you use the CPM variant of AOM, it supports the smaller increments of 5ms but if p3i doesn't have support for 5ms increments within Kodi itself, it won't stick. Kodi only allows 25ms increments by default. CPM's older A14 build supported the smaller increments, but I don't know if p3i kept those commits.

I'm also using the p3i build now, but I don't have to use AOM with it because it seems in combination with p3i + PM4K I don't have the same audio issues I had when I created this addon. But, the regular package (either 1.5 or 1.6b3 non CPM versions) is configured with 25ms offsets while the CPM labeled package are 5ms.

[avrignaud]

Gotcha, I asked Panni whether or not he plans to support the 5ms increments on his Discord thread. Do you plan to release a 1.6 final anytime soon? I do think p3i + PM4K seem to be much better in terms of audio sync delay issues, but it appears I still need to dial in some fixes to account for latency in my theater device chain. Thanks again!

[matthane]

I'll reply here in addition to our conversation elsewhere, for posterity in case anyone else reads this:

I've tested and confirmed that p3i supports 5ms increments, so using the "CPM" labeled packages of AOM will ensure that audio offset changes stick. The difference between 1.6 and 1.5 is exclusively related to PM4K compatibility, so there are no gained or lost features between the versions. I'm hesitant to push 1.6 because of some extensive changes and workaround implementations that I'm not quite pleased with yet, but if it works, it works.