Hi,

I have local trailers for almost every movie, and do not have the YouTube add-on installed because historically for me is stays broken a lot. So I do not want that to be part of the PreShow Experience. I want PreShow to use only the trailers scraped into the KODI database. Yet when I use PreShow, I get the message that the YouTube add-on is required during the trailer sequence. Is there no way to prevent this?

This happens with versions 3.41. and 3.4.3. Never had this issue with CV before, so something in PreShow is different.

thx

PreShow should read whatever is in Kodi's database. It doesn't allow you to pick within the kodi trailers to eliminate YT trailers though, but neither did CV. My guess is that you either don't have local trailers for all of your movies or you also ahve the tmdb trailers enabled.

I may add an option to only show local videos for kodi trailers.

Hi Matt,

I do not have the tmdb trailer module enable. The differences now versus my previous CV KODI Matrix Win 10 setup is that I am now running KODI Omega on LibreElec, with the same movie folder as before, just now mapped using NFS vs. SMB with Windows. There are some movies that do not have trailers, but less than 10 out of 278 movies, yet the trailer module quite often wants to play a YouTube trailer, and when I say no, it skips out of playing the sequence modules after that. So not sure if these changes would impact that behavior or not.

The current setting is a bit confusing with the way it is worded, because to me having the mention of YouTube included in the name implies that YouTube trailers are going to be played. Maybe this option should be split into 2 options, KODI Database Local Trailers and KODI Database YouTube Trailers. But assuming nothing here has changed since CV, not sure what the cause of my issue is.

Is it possible now that I am using NFS that the Synology @eaDir folders are being scanned in as movie folders, and causing the increased number of movies without local trailers?

thx

I get how the wording is confusion in your case. I added in the (YouTube) because for the majority of people that use kodi, their only option will be to stream YT videos since they won't have local trailers with their movies. It was something that came up a lot. You are the 1st person that I've talked to in a long time that has used local trailers with their movie files.

This is a waste of storage space, but an option for you would be to copy your trailers into the PreShow's trailer folder and set that as your content. It would quickly fix the issue so that you are only getting your movies and no YT, but obviously doubles the space.

I'll look into it more after I get through the current beta development process.

I need to correct my statement about the YT trailers. There used to be a setting for "Ignore YouTube trailers" that was commented out at some point. I need to test it, but will add it back in an upcoming version of PreShow.

I am also going to revise the setting text for Kodi trailers to be "Kodi Database (YouTube or Local)."

Thanks. There simply might just be a bug here. I have observed a pattern. My sequence is set to play 1 trailer from the content folder and 2 from the KODI DB. Right after the last trailer plays the dialog that says YouTube add-on is required pops up, and when I say no, the trailer outro and sound module are skipped. I have attached the log from that session if that helps and my sequence.

my default.seq

01_KODI.zip

There are a lot of things going on in your logs, with 72k lines of info.

There's 1 issue that I think I've fixed in a future version, but has separate issues. Ultimately, I think I am going to create a separate version of PreShow with the bug fixes and without the metadata and then another version moving forward with the metadata.

Your trivia has a lot of issues with it in the logs. There are some folders that aren't scanning correctly. I'm not sure what the issue is with it at this point though.

I'll look into this further when my work lets up and I get more time, and will respond back when I have a new version.