Closed QueenLinuxGlitch closed 11 months ago
Oh I see what you mean now. Hmm video play detection works almost instantly for me. I have two thoughts:
For reference, here's how quickly streams get found in my case. I've only tested with macOS and Linux so far so that may be the difference here.
https://github.com/gabe565/CastSponsorSkip/assets/7717888/1ad520d1-361d-447a-9b1a-3fbab3cd64bf
So in my case, here's my full breakdown. a Chromecast Ultra w/ Google TV running Android 12, and I am not actually casting, I am playing the videos through the app loaded onto my chromecast, so that may be a difference there. As mentioned before, the two relevant devices are ethernet-ed in. Hoping that helps give context
Thanks! Hmm so I only ever cast. I'll see if it behaves similarly for me if I start a video directly on the device!
Just updated, will report results later, that is so interesting, but makes a lot of sense, as I was usually pulling long videos that would not buffer immediately
Probably unrelated, but what does it mean when "Failed to find video on Youtube", "Search returned no videos", was just on a video with sponsor and that was in the log immediately.
In another instance, i got the above error, but then it immediately resolved correctly
2023/08/28 22:16:43 INFO Video ID not found. Searching for video on YouTube... device="Living Room TV" 2023/08/28 22:16:44 ERROR Failed to find video on YouTube. device="Living Room TV" error="search returned no videos" 2023/08/28 22:16:46 INFO Video ID not found. Searching for video on YouTube... device="Living Room TV" 2023/08/28 22:16:46 INFO Detected video stream. device="Living Room TV" video_id=Fio7yA44Amc 2023/08/28 22:16:46 INFO No segments found for video. device="Living Room TV" video_id=Fio7yA44Amc
Otherwise, detection is working immediately, so problem solved lol, but question above.
Interesting! Lol It's good to know the delays are fixed at least.
I'll do some more testing. I suspect that might have happened because it started looking for the video ID before the actual video was playing. Maybe due to buffering or an ad, but it tried to find the video ID with the YouTube API a couple of times before it was able to find the video data. I'll see what I can figure out, but hey at least it's working!
Indeed!
As of yesterday, no detections are occurring. Restarted the CLI multiple times, connects to both my cast devices immediately, but no youtube streams are being read anymore, I'll test more later, something must be up but I can't tell what.
EDIT: After using v4.0, still no change, although I really like the changes, assuming I can get them functional again.
EDIT 2: Neither through casting or launching through the youtube app are being detected from either of my casting devices.
EDIT 3: After a while, videos were being detected when I would cast from my phone, but not through normal play through app.
EDIT 4: All good, had to cast videos manually to both devices and restart them before they started registering, one of my Cast devices started not reacting to any casts
EDIT 5: Finally got it to work, only for youtube to say i've exceeded my quota. did not expect that one
Using new version, on advise to not change pause interval Both the device running the program (Windows 11 Laptop) and the YouTube-playing chromecast Ultra w/ Google TV (Using standard youtube app) are on ethernet. Still most of the time, the detection of the playback of a video doesn't occur until 30s-45s in, sometimes missing content at the beginning of the video