Hello, I am creating a player for DASH streaming.
I have already tested several samples from github and several feeds as well, and there is a format for the MPD that freezes my TV and forces a reboot.
Under the <Representation> tag, this sample content plays fine:
<Representation id="0" mimeType="video/mp4" codecs="avc1.64081f" bandwidth="900000" width="1280" height="720" frameRate="24/1"> <BaseURL>videoO.mp4</BaseURL> <SegmentBase indexRange="868-2951" timescale="15360"> <Initialization range="0-867"/> </SegmentBase> </Representation>
On the other hand, this code reboots my TV:
<Representation id="0" mimeType="video/mp4" codecs="avc1.64081f" bandwidth="900000" width="1280" height="720" frameRate="24/1"> <BaseURL>picta-video0-900000</BaseURL> <SegmentList timescale="1000000" duration="5000000" startNumber="1"> <Initialization range="0-810" /> <SegmentURL mediaRange="811-90824" /> <SegmentURL mediaRange="90825-434414" /> <SegmentURL mediaRange="434415-738807" /> </SegmentList> </Representation> <Representation id="1" mimeType="video/mp4" codecs="avc1.64081e" bandwidth="500000" width="854" height="480" frameRate="24/1"> <BaseURL>picta-video1-500000</BaseURL> <SegmentList timescale="1000000" duration="5000000" startNumber="1"> <Initialization range="0-810" /> <SegmentURL mediaRange="811-90824" /> <SegmentURL mediaRange="90825-434414" /> <SegmentURL mediaRange="434415-738807" /> </SegmentList> </Representation>
I believe that it could be something I am missing, BUT maybe it is something related to the system and I need to do a workaround.
I have tested the problematic feeds, because it all comes from a streaming site, here:
https://players.akamai.com/players/dashjs
and it plays without problem.
Here is a test URL for a feed if anyone wants to try it:
https://www.picta.cu/videos/5602a849e37e4ade905f3d00eaa3de1e/manifest.mpd
Please, point me in the right direction, because if it doesn't stream, then my work is worthless.
Thank you.
Do you get any errors in the telnet log?
When I play the mpd file correctly, the on ethat works, it shows:
We’re upgrading Roku Community to bring you a faster, more mobile-friendly experience. You may notice limited functionality or read-only access during this time. Read more here.
Planned Downtime:
Community will be unavailable for up to 24–48 hours during the upgrade window during the week of May 19th and you may notice reduced functionality.
In the meantime, for additional assistance, visit our Support Site.
We're sorry for this disruption — we’re excited to share what’s next!