Paul Berberian

NOTE: I found out that I didn't at all understand the `swc` API (or even babeljs for that matter), so this PR is back to WIP until we know what...

For now closed in profit of #1435

Hi @TomaszKowalik, I think this is the known samsung issue we had countless times where we attempt to seek forward over an audio discontinuity but samsung silently seek-back to some...

Hi @TomaszKowalik, The problem appears to be a little different with the v4 here, as it's now the HTMLMediaElement's `readyState` which does not go further than `1`, which is generally...

OK thanks, so for the v4, I would more probably explore DRM issues. Is it the same content in both tests? I see different bitrates in the logs. Is is...

Hi, For that second issue, nothing seems to be problematic from reading the logs sadly :/ Here also, I would first guess that this is DRM related, e.g. it could...

> I was experimenting with the reload method. It partially solved the problem: When... I was even thinking - just for the test for now - to just reload after...

OK :/ Maybe that's an issue with those TV models, Canal+ do not target those older 2017 Tizen models so I don't have enough data about them.

As discussed while drafting things after https://github.com/canalplus/rx-player/issues/1427 for what I would call support of "accidental multi-key responses" scenarios where the license server would respond with multiple keys despite a `keySystems[].singleLicensePer:...

I'm writing about a pretty rare scenario but now that I think of it, I don't see how the same cases couldn't arise in the other `singleLicensePer` scenario. We could...