-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new value for tolerance on playback duration #118
Comments
@jpiesing The current tolerance on the playback duration is 2 frames + 20ms as defined in test-config.json file.
Wording from spec: eg: for 25H which is 100ms and for 50H it is 60ms |
I may be missing something but that's for the observation about currentTime, not for the duration observation. vs Also that's not what it says in the test report .... |
Sorry @jpiesing completly my bad I was looking at wrong value. Indeed they were for current Time match.
Which are 0 frame with 20ms at the moment. |
@jpiesing @yanj-github we will collect the number from the test results and then we can calculate the default tolerance for duration |
@jpiesing and @louaybassbouss coming from the audio perspective this going to impact on audio as well.
#116 this issue I have same question as tx_mas shared for both video and audio. |
@yanj-github I don't have preferences regarding for audio and video tolerance and I am fine to apply for now the same tolerance to video and audio. |
I would not expect audio to have the same tolerance as video as the reasons for the tolerance are somewhat specific to video frame rate conversions, from the encoded frame rate of the content to the frame rate of the display (panel) and from that to the frame rate of the camera. |
Thanks @louaybassbouss and @jpiesing for the comments. |
See @jpiesing comments in his post at https://standards.cta.tech/wg/dpctf/mail/thread/46870 |
A new issue is opened for audio duration linked above. But not for maximum permitted start-up delay, I think it is better to leave tx_mas is shared for both video and audio. |
@FritzHeiden Please can test-config.json be changed to 50ms as agreed above. Once you've done this, please close the issue. |
Changed |
The current tolerance on the playback duration is 20ms.
This is 1/2 frame at 25Hz which seems too demanding given that errors accumulate between the video decoder, the panel, the camera and the OF.
I recommend it should be at least 40ms for 25Hz video but this needs to be validated by Fraunhofer from analysis of plugfest results.
The text was updated successfully, but these errors were encountered: