(2024-11-29, 19:35)phyrros1 Wrote: The second one does not appear in the list.

(2024-11-28, 19:16)MoojMidge Wrote: @jim_p - Yes, please advise what other strings are missing that you have noticed.

(2024-11-29, 23:34)jacen05 Wrote: The setting "Use InputStream.Adaptive" was on, I disabled it.

(2024-11-29, 23:34)jacen05 Wrote: but same error happened when trying to play anything (tried several videos using several menus).

(2024-11-29, 23:34)jacen05 Wrote: inputstream.adaptive returned bad status "Permanent failure" during instance creation

(2024-11-28, 23:13)Chillbo Wrote: 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.

(2024-11-28, 23:13)Chillbo Wrote: 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. 😊

(2024-11-28, 23:13)Chillbo Wrote: 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.

(2024-11-29, 08:04)doko-desuka Wrote: 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.

(2024-11-29, 17:14)flhthemi Wrote: Soooo...anytime the Setup Wizard DOES pop up then we ARE supposed to run it? 

(2024-11-29, 19:35)phyrros1 Wrote: 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.

(2024-11-29, 23:34)jacen05 Wrote: What else can I try?

(2024-11-29, 23:45)izprtxqkft Wrote:

(2024-11-29, 23:34)jacen05 Wrote: The setting "Use InputStream.Adaptive" was on, I disabled it.

(2024-11-29, 23:34)jacen05 Wrote: 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
 

(2024-11-29, 23:34)jacen05 Wrote: 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.adaptive/issues/866#issuecomment-1002675624

(2024-11-30, 00:10)MoojMidge Wrote: 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?

(2024-11-30, 00:10)MoojMidge Wrote: 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.

• 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.
  

(2024-11-30, 00:10)MoojMidge Wrote: 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.

(2024-11-29, 19:39)izprtxqkft Wrote:

(2024-11-29, 19:35)phyrros1 Wrote: The second one does not appear in the list.

what's the video link?

(2024-11-30, 00:10)MoojMidge Wrote:

(2024-11-29, 19:35)phyrros1 Wrote: 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.

(2024-11-30, 18:47)Shredder_guitar Wrote: 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?

(2024-11-28, 14:56)Chillbo Wrote: 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? 😊