Video with fragments break after 11~ seconds #104
Comments
|
is that kodi 21/22? because i'm still on 20... |
|
I've amended my original message to include version numbers for both devices that I can reproduce the issue on. Happens on both v20 and v21, though. I haven't tested on v22! |
|
so i just tried the ltt vid it works with no problem here. can you humor me and try starting kodi (the 20 one) with it is consistent that it doesn't work with dash on browser and not on kodi either because the plugin uses dash manifests to play the video, this points maybe to a configuration problem with your instance... in fact i wasn't aware that there was any other way to play the vids from invidious than dash |
|
what you can also try to see if it really is a instance problem is trying to play it from yt (context menu) because the the source for the dash manifest is different... |
|
Hi! Yep, I'm pretty sure I'm suffering from the same issue. I am:
I've got some logs attached. Like @SethFalco, I see a whole bunch of 403, but what really jumps out to me are the I installed a whole bunch of encoder packages from Archlinux because I didn't know any better; nothing helped: I have tried changing the Audio output to my expected HDMI sink but it didn't make a difference. I searched online for these "large audio sync error" messages, but without luck so far. Am a little clueless. Any chance you've had better luck with this? Thank you for the project by the way 🙏 |
|
Oh, attaching the logs is better. |
|
I'm experiencing the same since a couple of days... investigating |
|
there are 2 things:
Now, the sad truth is, given the lack of public instance supporting the json api, i cannot test anything anymore, it seems to me that this addon is going the way of the dodo... |
|
Hey @lekma , thanks for looking into this. The extinction of the dodo was a sad event indeed. I don't have access to my Kodi being at work now, so I'll try your first suggestion later and let you know if that improves it.
What's jumping out to me is how my local Invidious instance is stable and working, and pretty much up-to-date as well. This kinda tells me that upstream is fine, so I'm not sure I understand why this addon should be doomed! I could potentially provide a public instance for you to have a play/test with? If you let me know your favourite DM contact we can have a chat on this. |
i think the problem is iv is prioritizing their html interface over their json api, and again i can't test anything anymore because no public instances available (I'm open to transfer the repo to someone who has a private instance and can do the work)
lekma at duck dot com |
|
@lekma I had actually emailed you via the email address attached to your git authorship already. Do you have access to that one, or shall I pester you via the email you sent above instead? (i.e. I had done |
|
I just saw that, responding right now |
|
Hey @lekma, I know you folks are mailing with @SethFalco but I just mailed you with a public instance URL in case that's helpful (maybe check your junk folder) |
|
do you guys run inv_sig_helper? |
|
Yes I do.
14 Jan 2025 16:51:36 lekma ***@***.***>:
…
do you guys run
inv_sig_helper[https://docs.invidious.io/installation/#run-inv_sig_helper-in-background]?
—
Reply to this email directly, view it on
GitHub[#104 (comment)],
or
unsubscribe[https://github.com/notifications/unsubscribe-auth/AEVJ2GUWUASIROU4DAEP4TD2KU6BNAVCNFSM6AAAAABQIXIVXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJQGUZTSMZZHA].
You are receiving this because you commented.
[Tracking
image][https://github.com/notifications/beacon/AEVJ2GRWBVR2AZWM7GPSQWD2KU6BNA5CNFSM6AAAAABQIXIVXWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTU2NB7IM.gif]
|
So I tried that without success I'm afraid. Kodi seems to be picking up Alsa correctly from the logs. I also tried changing audio outputs to the expected output instead of the default one but that didn't help. Note that I'm using Also, I got a warning that Attached some logs. Hope that helps 🙏 |
Scratch that; even though that's the command I found in |
|
@czardien: i may have been unclear, the "large audio sync error" errors you're seeing after the http 403 errors are due to those. |
|
Hey @lekma, gotcha thank you! I haven't had time to dive deeper into this but I'll probably do some more digging in my Invidious setup next and see what knobs I can tweak. |
I'm running with a fresh self-hosted instance of Invidious. It's working fine on my browser, unless I enable DASH which screws things up for some reason with network errors.
However, videos work on browser, they don't work in Kodi for some reason. 🤔
Do you have any thoughts on if this might be related to the Kodi add-on, or to Invidious itself? I'm unsure as it works in browser which suggests Invidious should be fine, but can't find obvious problem with the add-on.
The issue appears to ultimately be that we're getting a 403 to
*.googlevideo.com. I can investigate this further if you're not sure either.Environments
This issue occurs on both:
Screenshots
Here, you can see that Invidious is working fine in my browser:
browser.webm
Here, you can see that Invidious doesn't work well on Kodi. When the video stops loading, it's playing a very loud/painful sound. (I think it's the last audio segment repeating rapidly?)
kodi.webm
Logs
Here are some logs if it helps. It's clear the issue is regarding video fragments, especially as this issue does not occur on videos that are 30 seconds long. (Presumably, they are not fragmented.)
I'll come back to you on any other reviews/comments you've left on my other PRs as soon as I have Invidious working on Kodi again!
The text was updated successfully, but these errors were encountered: