Closed kaieberl closed 2 years ago
I pushed my version now to this repo. Since I didn't directly fork the repo, I cannot make a PR, but maybe you could have a look at my commits. Besides catching the error, I added compatibility with Python 3.8 (hope it still works with 3.9) and fixed other issues, e.g. pause between requests (else the server sometimes blocks you), the xpath in tum_live.py etc. I also disabled jump cutting and the semaphores because that threw some errors, please feel free to ignore that.
I experienced this as well (with panopto). Apparently I didn't even found a m3u8
in the page source. Maybe an alternative would be to use the pendant to the Network
-tab in the developer options of the browser.
We should be able to access the data via
logs = driver.get_log("performance")
json.loads(logs[i]["message"])["message"]["params"]["request"]["url"]
(and then searching for some master.m3u8
or index.m3u8
).
But we'd need something like capabilities["goog:loggingPrefs"] = {"performance": "ALL"} # chromedriver 75+
for the selenium setup.
Didn't test this again, just used this some time again (but the code wasn't pretty since not all elements of logs
consist of all the members used to extract the url)
EDIT: Oh your problem was with tum_live I see. Well I didn't check on that, but maybe checking the chrome log helps in this case as well.
The URL issue with TUM-live is fixed in the latest version. If this reoccurs, please open a new issue.
re.search(prefix + '(.+?)' + postfix, source)
does finds nothing for the source attached below. Will create a PR to at least catch the error.