[2.2.2] Incorrect date returned on HLS live streaming's #EXT-X-PROGRAM-DATE-TIME through mediaPlayer.Control.GetProgramDateTime() API.

[kodai100]

Describe the issue Cannot get value of HLS live streaming's #EXT-X-PROGRAM-DATE-TIME through mediaPlayer.Control.GetProgramDateTime() API.

https://www.renderheads.com/content/docs/AVProVideo/articles/feature-streaming.html In the document, clearly we can get a #EXT-X-PROGRAM-DATE-TIME tag value through mediaPlayer.Control.GetProgramDateTime() API.

Your Setup (please complete the following information):

• Unity version: Unity2021.1.24f1
• AVPro Video version (number and edition (trial/core/ultra/enterprise)): 2.2.2 Ultra
• Operating system version: Windows10 Home 19042.1288
• Device model: Intel Core i7-8700K, NVIDIA GeForce GTX 1080Ti
• any resolution (HLS streaming)

To Reproduce

1. Setup AWS IVS live stream and go live (AWS IVS can have #EXT-X-PROGRAM-DATE-TIME tags every segment)
2. Enter a m3u8 address to MediaPlayer
3. call mediaPlayer.Control.GetProgramDateTime(); and always returns initial value of DateTime type (0001/01/01 0:00:00).

Logs

void Update() {
    Debug.Log(mediaPlayer.Control.GetProgramDateTime());
    // always 0001/01/01 0:00:00
}

Screenshots Here is get a video stream of AWS IVS on AVProVideo MediaPlayer (logging 0001/01/01 0:00:00)

And here is AWS IVS's m3u8 index file (clearly included #EXT-X-PROGRAM-DATE-TIME tags)

Videos it will be reproduce any live streaming video.

Please DO NOT LINK / ATTACH YOUR PROJECT FILES HERE

Instead email the link to us unitysupport@renderheads.com

[AndrewRH]

Can you try switching the Video API to WinRT instead of the default Media Foundation?

Thanks,

[kodai100]

Thank you for your reply.

I switched the video API to WinRT and it seems to work!

However, the year parsing seems to be wrong like as follows. (2021 is expected, but displayed 2390)

this is unity's log

and this is AWS's m3u8 file detail

Thanks,

[AndrewRH]

OH that's interesting...we'll take a look

[AndrewRH]

Our date-time conversion calculate was off by 11644473600 seconds (approx 369 days) due to using the Windows NT epoch date 1601 instead of Unix epoch 1970.

This has now been fixed and will be in the next release.

Thanks for submitting this issue report.

[kodai100]

Thank you for your quick support !

[AndrewRH]

@kodai100 AVPro Video 2.2.4 has just been released and should resolve the issue you reported. Thanks,

[guerwan]

@AndrewRH we have the same issue on macOS/iOS with the latest version (2.6.3): Issue