All Activity

Audio Format Bumper: THX - Sphere

Tue, 07 Apr 2026 14:57:26 +0000

THX - Sphere THX Sphere Trailer in 4K with 7.1 Audio in Dolby TrueHD and Dolby Digital Plus (secondary track). File Information Submitter ToastyMaster07 Submitted 04/07/2026 Category Audio Format View File

THX - Sphere

Tue, 07 Apr 2026 14:57:26 +0000

THX Sphere Trailer in 4K with 7.1 Audio in Dolby TrueHD and Dolby Digital Plus (secondary track).

Kodi News: Kodi 22 "Piers" Alpha 3

Wed, 01 Apr 2026 14:22:00 +0000

Announcing the release of Kodi 22 “Piers” Alpha 3! Usual words - the step from 21 to 22 is a major release, but it’s also an Alpha at this stage, so you’re going to get some bugs as well as funky new features. That is, of course, a major part of the point of early release software: please raise Github issues with full debug logs to help us resolve any regressions you wonderful testers come across. Okay, what’s new in this version? Changelog Release highlights Added support for taglines in TV shows Added support for H264 AVCC subtitles Added support for full IANA language tags Added JSON RPC methods “Player.GetChapters” and “Player.OnPropertyChanged” Upgraded FFmpeg to v8.0.1 Upgraded Python to v3.14.3 Changed MySQL/MariaDB charset to utf8mb4 and collation to general_ci (case insensitive) Video Improved Blu-ray support for both menus and playback Improved TV show episode handling for blu-ray Improved changing chapters in movies Improved seeking during tempo change Audio Changed default samplerate from 44.1kHz to 48kHz Fixed missing 200ms of audio at the start of video playback Fixed occasional missing audio when changing playback speed Fixed AC3 audio duration being incorrect for non-48KHz content Improved handling of low-latency audio Subtitles Fixed handling of WebVTT (ISOBMFF) subtitles Fixed PGS/VobSub subtitle selection for foreign audio tracks Fixed crash when handling some BCP47 language tags added in Alpha 2 Library Improved tagline handling for movies and TV shows Games Added N64 support using software rendering Improved shader support Fixed Black screen for games with unaligned textures Fixed crash when changing resolution Streaming and network Fixed playback of tcp:// streams Fixed media info display for strm:// streams Fixed occasional errors resuming UPnP playback Stacks and compressed archives Added support for folder stacks, useful for DVD/Bluray folders Improved playback of folder stacks Improved handling media inside compressed archives Fixed handling of zip files greater than 4GB Profiles Improved creating profiles in custom folders Fixed deadlock when viewing Weather with multiple profiles Highlighted current profile in profile selection dialog Platforms Android Fixed Auto Frame Rate (AFR) when resuming from standby Improved handling of Dolby Vision L5 metadata Improved handling of foreign subtitles webOS Video General improvements for Dolby Vision support Improved handling of Dolby Vision L5 metadata Fixed tempo control webOS Audio Improved audio passthrough support Improved volume handling in non-passthrough mode Improved Dolby Digital audio when using eARC Fixed AAC playback on some older versions of webOS Windows Added front-to-back rendering Changed default audio output to XAUDIO and WASAPI Fixed Kodi unable to run on Windows 8.1 Linux Improved power management for systems without logind Extended range of keyboard keys and remote buttons Fixed long-pressing keyboard keys on Wayland FreeBSD Extract to disk instead of RAM for large compressed archives A little love for developers and security researchers (For researchers) Dropped some unused code that kept tripping CVEs (For developers) New KodiAI app on GitHub (For developers) Added support for Visual Studio 2026 (For developers) Improved compatibility with C++23 (For developers) Added meson support for building dependencies Known Issues Kodi is incompatible with MySQL 9.6 (‘sets’ is now a reserved keyword). A fix will be devised for the next v22 prerelease. Blu-ray stream details aren’t saved in the library Builds If cutting-edge software is your thing, you can get Alpha 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. And take a backup first! As usual, in the full spirit of open source, you can see what’s changed since Alpha 2 here and from v21.3 here. View the full article

Kodi News: DevCon 2026 - Barcelona Revisited - Part II

Sat, 28 Mar 2026 19:54:00 +0000

So, here we are, back in the roo atm after a day of sidebar meetings, coding, hacking, experimenting, and general conferencing. Time for some more structured sessions, starting with some of our partner projects. Chewitt started us off with an overview of LibreELEC: hardware updates and changes, new chip set support, some challenges with older SoCs, plans for standardising e.g. kernel trees more, and so on. He also covered topics such as the challenges around supporting set-top box DVB tuners, plus deprecated video drivers and implications for users. Beyond that, the project is healthy, with a broadly stable user base and positive finances. Keeping with third-party projects, Flole next gave a brief update on Tvheadend, mostly around development status, plans for a new interface, CI/build process, and a few others. (As an aside, both projects have recently celebrated milestone anniversaries: LibreELEC is ten years old, and Tvheadend has just passed 20. Happy birthday to both projects!). And to collect the set, samnazarko then took the floor to talk about OSMC. As a turnkey, commercial consumer device, things are going well, although there’s pressure from RAM prices as you’d probably expect. He talked about the challenges around TV-led playback versus player-led (basically, where’s the decoding being done), and took a long detour through HDR technologies, colour spaces and tone mapping. Next up, sarbes spoke about upcoming UI changes, mostly in the sense of textures and component rendering. These will deliver significant performance gains on low-end and embedded devices, and anything using a heavier, multi-layer skin. razzee then took us through some website updates. These aren’t really user-facing, but shouldd give us some performance benefits as well as security improvements: library updates, a new framework, and updates to the CMS itself. We also discussed future options and suggestions for the site. This conversation segued into blog/website workflow, how we could streamline that or open it up to more contributions, and how our AI tools could perhaps help with some contect-aware automation.. Juddering towards the end of the conference, jernej talked us through Linux colour APIs, which expose hardware capabilities to help with HDR on this OS. And that’s about it. Thanks to everyone for attending, and, equally, thanks to everyone reading this for the support. You are the people who make Kodi what it is. See you in 2028 … probably 😉 View the full article

Kodi News: DevCon 2026 - Barcelona Revisited - Part I

Fri, 27 Mar 2026 19:00:00 +0000

Well, hello everyone! It’s that time of year again, when your favourite development team rouse themselves from their long winter slumber and emerge, blinking in the light, to reconnect with their fellow creatures. Welcome to DevCon 2026! We’re coming to you this year from about an hour outside Barcelona, which makes this a return visit. Not that it matters, I guess; you probably know how this works by now, so let’s get straight in … As seems to be tradition now, we kicked off with a round of reminiscences - how long people have been team members, how they first got involved in Kodi, and past DevCon glories. Hey, don’t judge, we don’t get to see each other very often. keith then gave a quick board/financial overview. The Kodi project remains firmly solvent, although we do get far less money from donations and sponsorships than once was the case. DevCon is our largest single expense, so we’ll almost certainly skip 2027 to make sure we can invest in hardware, hosting, Weblate, trademark fees and similar. Speaking of trademarks, we’ve been working through many years of Foundation legacy, tidying up loose ends. It’s all long overdue, but there’s a chunk of legal and government costs there that we still need to incur. We then moved onto a conversation about AI tools, options on the market, and their value - both relative costs and how they might work within the extended Kodi development ecosystem. Next up, GSoC 2027 - how much do we want to participate, who might mentor, what potential projects. razze then picked up a theme we’ve been watching for a couple of years now - the viability of moving from Slack to [matrix] as the latter continues to mature. One of the biggest challenges is the inability to migrate channel histories. As such, we’ll quite probably stay where we are unless we have some more compelling reason to make the switch. Sticking with razze, we then switched direction to Flatpak and how that’s shaping up for future releases. We have some challenges about packaging add-ons, the resultant size of any downloads and what options we might have there. Rewinding slightly, keith next lead a conversation about our existing use of AI, and our KodiAI tool. This is a home-grown capability that came about to get around the restrictions of mainstream tools, although it still uses those tools behind the scenes. We’re currently using this for PR code reviews and issues, but we also talked about future possibilities and where we might go next. We may well come back to this for a bit of a deeper dive over the next couple of days if time allows. Moving on, garbear took the floor to update everyone on progress with Retro player and peripheral/accessory support. Those updates include multi-disc support to emulated games that came on more than one CD - effectively, a playlist. He also covered further work on video filters - a long-standing “coming soon” feature formerly known as shaders - and how they can be used to alter the appearance of a game in realtime. While he was up, garbear then moved on to release management: some of the challenges we have with the 21.x series due to Android API bumps, and some of the plans for the release of 22.x alpha to beta to release. Next up, yol took us through some server topics, specifically around current OS versions, implications and options. A quick segue into upcoming conferences, events and similar, and we’re pretty much done for the night. Take care, all, and we’ll see you again tomorrow. View the full article

Preshow theater intros

Sat, 07 Mar 2026 09:24:45 +0000

OP this sounds awesome, maybe 15 years ago I followed a blender tutorial and made a 20th Century clone one. It took me forever and I thought it looked like pretty bad but I still rocked with it lol. UE can do some impressive stuff so I'll be checking back here so I can see what you end up creating. Pretty sure you're talking about vipid.com, I just checked and it's either gone or the database is down. They had some pretty cool intros, but if you wanted high resolution or more than 1 it got pricey pretty quick. I think the HD ones (1080p) were like $15 each. They had knock off's of a lot of the studios. Wouldn't be surprised if they're gone. I used to check it a few times a year for about 5 years, and they never added any new intros.

Preshow theater intros

Mon, 23 Feb 2026 21:56:17 +0000

I will probably have to share them from Google drive or something.

Preshow theater intros

Mon, 23 Feb 2026 20:11:52 +0000

@sea dog I look forward to seeing your intros. I will be providing an option for paid customizable intros at some point as a way to help support PreShow.

Feature Request: Support for Relative File Paths in PreShow Experience

Sat, 21 Feb 2026 16:52:29 +0000

I'll look into it. Thanks for the suggestion.

Preshow theater intros

Wed, 18 Feb 2026 23:07:24 +0000

That is cool! I remember seeing a website that did all kinds of video intros for like $5-10. Could have sworn one was Marvel. But I can't find the website anymore.

Dynamic Content Generation for PSE — Custom Title Cards & AI-Powered Trivia

Wed, 18 Feb 2026 20:16:55 +0000

Great work on this. I have a lot of new functionality that I've worked on with PreShow that is on a similar path to this. I may add an action or similar functionality to make it easier to do stuff like this without the need to modify PreShow.

Dynamic Content Generation for PSE — Custom Title Cards & AI-Powered Trivia

Wed, 18 Feb 2026 00:47:23 +0000

I've been working on a system that generates movie-specific content on the fly every time you launch a PreShow sequence. Instead of static slides, PSE now dynamically creates a "Tonight's Feature" title card and (optionally) 30 custom trivia slides tailored to whatever film you're about to watch. I wanted to share the approach in case others want to build on it. Here's what it looks like in practice: you press Start PreShow on "Fargo," and a few seconds later your sequence opens with a custom title card reading "FARGO" on a theater marquee background, followed by 30 slides of trivia, behind-the-scenes facts, and Q&A specific to that film — all generated fresh every time. The ProblemPSE's slideshow module is great for static trivia packs, but I wanted content that adapts to whatever movie I'm watching. The challenge is that PSE caches slideshow content when it builds the sequence, so you can't just generate images asynchronously and hope they show up in time. I tried a lot of approaches that didn't work before finding one that does: Action module with Python script — PSE runs Python actions inside Kodi's embedded Python, which doesn't have libraries like Pillow installed. Also runs asynchronously — PSE moves to the next module before the script finishes. Generating images and hoping the slideshow picks them up — PSE caches the slide directory contents at sequence build time. If your images aren't there yet, they won't appear. Overwriting existing placeholder images — PSE caches the actual image data, not the file reference. Overwriting the file after caching has no effect. Skin button interception — Tried adding a RunScript call before PSE launches from the skin's context menu. Unreliable timing. The Solution: Hooking into experience.pyThe key insight is that PSE resolves the feature film's metadata (title, genre, year, cast, etc.) before it builds and caches the sequence. There's a window between "PSE knows what movie you picked" and "PSE scans the slideshow directories" where we can inject code. The hook goes into PSE's experience.py, specifically in the method that resolves the feature film from Kodi's library. After PSE appends the feature to its internal list, we write the metadata to temp files and call external Python scripts that generate our content: # In experience.py, after self.features.append(feature) # and before "if not self.features: return False" if self.features and self.features[-1].title: import subprocess import json as _json _feat = self.features[-1] # Write title for the compositing script with open("/tmp/pse_feature_title.txt", "w") as _f: _f.write(_feat.title) # Write full metadata as JSON for other scripts _meta = { "title": _feat.title, "year": getattr(_feat, "year", 0), "genres": getattr(_feat, "genres", []), "directors": getattr(_feat, "directors", []), "cast": getattr(_feat, "cast", [])[:10], "rating": str(getattr(_feat, "rating", "")), "runtime": getattr(_feat, "runtime", 0), } with open("/tmp/pse_feature_metadata.json", "w") as _f: _json.dump(_meta, _f) # Run content generation scripts (synchronous — PSE waits) subprocess.call(["/usr/bin/python3", "/path/to/your/script.py"]) The critical detail is subprocess.call — this blocks PSE until the script finishes. PSE doesn't proceed to sequence building until our content is generated and sitting in the slideshow directory. Important: We call /usr/bin/python3 (system Python) rather than running inside Kodi's Python. This gives us access to any pip-installed library — Pillow for image compositing, requests for API calls, whatever you need. Kodi's embedded Python is limited to its bundled packages. Finding the Right SpotTo find where to inject, look for this pattern in experience.py: feature = self.featureFromId(movieid, episodeid) if feature: self.features.append(feature) # >>> YOUR HOOK GOES HERE <<< if not self.features: return False return True Search for self.features.append(feature) near featureFromId — there's one instance in the method that handles the "Start PreShow" button press. On my install it's around line 1060. After editing, you must delete the bytecode cache or Kodi will keep running the old version: rm ~/.kodi/addons/script.preshowexperience/resources/lib/__pycache__/experience.cpython-*.pyc Then restart Kodi. What You Can Build With ThisOnce you have the hook in place, the feature metadata is available to any external script. Here's what's in the self.features[-1] object: title — Movie title year — Release year genres — List of genres (Action, Horror, Drama, etc.) directors — Director names cast — Cast list with names and roles rating — MPAA rating runtime — Runtime in seconds studios — Studio names tags — Kodi library tags With this data you could: Generate a custom "Tonight's Feature" title card with the movie name Create genre-themed trivia (horror trivia for horror films, sci-fi for sci-fi) Select decade-appropriate trailers by dynamically populating a trailer directory Generate MPAA-style rating cards Pick studio-specific intro bumpers Call an AI API to generate movie-specific trivia and Q&A slides Create "on this day in cinema history" slides based on the current date and film era Example 1: Dynamic Title CardMy first use case was a "Tonight's Feature" title card — a theater marquee background with the movie title composited in a vintage font. The script reads the title from the temp file, uses Pillow to render text onto a template image, and saves it to a slideshow directory. The core of the compositing script: from PIL import Image, ImageDraw, ImageFont def generate_title_card(title): # Load background template img = Image.open("/tmp/template.png") draw = ImageDraw.Draw(img) font = ImageFont.truetype("/tmp/myfont.ttf", 80) # Center the title bbox = draw.textbbox((0, 0), title.upper(), font=font) text_w = bbox[2] - bbox[0] x = (1920 - text_w) // 2 draw.text((x, 450), title.upper(), font=font, fill=(0, 0, 0)) img.save("/path/to/pse/Slideshow/Tonight/tonight.png") The real script has auto-sizing logic (shrinks the font for long titles), word wrapping, and handles the CIFS font loading issue (Pillow can't load fonts from network shares — copy to /tmp/ first). But the concept is this simple. In the PSE sequence, a Slideshow module points at the Tonight directory and displays whatever image is in there. Runtime: About 1.4 seconds on a Vero 5. Barely noticeable in the PSE launch flow. Example 2: AI-Generated Trivia SlidesThe more ambitious extension calls the Claude API with the movie's metadata and asks it to generate trivia facts and Q&A pairs. The response is parsed and rendered into 30 slides — 10 trivia facts plus 10 question/answer pairs (20 slides). The flow: import json import urllib.request def generate_trivia(metadata): api_key = open("/home/user/.config/pse/api.key").read().strip() prompt = f"""Generate trivia about "{metadata['title']}" ({metadata['year']}). Director: {', '.join(metadata['directors'])} Cast: {', '.join(metadata['cast'][:5])} Return JSON with: - 10 trivia facts (behind the scenes, connections, legacy, etc.) - 10 Q&A pairs (movie trivia questions with answers) """ payload = json.dumps({ "model": "claude-sonnet-4-20250514", "max_tokens": 6000, "messages": [{"role": "user", "content": prompt}] }).encode() req = urllib.request.Request("https://api.anthropic.com/v1/messages", data=payload) req.add_header("Content-Type", "application/json") req.add_header("x-api-key", api_key) req.add_header("anthropic-version", "2023-06-01") resp = urllib.request.urlopen(req, timeout=30) data = json.loads(resp.read()) trivia = json.loads(data['content'][0]['text']) # Render each item as a slide image with Pillow for i, item in enumerate(trivia): render_slide(item, i, metadata['title']) Each slide gets rendered with a vintage cinema aesthetic — dark background, golden category headers, cream body text, decorative borders. Question slides use blue headers, answer slides use green. The trivia generation is opt-in — I have a toggle script that creates/removes a flag file (/tmp/pse_trivia_enabled). The generation script checks for this file and skips if it's not there. A Kodi notification confirms the toggle state. Runtime: About 8-10 seconds for the API call plus slide rendering. A progress notification shows during generation so you know it's working. Tips for ImplementationCIFS/Network Share Gotcha: If your PSE content lives on a network share, Pillow's FreeType library cannot load fonts from CIFS mounts. Always copy fonts and templates to /tmp/ before opening them with Pillow. Bytecode Cache: Kodi caches compiled Python as .pyc files. Every time you edit experience.py, delete the cache and restart Kodi or your changes won't take effect. PSE Updates: When PSE updates, experience.py gets overwritten. Keep a backup of your modified version and re-apply the hook after updates. The hook is small enough that re-applying takes 30 seconds. Testing: You can test your generation scripts independently from the command line: echo "Alien" > /tmp/pse_feature_title.txt echo '{"title":"Alien","year":1979,"genres":["Horror","Sci-Fi"],"directors":["Ridley Scott"]}' > /tmp/pse_feature_metadata.json python3 /path/to/your/script.py Then check the output directory for your generated slides. Keep Scripts Fast: Since subprocess.call blocks PSE initialization, your scripts need to finish in a reasonable time. The title card takes ~1.4 seconds, the AI trivia takes ~8-10 seconds. Much longer than that and the delay before the sequence starts becomes noticeable. Sequence SetupMy PSE sequence order: Slideshow — Tonight directory (dynamic title card, 30-60 second duration) Slideshow — Trivia directory (AI trivia slides, 10 second per slide) Trailer modules Audio Format Bumper Action — Enable refresh rate switching Feature The two slideshow modules point at directories that get populated fresh every time by the hook scripts. Everything else in the sequence is standard PSE configuration. What's NextI'm exploring a few more ideas with this system: dynamically selecting trailer folders based on the feature's genre/decade, generating "cinema history" slides that tie the film to its cultural moment, and creating custom intermission cards for double features. The hook pattern is flexible enough that any script with access to the movie metadata can feed content into the sequence. If anyone builds on this or has questions about the implementation, happy to help. The hardest part was figuring out the right injection point — once that's solved, the rest is just Python scripting.

Preshow theater intros

Tue, 17 Feb 2026 22:06:06 +0000

We work with a variety of intro templates that can be found on various stock sites, like Envato. They typically require apps like Adobe After Effects to render custom content into the template, but it's quite effective. You can search for a variety of known studio intros or work with logo reveals that are completely different from those found at the head of major motion pictures. There are also some people who you can pay to have intros built in the style of known studio intros. We couldn't find a Marvel style template for a student film festival, but found someone who had the ability to make one for us for about $50. It was incredibly similar to the comic book style Marvel intro - the kids were confused at first as this Marvel style intro began and then they lost their minds when they realize it was the title of the festival. They are out there. Just need to Google ;-)

Feature request: Slideshow Loop

Tue, 17 Feb 2026 21:57:46 +0000

That's a good catch. I don't think there is a volume control for slideshows. All of the volume controls are in playbook in module volumes. I'll add slideshow controls there. Thanks for letting me know about this.

Feature request: Slideshow Loop

Tue, 17 Feb 2026 20:43:03 +0000

@Matt - Regarding slideshows, we can't seem to figure out what commands the volume of the module. There isn't a volume setting in the module itself and there isn't a volume setting in the Playback section of the app settings. Thought maybe it was tied to Trivia, but it's not. Seems to come through at about 50% volume or something lower than 100%. If this isn't directly settable in the app, is this something we can manually "tweak" in the app folder outside of Kodi?

Feature Request: Support for Relative File Paths in PreShow Experience

Sat, 14 Feb 2026 23:12:06 +0000

Hello, We’ve run into a portability issue when creating sequences in PreShow Experience on a desktop or non-media-server player. Currently, PreShow stores all media references as absolute file paths tied to the original machine. This means that if we move a PreShow project folder to another server or workstation, the sequence breaks because the media paths still point to the original device location. This creates unnecessary extra steps when deploying sequences for: Short films Theatre intros Touring productions Multi-server installations Instead of simply moving the PreShow project folder and relinking a single base directory, we have to manually update or recreate paths due to the absolute references. Requested FeatureIt would be extremely helpful if PreShow could support relative file paths for media content. For example: When setting a content directory in PreShow, the software would treat that folder as the base path. All media within the sequence would then be referenced relative to that base folder, rather than to an absolute system location. When moving the project to a new machine, we would only need to update the base content directory once. BenefitsImproved portability between systems Easier deployment to media servers Cleaner project structure Reduced setup time for touring or distributed environments Fewer broken media links This enhancement would significantly streamline workflow and reduce errors when moving projects between machines. Thank you for considering this request.

Preshow theater intros

Fri, 13 Feb 2026 22:24:53 +0000

I am a bit lost on how to do even basic surround in Davinci Resolve. i was able to doa faux oen by duplicating the fronts to the back but if there is an AI tool out there i might do that. When i get to that point though, i may review some youtube videos on resolve. There has to be an easy way to sort of program sound.

Green The following Preview - Does anyone have or know where to get them

Thu, 12 Feb 2026 04:36:58 +0000

Those are Called MPAA ratings. The classic ratings version can be found here https://preshowexperience.com/files/file/94-mpaa-classic/ There's different styles you can download to fit your taste.

Preshow theater intros

Tue, 10 Feb 2026 19:05:24 +0000

I was working on a customized Intro with Davinci Resolve. The mixing of the atmos sound was quite time consuming, why I lost motivation at some point. But I will give it another try and add a voice and test, if it still sounds super cheap. If not, I will maybe be motivated to continue on it

Preshow theater intros

Mon, 09 Feb 2026 19:57:36 +0000

Yea but just the simple stuff Warner Brothers and other studios intros changed to my theater name , simpler stuff like that

Trivia Metadata testing v.1

Mon, 09 Feb 2026 15:30:39 +0000

In my first test, the system worked the way I initially intended: it grouped trivia by decade, rating, and genre, and selected content based on those matches. That part was fine and worked as expected for testing. However, once I started adding more detailed movie-specific trivia, it quickly became clear that this approach was pretty boring in practice. The system always chose the “best” match first, and because many movies have large trivia packs, it would end up playing all the trivia for a single movie before moving on to the next best match, and then the next, and so on. To fix that, I changed the behavior. In the current version, the system plays a slide from the best-matching folder, then skips that folder for a random number of slides (3–6). It then does the same with the second-best folder, and continues down the list. This creates the feel of randomness, while still giving higher priority to more relevant content. I had forgotten that I made this change until I went back and reviewed the code, which is why the behavior didn’t line up with how I described it, and wasn't what you were expecting.

Preshow theater intros

Mon, 09 Feb 2026 14:51:18 +0000

Currently working out a series of videos for theater intros. Using Unreal Engine. Slow going but I hope to make one for every genre. At least I have one. I customized the Regal Cinemas 1990's roller coaster to my theater. Used some AI to change some wording in the narration and Davinci resolve to edit the text on the marque scroller. Gruelling work as unreal Engine is hard to learn. Nothing is straight forward. Everything is a task. But I hope in the end it looks great. Doing an old West town for westerns. A spooky gothic castle on a hill for horror. I plan to do a parody or homage to the Disney Castle for family movies. But I really like watching the playlists on YouTube that feature simple CGI that reminds me of bowling alley animations. That is probably more easily done now with Unreal. I will probably sparingly use AI but for home theater intros it seems tempting. But AI programs seem expensive. Anyone else have customized intros?

Trivia Metadata testing v.1

Sat, 07 Feb 2026 00:21:34 +0000

After testing more i found out that only one works at a time if it has no rating the year will work if no ratings or year the genre will work 🤔

Trivia Metadata testing v.1

Fri, 06 Feb 2026 23:51:00 +0000

Ok after heavy testing, rating slides work flawlessly every time , But genre and year never do just random slides even tho the log shows them scoreing correctly.

What do you think is the scariest movie?

Mon, 02 Feb 2026 02:30:24 +0000

Subjective, yes. But here's a few "scary movies": The Conjuring 1 and 2 The Ring Insidious Presence The Exorcist Poltergeist