You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 21, 2023. It is now read-only.
I installed sponsorblockcast manually and get the following error;
/usr/bin/sponsorblockcast: 33: cannot open .segments: No such file
not sure what I'm doing wrong here?
I would love to get this to work! any steps I can take to debug this?
I'm casting to a Shield TV and this script is running on a Ubuntu Server 20 box.
I saw this commit, I'm already running that latest change (just installed this last week); eb629e4
The text was updated successfully, but these errors were encountered:
Might be a way to use the API to retrieve the video id by searching the title/artist.
I'm not well versed in bash scripting, otherwise I would give it a try myself.
Although this would be a bit of fuzzy logic (what if video with same title for example, not sure if tou can search on artist with the api), and not foolproof, so not sure if that's something to even consider.
I'm getting the same error when playing on a Chromecast with Google TV (4th gen) because go-chromecast doesn't return the youtube ContentID. This obviously breaks sponsorblock implementations which require it. Not sure if this is hardware dependent or something that Google has recently broken in the backend.
Related issues: vishen/go-chromecast/#112, erdnaxeli/castblock#24.
I installed sponsorblockcast manually and get the following error;
/usr/bin/sponsorblockcast: 33: cannot open .segments: No such file
not sure what I'm doing wrong here?
I would love to get this to work! any steps I can take to debug this?
I'm casting to a Shield TV and this script is running on a Ubuntu Server 20 box.
I saw this commit, I'm already running that latest change (just installed this last week);
eb629e4
The text was updated successfully, but these errors were encountered: