[jonboyp1976]

Thanks. Upgrading to 7.1.0.1 has fixed it. I did try to update from within Kodi (the official repo) but that wouldn't offer anything higher than 7.0.9.2.

Thanks again!

[jim_p]

I have the same problem as jonboy1976, but I am already on 7.1.0.1 (for leia though, installed manually), which is the current stable provided by github. Shall I try the beta too? If you want a log from a python3 version of kodi, I can do it on Sunday morning (or Saturday afternoon at best). My other kodi installation, which uses python3, is still on 7.0.x that the main repo has.

[JNRW]

I have the same problem as jonboy1976, but I am already on 7.1.0.1 (for leia though, installed manually), which is the current stable provided by github. Shall I try the beta too? If you want a log from a python3 version of kodi, I can do it on Sunday morning (or Saturday afternoon at best). My other kodi installation, which uses python3, is still on 7.0.x that the main repo has.

I recommend you should always install the latest beta from GitHub. The work undertaken by the developers is prodigious and deserves being put to use asap. Some time ago I had particular problems with live YouTube streams and I can say with every passing beta there was a noticeable improvement. I am a very happy user of the Kodi/YouTube addon.

[kadeschs]

As much as this addon requires updating to keep it working, why doesn't KODI just automatically update the clearly broken addon to the latest stable version?  The amount of time it takes to jump on a computer to go figure out what's going on and find the latest version to manually install is kind of annoying. To go official or not to go official.  To go beta or to go stable.  Seems like a lot of horsing around.  If 7.0.9.2 in KODI repository is broken and 7.1.0.1 is the latest stable version out, automatically update to it.  The biggest complaint I see all over Reddit about KODI is that it's difficult to configure and setup, esp. the addons.  I just think there should be a better more seemless approach to all of this.

[izprtxqkft]

As much as this addon requires updating to keep it working, why doesn't KODI just automatically update the clearly broken addon to the latest stable version?

it requires the developer adding an updated version to the kodi repo, if they don't then kodi doesn't even know there is an updated version and doesn't have the files to deliver said version
 

The biggest complaint I see all over Reddit about KODI is that it's difficult to configure and setup, esp. the addons.  I just think there should be a better more seemless approach to all of this.

same story here, if the developer submits a version to the kodi repo then kodi can deliver it
- if users are having issues with addons not in the kodi repo then developers should add them to the repo
- if these are addons not allowed in the kodi repo then that's their problem and users suffer installing these addons which probably shouldn't be installed in the first place

-----

none of these are a reflection of Kodi as Kodi operates perfectly fine with updating addons it has in it's repo

[jim_p]

Some random thoughts of mine that I want to share, because I will go afk tomorrow and I don't know when I will be back.

Installing the latest beta everytime, which for most people means manually updating, is not practical, because one has to constantly keep an eye on this thread here and on github. And if the addon version on the main repo does not work anymore, it should be marked as broken.

Yes, tha addon has improved since the first days of 7.0.x and the devs deserve a lot of respect for keeping it up to date. The ones to blame for any issues are the devs of the youtube api for all the unneeded changes every now and then. For the record, I had an old youtube 6.8.x installation on a system running kodi 18 and it was working with no issues until a couple of weeks ago, until it could no longer retrieve any search results from the api!

One other area that the addon's devs are not to blame, but the api's devs are is the tedious procedure to get the api keys. Most users (not me) would not mind just putting their google account credentials there and be done with it. Kodi is not hard to set up, if you do not want to set up every tiny detail in it, addons like youtube are.

[MoojMidge]

I have the same problem as jonboy1976

If you have this same exact same problem, then v7.1.0.1 probably won't fix it. A new stable release v7.1.1 is available which should.

@JNRW - thanks for the kind words
 

If 7.0.9.2 in KODI repository is broken and 7.1.0.1 is the latest stable version out, automatically update to it.

Installing the latest beta everytime, which for most people means manually updating, is not practical, because one has to constantly keep an eye on this thread here and on github. And if the addon version on the main repo does not work anymore, it should be marked as broken.

v7.0.9.2 is not broken, but if it hasn't been setup correctly then it likely won't work anymore. v7.1.0.1 and now v7.1.1 addresses this but is not yet available in the official Kodi addon repository.

It takes time for the addon repository to be updated, based largely on the time people can volunteer to reviewing updates to ensure that they can be safely rolled out to the entire Kodi userbase.

The beta versions are made available so that people can help with testing and but reporting, and are not intended for normal usage, but can be used if people don't mind the odd hiccup.

The unfortunate reality is that most people don't provide enough information to actually resolve issues that they encounter, so I am forced to suggest that the beta versions be installed on the chance that whatever issue someone may be having has already been resolved.

If you have a problem with updating manually then there are a number of options available to you if you have a look at the addon wiki: https://github.com/anxdpanic/plugin.vide...stallation

Latest stable version:
https://github.com/anxdpanic/plugin.vide...tag/v7.1.1

[doko-desuka]

It looks like the MediaConnect client now always requires OAuth (a YT user login) to work: https://github.com/yt-dlp/yt-dlp/issues/...2476783658
If you're logged in to the add-on then it should still work, but I got a 403 Forbidden on some video... will have to test some more.

[nycguy]

Ok Im little confused,  for issues should I be on 7.1.1+beta.6 or the stable thats linked above 7.1.1
Thanks

[jim_p]

It looks like the MediaConnect client now always requires OAuth (a YT user login) to work: https://github.com/yt-dlp/yt-dlp/issues/...2476783658
If you're logged in to the add-on then it should still work, but I got a 403 Forbidden on some video... will have to test some more.

I just logged in to write that bit. Even 7.1.1 stable failed to run here and pops this error. The error was similar on the previous stable, it just had some python errors too.
https://pastebin.com/ZCeRuhNa

Then I read the comment mentioned above on the issue of yt-dlp and now I am sure that the idiots of youtube broke it on purpose. I am not logged in on the addon, I never was and I will never be, especially if its devs keep doing such bs. However, enabling inputstream adaptive under the advanced section fixed it for me and it works without being logged in. I hope it helps someone

[splatterpop]

I switched to plugin.video.youtube-7.1.1+unofficial.1 today, after getting 403 messages.

With Inputstreamadeaptive enabled, videos will play, but the reported video+audio dropout after 3 sec is back. Also the application seems to have difficulty to exit cleanly.
https://paste.kodi.tv/mizezohiwu.kodi

With Inputstreamadaptive disabled, videos will not play, and the application will exiit cleanly.
https://paste.kodi.tv/oxanokurip.kodi

[MoojMidge]

It looks like the MediaConnect client now always requires OAuth (a YT user login) to work: https://github.com/yt-dlp/yt-dlp/issues/...2476783658
If you're logged in to the add-on then it should still work, but I got a 403 Forbidden on some video... will have to test some more.

Not sure that is exactly correct. Current versions of the addon remove the login for the YouTube TV OAuth authorisation, as they can no longer be used for accessing the YouTube Data v3 API.

Now there is only the personal OAuth authorisation, however a number of the player clients will not work with this and have also been disabled. If you are getting 403 errors then it may mean that that the MEDIA_CONNECT_FRONTEND client also won't work with personal authorisation tokens.

I have added these back in, along with some logic to use specific authorisation tokens if they are available:
https://github.com/MoojMidge/plugin.vide...master.zip

Are you able to test this after logging out, and logging back in? Will need to go through the two logins again.

Also what was the issue you were having with using InputStream.Adaptive? It is likely that the availability of these progressive streams will be further restricted in the future.


@nycguy - try the latest stable version:
https://github.com/anxdpanic/plugin.vide...g/v7.1.1.1


@jim_p - as mentioned previously the problems you were having with v7.0.9.2 was simply because you had not configured the addon correctly, and it was the same issue you were having before enabling InputStream.Adaptive. The addon has a Setup Wizard to help people configure it correctly, using it will avoid a lot of problems.
 

With Inputstreamadeaptive enabled, videos will play, but the reported video+audio dropout after 3 sec is back.

This is normal and I have explained what causes this to you previously.

Also the application seems to have difficulty to exit cleanly.

Can you try v7.1.1.1 and see if there is any improvement?
https://github.com/anxdpanic/plugin.vide...g/v7.1.1.1

With Inputstreamadaptive disabled, videos will not play

That is because you have disabled the only method to play the available streams. Don't do this.

[nycguy]

Thank you MoojMidge

[doko-desuka]

Not sure that is exactly correct. Current versions of the addon remove the login for the YouTube TV OAuth authorisation, as they can no longer be used for accessing the YouTube Data v3 API.

oh, I meant in the context of the YouTube API. Trying to get streams (like YT-DLP does) with that client and no Authorization header with the token, will return a "please login" error response.
If I find any problems I'll report back, but I haven't been finding any so far.

[dtechsrv]

The video durations are a bit weird in the Leia version:


This screenshot was taken yesterday from v7.1.1, but v7.1.1.1 is also affected.