All Activity
This stream auto-updates
- Today
-
[Kodi News] Flirc "Kodi Edition" Raspberry Pi 4B Case
Kodi has posted a topic in News & Announcements
Yesterday the new Raspberry Pi 4B was unveiled with a revised spec that guarantees it will be super-popular with Kodi users. It brings 4K media support, faster CPUs, faster memory, faster Ethernet, faster USB, and now handles HEVC natively. It's a great update on the previous 3B+ model, and at $35 for the 1G model it's also a bargain, and we predict it will be a massively popular way to run Kodi via distro's like LibreELEC, OSMC and Raspbian. The 4B's board layout is different to previous models so upgrading (and new) users will need a new case – and what better to wrap a Pi 4B in than a Kodi Edition Flirc case! Retaining the design language that made the original case great, the Flirc case has been re-tooled to accommodate the Raspberry Pi 4B's ports and CPU placement ensuring maximum cooling efficiency. Otherwise it's the same winning formula and gorgeous design as the previous 3B/3B+ Kodi Edition case. The main body is Aluminium and designed to act as a heatsink that keeps the BCM2711 chip in your 4B cool. The top surface of the Aluminium has been mirror-polished to catch your eye, and the Kodi branded top uses soft-touch plastics so it not only looks great, it feels great too. Flirc is well into manufacturing and are offering an early bird discount of 30%. At USD $11.20 (normal price USD $15.95) that's a steal! – and orders will ship in late July. Flirc is also offering the 3B/3B+ case at the same discounted rate to clear remaining inventory. Team Kodi receives a royalty on each Kodi branded case sold – and alongside t-shirt sales it's one of the main sources of funding for the Kodi Foundation. Flirc also donate a percentage of the sale to Cancer research at the USC Norris Comprehensive Cancer Center, which plays a key role in personal back-story to Flirc. Tags: Community Updates Featured Software and Hardware Site News Galleries: View the full article... -
spelljmr joined the community
- Yesterday
-
lewisp8 joined the community
- Last week
-
Dave95 joined the community
-
neko joined the community
-
HalfNelson joined the community
-
adamnolandjones joined the community
-
ammark226 joined the community
-
ngreen10774 joined the community
- Earlier
-
Version 1.0.0
1 download
These OFLC videos can be used in conjunction with my Guide on how to add Custom Ratings/Classification Systems to CinemaVision found here: I did not make any of these videos but there were instead created by Derek McDonald 5 years ago for his own personal home theater. These can be found on YouTube here: https://www.youtube.com/watch?v=xsZbAhyXcCU&list=PLZ4Ym5N7tLErQFenUVmLruf2zjnrgWwmR&index=15 I'm reposting this here in the hopes CinemaVision users can benefit from them and these videos can reach a wider audience who will benefit from its intended use as opposed to a YouTube video getting lost to the void. There isn't a bumper for E, nor is there one for CTC because films aren't actually classified as CTC, only trailers are. All videos have been downloaded at the highest quality, and are all based on a (no longer available) VideoHive template found here: https://videohive.net/item/shapes-logo-reveal-intro/8073694 -
Adding Custom Ratings to CinemaVision CinemaVision Version: 1.1.0 For the past year or two, I've been enjoying CInemavision but have always been very disappointed that the rating systems included are only for those in the US and a few countries in Europe. I've asked multiple times for the Australian rating system to be included and I've been told it's pretty easy but it hasn't really gone anywhere, which is fair enough considering I don't think it's fair for the devs to be focused on every country but instead, it should be a community effort. Upon digging through the add-on files and figuring out (to the best of my ability) how CInemavision includes a countries rating system, I've managed to add the OFLC to my copy of Cinemavision and I thought I'd document how I went about it in the hopes others who might be hoping to introduce their own rating system into Cinemavision can do so. Or, you know, improve on whatever I've managed to do. In any case, here's what I did to introduce the OFLC (Australia's rating system) into CInemavision. Requirements: Text Editor (Notepad++ Recommended) Custom Bumpers for your rating system (Either from the 'files' section or by creating your own) Movie Scraper Settings properly set to scan for your rating system (eg. TMDB classification set to your country code) Resources: Country Code Lookup: https://laendercode.net/en/2-letter-list.html Australian Classification Youtube Playlist (Try to find something similar for your country!): Kodi Addons Directory: Windows: %APPDATA%\kodi\addons\ MacOS: /Users/<your_user_name>/Library/Application Support/Kodi/addons/ Linux: ~/.kodi/addons/ Other: https://kodi.wiki/view/Userdata#Location_of_the_userdata_folder (replace 'userdata' with addons) CinemaVision Location: addons/script.cinemavision/ NOTE: MAKE A BACKUP BEFORE PROCEEDING. I AM NOT RESPONSIBLE FOR ANY DAMAGE OR ERRORS INCURRED Step 1: Creating the XML Reference Sheet Inside "lib/cinemavision/rating_systems/" we can see a list of .xml files that act as reference sheets. The is the BBFC as an example: <system name="BBFC"> <region>GB</region> <rating value="185">R18</rating> <rating value="180">18</rating> <rating value="150">15</rating> <rating value="125">12</rating> <rating value="120">12A</rating> <rating value="80">PG</rating> <rating value="0">U</rating> <rating value="0">Uc</rating> </system> The name parameter holds the classification name, with the region holding the countries region. After that, within the <system> tags, we create a new <rating> tag for every classification within our system. You'll also notice the value parameter within every <rating> tag. This is (to the best of my knowledge) what CinemaVision uses to determine the severity of the rating because it differs from country to country. For example, both 'U' and 'Uc' are 0 because they are different classifications but are both 'Universal' with the latter being specifically for children. In creating your own, you can adjust these values however you want, but I found it helpful to compare the values against the MPAA's values. In fact, it looks like the values represent the "minimum age" with a 0 at the end. The MPAA doesn't have a .xml file because it's hardcoded within 'ratings.py' but we can see there that the values are as follows: MPAA Values Rating Value G 0 PG 120 PG_13 130 R 160 NC-17 170 NC 1000 Note how PG-13 is '130' and NC-17 is '170', they represent what the rating states the minimum (or suggested minimum age) is. It doesn't really matter how closely they match the MPAA system but it can be a good point of reference when incorporating your own rating system into CInemaVision. For the most part, Australia's rating system is pretty similar to the MPAA, and this is what I came up with the OFLC: <system name="OFLC"> <region>AU</region> <rating value="180">R18</rating> <rating value="150">MA15</rating> <rating value="120">M</rating> <rating value="80">PG</rating> <rating value="0">G</rating> <rating value="0">E</rating> </system> E and G are both 0 because E films are 'Exempt' and G are 'General' so they both have no 'minimum' age. Using this as a template, you should have a pretty good idea of how to go about creating one of your own. When you're done, save the .xml as the classification name within the 'rating_systems' folder (in my case, OFLC.xml). Step 2: Adding references within the Python Code Wait, don't leave! I promise this isn't as scary as it sounds! Hear me out. What we need to do is go into 3 python files and add references to whatever classification we are adding. The first of which is located within the 'lib/cinemavision' directory, wherein we found 'rating_systems'. You'll notice a file called 'ratings.py' and that's what we need to edit, so open it in Notepad++ or your code editor of choice. All that we need to worry about is this little dictionary at the top: COUNTRY_SYSTEMS = { 'DE': 'FSK', 'GB': 'BFS', 'BR': 'DEJUS', 'ES': 'ICAA', 'US': 'MPAA' } It should be pretty self-explanatory - there's a country code and the corresponding classification system. Kodi actually uses these country codes internally instead of the system name, and it's here where CinemaVision links them up. Kodi uses the 'ISO 3166-1 alpha-2' convention (bit of a mouthful) but if you aren't sure, head up to the resources tab at the top of this post to find a lookup table for your country. As you might have guessed, it's pretty simple to add a new entry to the list. Make sure you add a comma to what came before and match this template: "country_code" : "classification_name" And that's it! Save ratings.py and we can move on. So my current COUNTRY_SYSTEMS dictionary looks like this: COUNTRY_SYSTEMS = { 'DE': 'FSK', 'GB': 'BFS', 'BR': 'DEJUS', 'ES': 'ICAA', 'US': 'MPAA', 'AU': 'OFLC' } The second file is just as harmless. In the same 'lib/cinemavision' directory, open 'content.py' and in the UserContent class you should see the 'Ratings Bumper' section: ('Ratings Bumpers', ( 'MPAA', 'BBFC', 'DEJUS', 'FSK', 'OFLC' )) Same as before, simply add a comma to the last entry and in single quotes add the classification name. Save, and we can move on the slightly harder part, but also the last of coding! Go back a directory so we're just in the "lib" folder, and you'll see 'cvutil.py'. Open that up, and do a search for the "RatingParser" class. It should be on line 393, but this is what we're looking for: class RatingParser: SYSTEM_RATING_REs = { # 'MPAA': r'(?i)^Rated\s(?P<rating>Unrated|NR|PG-13|PG|G|R|NC-17)', 'BBFC': r'(?i)^UK(?:\s+|:)(?P<rating>Uc|U|12A|12|PG|15|R18|18)', 'FSK': r'(?i)^(?:FSK|Germany)(?:\s+|:)(?P<rating>0|6|12|16|18|Unrated)', 'DEJUS': r'(?i)(?P<rating>Livre|10 Anos|12 Anos|14 Anos|16 Anos|18 Anos)' } RATING_REs = { 'MPAA': r'(?i)(?P<rating>Unrated|NR|PG-13|PG|G|R|NC-17)', 'BBFC': r'(?i)(?P<rating>Uc|U|12A|12|PG|15|R18|18)', 'FSK': r'(?i)(?P<rating>0|6|12|16|18|Unrated)', 'DEJUS': r'(?i)(?P<rating>Livre|10 Anos|12 Anos|14 Anos|16 Anos|18 Anos)' } It's...a little intimidating, but it's really not that bad. Basically, this is a 'regex' command that is designed to sort data and in this case, it's parsing ratings for every country. It follows the same structure that we've seen thus far with the classification name on the left, and the 'data' or 'result' on the right of a colon. All we really need to worry about is the result side of the dictionary, so I'll show you what I came up with for the OFLC and how I got there: SYSTEM_RATING_REs: 'OFLC': r'(?i)^(?:AU)(?:\s+|:)(?P<rating>E|G|PG|MA15|R18)' RATING_REs: 'OFLC': r'(?i)(?P<rating>E|G|PG|MA15|R18)' They're the same except 'SYSTEM_RATING_REs' looks for the country code whilst 'RATING_REs' doesn't. For your country, all you need to do for SYSTEM_RATING_REs is fill in your classification system, change the country code and add all of your ratings after the <rating> tag, with every rating having a | in between. and in RATING_REs, do the same except without the country. My recommendation here is to duplicate one of the lines that are already there, add an extra comma and replace the relevant information. I copied the BBFC and used that as a reference but it really doesn't matter, they all follow the same format so long as your country code and classifications are in there, next to your classification system. So this is how it should look, with the relevant information filled in of course: SYSTEM_RATING_REs = { # 'MPAA': r'(?i)^Rated\s(?P<rating>Unrated|NR|PG-13|PG|G|R|NC-17)', 'BBFC': r'(?i)^UK(?:\s+|:)(?P<rating>Uc|U|12A|12|PG|15|R18|18)', 'FSK': r'(?i)^(?:FSK|Germany)(?:\s+|:)(?P<rating>0|6|12|16|18|Unrated)', 'DEJUS': r'(?i)(?P<rating>Livre|10 Anos|12 Anos|14 Anos|16 Anos|18 Anos)', 'CLASSIFICATION_SYSTEM': r'(?i)^(?:COUNTRY_CODE)(?:\s+|:)(?P<rating>EACH|SEPERATE|RATING)' } RATING_REs = { 'MPAA': r'(?i)(?P<rating>Unrated|NR|PG-13|PG|G|R|NC-17)', 'BBFC': r'(?i)(?P<rating>Uc|U|12A|12|PG|15|R18|18)', 'OFLC': r'(?i)(?P<rating>E|G|PG|MA15|R18)', 'FSK': r'(?i)(?P<rating>0|6|12|16|18|Unrated)', 'DEJUS': r'(?i)(?P<rating>Livre|10 Anos|12 Anos|14 Anos|16 Anos|18 Anos)', 'CLASSIFICATION_SYSTEM': r'(?i)(?P<rating>EACH|SEPERATE|RATING)' } Save that and, phew, done! That's all of the coding out of the way, and we're almost done too! Just one more thing... Step 3: Adding Classification into UserData After all of this, you'd think we'd be done. And I did too, but for the longest time I couldn't figure out why when I went to select OFLC in the CinemaVision settings it wasn't there. That's because the options are actually generated in a completely different directory. Go right out, back into the Kodi base directory, so out of addons and go to the following directory: kodi_base/userdata/addon_data/script.cinemavision/settings/ratings Here, you'll see a folder of every classification. And inside every folder is null files with a name following this format: CLASSIFICATION_SYSTEM.RATING So we need to create a new folder with the system name and fill it with void files that have the same naming structure. I simply copied the MPAA files and renamed the ones I needed to and copied and pasted an additional one for 'E'. You're going to need to be able to alter file extensions so make sure you can see file extensions and alter them before going forward - Google is your friend! Step 4: Profit! ... for now And that's it! Now if you go into the CinemaVision settings and go to change settings, you'll be able to select your new system! So, what now? Well, assuming your movie scraper settings are set to support your country, the next time you try to run CinemaVision with your new system you should see it in the menu but you won't get any rating bumpers because we don't have any! This part should be pretty easy for those who have bothered to read this far as you should be familiar with adding custom content. Basically just set a content folder, go into Ratings Bumpers, create a folder for the new system and fill it with videos/images with the rating for the name (MA15.png/MA15.mp4), then update the content in the settings every time you add something new. I managed to find a collection of videos on youtube someone had made for their own personal collection which I am planning on reuploading for Australians who stumble here wanting to find OFLC content. That playlist can be found in the resources up the top, but google your classification with "bumper" or "ident" on the end and things should start to pop up. Or maybe, if you felt so inclined, you could find the classification assets and create the content yourself! Just remember to share it with the rest of us! Final Thoughts: I'll be the first to admit that this is a SUPER hacky way of adding in custom ratings, but it's the only way to go about it for the time being. I've been told that it's been as simple as adding the XML with the values but it's clearly not that easy. Hopefully, now, others can start to jump through these pretty easy hoops and share it with the rest of us, or perhaps one brave warrior can go through and add every classification? Last I checked though, the GitHub is locked down so I'm not sure how we'd even distribute these files. In any case, this is my first guide so I really hope this doesn't crash when I try to post and that it's been helpful!
-
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...
-
maddox01 changed their profile photo
-
Kodi Leia 18.1 with 1.1.1a8 Error
ELPTheater replied to ELPTheater's question in CinemaVision Add-on Support
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! -
Kodi Leia 18.1 with 1.1.1a8 Error
Fisherman456 replied to ELPTheater's question in CinemaVision Add-on Support
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. -
Kodi Leia 18.1 with 1.1.1a8 Error
ELPTheater replied to ELPTheater's question in CinemaVision Add-on Support
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/ -
Is CinemaVision still being developed?
ELPTheater replied to ELPTheater's topic in General Discussion
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/ -
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
-
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
-
Kodi Leia 18.1 with 1.1.1a8 Error
Fisherman456 replied to ELPTheater's question in CinemaVision Add-on Support
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. -
Kodi Leia 18.1 with 1.1.1a8 Error
MidnightWatcher replied to ELPTheater's question in CinemaVision Add-on Support
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 -
Kodi Leia 18.1 with 1.1.1a8 Error
Fisherman456 replied to ELPTheater's question in CinemaVision Add-on Support
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. -
Kodi Leia 18.1 with 1.1.1a8 Error
ELPTheater replied to ELPTheater's question in CinemaVision Add-on Support
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... -
Kodi Leia 18.1 with 1.1.1a8 Error
MidnightWatcher replied to ELPTheater's question in CinemaVision Add-on Support
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. -
Kodi Leia 18.1 with 1.1.1a8 Error
Fisherman456 replied to ELPTheater's question in CinemaVision Add-on Support
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 -
I paid to be a lifetime supporter of this plugin. Can we please get a fix?
-
Sounds like something similar to MoviePoster. https://www.movieposterapp.com/index.html Other things you mentioned should be possible using action files.
-
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.
-
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.
-
Kodi Leia 18.1 with 1.1.1a8 Error
MidnightWatcher replied to ELPTheater's question in CinemaVision Add-on Support
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. -
pierow changed their profile photo
-
Kodi Leia 18.1 with 1.1.1a8 Error
Matt replied to ELPTheater's question in CinemaVision Add-on Support
There is nothing new that I can share right now. -
Kodi Leia 18.1 with 1.1.1a8 Error
Smithmk replied to ELPTheater's question in CinemaVision Add-on Support
Any news? -
Version 1.0.0
16 downloads
2 min tribute to Stan Lee. Good bumper for your marvel/comic movies. -
Is CinemaVision still being developed?
DavetheMinion replied to ELPTheater's topic in General Discussion
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.
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!