Matt

That's great.

Current Status - Last Updated, Monday 01 May 2023 Forum, Wiki and Paste sites are now all active. Systems have been rebuilt from scratch with new images, software and patches. All users will need to reset their passwords before they can log in. Forum registration is now open for new users. Known issues Fixed: We identified a login bug in the forum software which we've fixed and are reporting to the authors. The resolution may require some users to reset their passwords again. Fixed: There was an initial problem with registration of new accounts on the forum after we re-enabled registrations. This has now been resolved. Open: MyAlerts/Pings were not available because there's no supported plugin to provide this functionality. We believe that we've found a fix, though, so will let you know soon. Open: Some users are having issues with unexpected logouts. Monitoring to understand. No further action: We do not have, nor do we plan on implementing, Tapatalk integration. View the full article

As you may have seen on other posts, we're broadly back on line now, with the forum, Wiki and paste sites all operational. It's been a huge effort by several key team members - I won't name names, but you know who you are - and we're all immensely grateful for their work. So, without putting on a hair shirt...in the interests of transparency and minimising the chances of anything like this happening again, we've really had to dig into this to see what we can learn. First of all - what happened? This is probably the most important question, and actually one of the hardest to definitively answer. We've been open about the attack vector being an old administrative account. What we can't wholly conclude is how this was used to gain access. Access logs from the period in question are not available any more, so we can't see who accessed what, how, or when. A 'brute force' attack on an account is unlikely given that MyBB locks accounts quickly if there are too many login attempts. The version of MyBB we were using didn't have any publicised security issues that would permit an unauthorised admin login. We've had limited background from the owner of the account, but we've no reason to believe they were complicit in any way. It's most likely that login data from another breach was used - depending on how often this person changed their password (and, given they were inactive, it's likely to be some time ago), this may well have been years ago. It's possible that their browser was compromised, but we're not aware of any other credentials being stolen. Similarly, it's possible that a current session was hijacked, but these should have long-since timed out and disconnected, so there shouldn't have been an active session to open up. And, finally, some XSS vulnerability in the forum might have been used (these did exist) to hijack the session of an administrator. All difficult to prove, and it's very much bolting stable doors after the horse has bolted and long since run away. We will continue to look, though. So, next up - what have we done? Given that we can't categorically say what the cause was, all we can do is take as many actions as possible to eliminate as many likely vectors as possible - which is good practice, anyway. Actions we've taken, then, include: The hosting server(s) have all been rebuilt from scratch, with latest OS and application patches and further hardening wherever we thought it appropriate. Server software (MyBB for the forum) has been reinstalled from scratch - again, latest software versions, latest plugin versions. Where we haven't simply started again, we've checked configuration files to ensure there are no obvious unauthorised changes or vulnerabilities. Unmaintained or deprecated forum plugins have been removed (which may impact functionality in some instances, but we'll have to live with this). Password hashing has been updated, so we're using a more modern algorithm instead of the older MD5 mechanism. We've followed and implemented MyBB's recommendations and best practices. In addition, we initially disabled new user registration for a few days to keep things calm and testable. For existing users, we've reset all passwords and made sure every active session is logged out - you'll need to use the "lost password" function to your registered email address to regain access. We've also gone through a host of non-forum actions, including: We've reported the security breach to the overseeing information authorities and to the national police in whose jurisdiction the "theft" occurred. We've audited admin rights and made sure we've no other inactive-but-privileged accounts. We've taken the opportunity to reduce the number of privileged accounts wherever we can. We've improved our "ageing out" process for inactive members. This is an ongoing challenge given the revolving door nature of open source contributors, but we need to manage this better. We've implemented MFA on all admin-level accounts where practical. We've shared all affected email addresses with haveibeenpwned.com (interestingly, the majority of addresses were already in their database from previous breaches on other sites - a lesson to all of us to change our passwords regularly). We think we're most of the way there, but there will inevitably be further tweaks, adjustments, and general bug-fixes as we get things back to an acceptable standard on the new infrastructure. Please, expect further downtime and hiccoughs in the coming days as we iron out any remaining problems - we'll open and maintain a pinned post of known issues, so please check this and let us know if you see anything. View the full article

This release is so fresh that we don't yet even have an image... oops! It's been a hectic last couple of months in the world of Kodi, but the wheels keep on turning. Without any further ado, we are happy to announce the first Alpha release for Kodi 21.x "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 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 regressions you wonderful testers come across. So, all that aside... what's actually changed? Build/Dependencies Build support for GCC13 has been fixed by some users. This allows Kodi to be built on newer toolchains that refactored some header inclusions. Some general version bumps have been made for an assortment of dependencies for Android/Apple/CI platforms. Thanks @craigcarnell, @fuzzard. @lrusak has endeavoured to improve the way some of the Android/Apple/CI dependency systems work and handle different states. @Rechi has fixed a few cmake deprecations and pkgconfig detection issues. Documentation Some new contributors noted some of our contributing guideline documentation was lacking. A few people have helped contribute to hopefully make them more helpful/informative. @fixthething has updated some of the Ubuntu build documentation to reflect some modern package names used in more recent Ubuntu versions. FFmpeg Use upstream FFmpeg. This is a big achievement and allows easier FFmpeg updates in the future. Update to version 6.0. This puts us inline with the latest FFmpeg release. Compatibility with 5.1.x has been retained for Linux distro support. Filesystem With the introduction of NFSv4 support, a number of issues were quickly discovered by users. @thexai has fixed a many of these, such as timeouts/chunk size defaults for NFSv4. General @repojonray has provided a number of general fixes/improvements to various areas to address e.g. memory leaks and performance improvements. Modernisation of several areas of Kodi have been undertaken by a number of developers. A lot of this work will go unseen by users, however it's helping to make Kodi's huge amount of code more maintainable for the future. @lrusak, @neo1973 , @repojohnray, @enen92, @Rechi . Add setting to disable screensaver while playing audio. @DeltaMikeCharlie has contributed some improvements to the UX regarding date format options. Games Improvements are continually being made to the Retroplayer ecoystem by several devs/users. Thanks to @KOPRajs, @garbear . JSON-RPC genre has been added to the Video.Fields.Episodes field. Music Add support for reading (and writing) M3U8 playlist files. This provides support for non-ASCII characters in the playlist files (UTF-8 character support). Platform Specifics Android: Improved Dolby Vision detection and compatibility: implemented support of DV in MKV containers, better handling of different DV profiles with fallback to HDR10 when is possible and display is not DV capable. For some devices, we can now also support hardware tone mapping DV profiles 4, 5 to SDR. Supported profiles vary on different Android devices: for example, the 2019 Shield supports profiles 4, 5, 7, 8 in DV and fallback to HDR10 (profiles 7, 8) but not HW tone mapping to SDR. Similarly, the Fire TV Stick doesn't supports profile 7 although it does support HW tone mapping of profile 5 to SDR (profiles 4, 5, 8 are supported with DV display). Implemented minimise shutdown function in Power Saving settings. Multiple small internal improvements and use of newer Android APIs to replace deprecated ones. @joseluismarti is slowly improving/updating a number of Android-specific features that enable the project to stay up to date with Google Play Store submission requirements. iOS/TVOS: Support for Channel Up/Down keys when using the iPhone Apple TV Remote app connected to an Apple TV has been added. Linux: Pipewire: Fix implementation to work properly with AudioEngine. Add support for passthrough formats. This includes HD audio formats like DTS-HD and TrueHD. GBM: Add support for libdisplay-info to help parse EDID information and determine display capabilities. macOS: @enen92 has been slowly but surely improving lots of the macOS native windowing implementation (mouse, resizing, menu bar, shortcut key handling, etc.) that was introduced in Nexus. The official macOS builds do not use this functionality at this point, but with enen92's work, we are inching closer to using it as our default for v21. macOS CD/DVD drive handling has been fixed. This also allows M1-based machines to read disks correctly. Windows: Minimum Windows supported version has been raised to Windows 8.1. If they're available, we will now use displays' friendly names in settings (e.g. "LG TV #1"). Added a setting to use the Windows HDR/SDR brightness balance setting for GUI and subtitles when the display is in HDR PQ mode, and also improved the curve of internal method GUI SDR max peak luminance. Improved read performance over SMB in some special cases, e.g. playing full Blu-ray folders. Improved graphics compatibility and fallback to enable running in some limited VM hardware (Hyper-V) even without video decoding support. Various improvements in DXVA render method to avoid incompatibilities in old hardware or Windows 8, especially in the case of sources with BT.2020 colour space. Implemented support for DXVA2 AV1 hardware video decoding 8-bit and 10-bit. Specific SDK requirements for building UWP packages have been removed to allow the use of newer SDKs from Visual Studio. Picture Fix security issues discovered regarding image EXIF metadata. Further fixes were also backported from the upstream EXIF data parsing library that is in use in Kodi. PVR Add possibility to sort channel groups to your liking. Settings Some fixes to regressions in Settings visibility have been made. Subtitles: The display of MKV files containing text subtitle entries without the duration set on the Matroska block were fixed, retaining Kodi v19 behaviour. This includes the teletext autoconversion to srt done in PVR backends (e.g. tvheadend). Fixed setting of subtitle offset when auto-close video OSD is set. @CastagnaIT has continued to support/fix issues with the new subtitle system as they are reported. UPnP: Improved compatibility with official smart TV applications when displaying and browsing served UPnP Kodi libraries. Fix artwork when playing/refreshing UPnP items. As this blog is, let's say, slightly delayed from when the actual Alpha 1 downloads were available, there are already a number of fixes that have been made to issues found in this release. If you come across any issues, it may be worthwhile testing a newer nightly of your desired platform, otherwise, please do log any issues so we can continue improving for Omega v21. If you love to live on the bleeding edge of new, you can get Alpha 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. As usual - well, it is open source - you can see what's changed between v21 and v20 here. Even though its only been 3 months, it's a long list... View the full article

What @MidnightWatcher said. No such file or directory: 'smb://Video/Backup/PreShow Experience/Music/Awards Music Background.mp3'

Install the add-on Kodi Logfile Uploader. Close Kodi and restart it. Play a sequence with trivia that crashed and then use that add-on to post the logfile and share the link. I'll look at it and get back to you.

What version of PSE do you have? This was fixed in 0.1.1.

I can only guess that PSE isn't compatible with the add-on.

Famous Movie Visitors (2020 Walmart) View File Submitter Matt Submitted 04/14/2023 Category Commercials  

Don't Talk PSA from B.J. Novak View File Submitter Matt Submitted 04/13/2023 Category Courtesy Bumpers  

View File Concession (1975) Concession bumper from 1975 Submitter Matt Submitted 04/12/2023 Category Theater Bumpers  

View File Coming Soon 1965 Coming soon bumper from 1965 Submitter Matt Submitted 04/12/2023 Category Courtesy  

View File Audio Format Bumpers Starter Set This file contains 1 video of every audio format available for use in PreShow Experience. It's a great download to start your audio bumpers collection. Audio Bumpers include: Auro-3D Datasat Dolby Atmos Dolby Digital Dolby Digital Plus Dolby TrueHD DTS DTS-HD Master Audio DTS-X THX Submitter Matt Submitted 04/11/2023 Category Audio Format  

View File 20th Century Fox 20th Century Fox Submitter Matt Submitted 04/11/2023 Category Company  

View File Warner Bros Warner Bros Submitter Matt Submitted 04/11/2023 Category Company  

View File Walt Disney Walt Disney Submitter Matt Submitted 04/11/2023 Category Company