[CalebChambers]

Someone needs to make an app that only points to the YouTube website...
Having the option enabled to use YouTube URLs with default player still requires API keys for some reason... Any bot could go to the website YouTube and look at any video...
Google's obsession with "protecting privacy" Make no sense...


I wish Elon musk were just by Google already..

[bestboy]

Uh that's painful to read.

[DJ_Izumi]

I wish Elon musk were just by Google already..

This is a wildly backwards take.  Musk made it so Twitter could barely be viewed unless you're logged in.  You think he'd magically make YouTube access better?  He even cranked up API costs to basically drive out third party Twitter clients.

This is not a man who does 'Open accessibility'.

[MoojMidge]

@Luterin - both your issues are caused by the same thing - you are either not using any OAuth credentials or are trying to use OAuth credentials and/or sign in using a Google account that does not have a YouTube account associated with it. The snippet you have provided of a non-debug log is insufficient to provide any more assistance.

First and foremost, thank you for finally giving an explanation on the high cpu usage issue.

I already explained what the CPU usage was associated with, and it certainly is not "high" CPU usage:

It is not a bug, the CPU usage is a result of local stream requests being performed to workaround server blocks, that result in errors that InputStream.Adaptive can't handle, which prevent playback.

However you seem to have made a habit of ignoring the comments and advice directed at you while continuing to make uninformed/off-topic/pearl clutching comments in this thread. There is really no need for it, and it is quite unhelpful in the context of having to read and respond to all these other posts.

I am happy to provide assistance but please take the time to read and understand things before posting additional questions and comments. I have already answered all your other questions previously in my previous response to you. Take some time, go through it and try it, and if you are still having issues, then detail exactly what the problem is.

Is it possible to still sign out and still watch?  Because the stuff i watch in kodi does normally not affect the recommendations i get in the normal chrome youtube site... I would like to keep them seperate.

You can make a separate account for use in Kodi.

I wrote it in my case consecutively, without hyphens, without spaces, and even all in lowercase.
The hyphens are only meant for us humans to provide a better memory aid while typing and to avoid reading errors.
For this reason, the codes are presented in blocks that are separated by hyphens.

Yes, this is correct, anything will work as long as the case insensitive alpha-numeric input matches.

Yes, it is now required to provide a Google account in order to use API keys, as Google has recently started asking who belongs to its testers that have access to the Developer API keys.

This is not correct. You can still use an API key without an account, although you obviosly need an account to create an API key in the first place, anyone can use if afterwards if they know what it is.

The only change is that YouTube have for many months being trying to prevent the use of ad-blockers, 3rd party clients and downloading tools, or modified official clients.

In order to verify that you are a real user, you now need to sign in. There are other ways to get around this, but for Kodi, this is the simplest and most robust method.

They can now track in detail which account user is doing this.

Therefore, I recommend creating a separate Google account for using KODI in conjunction with the YouTube add-on.

They could always do this simply by tracking and blocking IP addresses which they are doing, but I agree that using a separate YouTube account is a good idea.


@arsMOBILIS - see how it works in the next beta version.


@CalebChambers - If you have something to discuss about this addon then feel free, otherwise you can share your thoughts about other topics somewhere else.


To everyone else - I will re-iterate that there is nothing wrong with using whatever alternative you want to use to watch YouTube videos, just don't clutter up this thread with those discussions. I will also repeat the following:

As the last comment about the use of alternative addons that are based on yt-dlp as an example - everyone is free to use whatever they want, but the reason people are also having problems with those other addons is because those addons suffer from exactly the same issue as this one (plus additional problems that remain unresolved in yt-dlp, but are resolved in this addon because of how this addon can act as a proxy to modify requests on the fly as you are streaming i.e. the cause of the higher CPU usage that you were complaining about).

If you get blocked using those addons the only way to get unblocked is significantly more difficult and inconvenient to resolve than simply having to login.

You have been warned, the choices are yours to make, and whatever people choose to use is is completely fine, just don't make it any more difficult to read through this thread.

[Bindou]

Thank you, thanks to your interventions, I managed to get my trailers back in working order.

When will there be a TMDB / FanartTV dedicated to trailers? It's nice to dream.

[jim_p]

@MoojMidge
Excuse me for not knowing how to multiquote single lines of text.

I already explained what the CPU usage was associated with, and it certainly is not "high" CPU usage

When you have a video playing with hardware decoding from the gpu, the cpu should be below 15% during the entire time the video plays. Right now, and only on youtube, one core is always at 100% while the video plays. The kernel's scheduler makes it so that the cpu usage is not on one core all the time so as to not fry it, and it moves it around the cores.
If the really high cpu usage, the high temperature it creates (you said you obsever a rise of 10oC in your low powered system) or the reduced battery life are not an issue for you, then I have no other way to convince you. I will add that neither mpv, which uses yt-dlp (and it also does a proxy as you say), nor youtube-viewr (which also uses the api tor scraping and mpv for playing) have such an issue. Everything works with hardware decoding and the cpu sits at <15% of usage.

This is not correct. You can still use an API key without an account,

You definitely can, if you only care about searches and the like and not playback. Because the moment you will try to play something, it will play one or two videos, at most, and then you will get the "sign in to confirm you are not a bot" notification. Here, on the system that I have 7.2.0beta4, it plays exactly ZERO videos wiithout popping that notification. 

In other news, I think that my failed attempt from yesterday to add an account comes down to this: I had created my api keys with my credentials, but now I decided to use a throwaway account for logging in. Could that be a reason? If so, I have to make new ones with the throwaway account.
Also, the other addon, may use something extra, because my api_keys.json has that "developer" bit at the top

Code:

# cat api_keys.json
{
    "keys": {
        "developer": {},
        "personal": {
            "api_key": "(removed)",
            "client_id": "(removed)",
            "client_secret": "(removed)"
        }
    }
}

[kaminix]

Hi, it is going to take as long as it takes, but just out of curiosity, those who already had their own Api and credentials like myself and then applied for a brand new and different Api and credentials how long did it take for you to receive the verification from Youtube. I ask because two different times yesterday I had tried to sign in my device using the device codes and after entering the second set of codes I received a pop-ups. First pop up reads in big letters Access blocked: (project name) has not completed the Google verification process. In small letters (project name) has not completed the Google process. The app is currently being tested, and can only be accessed by developer-approved testers. If you think you should have access contact the developer. If you are a developer of (project name) see 'error details'. Error 403 access_denied.
When I click on 'error details' it show a second pop up 'Error 403: access-denied: Request details: access_type=offline dfi=(shows an Api key that is not my new Api key) response_type=none pageld=none prompt=consent client_id=(my correct client ID) .apps.googleusercontent.com scope=https://googleapis.com/usth/youtube flowName=GenerlOAuthflow.
Can anyone decipher this info and explain to me what I have done wrong getting my newer Api Keys? Thanks much

[kaminix]

This is in reference to my last posting about the 403 error while trying to enter Device codes. Currently my Api Publishing status is only set to 'testing' should it be set this way? And if not how do I change it to the correct setting. Thank you

[otinley]

@kaminix

There is nothing to wait for.
The errors you are getting are because something is amiss or you did not register the app twice.

First, create an API which will give you the 1st field needed,

Second,  create an OAuth 2.0 Client IDs which will give you two fields:
- Client ID.  You need to strip .apps.googleusercontent.com from the clientID if present.
- Secret key. 

Please check linked image. (download or open image for full size)
With those 3 fields go back to Kodi and add them to the YouTube addon settings,
Then 
You will have to sign in and register your device twice.
"The second time you Connect a device, you will be prompted with:
This app isn't verified This app hasn't been verified by Google yet. Only proceed if you know and trust the developer.
From there clicking Advanced and Go to <your project name> (unsafe) allows you to complete the process."

https://imgur.com/a/api-V9Op7GL

[kaminix]

@kaminix

There is nothing to wait for.
The errors you are getting are because something is amiss or you did not register the app twice.

First, create an API which will give you the 1st field needed,

Second,  create an OAuth 2.0 Client IDs which will give you two fields:
- Client ID.  You need to strip .apps.googleusercontent.com from the clientID if present.
- Secret key. 

Please check linked image. (download or open image for full size)
With those 3 fields go back to Kodi and add them to the YouTube addon settings,
Then 
You will have to sign in and register your device twice.
"The second time you Connect a device, you will be prompted with:
This app isn't verified This app hasn't been verified by Google yet. Only proceed if you know and trust the developer.
From there clicking Advanced and Go to <your project name> (unsafe) allows you to complete the process."

https://imgur.com/a/api-V9Op7GL

Thanks for the reply otinley, yes the 3 fields have been installed into the App like always and they show up in the Apps settings so that is not the issue and signing in the first time is excepted and shows my project name and the second time I enter the connect a device code I get the message "The app is currently being tested, and can only be accessed by developer-approved testers." I do not get a chance to: "From there clicking Advanced and Go to <your project name> (unsafe) allows you to complete the process." as stated in your last line. Something is off with that "being tested" statement. Thanks again but it looks like I'll have to keep trying. Somewhere along the ways I read that under the testing it needs to be published but I don't think I should do that....anyways thanks

[otinley]

Good luck kaminix .

[kaminix]

Good luck kaminix .

Thank you

[mcarni]

@kaminix

There is nothing to wait for.
The errors you are getting are because something is amiss or you did not register the app twice.

First, create an API which will give you the 1st field needed,

Second,  create an OAuth 2.0 Client IDs which will give you two fields:
- Client ID.  You need to strip .apps.googleusercontent.com from the clientID if present.
- Secret key. 

Please check linked image. (download or open image for full size)
With those 3 fields go back to Kodi and add them to the YouTube addon settings,
Then 
You will have to sign in and register your device twice.
"The second time you Connect a device, you will be prompted with:
This app isn't verified This app hasn't been verified by Google yet. Only proceed if you know and trust the developer.
From there clicking Advanced and Go to <your project name> (unsafe) allows you to complete the process."

https://imgur.com/a/api-V9Op7GL

Thanks for the reply otinley, yes the 3 fields have been installed into the App like always and they show up in the Apps settings so that is not the issue and signing in the first time is excepted and shows my project name and the second time I enter the connect a device code I get the message "The app is currently being tested, and can only be accessed by developer-approved testers." I do not get a chance to: "From there clicking Advanced and Go to <your project name> (unsafe) allows you to complete the process." as stated in your last line. Something is off with that "being tested" statement. Thanks again but it looks like I'll have to keep trying. Somewhere along the ways I read that under the testing it needs to be published but I don't think I should do that....anyways thanks

@kaminix, maybe i stumbled upon the same thing, i am not sure 100% but it might be worth a try, it has to do with the new layout of one of the pages....
please try to check on your google developer console page
you have on the left a "Oauth consent page" tab
there you have a "pusblishing status"
i believe as default it is set for "TEST", you can click on it and turn it into "PRODUCTION"
try to see if setting the status to production helps

PS. wording might be slightly different, my page is not set in english and the above is my rough translation
PPS. I can take some print screen if you cannot find what i am referring to

I hope this helps
M

[otinley]

You are right @mcarni,
This is one step I had forgotten about and I do not think it's in any doc since the new layout differs from what was published.

[kaminix]

@kaminix

There is nothing to wait for.
The errors you are getting are because something is amiss or you did not register the app twice.

First, create an API which will give you the 1st field needed,

Second,  create an OAuth 2.0 Client IDs which will give you two fields:
- Client ID.  You need to strip .apps.googleusercontent.com from the clientID if present.
- Secret key. 

Please check linked image. (download or open image for full size)
With those 3 fields go back to Kodi and add them to the YouTube addon settings,
Then 
You will have to sign in and register your device twice.
"The second time you Connect a device, you will be prompted with:
This app isn't verified This app hasn't been verified by Google yet. Only proceed if you know and trust the developer.
From there clicking Advanced and Go to <your project name> (unsafe) allows you to complete the process."

https://imgur.com/a/api-V9Op7GL

Thanks for the reply otinley, yes the 3 fields have been installed into the App like always and they show up in the Apps settings so that is not the issue and signing in the first time is excepted and shows my project name and the second time I enter the connect a device code I get the message "The app is currently being tested, and can only be accessed by developer-approved testers." I do not get a chance to: "From there clicking Advanced and Go to <your project name> (unsafe) allows you to complete the process." as stated in your last line. Something is off with that "being tested" statement. Thanks again but it looks like I'll have to keep trying. Somewhere along the ways I read that under the testing it needs to be published but I don't think I should do that....anyways thanks

@kaminix, maybe i stumbled upon the same thing, i am not sure 100% but it might be worth a try, it has to do with the new layout of one of the pages....
please try to check on your google developer console page
you have on the left a "Oauth consent page" tab
there you have a "pusblishing status"
i believe as default it is set for "TEST", you can click on it and turn it into "PRODUCTION"
try to see if setting the status to production helps

PS. wording might be slightly different, my page is not set in english and the above is my rough translation
PPS. I can take some print screen if you cannot find what i am referring to

I hope this helps
M

Thanks macarni I think I went in and did that because it is showing 'In Production' and I was able to get this one device to sign in and it is now working completely. Now I am trying to sign in to a second device in another room and I am only able to sign in the once and it automatically goes to what you would normally see in the second device code entry so when I go back to the youtube app to see the second device code it does not show it like it did for my first Android and there is no 'sign in' icon only a 'sign out' icon so the app doesn't work because it doesn't have the second device code entered. It thinks I am signed in but doesn't have the second code. Very strange indeed.