Jump to content

Welcome, Guest!

Be a part of CinemaVision today! Once registered and logged in, you will have access to public chat and your own private messenger, you can view and contribute guides, collaborate on the forums, review downloads, give reputation to your fellow members, contribute content and so much more. Registering is quick and completely free, so what are you waiting for?
   Sign In    Sign Up

Become a RedCarpet Club Member Today!

   Join Now

All Activity

This stream auto-updates     

  1. Today
  2. Yesterday
  3. Last week
  4. Earlier
  5. Repos: When All-in-one Can Be No Fun. For better or worse, one of the most powerful features of Kodi is the ability to extend its capabilities via addons. Key components in this are the repositories, or "repos" as they're more commonly known. They allow for quick and simple installation and upgrade of addons, but as with the whole topic they too have a darker and riskier side that many users do not consider. Before we go into details of those risks, let's first set the background by considering what a repo actually is and what it enables. As most users know, there are two main ways of expanding Kodi's functionality with addons - install from zip and install from repo. Install from zip does exactly what it says on the tin: it installs a given addon into Kodi using a zip file package that contains the addon code. That zip file may be either downloaded from the internet and transferred onto the device where Kodi is running, or it can be accessed directly over the internet via an added source (most commonly through the Kodi file manager). This route is mainly intended for addon development purposes, prior to release and inclusion in a repo. There are two main issues with this approach. The first problem is that the installation is then static. If the addon is updated or modified, Kodi won't know this and any updates will need to be manually installed by the user. The second issue, however, is the one most commonly encountered by users, in that any other addons or code that the original addon depends on (that it uses or references, and requires to be installed for it to run) will not be automatically installed. Thus, for the original addon to operate and not just generate log errors or crash, all of its dependencies, both the correct packages and the correct versions, need to be manually located and installed separately. So, What's a Better Way? Using a repo can solve both of these issues. A Kodi repo contains links to the current (and, commonly, also older) versions of the addon plus any required dependencies. So it acts as a "one stop shop" to install the given addon, with the bonus that it can be done via the Kodi GUI using the Install from repo option. With the exception of the official Kodi repo (which comes built into the Kodi core code), the only install from zip that is required is the original one to install the repo itself. The real power of the repo, though, is that when the addon author updates their addon and pushes that new version to the repo (whether the official one or their own third-party one which the user has installed), then Kodi will see that the update is available and can either offer the update or just update it automatically, depending on configuration. So, with minimal or even no user effort, addons can be quickly and easily maintained, and distributed, keeping all user devices up to date. Sounds Great - What's the Catch? That update functionality is where the potential risks come into play, however, especially for the common third party "all-in-one" repos (containing addons from multiple authors) that can be obtained from various internet sites and sources. Currently, if a newer version (with a higher version number) of a given addon is pushed to an installed repo, then the addon can be updated regardless of which repo the addon originally came from. Hence, if a malicious programmer pushes a new version of an addon (which may or may not be their own) to an installed repo, then anyone who had the original version will get the poisoned version installed onto their device instead. This is a obviously a very undesirable outcome and would lead to widespread issues if a popular addon were to be subverted. Another big issue with third-party repos is the fact the domain name might be abandoned and expire while users still have the repository installed. This could enable an attacker to later register that expired domain, effectively taking it over. They could then replace the existing addon content with malicious code. This exact scenario is a significant enough risk to have been covered in several security conferences last year, for example this one. If Only Someone Could Do Something... There have been internal Team Kodi discussions on how to manage this risk, ranging from disallowing third-party repos completely, through to only allowing addons to update from their original repo, and on to the official stance of leaving things as they are as all of this should be the user's responsibility anyway. Another issue is that there are cases which complicate any such restrictions, such as the use of testing "beta" repos for unstable versions of addons either under construction or for adding new features. This most commonly applies to skins, but also when addon authors make early or "bleeding edge" versions of new or existing addons available for public testing using this method. In the case of the built-in official repo, each and every addon submitted to it is thoroughly reviewed, examined and tested by the repo maintainers (all Team Kodi members) to ensure it poses no risk to our user base. There are also limitations placed on addons - such as containing no pre-compiled, obfuscated or executable code ("binary blobs") - all to try and stop our addon update system becoming a distribution path for malware. For third-party repos though, no such checks are, of course, performed by the team. So for each repo to be installed, the user - that means you! - should consider where it has come from, and whether they trust the author or organisation that has supplied it. Ask yourself whether they maintain such diligence over what is included in the repos they provide. For cases such as the well-known individual addon author and their beta repos containing only their own work, the risks are often minimal. The "all-in-one" style repos, though, obviously offer a significantly higher risk of problems, especially for those that just seem to scrape any and all repos that they can access on the net, often without author agreement or consent. This is why many such repos are included on the Team Kodi banned addons list, although their common inclusion of banned piracy addons would place them on the list anyway. It's also why Team Kodi offers no support for "builds" which pre-install addons or repos, as this is another common gateway to malware problems. And for those who may be under the illusion that this is just a hypothetical scenario, the stark reality is that such hijacking cases, "code flame wars" and distribution of malware-infected code have all actually occurred in the past using these exact methods. It is a genuine and real risk. Team Kodi and its members are working towards improving the addon/repository infrastructure. A lot of tools have been developed in the last few years. Some examples of this include: Kodi-addon-generator by Razzeee - simplified creation of new addons based around a standard requirements template. Kodistubs by romanvm - stubs for the Kodi Python API. Kodi-addon-submitter also by romanvm - simplify addon submissions to the repository via Travis. Addon-check (initiated/mentored by Razzeee and implemented as a GSOC 2018 project) - check addons for known problems and deprecations. In conclusion, then: before you install any third-party addon, repo or build onto your Kodi device, pause and consider whether you really trust the source you're getting it from and any repercussions that may result from that install. Tags: Addon Banned addons Education Repos tips View the full article...
  6. ELPTheater

    Kodi Leia 18.1 with 1.1.1a8 Error

    May not have anything to do with the original developer or this site. That's why I brought the reddit post here in case anyone else was interested. We will see. I don't have any idea if "Team-Kodi" is official in any capacity or not - but at least it's the first indication that I've seen that someone was interested in doing something!
  7. Fisherman456

    Kodi Leia 18.1 with 1.1.1a8 Error

    Intriguing, but it's somewhat weird that this new Kodi developer or the Kodi team never posted anything on this site so far. Of course I hope it's true and in that case an ETA would be very much appreciated.
  8. ELPTheater

    Kodi Leia 18.1 with 1.1.1a8 Error

    So here's a potentially interesting update - was surfing around seeing if there was any kind of alternative to CinemaVision and came across this recent Reddit posting from a user named "Team-Kodi" who claims that although the original developer is busy they are seeking a new developer. Anyone have an info on that at all? It may be be bogus, not sure. Here's the posting: https://www.reddit.com/r/kodi/comments/b4830q/alternative_to_cinemavision/
  9. ELPTheater

    Is CinemaVision still being developed?

    So here's a potentially interesting update - was surfing around seeing if there was any kind of alternative to CinemaVision and came across this recent Reddit posting from a user named "Team-Kodi" who claims that although the original developer is busy they are seeking a new developer. Anyone have an info on that at all? It may be be bogus, not sure. Here's the posting: https://www.reddit.com/r/kodi/comments/b4830q/alternative_to_cinemavision/
  10. gui26

    Philips hue

    Hi , In addition to my previous question, I have set a bunch of actions file following the steps described in this topic, but when I try to lunch those for test in Cinema vision, I have the following error message "This action is not set or not yet applied". You will find enclosed the files for review. Thanks in advance for your help. Guillaume Hue lights off.cvaction Hue purple.cvaction Hue red.cvaction
  11. gui26

    Philips hue

    Hi there, Very interesting topic ! I was wondering if, to make it easier, it would be possible to assign, within an action file, a light profile (or scenario, I'm not sure the correct term) previously created with the hue app ? What would be the way to write the PUT section in that case? Many thanks for your help. Thanks Guillaume
  12. Fisherman456

    Kodi Leia 18.1 with 1.1.1a8 Error

    That's why I'm thinking that we need to find another developer that is more motivated and communicative to make the fix. I don't think we necessarily need the developer that initially created the addon. The Python code is nothing unique. I think any experienced Python developer can understand what has happened, but we just need one that fixes one thing for us. It would help though if the person understands the Kodi platform.
  13. MidnightWatcher

    Kodi Leia 18.1 with 1.1.1a8 Error

    The name of the CinemaVision developer according to Github is Rick Phillips (Ruuk). I sent him an IM on Facebook a couple weeks ago but hadn't heard back. Maybe he's too busy with his new job at Plex. https://m.facebook.com/profile.php?id=1352390960
  14. Fisherman456

    Kodi Leia 18.1 with 1.1.1a8 Error

    Could we consider setting up a go fund me page to hire a developer to just make this code compliant for Kodi v18.2? I think any Python developer should be able to analyze the code and fix it for Kodi. Perhaps we can persuade one of the Kodi developers/contributors to do this for the right amount. It's not that they really have to add extra functionality to the addon, just to debug some issues. Since the code for Cinemavision is relatively small, I'm thinking that the fix might only take 3-4 days. Let's say that we compensate the developer for $30 per hour (just throwing a number), then that would equate to $960 based on a 8 hour workday. If everyone is donating $5, then we need a 192 people to get this out of the way or wait a bit until we have enough money raised.
  15. ELPTheater

    Kodi Leia 18.1 with 1.1.1a8 Error

    I've given up and moved on. Kodi 18 brings a lot of features I've been waiting for, including bluray menu management and some better support for my high-end sound system. So I don't have an interest in going backwards. Nor do I want to take the time to do this all manually. Besides, even if you were to do it with the queue list, you still lose out on the trivia and the trailers, which I suppose you could emulate, but that would require a lot of set up every time you have someone over to watch a movie. Having the trivia, the trailers, etc. is what, at least for me, made it a true "cinema" experience - and once it was set up, it was almost like magic. Everyone I ever showed it to was highly impressed. I'll keep an occasional eye here to see if this magically revives at some point, but I've already uninstalled it from my Shield. Really too bad - was the closest to the real thing...
  16. MidnightWatcher

    Kodi Leia 18.1 with 1.1.1a8 Error

    Right now I'm not using CinemaVision at all since it isn't working. I'm queuing the folder manually by navigating to the Trailers folder (I have the CinemaVision folders saved as a Favorite), then bringing up the context menu and then selecting Queue Item. I then queue the THX Eclipse bumper and my home theater intro, followed by the feature film. Once I have the playlist ready, I'll navigate to the current playlist and play from the top. It plays through each video in sequence.
  17. Fisherman456

    Kodi Leia 18.1 with 1.1.1a8 Error

    Hi, how do you queue a folder in Cinemavision? If this doesn't work, I may have to start looking into using Emby with their 'cinema' features
  18. Sledge

    can't get it to run, help?

    I paid to be a lifetime supporter of this plugin. Can we please get a fix?
  19. Sounds like something similar to MoviePoster. https://www.movieposterapp.com/index.html Other things you mentioned should be possible using action files.
  20. It would be great if you could maybe build in a feature to display a website as content (either, through linking to the .html but preferably to an IP, with support for JS, PHP, etc.). This would enable a ton customization fine-tuned to the movie being played, through setting up an external webpage with a countdown (in minutes) while maybe displaying the latest film news, playing some music in the background and would also enable things like polling the audiences for opinion. Obviously, this is just one use case example for this feature that I came up with off the top of my head, I'm sure there would be many more and probably better things this community could come up with if it could integrate websites into the addon. There should also be an option to determine in what intervals to refresh the site. I hope my gibberish made sense, and thanks for all the work you've put in this amazing addon so far.
  21. bullwinkl

    Apple Trailers issue

    Unfortunately not. Now I just have mediahuman download trailers from youtube to a 'recent trailers' folder and tell cv to play 2 randoms from there. I set up a script to delete everything in that folder to delete anything more than a month old every night.
  22. MidnightWatcher

    Kodi Leia 18.1 with 1.1.1a8 Error

    Until a working version is made available, you can manually create a playlist to mimic a CinemaVision trailer and video bumper sequence. I've been downloading movie trailers from http://www.hd-trailers.net and place them in a folder. I queue the folder, then add a short THX Eclipse bumper from https://www.demo-world.eu followed by a personalised home theater intro to the queue, then the movie. Notes: 1. If you have "Adjust Display Refresh Rate" enabled (On start / stop) then all videos in the queued playlist should be 23.976 fps so that there are no delays between videos of different frame rates (especially for projectors). All movie trailers are at 23.976 fps but I had to use Handbrake to re-encode the THX bumper and my HT intro bumper (they were both 24.0 fps instead of 23.976). It's also a good idea to enable the "Delay After Change Of Refresh Rate" in the System > Display settings to match the time you'll need for your display device to catch up with the beginning of the first movie trailer. 2. I use the Rapier skin, which can hide the on screen seek bar in between videos (System > Skin > Configure Skin > Media > Hide Seek Bar OSD During Fullscreen Playback). 3. To hide the Busy dialog during fullscreen video playback, manually replace line 12 in DialogBusy.xml with: <visible>!Window.IsVisible(fullscreenvideo)</visible> Note -- If the skin receives an update, this could get overwritten so I've disabled automatic updates for the skin and will manually update when needed to know I may need to manually update the DialogBusy.xml again. 4. I have Philips Hue lighting and relied on action files to control the lights. This now has to be done manually. You can create scenes in any hue app (I have one for Normal Lighting and one for Trailers, then of course one to turn off the lights as the movie begins). The official Philips Hue app doesn't allow me to adjust the transition time (I like a 5-second transition between each scene) so I had to find another app. I miss the movie trivia and I'd like to have a one or two second gap in between the videos on the playlist, but until we have CinemaVision working again, it's the next best thing.
  23. Matt

    Kodi Leia 18.1 with 1.1.1a8 Error

    There is nothing new that I can share right now.
  24. Version 1.0.0


    2 min tribute to Stan Lee. Good bumper for your marvel/comic movies.
  25. DavetheMinion

    Is CinemaVision still being developed?

    I think most people would be very happy if any further development, added features and such were put on hold but the CV itself in it's current form would get the required bump to continue working with the latest versions of Kodi. This and 1 other addon that is seemingly simple yet cause a huge silly argument with "Team Kodi" are the reasons I've not upgraded.
  26. It's that time again. After unleashing Kodi v18 Leia into the wild, it's time to give the upcoming Kodi 19 a codename. As usual, our users suggested a myriad of names, most right up our alley, some less... erm... "appropriate". After compiling suggestions from the community thread, Facebook and Twitter, we arrived at the top 10 list: Magneto Mars Marvel Marvin Matrix Megatron Merlin Metropolis Mordor Morpheus At first glance it seems a consensual list. Nothing out of the ordinary and, with the possible exception of "Mars", all science fiction related. Next, we needed to decide what to do: follow the users' top suggestion as we've done in the past? Have team members vote to decide the name? Or maybe pick a completely different codename for Kodi v19 – Kodi "Muppet", maybe? With so many great suggestions, we decided a team vote was the way to go. So we did, and "Matrix" won the vote. And then all hell broke loose. Some team members argued we should be less predictable and geeky, that we could use some out-of-the-box thinking, choose something completely different, etc. What ensued was truly horrific. Geeks cursed each other, pizza boxes got thrown, beer was spilled, perfectly-formatted CSS insults flew, moms' basements destroyed all over the world. I mean, spilled beer! Utter madness. Bottom line – with such a great list of suggestions and a team vote, we still couldn't reach an agreement. And, for a while, we actually contemplated settling for Kodi "MultiPass". Nahh, just kidding! The users have spoken, the team has voted and, in the end, geekiness has won! Kodi "Matrix" it is. Tags: Community Updates View the full article...
  27. Mjerome2000

    Stuck in Demo Mode

    Anyone figure this out? I'm having the same issue
  28. Just when you thought we were all having a rest for Easter, here's some surprise news for you: Kodi "Leia" 18.2 is ready to roll. The sun is shining and the sky is blue here in western Europe, and we're all tied to our keyboards to bring you the latest Kodi loveliness. We're kind like that. In keeping with the 18.x maintenance release cycle, this is a bug fix release, with no real new functionality. What's worth noting, however, is how we've identified and managed the bugs this time. We've always valued high-quality bug reports, and, for this reason, for 18.x we implemented an issue template and an automated verification system in the GitHub issue tracker. This makes the bug reports more complete, and gives the Kodi developers a better chance to pinpoint problems more accurately and fix them more quickly. The aim is to solve the problem of waiting for proper full debug logs, samples and suchlike, hopefully saving a lot of time and getting issues resolved more quickly. Hopefully, you can see the results of this new process in the 18.x bug fix releases. For this 18.2 release we are also grateful to have received many code contributions from outside Team Kodi. With this help we were able to fix performance and dependency regressions in our GLES rendering path. Similar fixes were contributed for the AML platform, which really hasn't received much love over the past years. VAAPI on Intel has gained some corrections for interlaced content that toggled interlaced flags during playback, and therefore caused stutter by reconfiguring the decoder. Amongst other things, work has continued on Kodi's music experience: database access speed has been optimised as well as improved import functionality. Similarly, there have been fixes and improvements across all aspects of PVR, with a couple of particularly nasty bugs sent on their way. You can also find a huge number of improvements for the Android platform. Because of the automated Google tests done in the Play store, we were able to track down and resolve a lot of issues revealed by those "drunken monkey" tests. Beside all the fixes, we have introduced a Codec Factory (Android only) where power users can configure HW-Decoder usage in a fine-grained way. Most box sellers only provide usable codecs for formats which they use to sell content. Other format support tends to be poor, and therefore a configurable heuristic-based codec and video dimensions was added. The settings can be configured by the user in human-readable and writable XML format. More information can be found in the related pull request. We will continue to work on Leia: an 18.3 release will be drafted once we have important fixes for this release. In the meantime, development on version 19 M* has begun. We will officially announce its new codename shortly. A small spoiler: "May the force be with you - always". But this time we will switch universes (and here's another hint: you might find it on GitHub already if you know where to look...). The full v18.2 changelog can be found in our GitHub milestone. If you want to read back on what was actually changed in v18 itself, you can find the corresponding articles in the blog posts - Kodi 18, Kodi 18.1. Tags: Release Announcements View the full article...
  1. Load more activity

About Us

CinemaVision began in 2014 as a collaboration to create content for use with your home theater, offering movie trivia slides and video bumpers. It has since grown to be THE PREMIER WAY to create and customize your preshow experience. Download the CinemaVision add-on for Kodi today from the official Kodi repository, and easily create a sequence of trivia, videos, trailers, home automation triggers and more that will bring the experience of a movie theater straight to your screen!


Important Information

By using this site, you agree to our Guidelines and Terms of Use.