H265+ play video

[ktatar156]

zmNinjaNg version and build number

1.1.15

Platform

iOS

OS / browser version

Android 14

Device

No response

ZoneMinder version

1.38

Event Server (ES) version

No response

zm_detect version

No response

Describe the bug

Hello,

I have setup X streams for 2K H265+ recording and X substreams with low resolution for live preview only.
I think that you should allow to play H265+ video - for now, I can see only black screen (but what is strange, on event's list, I can see thumbnails of H265+ videos).

Steps to reproduce

Try to stream H265+ recorded event.
Video does not play.

Expected behavior

Videos plays.

Screenshots / logs

No response

Additional context

No response

[pliablepixels]

The thumbnails are rendered via ZM's index.php and are an image, so it works.
Are you able to play H265 on Android on its chrome browser? (not desktop)

[ktatar156]

Yes, I'm able to play it even on Android on its Firefox browser.

[pliablepixels]

Are you able to play it on Android and Chrome?

[ktatar156]

Yes

[pliablepixels]

I might not be able to support it - a full device browser has different capabilities from the embedded webview zmNinjaNg uses - that doesn't carry H265 decoding. However, I can give it a shot if you are able to give me access to an instance that has a H265 setup so I can test. If you are able to, please send to pliablepixels at gmail.

[ktatar156]

I cannot provide access to my camera due to privacy reasons :)

Maybe, in the app you should introduce some changes into the source code?
extend the CODECS array in video-rtc.js to include additional H.265 codec profiles (hvc1.1.2.L93.B0, hev1.1.2.L93.B0) - now there is only one Chromecast-specific profile H265
add a WebView detection helper and fallback logic that includes H.265 codecs in the MSE negotiation even when MediaSource.isTypeSupported() returns false
wrap the addSourceBuffer() call in a try-catch to gracefully fall back to H.264 if the HEVC MIME type is rejected, preventing playback failures.

[pliablepixels]

I can't introduce changes without testing. Video-rtc.js is a 3rd party file and I don't believe just adding them to the negotiation list will be all - the core issue is whether the webview has access to the platform H265 codec. Maybe you can try making these changes you are suggesting to the source and test it on your instance, if that is possible?

[ktatar156]

Sure, I understand your point of view, unfortunately, it's not possible for me to test this....
So we should wait for someone who will find a solution for this :)

[pliablepixels]

As it turns out, some H265 videos play (I tested on Isaac's servers some of which are 265). This seems to be likely a combination of plaform/device + profile of codec + support of an embedded webview for them. Not something I can test/implement myself w/o access to the right combination. I'll keep this open for now and see where it lands in the future and then take a call on keeping it open or closing it.