Matt

Thanks for posting this. IMDB changed the way they list their content and that broke the scraper. I am aware of it and am working on a fix.

I know that there's an issue with it in the current version, but this is pretty much what the Slideshow module is for. You can set it to show the image for a long duration and then jump to the next module. There's a bug with it the time format currently that's been fixed in the next version. I wanted to add functionality to escape a loop with a button press, but some remotes don't have many buttons and they could all be used for the trivia module.

Can you feel the excitement building in the air? Well, you should, as we are ready for our first Release Candidate for Kodi 21.0 "Omega"! This is a major release, so, as you'd expect, it comes with many new features. However, with a core change to FFmpeg 6.0, there is a very good chance that we'll get some regressions As such, please be aware that installing this will most likely break things, and we'd really like your help at that point to identify the problems and get them fixed. Please raise Github issues with full debug logs to help us resolve any issues that you wonderful testers come across. First, we'd like to make a few targeted announcements. Android users Many users may still be on the Kodi testing track for their Android devices. It's far easier to leave the testing track from a 'phone-based device, but be aware that if your device is on the testing track, we will be continuing to deploy Beta 3 releases over the next week or so. If you wish to opt out of the testing group, one way you can is by visiting the following link Google Play - Kodi testing track. From here, you can opt out for your Google Play account. This is the best (and possibly only) way to opt out on many Android TV devices (e.g. Nvidia Shields). With that said, for those adventurous types who would like to help us with testing, you can use the same link to opt in for a Google Play account. Xbox users As we do not have a testing track available for Xbox users, we will continue our customary deployment of RC1+ of our major releases to the Microsoft App store. This means that Xbox users will start to see their Nexus deployments updated to Omega RC1. If you do not wish to receive this update, the only option we are aware of is for you to disable auto updates for all apps/games on your Xbox. You can disable auto updates to games and apps in the Microsoft Store through the Store's settings. Select the Start screen, then select Microsoft Store. In Microsoft Store at the upper right, select the account menu (the three dots) and then select Settings. Under App updates, set Update apps automatically to Off. The UWP store deployment is scheduled to begin rolling out on the 16th March. Skin Developers An API bump has been made for Kodi 21's testing cycle. See the following PRs for details: https://github.com/xbmc/xbmc/pull/23926 https://github.com/xbmc/xbmc/pull/23862 This will require changes and submissions to the Omega branch for skins for those who submit to the Kodi Repository. Reach out on the forums if you have any questions/concerns. Please note, https://github.com/xbmc/xbmc/pull/23927 was merged shortly after Beta 2, and all skins will need to update the GUI version number to be available in Omega repos for any builds (including nightlies) after Beta 2. The following forum thread has the skinning change info for Omega: https://forum.kodi.tv/showthread.php?tid=372280&pid=3174566#pid3174566. And now, for the list of changes for RC 1. Estuary A consistency fix was made by @Hitcher to make OSD controls for some buttons to just be disabled, rather than hidden, so the buttons stay shown in a consistent manner. Filesystem A partial revert has been made that fixes some binary addons being unable to correctly parse some XML files. General @ksooo continues to clean up things related to the Video Version feature. This time he has fixed a media name label that would be blank under certain circumstances. A first time contributor, @hagaygo, has made a fix to allow users to set a subtitle save path rather than using a temp location under some circumstances. @CrystalP submitted two fixes that fix list locations after adding/removing versions/extras and their art related management. Music audiobooks were showing their last chapter with no duration; this has been fixed by @the-black-eagle. Platform Specifics Android: Cleanups to build/package files have been made by @joseluismarti. This helps get the codebase nice and clean for the newer Android SDKs leading into the future, meaning we can more easily backport to Omega when we are making changes for v22 "P" in the future. @thexai has made a change that allows subtitles to be tonemapped to avoid extreme brightness for HDR playback. Linux: @fritsch, our resident audio expert, has submitted a change to allow Pipewire to properly identify HDMI for passthrough usage. macOS: @enen92 has implemented Hotkeycontroller for media keys on macOS. This allows Kodi to more accurately capture and handle media-related keys and allows us to play more nicely with other running apps on a system expecting to use the same media keys. Windows: @thexai has submitted some colour accuracy changes for 10bit SDR/HDR colour mapping. PVR A fix for icons not being correctly refreshed was made by @ksooo. VideoPlayer @popcornmix has tracked down a variable initialisation bug that helps to reduce video stalls under certain conditions. A fix that stops incorrect refresh rate changes occurring for interlaced content in some circumstances was submitted by @CrystalP. Known Issues You can see open issues on our tracker at https://github.com/xbmc/xbmc/issues. However, to call out a couple of specifics, please be aware of the following if you're planning on upgrading: There are seek issues with multi-part MP4 files on Android (https://github.com/xbmc/xbmc/issues/23673). We've had reports that the new splash screen looks like an OpenGL corruption; we know, it's not a problem, so don't panic. We'd be happy to have your artwork contributions if you'd like to work on an alternative. If remote sources are unavailable at startup, users are seeing significant delays while waiting (https://github.com/xbmc/xbmc/issues/23958). We continue to march forward to what we hope will be a successful v21 "Omega" release. If you love to live on the bleeding edge, you can get RC 1 from here. Select your platform of choice, and look in the "Prerelease" section. Again, though, please: expect some breakage, don't use this as your daily installation unless you know how to get things working again, and please share your experiences back with us so we can really get going on those bugs. There is always a great deal more changes/fixes/updates than we can highlight in these reports, so, as usual, you can see a fuller list of what has been merged between v21 and v20 here. For a more targeted look at the changes made since v21 Beta 3, you can see those changes here. View the full article

Nexus just won't end, it seems: we're back already, this time what we hope will be the final release for the Nexus line. Welcome to 20.5! An assortment of bug fixes, some backports, no real new features. Full changelog since 20.4 on Github, as usual. Release notes Input Reverted a number of controller changes that caused massive failures on Android devices. Input handling will now be the same as what was available in 20.3. Platform Specific Android Some great detective work was done by @spdfrk for a fix that meant Kodi would close the app during potential colour mode changes. A backport by @fritsch that intends to bring Nexus inline with Omega behaviour for AudioTrack on Android. This means that some device users will need to add an extra setting to their AdvancedSettings.xml file. Details can be seen at https://github.com/xbmc/xbmc/pull/24729. Linux Branding colours have been added to the metainfo file so that they can be used by things like the Flathub store. Info about this can be seen at the Flathub blog post https://docs.flathub.org/blog/introducing-app-brand-colors/. iOS/tvOS A change that wasn't actually in Kodi's codebase, but a fix nonetheless, means that the inputstream.ffmpegdirect addon is now available to the iOS/tvOS release debs. ... plus, of course, some behind-the-scenes fixes and updates for e.g. library versions. Thanks, as always, to everyone who has helped us track down and fix any issues. We endeavour to minimise the issues everyone experiences, but with such a large project, and the fact everyone contributing to Kodi is a volunteer, issues and bugs are a part of life. if you happen to experience any bugs/issues, don't hesitate to reach out on the forums, or raise an issue on Github. As this is a point release, there are no major changes since the previous version, and you should be fine to install this straight over the top of any existing Kodi 20.x installation - indeed, this will happen automatically on many platforms. However, as for all software installations, back up your userdata beforehand if you've any doubts or have anything you can't afford to lose (and definitely do this if you're going for a major version upgrade). A list of all changes for this version can be found at GitHub. If you want to read back on the full history of v20 itself, or of previous versions, you can find the corresponding articles in the relevant blog posts. Application deployment on different platforms (notably the Microsoft Store) can vary considerably due to circumstances outside of our control, so just be patient, and the update will inevitably find its way through. Android Deployment We always do what's known as a "staged" deployment roll out for Android. So if you don't receive the update immediately, be patient, as it will come through over the next week. As the majority of fixes are related to Android Playstore deployment, we will be cautious with the deployment time. If you do receive 20.5 and have any issues with the Playstore deployment, please let us know as soon as possible. View the full article

Editorial note: this blog post has been delayed for technical reasons, so the release is already available. Time marches on for Kodi 21 "Omega", we are here with the third Beta release! This is a major release, so, as you'd expect, it comes with many new features. However, with a core change to FFmpeg 6.0, there is a very good chance that some regressions may occur. As such, please be aware that installing this will most likely break things, and we'd really like your help at that point to identify the problems and get them fixed. Please raise Github issues with full debug logs to help us resolve any issues you wonderful testers come across. First, we'd like to make a few targeted announcements. Android users Many users may still be on the Kodi testing track for their Android devices. It's far easier to leave the testing track from a 'phone-based device, but be aware that if your device is on the testing track, we will be continuing to deploy Beta 3 releases over the next week or so. If you wish to opt out of the testing group, one way you can is by visiting the following link Google Play - Kodi testing track. From here, you can opt out for your Google Play account. This is the best (and possibly only) way to opt out on many Android TV devices (e.g. Nvidia Shields). With that said, for those adventurous types who would like to help us with testing, you can use the same link to opt in for a Google Play account. Skin Developers An API bump has been made for Kodi 21's testing cycle. See the following PRs for details: https://github.com/xbmc/xbmc/pull/23926 https://github.com/xbmc/xbmc/pull/23862 This will require changes and submissions to the Omega branch for skins for those who submit to the Kodi repository. Reach out on the forums if you have any questions/concerns. Please note, https://github.com/xbmc/xbmc/pull/23927 has been merged shortly after Beta 2, and all skins will need to update the GUI version number to be available in Omega repos for any builds (including nightlies) after Beta 2. The following forum thread has the skinning change info for Omega: https://forum.kodi.tv/showthread.php?tid=372280&pid=3174566#pid3174566 And now, for the list of changes for Beta 3. Build/Dependencies Support for building with swig 4.2.0 General The way in which buffer fill was handled was changed to care more for low-power CPU devices. Under certain circumstances, and with especially high manually-configured readbuffer factors, the buffer filling thread caused high CPU usage and introduced stutter by itself. Implemented new "Adaptive" setting in Services / Caching / Read Factor that allows a variable read factor based on cache level. This means that the cache fills faster, while at same time using a less aggressive read factor when it's already filled. Fixed media served through plugins not being accessible when a master lock is used. JSON-RPC Add command to change playback speed (tempo). Add a command to activate screen saver. Music Fix an issue with m3u playlists which didn't show art for the second and subsequent tracks: https://github.com/xbmc/xbmc/pull/24675. Allow navigation from artists directly to songs, missing out albums and discs. This is more like how Spotify et al. navigate: https://github.com/xbmc/xbmc/pull/24649, forum thread https://forum.kodi.tv/showthread.php?tid=375313. Only drop music database triggers on clean if they exist, which fixes a problem that occurred if Kodi was closed/crashed whilst a clean was underway on the Music database. Platform Specifics Android: The audio changes for the Android ecosystem were documented in https://forum.kodi.tv/showthread.php?tid=376161. Due to various firmware bugs on multiple devices we were forced to add some opt-in audio settings for (especially) the widely-used FireTV Cube 3rd Gen, which were enabled by default until this beta, but sadly regressed on half-broken firmwares of other devices. It's not possible to maintain a deny list as available systems and versions change too quickly, plus Kodi release cycles can't be synchronised with every big vendor putting out fixes. As such, we decided to move this into an advanced setting, with more information available in the linked forum thread. Feel free to open new issues if you see regressions of some sort, but please don't forget your debug log, as help isn't possible otherwise due to the sheer variety of differently-broken boxes. Another advanced setting now allows the output of high-precision 32-bit float from within Kodi for multi-channel PCM files. This is again an advanced setting because some devices fail silently when opening this combination. Float32 is the highest precision Android's Audiotrack Soundserver can handle. It was tested and is working on Shield and FireTV 4K 2nd Gen. We received a whole lot of bug fixes from external contributors this time, with the focus on HDMI Hotplug after refresh rate changes and also Audio device enumeration. The long-standing bug of losing Android IEC devices during IDLE is solved. We are very thankful for these contributions. @quietvoid has implemented a new setting in Player / Processing that allows filtering of HDR dynamic metadata HDR10+ and/or Dolby Vision to improve compatibility on devices that had issues, especially with hybrid videos that includes both types at same time. iOS/tvOS Disable VTB (hardware decoding) for real-time interlaced videos. Linux: Pipewire sink got a fixup for sample rate switching. With that updated code, the back-end server of Pipewire will switch the base sample rate whenever Kodi is run without additional other clients. This way, Kodi's audio will be output in the best possible and lossless way throughout the audio chain, including soundserver and audio device. Adjusted dependencies to build packages compatible with Ubuntu Focal to Noble for CPack building @fightforlife has fixed an issue with RenderCapture used by things like Hyperion that fixes sporadic black screen captures webOS Map info key on webOS remotes. Disable core dumps by default to reduce less storage being used on webOS TVs. Implement shutdown/reboot . Windows: Improved chroma upscaling when using Pixel Shaders or Software render methods, and also DXVA only in specific cases: AMD + old drivers + 10-bit SDR. Improved channel layout match in WASAPI when audio drivers do not support the exact speaker layout. This is only relevant for PCM (not passthrough). Increased the number of video surfaces in DXVA H.264 decoding to prevent video corruption in some rare H.264 streams. Pictures Long time contributer @notspiff added avif image support. @enen92 fixed an Exif parsing regression that was introduced in Matrix (v19). Scraping .nomedia files can now be used to exclude folders inside a TV show: https://github.com/xbmc/xbmc/pull/24330 @78andyp fixed what looks like has been broken for a long period - the ability to scrape episodes in Bluray folders (BDMV). Skinning The estouchy skin has been retired from default installs. If anyone would like to continue working on the skin for future use/availability, you can find the new home for the skin at https://github.com/jjd-uk/skin.estouchy for now. The player control dialog for Estuary has been updated, along with other changes to bring the skin up to date for 5.17.0 API. A fix for duplicate music flags was made by @jjd-uk. UPnP @enen92 has once again made an assortment of fixes for UPnP, such as fixed broadcasting of item updates and 'mark as watched' state. An option was added to avoid volume synchronisation to a UPnP target. Known Issues You can see open issues on our tracker at https://github.com/xbmc/xbmc/issues. However, to call out a couple of specifics, please be aware of the following if you're planning on upgrading: There are seek issues with multi-part MP4 files on Android (https://github.com/xbmc/xbmc/issues/23673). We've had reports that the new splash screen looks like an OpenGL corruption; we know, it's not a problem, so don't panic. We'd be happy to have your artwork contributions if you'd like to work on an alternative. If remote sources are unavailable at startup, users are seeing significant delays while waiting (https://github.com/xbmc/xbmc/issues/23958). We continue to march forward to what we hope will be a successful v21 Omega release in the new year. If you love to live on the bleeding edge, you can get Beta 3 from here. Select your platform of choice, and look in the "Prerelease" section. Again, though, please: expect some breakage, don't use this as your daily installation unless you know how to get things working again, and please share your experiences back with us so we can really get going on those bugs. There is always a great deal more changes/fixes/updates than what we can highlight in these reports, so as usual you can see a fuller list of what has been merged between v21 and v20 here. For a more targeted look at the changes made since v21 Beta 2, you can see those changes here. View the full article

It's a bug in that version. I've already fixed it, but am traveling (multiweek for work) and haven't been able to add the fix. You can always go back to 0.2.4 until I can get the update added.

Are you going into movies and opening the context menu?

I unfortunately have no idea how to do this. I don't have anything with a disc drive with Kodi on it.

PreShow should be in the context menu after you restart Kodi. The skins on the site are all for 20.

Awesome. Great job. Thanks for explaining how you did it.

It looks like one last hurrah was premature for the "Nexus" line: we find ourselves back again already, this time with a new 20.4 release. An assortment of bug fixes, some backports, no real new features. Full changelog since 20.3 on Github, as usual. Release notes Build A backport aimed at fixing the failure rate of binary addon builds has been merged by @garbear. Input Update to the controller addons. Platform Specific Android Several fixes have been backported from master to fix deployment issues on Google Play. Thanks to @joseluismarti for working with us on these. A number of fixes backported to resolve input issues (remotes/controllers). iOS/tvOS A long-time-coming fix to reduce black screen playback when interlaced content is played on iOS/tvOS. Users should no longer have to specifically disable VTB Hardware playback for most interlaced content. Please keep in mind some methods of content playback (HTTP URLs provided in .strm files) will still be affected. A memory leak with game controllers on iOS/tvOS has been fixed by @kambala-decapitator. tvOS @kambala-decapitator fixed what seems to be a long standing bug regarding framework plist metadata for shared library frameworks. Windows A fix for AESinkWASAPI to improve fallback when the exact output channel layout isn't supported by drivers or hardware. Thanks, as always, to everyone who has helped us track down and fix any issues. We endeavour to minimise the issues everyone experiences, but with such a large project, and the fact everyone contributing to Kodi is a volunteer, issues and bugs are a part of life. if you happen to experience any bugs/issues, don't hesitate to reach out on the forums, or raise an issue on Github. As this is a point release, there are no major changes since the previous version, and you should be fine to install this straight over the top of any existing Kodi 20.x installation - indeed, this will happen automatically on many platforms. However, as for all software installations, back up your userdata beforehand if you've any doubts or have anything you can't afford to lose (and definitely do this if you're going for a major version upgrade). A list of all changes for this version can be found at GitHub. If you want to read back on the full history of v20 itself, or of previous versions, you can find the corresponding articles in the relevant blog posts. Application deployment on different platforms (notably the Microsoft Store) can vary considerably due to circumstances outside of our control, so just be patient, and the update will inevitably find its way through. Android Deployment We always do what's known as a "staged" roll out for Android - so, if you don't receive the update immediately, be patient, as it will come through over the next week. As the majority of fixes are related to Google Play deployment, we will deliberately be cautious with the schedule. If you do receive 20.4 and have any issues with the deployment, please let us know as soon as possible. View the full article

I have temporarily disabled the repo. I will add it back when the next version comes out.

Restart kodi and open the context menu for your local movies to see the PreShow Experience. Some skins have a button to launch Preshow, and there are a few that been unofficially modified here: https://preshowexperience.com/files/category/7-skins/

Thanks for pointing this out. Yes, the Slideshow module has some bugs in the current version. I believe I have them all fixed in the upcoming version. Thanks again.

View File Happy Valentine's Day 2024 Valentine's Day PreShow video. I take no responsibility if you show this bumper before SAW. https://youtu.be/4oViFjEXSNI Submitter Matt Submitted 02/08/2024 Category Holiday Bumpers  

Look in video bumpers. There are a bunch of folders in there for preset videos. You can also create a new module in a sequence and set it to directory. Then you can pick any folder you want to play those videos.

Unfortunately none of the bumpers that I have created are 7.1. Most are 5.1 though. Tuya requires Home Assistant and isn't an easy option. This thread may help when you get to that point:

Have you set up your content folders? Do you have any content downloaded and placed into the folders? What do you want your preshow to include? Do you know how to edit a sequence? Do you know how to launch PreShow?

Glad that you figured out how to make it work. The content folders use Kodi's built-in path functionality, so it isn't something that I really have any control over.

You can follow the guides starting here: You need to create your PreShow content folder somewhere that your system can access and that you can move files to from another computer. You can then download content from this site or use content you find elsewhere. https://preshowexperience.com/files/category/2-preshow-videos/ Please let me know if you need more assistance. What system do you have kodi on?

Go into Kodi's settings and click "File Manager." Then "Add source" and select your USB hard drive. See if that will make it show up as a location option in PreShow.

PreShow will only play the trailers that are streamed or in the content's trailer folder. You can also select another folder for trailers, or any video, with a video bumper set to directory. There currently isn't any way to selective pick certain files in those folders though. I may look into any option for that.