Error obtaining video/mp4 segment: Failed to execute 'btoa' on 'Window': The string to be encoded contains characters outside of the Latin1 range

Support
1

Hi All,

We have a stream that is playable on MediaElements.js (we are testing out migrating to Bitmovin for live streams and VODs).

When the player loads a certain source, the source is loaded successfully, however it just hangs and buffers. If I turn on logging we get the following error:


Error obtaining video/mp4 segment info DOMException: Failed to execute 'btoa' on 'Window': The string to be encoded contains characters outside of the Latin1 range.
    at e4.load (http://localhost:5173/node_modules/.vite/deps/bitmovin-player.js?v=6fee96fb:25920:427)
    at e4.load (http://localhost:5173/node_modules/.vite/deps/bitmovin-player.js?v=6fee96fb:26113:157)
    at e4.getDataSegment (http://localhost:5173/node_modules/.vite/deps/bitmovin-player.js?v=6fee96fb:26411:204)
    at e4.getSegment (http://localhost:5173/node_modules/.vite/deps/bitmovin-player.js?v=6fee96fb:26403:78)
    at e4.loadSegment (http://localhost:5173/node_modules/.vite/deps/bitmovin-player.js?v=6fee96fb:25019:102)
    at e4.loadFromSegmentInfo (http://localhost:5173/node_modules/.vite/deps/bitmovin-player.js?v=6fee96fb:25016:231)
    at http://localhost:5173/node_modules/.vite/deps/bitmovin-player.js?v=6fee96fb:24913:31

I have 2 issues:

  1. How do I catch this event so that the player can indicate to the user there is an issue, instead of the loading screen just looping. We’re having trouble catching some error events using the player.on("error… listener event or the player.on("warning… listener event (Framework: Vite + React JS)

  2. What could potentially be causing this issue? The difference between the 2 videos is, one was “Harvested” from the original stream, and the one that’s broken was converted from a MP4. They’re both HLS but that’s the difference between them - would this be the cause? And are there known workarounds in this case?

Thanks

2

Hi Ronan,
Thanks for reaching out to us.
Can you please share steps to reproduce the issue, as well as which player version you are using ?
Does it also happen on a simple player page such as the below ?

Thanks in advance for your feedback. I’m looking forward to investigating further