Matt

What version of PreShow are you using? The "working" pop-up is skin related. You can download 1 of the skins in the downloads section to remove that.

0.3 is the next version. It's still in testing, but that issue should have been resolved. https://preshowexperience.com/files/file/169-preshow-experience-dev-build/

I just looked at the file listed here: https://forum.kodi.tv/showthread.php?tid=371494 and it included PreShow already: https://holybid.com/kodi/lattsrepo/master/nexus/skin.aeonmq8.nexus.mod/skin.aeonmq8.nexus.mod-1.0.1.7.zip There's nothing in it specific about ZDMC, but I don't know if that's necessary or not.

@FlexThat was a mislabeled file. Nature's Fury is for Dolby Atmos and is available here: Thanks for catching the issue.

I have continued to work on this and have added a new setting for Kodi's listed aspect ratio. My issue with this setting, and the reason that I didn't go this route originally, is that I don't know if it is correct. Unless you use TMM as @hslansky suggested or have your videos cropped and recompressed like @Epitaph's list, they will all be 1.78 : 1 as that's what a full frame blu-ray with black bars is. I have made the assumption that if you use nfo files, Kodi will have already scraped the data from them and we can just use that. So there is now a sub-setting for this in PreShow to select how you want it handles. I'm not sure if that's the right wording, but Kodi has a character limit on the settings, and to explain it properly requires scrolling. And then I've modified the IMDB selection option to give the user some more control. Originally I tried to make it so that it would pick the most likely option for movies that list multiple options. That worked for the majority of cases, but not all. There are some that aren't labelled correctly, and then there's always the multi-aspect movies. Now you'll get a pop-up so that you can select which one you want.

Thanks for the suggestion @hslansky & @Epitaph. My goal is to always make a solution that works without the need for other applications. I'll explore other options in the future and already have plans to do some work with nfo files, which may offer better options for a few processes.

@FlexMake sure you restart kodi after installing PreShow. The context menu doesn't load until after a restart. Or install a skin that supports PreShow. Here's a link to the skins that I've worked on to make PreShow compatible: https://preshowexperience.com/files/category/7-skins/ The skin in the images is Aeon Nox: Silvo

I think that the file you want to edit is DialogNotification.xml.

Are you trying to show an image for the intermission with GUI.ShowNotification? If so, I think that the only image in the notification is the icon.

I haven't tested youtube links, but will look into it.

The kodi trailer issue was reported in the discord ane has been fixed. I am testing a couple other things that have been reported and will post an update for it as soon as I can.

Skin: Confluence for PreShow Experience in Kodi 21 View File This is a modified version of Confluence for use with PreShow Experience in Kodi 21 Submitter Matt Submitted 04/28/2024 Category Skins  

The code that you want is something along the lines of: sleep://3600000 http://username:password@ip#:8080/jsonrpc {"jsonrpc":"2.0","method":"Input.ExecuteAction","params":{"action":"playpause"},"id":0} sleep://600000 http://username:password@ip#:8080/jsonrpc {"jsonrpc":"2.0","method":"Input.ExecuteAction","params":{"action":"playpause"},"id":0} Add other functions a you want. Make sure you have your system set up to allow this in settings > services > control.

Skin: Estuary for PreShow Experience in Kodi 21 Omega View File This is a modified version of the skin Estuary for use with PreShow Experience in Kodi 21 Omega. Submitter Matt Submitted 04/28/2024 Category Skins  

Damn, 37 is young.

This won't fix your problem, but as a recommendation to people that may see this, please turn off app auto updates on the shield. I am still mad about it modifying my system after I had it dialed in and not being able to quickly get it working perfectly again.

It is. I also PMed it to you yesterday.

In 2015, Kodi’s default theme Confluence was growing long in the tooth. Most of the really exciting skins from that time accomplished far more, and Confluence was ultimately a 2009 update to an existing skin called MediaStream that was itself several years old. It was time for Confluence to retire. We needed something new that adhered to the UX best practices of the time. I proposed some wireframes based on Google’s Material Design that were pretty vague, but I hoped would be enough to get us started. Almost immediately, members of our team of skilled skinners (Phil65 and Piers) jumped on the task. I made my initial suggestion early on the 17th of June, and Piers had already mocked up a complete home page later that day. His post at that time introducing the mockup had me chuckling for days. Once an idea struck him, the guy worked tirelessly to see it through. By the 18th, a day later, Piers’ mockup was revamped and looked remarkably complete. Unfortunately, those early designs have been lost to the internet gods, but we do still have a screenshot of the first alpha created in August that remained quite true to those early mockups. By September, Estuary was pretty well complete with two primary themes, the 3D-styled curial and the flat style which remains the default to this day. Piers and Phil65, along with several other skinners, notably BigNoid, had introduced a variety of features including the ability to select different color styles, like pink. The team also created a separate second skin designed specifically to work for mobile devices. In 2016, these skins were officially released with Kodi 17 to universal praise within the community (for those interested in history, you can find the original blog post here). The work done by Piers and the team on UX/UI in 2015 and 2016 cannot be understated. They developed a lasting and original skin that remains in use to this very day. We recently learned that Piers passed away. He was 37. He will be missed by those of us who worked with him on this project. We cannot emphasize enough his contribution to software seen and used by millions of people worldwide. Thank you for everything, Piers. View the full article

I think the issue that marius had has been resolved.