1. No user installed addons are supported, python or otherwise.
2. No, they really are not supported.
3. They are not coming back
4. Read from 1. again
Any mention of illegal streaming sites, addons or any pirated material will not be tolerated. This is not democracy and any offenders will be banned and posts deleted immediately without warning.
Other than that, we hope you enjoy MrMC so far and we welcome any input and feedback you might have.
davilla wrote: 05 Apr 2018, 03:44
Heads up, the next TestFlight push will alter iOS/tvOS a/v sync. For me, I was running 150ms delay, now zero.
Do not use codec debug OSD to adjust a/v sync. Use test clips or actual video content.
Wait, how would one use the OSD to adjust sync??
Anyway, agree, the new testflight is better with regard to sync of 23.976 material. Perhaps even 0. Sometimes it seems a little delay is needed, then it seems to correct itself. Thanks!
While buffers are being filled and player is starting up, a/v sync might be changing. Depends on a lot of things. Generally after a few seconds, it should be in sync.
The codec debug OSD shows a dynamic value for a/v sync. The aim is zero but that's impossible as buffers are filling and draining. Before, one might have see +0.250 values there and assume a/v sync is off. While that value is related to a/v sync, only using your eyes and ears can tell if audio is in sync with video.
The problem with test patterns is they tend to use only one audio codec setup. A/V sync is very much effected by audio format and channels as this determines the audio output latency. That is how long from when an audio packet goes into sink to when it it hits your ears
davilla wrote: 05 Apr 2018, 16:44
The problem with test patterns is they tend to use only one audio codec setup. A/V sync is very much effected by audio format and channels as this determines the audio output latency. That is how long from when an audio packet goes into sink to when it it hits your ears
That's why you have test patterns with different audio codecs. You may end up having to use different offsets for each codec. That's just the way it will be.
