You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that some Live TV M3U channels aren't being direct played in the native Android app but they are in the web client (also on Android).
I think I found the reason: The h264 codec profiles in the native Android app require (by default) a VideoProfile and VideoLevel to be defined but the web client treats them as optional by explicitly setting IsRequired to false. The end result is that direct play is disallowed by the native Android app when the device profile doesn't specify a video level or profile but is allowed in the web client.
Is this an omission or oversight that should be corrected in the native Android app?
For example, here are the CodeProfile definitions for VideoProfile and VideoLevel in the web client. Note that IsRequired is explicitly set to false.
And here are the corresponding CodecProfile definitions in the native Android app. Note that IsRequired is not specified, which means it gets set to true by default on the server.
Should we add `IsRequired: "false"`` to the codec definitions in the native Android app to match what the web client does and allow more channels to be direct played?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I noticed that some Live TV M3U channels aren't being direct played in the native Android app but they are in the web client (also on Android).
I think I found the reason: The h264 codec profiles in the native Android app require (by default) a
VideoProfileandVideoLevelto be defined but the web client treats them as optional by explicitly settingIsRequiredtofalse. The end result is that direct play is disallowed by the native Android app when the device profile doesn't specify a video level or profile but is allowed in the web client.Is this an omission or oversight that should be corrected in the native Android app?
For example, here are the
CodeProfiledefinitions forVideoProfileandVideoLevelin the web client. Note thatIsRequiredis explicitly set tofalse.And here are the corresponding
CodecProfiledefinitions in the native Android app. Note thatIsRequiredis not specified, which means it gets set totrueby default on the server.Should we add `IsRequired: "false"`` to the codec definitions in the native Android app to match what the web client does and allow more channels to be direct played?
Beta Was this translation helpful? Give feedback.
All reactions