Open kumarashu123 opened 1 week ago
Please check against the latest development branch (nightly build)
@dsilhavy Yes, i will give a try What changes or pull requests in the nightly version do you think could resolve this issue?
@dsilhavy Yes, i will give a try What changes or pull requests in the nightly version do you think could resolve this issue?
The filtering based on the device capabilities was improved. In addition, there are less calls to Sourcebuffer.changeType()
.
@dsilhavy I have checked against the latest development branch (nightly build) issue is seen.
Thanks for checking. We dont have the resources to debug issues on SmartTVs. You will need to examine yourself, it is probably a device or content issue. If you find a bug in dash.js please report it here and we can check your fix.
@dsilhavy Is abr setting movingAverageMethod removed in development branch (nightly build)?
What is the best streaming configuration for smart tv?
there is a detailed documentation about the abr options in v5 (nightly build) here: https://dashif.org/dash.js/pages/advanced/abr/
we dont have a recommendation for a smart tv config. adjusting the buffer targets is something application providers typically do on smart tvs.
@dsilhavy There is one observation when Full HD height="1080" width="1920" video profile is present in the manifest then only distorted issue is seen. when i remove video profile with Full HD height="1080" width="1920" issue is not seen. and if i keep only one profile with Full HD height="1080" width="1920" in this scenario also issue is not seen.
Below is sample AdaptationSet for video
`
`
Sounds like the device can not handle an upswitch from a Representation < 1080 to the Representation with 1080. Worst case, you need to prevent this upswitch by either filtering the 1080p track or limiting the maximum bitrate.
What you can also try is disabling fastSwitch
: https://reference.dashif.org/dash.js/nightly/samples/abr/fastswitch.html.
Some other things:
height
in your manifest is set to 1084 instead of 1080fastSwitch is disabled already. height in manifest i changed to 1080 does not observed any improvement.
@dsilhavy i have below AdaptationSet in my mpd. video track video7 scanType is interlaced and others are progressive does dash js version 4.7.2 can switch from interlaced to processive and vice and versa ?
`
`
dash.js will switch to the Representation with scanType="interlaced"
as we do not use the scanType
attribute in the code. However, trying to play an interlaced video on a SmartTV will probably cause issues.
Environment
LG 2023 firmware 03.31.82
Steps to reproduce
I have below abr config abr: { movingAverageMethod: 'ewma', bandwidthSafetyFactor: 0.7, },
Note : when i disable abr autoSwitchBitrate: {audio: false, video: false}, issue is not seen
Play any VOD content and perform seek or subtitle change
Observed behavior
Describe what the player is doing that is unexpected or undesired behaviour.
distorted video is seen.
https://github.com/user-attachments/assets/45bb34df-5b4f-4923-9280-88051fbc9543
Console output
Expected behavior
Playback should be smooth