[izprtxqkft]

The second one does not appear in the list.

what's the video link?

[jim_p]

@jim_p - Yes, please advise what other strings are missing that you have noticed.

This will take a while, because I think most of the missing ones were related to the "live" label strings which were missing in 7.1.1.1 but were fixed in 7.1.1.3.

[jacen05]

Hello,

First, thanks to the plugin authors and all contributors.
I used this addon some months ago, but it doesn't work anymore in my case.
I was on version 7.0.9, so I first updated to latest version 7.1.1.3
I got an error

Code:

IAddonInstanceHandler::CreateInstance: inputstream.adaptive returned bad status "Permanent failure" during instance creation

.
The setting "Use InputStream.Adaptive" was on, I disabled it.
After that I got the error

Code:

Response:   {'error': {'code': 403, 'message': 'The caller does not have permission', 'errors': [{'message': 'The caller does not have permission', 'domain': 'global', 'reason': 'forbidden'}], 'status': 'PERMISSION_DENIED'}}

. Searching in this forum, only information found was that credentials were not properly set. I think they were correctly in my case (because I could play the videos in the past, and I still could access the "recommended" videos that is linked to my account), but to be sure I logged out, then did again the signin process mentionned here. This worked, I was able to access again my recommended videos, but same error happened when trying to play anything (tried several videos using several menus). I also tried playing video after logging out, no success. I also tried creating a new API key in Google console, configured it in Kodi, loggued in again, no success.

What else can I try?

[izprtxqkft]

The setting "Use InputStream.Adaptive" was on, I disabled it.

but same error happened when trying to play anything (tried several videos using several menus).

use of ISA is supposed to fix problems but you just disabled it
 

inputstream.adaptive returned bad status "Permanent failure" during instance creation

you need to fix this

see https://github.com/xbmc/inputstream.adaptive/issues/866
and the pertinent response is here https://github.com/xbmc/inputstream.adap...1002675624

[MoojMidge]

I assumed the issue was only present in the unofficial repo, but it showed up when installing the addon from the official testing repo as well.

I had a quick look through a few zip files and couldn't see the unofficial changes in the non-unofficial testing repo. What version did you see this in?
 

Addons shouldn't try and circumvent basic Kodi guidelines for addons and skins. The same applies to forced view types as well as hard-coded colour tags provided by an addon. That should be the skin's business really. 😊

I don't use the unofficial version myself, but I don't fully agree with this. The problem is that there is core Kodi functionality that does not work when using a video content-type. Selecting views is also problematic because of the dynamic nature of plugin URIs and the way that Kodi stores paths in its ViewModes db. There is also no standard way for addons to identify the purpose of various label parts so that skins can display them in a way that is appropriate to the context in which they are used while still styling them according to the aesthetic of the skin.

It is not ideal behaviour because there are limitations in the plugin API, but removing functionality when there are no alternative is not necessary imo, it does however require compromises in the addons, skins and core until someone comes up with a better way.

There's no chance of switching views with our skin anymore, if the content type has been manipulated. The amount of views we offer depends entirely on the content type - the reason for it being that we'd like to offer only view types useful for certain content types, not all of them at all times. If a wrong content type is being set by an addon, this will mess with the skin's intent.

Not an OSMC (skin) user, so don't know if this is not already the case, but perhaps there should be some common basic views shared among all content-types to avoid the inability to switch away from a bespoke view that may not be appropriate for the content available? While this addon does not primarily provide episodic content, there are actually shows and episodes available on YouTube. Similarly there are other plugins that do provide shows and episodes, however the infolabels that may be populated for the plugin listitems may not contain the same information as library content. I don't think it is appropriate to say that these plugins cannot use an episode content-type, and I think it is the role of a default skin to try to provide as much usability as possible for as many use cases as possible/reasonable. Just my 2c.

 

The reasoning is: "Since my device is slow in decoding VP9, if there are no playable H264 streams then at least try the smallest VP9 stream so it's watchable" -- because a 360 height VP9 can keep up with the audio and doesn't desync, at least on my device of course.

That makes some sense, but I'm not sure whether such a scenario could/would ever eventuate when using the custom MPEG-DASH manifests that this addon creates. Anyway added this: https://github.com/MoojMidge/plugin.vide...b47ecf676f

 

Soooo...anytime the Setup Wizard DOES pop up then we ARE supposed to run it? 

Generally, yes. The only time the Setup Wizard popup appears is when there are some default settings that need to be changed to allow the addon to work properly. At a rough guesstimate, more than 75% of issues that are reported could have been avoided by simply running the Setup Wizard, case in point - many of the response in this thread...

 

However, the add-on  ( 7.1.1.1 unofficial) only supports playing the first audio track. The second one does not appear in the list.

This addon has supported multiple audio track for almost (more than?) 2 years now. I make use of it all the time. Without knowing what video you are trying to play, or what list you are referring to, I can only presume that you are not using MPEG-DASH, which is why it doesn't work for you. Run the Setup Wizard and if you are still having problem provide a debug log.

 

What else can I try?

Restart your system/device as advised by @izprtxqkft, and run the Setup Wizard afterwards.

[jacen05]

The setting "Use InputStream.Adaptive" was on, I disabled it.

but same error happened when trying to play anything (tried several videos using several menus).

use of ISA is supposed to fix problems but you just disabled it
 

inputstream.adaptive returned bad status "Permanent failure" during instance creation

you need to fix this

see https://github.com/xbmc/inputstream.adaptive/issues/866
and the pertinent response is here https://github.com/xbmc/inputstream.adap...1002675624

Thanks @izprtxqkft and @MoojMidge for the quick answer, that was indeed the problem: I didn't rebooted the device after updating.
I did that, run the setup wizard again, that worked!

[Chillbo]

I had a quick look through a few zip files and couldn't see the unofficial changes in the non-unofficial testing repo. What version did you see this in?

Thank you for your extensive reply! Upon checking this again, it seems to me the issue was installing different versions of the addon over one another. If you uninstall and reinstall it, even keeping addon settings intact, it seems to work. So, probably an issue not with the addon, but with the way I switched between addon versions 😊
 

I don't use the unofficial version myself, but I don't fully agree with this. The problem is that there is core Kodi functionality that does not work when using a video content-type. Selecting views is also problematic because of the dynamic nature of plugin URIs and the way that Kodi stores paths in its ViewModes db. There is also no standard way for addons to identify the purpose of various label parts so that skins can display them in a way that is appropriate to the context in which they are used while still styling them according to the aesthetic of the skin.

It is not ideal behaviour because there are limitations in the plugin API, but removing functionality when there are no alternative is not necessary imo, it does however require compromises in the addons, skins and core until someone comes up with a better way.

I agree, compromises are necessary and the situation is not ideal. It's still evident that most of Kodi's skin related functionality is not made for addons in the first place.

From the skin side, I can provide a few examples why implementing a default override to usual Kodi behaviour is problematic:
 

• The OSMC Skin offers an override to one of the most annoying problems with addon views: any view change will only stick for one page the addon loads. This override lets users pick a view in the skin settings and force it for all video addon pages. This can only rely on the videos content type as it would otherwise also force views on library windows, etc.
  
• A skin either offer views only for poster fan art or more types of art, but it has to adjust either the art or the view to look proper: A view type that is made for horizontal thumbnails won't look good with vertical poster art - lots of whitespace being the consequence. The OSMC Skin is made to work primarily with poster fan art, but as video addons like the YouTube addon mostly don't offer that type of fan art, it offers a full set of specific views only for video addons, with adjusted spacing and use of info labels. If any content type other than videos is set, the appropriate views cannot be used anymore.
  
• A more minor issue, but one nonetheless: Wording built into the skin has to rely on hints as to what is currently shown on screen. Having a list of YouTube videos that don't happen to be episodes accompanied by an item counter saying "35 episodes" is somewhat strange 😅
  
• Some skins like the OSMC Skin try to use as little overlay textures as possible to ensure background fanart is not hidden while keeping skin elements like texts readable in the foreground. This makes it imperative to match colours of all sorts of items so not one is e.g. barely visible due to a colour match of text and background. If an addon mandates text colour by adding colour tags to the text it provides, this whole effort will be overridden - the addon can never know what a skinner had in mind and vice versa. Only one side should be responsible for colours IMHO.
  

 

Not an OSMC (skin) user, so don't know if this is not already the case, but perhaps there should be some common basic views shared among all content-types to avoid the inability to switch away from a bespoke view that may not be appropriate for the content available? While this addon does not primarily provide episodic content, there are actually shows and episodes available on YouTube. Similarly there are other plugins that do provide shows and episodes, however the infolabels that may be populated for the plugin listitems may not contain the same information as library content. I don't think it is appropriate to say that these plugins cannot use an episode content-type, and I think it is the role of a default skin to try to provide as much usability as possible for as many use cases as possible/reasonable. Just my 2c.

What comes to mind: Why set episodes as the content type, if not all content the addon offers is episodes? That's what the videos content type should cater to: different types of videos in one list. Forcing views made for episodes on all of them doesn't make sense IMHO.

But don't get me wrong... Obviously, views shouldn't be too limited, yes. And it should be possible to work around limitations (something one has to do as a skinner all the time - as the Kodi skin engine has substantial limitations). But an addon setting a content type not meant for an addon by default will lead to issues... A skinner has to decide what to rely on: Kodi guidelines and functionality or what single addons do differently. With the second approach, a skin has to basically be coded to work perfectly with one single addon - the next addon might approach this differently already leading to new issues.
The basis is that Kodi addon and skin guidelines mandate the appropriate content type to be set by an addon (music for music addons, videos for video addons, programs for other types of addons) and not force any view types by setting other content types: https://kodi.wiki/view/Add-on_rules#Requ...hon_addons

I do like customizability, especially if and when a system has undesirable limitations. But my 2 cents: overrides of default behaviour should only be optional, not the default. That's what I'm trying to get at 😊 The override of a content type as well as colour tags or forced view types should only be options for users to set.

I apologize for the novel of a reply I wrote 🙈

[graham-h]

Thanks for this excellent Add-on!! I've been getting random pop-ups asking 'Configure Settings?'  which I've been dismissing but the last time I decided to click Yes.  It seems this is from YouTube - maybe the name YouTube should be added to the dialog?

Anyway, after going through the questions and getting to the one about keeping search history I get an error and this in logs.
https://paste.kodi.tv/olimelenul.kodi

I upgraded from 7.0.6.3 to 7.1.1.3 and ran the wizard again, with the same error.  Is this the right place to report it?

[phyrros1]

Here are the links for two videos:

https://youtu.be/I1KqalXTA_Y?si=mG6FuV-SmQ0YyMAE
https://youtu.be/zPmazQ9OqIs?si=UAY7dyUUlaV5YGzG

[phyrros1]

The second one does not appear in the list.

what's the video link?

Here are the links for two videos:

https://youtu.be/I1KqalXTA_Y?si=mG6FuV-SmQ0YyMAE
https://youtu.be/zPmazQ9OqIs?si=UAY7dyUUlaV5YGzG

[phyrros1]

However, the add-on  ( 7.1.1.1 unofficial) only supports playing the first audio track. The second one does not appear in the list.

This addon has supported multiple audio track for almost (more than?) 2 years now. I make use of it all the time. Without knowing what video you are trying to play, or what list you are referring to, I can only presume that you are not using MPEG-DASH, which is why it doesn't work for you. Run the Setup Wizard and if you are still having problem provide a debug log.

I know that this add-on previously worked with multiple audio tracks. Its's only that it does not seem to work for me since I have installed 7.1.1.1.   I have enabled MPEG-DASH otherwise nothing would play at all - I would only get the UNKNOWN error message. As posted in my previous message here the links to two vids with this issue:


https://youtu.be/I1KqalXTA_Y?si=mG6FuV-SmQ0YyMAE
https://youtu.be/zPmazQ9OqIs?si=UAY7dyUUlaV5YGzG

[Shredder_guitar]

Looks like my version of youtube plugin was several versions behind the latest release, when I check for updates in the kodi platform there was no update, why was no update found when checking for updates on the plugin?

[izprtxqkft]

Looks like my version of youtube plugin was several versions behind the latest release, when I check for updates in the kodi platform there was no update, why was no update found when checking for updates on the plugin?

because the newer versions are not in the repo yet
manual installation from github is required until the updates are submitted to kodi and reviewed

[scott967]

With newer versions of the addon, from the testing or the unofficial repo, the content type is once again being set to episodes rather than videos which it should always be set to... No video addon should ever set content types other than videos. Other content types are reserved for library content and will mess with skins.

Can this be reverted again, please? 😊

That's not what the documentation says.  There are 11 specific content types available for xbmcplugin.setContent() and the documentation says as a remark:

"Use videos for all videos which do not apply to the more specific mentioned ones like "movies", "episodes" etc. A good example is youtube."

https://xbmc.github.io/docs.kodi.tv/mast...fc1e2318d6

scott s.
.

[Shredder_guitar]

Thanks for the reply. Sounds like Kodi needs to evaluate their approval criteria for this plugin (at the very least)... I don't recall the version number I came from but it was several minor changes and several patch number difference. Ideally, I should be able to hit check updates on  Kodi and all plugins that have been updated since the last check contain the latest version of a plugin. If that is not happening, then I have questions. When my wife comes into my office and says youtube's not working, it's a big deal.