Matt
Administrator
-
Joined
-
Last visited
Everything posted by Matt
-
US Patriotic Holiday Bumper Set View File 4K US patriotic holiday bumper set with surround sound Videos include: 3D Intro 3D Outro Countdown Courtesy Feature Intro Feature Outro Intermission Theater Intro Theater Outro Trailers Intro Trailers Outro Trivia Intro Trivia Outro Sponsors PreShow Experience (4th of July, Memorial Day & Veterans Day) Submitter Matt Submitted 06/30/2023 Category PreShow Videos -
How are you launching your action file? Do you have it in your settings or in a sequence? I'm trying to get home assistant set up here so that I can help out.
-
Confirming this bug. Thanks for letting me know. It has now been reprogrammed to keep track of what is already disabled and to return the sequence to the state that it was prior to the preview.
-
Time for the next milestone release for Kodi 21 "Omega". This is our second Alpha release for this cycle. 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. Over the last couple of months we've merged 120 pull requests - fixing issues, adding features, and improving Kodi. So... what's actually changed? Build/Dependencies Apple platforms are now all built using newer version of Xcode (14.2) and the relevant SDKs. Thanks to a combination of a new M1 Mac mini hardware donation from long time supporter of the project, MacMiniVault.com, and also the Kodi foundation purchasing a second M1 Mac mini, we have been able to decommission our ageing Intel Mac mini's that have been in use for a long time. Building on Windows now uses the system curl executable instead of our formerly bundled (ancient) wget executable. Improvements to dependency building have been made by @lrusak to make the downloading/hash checking more robust. Estuary Improvements to the seek window timeouts have been made to more correctly disappear after appropriate timeouts. Fix visibility of 'next recording' label in PVRTimers was made by @ksooo. FFmpeg One of our newer team members, @neo1973 , has made some cleanups and fixed some crashes in our ffmpeg side data usage, as well as other improvements with our ffmpeg API usage. General Improvements made to handling of movement keys (e.g. PageUp, Down, Home, End) in certain lists such as Settings. @rmrector has been endeavouring to improve image cache handling for GUI items. We look forward to the further work he has in the pipeline to improve the cache handling. Extraart configurations in advancedsettings.xml for Kodi 18 will no longer be migrated to the new GUI settings when upgrading. If you had meaningful configuration there, check that the artwork settings in the GUI match your preferences. @CrystalP extended the navigation history to track the line number of the selected item so that it can be restored when the item disappears from the list, instead of resetting the selection to the top of the list (usually the ..) after the end of playback or changing the watched status of an item. The generation of thumbnails was fixed for pictures in portrait orientation. The existing thumbnails in KODI_HOME/userdata/Thumbnails/* must be deleted in order to have new correct ones recreated. JSON-RPC VideoLibrary.GetEpisodeDetails now returns "studio" and "genre" added by @scott967 in https://github.com/xbmc/xbmc/pull/23112. Platform Specifics Android: @joseluismarti has continued with more cleanups and improvements to the Android codebase. Each improvement makes things easier to manage, and is greatly appreciated. @fritsch has been able to make further improvements to AudioTrack to handle hardware that has sinks that get "stuck". Its always a fine line making changes in the Android world, as the multitude of hardware vendors have widely varying implementation qualities of the standard Android APIs. Linux: @lrusak has added the ability for users to select the audio backend with a command line switch when starting Kodi. This also allows seeing with which enabled audio backends Kodi was built. For more information check out the following PR. macOS: The minimum OS required for Kodi on macOS is now Mojave (10.14). This was done to allow the project to continue using more modern C++ 17 features. macOS Mojave was released on 24th September 2018 and hardware supported can be seen at Apple.com. @enen92 has continued to further improve what is known as "Native windowing" for our macOS codebase that will eventually lead to a formal Apple Silicon version. Improvements to window resizing, menu's, window blanking, improved multiple monitor handling and more. For developers, Kodi can also now more easily be run from Xcode without having to alter schemes. @ksooo has now correctly added Speechrecognition entitlements for Apple platforms (including iOS/tvOS) which fixes a crash when microphone usage was triggered. Support for HiDPI resolutions, such as those marketed as Retina displays, has been introduced in the native windowing version. This enhancement allows Kodi's graphical user interface (GUI) to showcase higher pixel densities, resulting in a sleek and polished appearance on modern Macs. webOS @sundermann and @craigcarnell have made further improvements to the new webOS platform. Screensaver support has been added, along with audio sink improvements and updates to codec hardware support. Windows: Minimum Windows supported version has been raised to Windows 8.1. @CrystalP and @thexai have made a number of improvements to windows HDR/SDR/HLG display including tonemapping and hardware DXVA support for a number of combinations of those media types. @thexai implemented support for "Video Super Resolution" for Nvidia (RTX ) and Intel (ARC) compatible hardware. Please note, we obviously cant test all combinations of hardware, so don't expect this to work for every combination under the sun. Give it a try and report any issues WITH debug logs. Bump to libdav1d to version 1.20 should improve AV1 playback support for windows platforms. Python A fix for a regression was made by @lrusak that puts addon paths at the front of the system paths. This fixes addons using system modules instead of potentially customised Kodi modules of the same name. This mostly affects Linux based systems. If you love to live on the bleeding edge of new, you can get Alpha 2 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. For a more targeted look at the changes made since v21 Alpha 1, you can see those changes here. View the full article
-
Unfortunately PreShow isn't compatible with streaming services.
-
The loading icon is controlled by your skin. Here is a thread about it: Here are some skins set up for PreShow: https://preshowexperience.com/files/category/7-skins/
-
Glad you got it working. Let us know if you have any other issues that you need help with.
-
There is not. You would need to use CinemaVision for anything below Kodi 19. -
@TRJCan you redownload and reinstall PreShow and see if it changed anything. Sequences need to have the .pseseq extension and I'm not sure why yours don't. You can manually rename the file for now to see if that works.
-
Sort of. I removed the broken code from the previous version related to the external database. I didn't update the changelog since this is just a short term fix.
-
Here's my first pass at the guide for action files: Anything that works in CV should also work with PreShow.
-
To create an Action File, follow these steps: Create a new text document. Input the command that you want to use. Save the file as <file_name>.action in the Actions directory of your PreShow Experience content folder. You can also find pre-built Actions for different home automation solutions in the Downloads section of our website. If you have any improvements or new Actions that you create, please share them with us. We can host them on the site for others to use. Action Files use the following Syntax, Methods, and Protocols: Syntax: Use "#" at the beginning of a line to ignore the contents of that line. Use "<protocol>://" at the beginning of a line to specify the protocol for that command. Use "<method>:" at the beginning of a line to specify the method for that command. Protocols: Currently supported protocols: "http://" or "https://": Passes JSON commands via a URL. "addon://": Runs a script or add-on. "command://": Runs a command or application at the OS level and pass arguments. "module://": Runs a Python script with a main() method that is imported and called. "python://": Run a Python script. "sleep://<milliseconds>": Pauses the Action File for the specified time in milliseconds. Methods: Currently supported methods to communicate with the target device or application: "HEADERS:": Sends header information. "POST:": Sends a POST command to create information. "PUT:": Sends a PUT command update information. "DELETE:": Sends a DELETE command to delete information. Actions in Action Files can be single-line or multiple-line commands. Blank lines are used to separate commands. The first line of any Action is the Execution Line. The line following the Execution Line can be a Headers Line or a Data Line. Headers Line: Specifies the content type or any other headers. Prefix the line with "HEADERS:". Data Line: Used to pass arguments or data. Prefix the line with the desired Method ("POST:", "PUT:", or "DELETE:"). If no method is specified, the default method used is POST. Examples Example 1: Sending a JSON command via URL # This is a comment http://api.example.com/endpoint?param1=value1¶m2=value2 Example 2: Running a script or add-on by add-on ID with arguments addon://1234567890?arg1=value1&arg2=value2 Example 3: Running a command or application at the OS level with arguments command://path/to/executable --option1 value1 --option2 value2 Example 4: Running a Python script with a main() method that is imported and called module://path/to/script.py Example 5: Calling a normal Python script via the operating system python://path/to/script.py Example 6: Adding a sleep (pause) of 500 milliseconds before moving to the next action sleep://500 Example 7: Sending a POST command with data and headers to activate a Home Assistant Webhook https://YOUR_DNS_HOSTNAME.com/api/services/scene/turn_on HEADERS: {"Authorization": "Bearer LLATStringOfRandomCharacters", "Content-Type": "application/json"} POST: {"entity_id": "scene.movie_start"} Example 8: Sending a PUT command to change Hue brightness http://<hue-bridge-ip>/api/<hue-bridge-user>/groups/<hue-light-group>/action PUT:{"on":true,"bri":40,"transitiontime":10} Example 9: Sending a PUT command to turn off Hue light http://<hue-bridge-ip>/api/<hue-bridge-user>/groups/<hue-light-group>/action PUT:{"on":false,"transitiontime":30} These examples demonstrate various use cases and combinations of syntax, methods, and protocols in Action Files.
-
Yes, you can use webhooks. I don't use home assistant, but I'll see if I can find someone else to offer suggestions.
-
I can confirm there's a write error with it.
-
I'm not sure exactly what you are asking for. The context is built into the main addon. Let me know if you are asking about something else.
-
It needs to be tested by others, but I think I have this fixed. If so, it will be in the next version.
-
Custom horror movie R rated bumper -
Horror Movie R Rated Bumper View File Custom horror movie R rated bumper Submitter Matt Submitted 05/11/2023 Category PreShow Videos
-
This module is only recommended for advanced users. Action modules allow you to add dynamic functionality to your sequence, including changing settings in Kodi or interacting with your home automation. Action scripts must be configured outside of the sequence editor and saved in your action folder of your PreShow sequence. More information about creating action files can be found here: -
This modules allow you to set up loops in your sequences. This you to set loops in your sequence or skip content before your first or last movie in your queue. Settings for this module include: Direction - Back or Skip Number of modules - Number of modules to jump back or forward Condition - Set the condition for the loop Duration Time of Day Number of loops Feature queue is full (This requires your to have your feature count set to greater than 1.) Feature queue is empty -
This module includes your feature film and ratings, if you choose to show them. Settings for this module include: Count - The number of movies you want to show. Rating Bumper - You must have ratings content in your content folder to display these. Options include: Default - Use whatever you have selected in your PreShow settings. Video - Show only videos from your ratings bumper content folder Image - Show only images from your ratings bumper content folder None - Don't show ratings Ratings Style Selection Default - Use whatever you have selected in your PreShow settings. Random - Randomly pick from any files that you have in your ratings bumper content folder Style - Creates an additional option of Rating Style Ratings Style -Select a single folder from your ratings bumper content Volume (% of current) This module is required to be in every sequence. -
This module will display a video based on the detected audio format of your feature film. You must have audio format bumpers in your content folder to display these. Audio Format Bumpers can be downloaded here: https://preshowexperience.com/files/category/5-audio-format/ Settings for this module include: Method - The default is Auto select from source. Other options include Choose format and Choose file. If file is selected, a new option of Path will appear below File - Select the video that you would like to play Fallback - You can choose a file or format here in case your video doesn't match any of existing audio bumpers. Format - Select a default format folder to be played Play 3D if 3D Feature - Select a default single video file to be played. Volume (% of current) - Sets the volume for the audio format bumpers Dolby Atmos and DTS:X are not currently detected in Kodi. In order to properly trigger those animations, your movie file name must include "atmos" or "dtsx" to show the appropriate video. -
Module: Trailers The settings for the Trailers module include: Source - Select your trailer source from the following options: Content Source filter (scraper) - Select from the scrapers selected in your settings. Scrapers include: PreShow Trailers Folder - These are any trailers that you have in the Trailers folder in your PreShow content directory. Kodi Database - These are YouTube trailers for movies on your system Apple iTunes - iTunes trailers from the apple site.. The Movie Database - These are YouTube trailers from TMDB. Content order - Select how your content is selected: Newest Random Directory Path - Select a folder on your system that may contain multiple files to be selected randomly Single File File - Select a single trailer file to show. Count - The number of trailers to be shown. Rating Limit - Options include: None - Allows any trailers of any ratings Max - Limit the ratings to a selected in the Max setting below Match Feature - Filters trailers with a rating that matched the feature film Match feature genre - Selects trailers with one of the same genres as the feature film Filter for 3D based on feature - Will play 3d trailers, if available Quality - select your preferred resolution of 720 or 1080 Volume (% of current) - Sets the volume for trailers -
Trivia Packs can be downloaded here: https://preshowexperience.com/files/category/6-trivia/ Trivia is a set of images in a folder that is either grouped as Question and Answer or Facts. Question slides contain multiple images. A question image and answer image are required. Up to 9 clues can also be added. Filename requirements Question images must end with _q. Answer images must end with _a. Clue images must end with _c(#1-9). Fact images can't end with _q, _a, or _c#. Here is an example ..\Trivia Pack Name\PackNameFact1.jpg ..\Trivia Pack Name\PackNameFact21.jpg ..\Trivia Pack Name\PackNameQA1_q.jpg ..\Trivia Pack Name\PackNameQA1_c1.jpg ..\Trivia Pack Name\PackNameQA1_c2.jpg ..\Trivia Pack Name\PackNameQA1_c3.jpg ..\Trivia Pack Name\PackNameQA1_c4.jpg ..\Trivia Pack Name\PackNameQA1_a.jpg ..\Trivia Pack Name\PackNameQA2_q.jpg ..\Trivia Pack Name\PackNameQA2_c1.jpg ..\Trivia Pack Name\PackNameQA2_c2.jpg ..\Trivia Pack Name\PackNameQA2c3.jpg ..\Trivia Pack Name\PackNameQA2_c4.jpg ..\Trivia Pack Name\PackNameQA2_a.jpg Trivia must be contained in a subfolder within your PreShow Trivia content folder. Files in the root PreShow Trivia content folder will not be scanned. Module Settings The settings for your trivia module are primarily the same as the PreShow Experience Trivia settings. You can use the defaults or select unique settings per sequence is desired. Format - Select between slide or video. You need to have the appropriate files in the trivia folder of your PreShow content. Select Trivia - This is the one option that isn't in your basic settings. Default - randomly select trivia from all the folders in your Trivia content folder. Directory - Reveals Directory (in trivia folder) below. Directory (in trivia folder) - Select the trivia folder in your content settings that you want the sequence to pull from. The sequence will only select files from this folder. It currently allows you to select any folder. If you select a folder that's outside of your trivia folder the sequence will not play trivia. Duration (minutes) - Set how long you would like your trivia sequences to run. Question duration (seconds) - Set how long you would like your trivia questions to be on screen. Clue duration (seconds) - If a pack includes them, set how long you would like your trivia clues to be on screen. Answer duration (seconds) - Set how long you would like your trivia answers to be on screen. Single duration (seconds) - If a pack includes them, set how long you would like your trivia single slides to be on screen. Transition - Transition between slides. Options include fade, slide up, slide down, slide right and slide left. Transition duration (milliseconds) - Set the transition time between slides. Music Music - Select your music source if you want to play music during your trivia. Options include: None - No music will be played Content - This will play from the music folder in your PreShow content folder. Directory - This will play from the folder selected below in Music: Path. File - This will play the track selected below in Music: File. Music: Path - Select a folder that contains your music that can be anywhere. Music: File - Select a single file to play with your music. Trivia Controls Here is a list of controls to navigate your trivia slides. Space - Pauses trivia Left Arrow - Jumps to the previous trivia slide Right Arrow - Jumps to the next trivia slide Up arrow - Jump 3 questions/facts back Down Arrow - Jump 3 questions/facts forward Page Up - Fades out the currently trivia image and music and jumps to the next module Pade Up (Double Click) - Jumps to the next module immediately with no fade Page Down - Jumps to the previous module -
Video Bumpers are probably the module that will appear the most in any sequence. The module plays videos from your PreShow content folder. You must have video bumpers in your content folder to display these. Video bumpers can be downloaded here: https://preshowexperience.com/files/category/2-preshow-videos/ Settings for this module include: Type - Each type represents a folder in your PreShow content video bumper folder. The types/folders are: 3D Intro 3D Outro PreShow Sponsors Commercials Countdown Courtesy Feature Intro Feature Outro Intermission Short Film Theater Intro Theater Outro Trailers Intro Trailers Outro Trivia Intro Trivia Outro Random - If set to yes, it module editor will add options for Count and Play 3D if 3D Feature. If set to no, it will add options for Source. Count - The number of videos that you want to show. Play 3D if 3D Feature - Will play 3d video, if available and feature is 3D Source - Select a single video to play Volume (% of current) - Sets the volume for the video bumper
