Leaderboard

v2.0.3.3 (I think that version number is correct) New algorithm when calculating the Hamming distance between chromaprints. Interested to know if anyone else sees an over all improvement in task time. Advanced settings: Series Ignore list (currently disabled). It's almost finished. Fixes Title Sequence detection task finishes early. IntroSkip_v2.0.3.3.zip What I experience is no longer then 1 second for title sequence detection. Sometimes, it is 0 seconds because our lowest read of detection is in seconds. Perhaps a 'todo' item is to actually look at the milliseconds of each detection since it seems to have become much faster at calculating the differences in the chromaprint. @Sammy

Man this is getting so good and so close I can taste it. @chef or @Cheesegeezerdo you have any incriminating photos of anyone you can use as leverage to get Emby changed to add the skip button to the UI?

Hold fire because we are on fire!!! Chef will upload a new one later on today. This will be the one to test as it has fixes in it and also a new detection algorithm that is fricken AWESOME!!!! However all the latest dll files are posted on this thread now IntroSkip Instructions & Beta Releases - Tools and Utilities - Emby Community

INTRO SKIP PLUGIN Current Status - Beta Release - Awaiting MB Admin to merge this into the Core ADVISORY: It is advisable to test these DEV/Beta releases on a small test library with a few TV shows that have a good amount of content. About 300-500 episodes. DISCLAIMER: The following has been analysed & tested this now: If your audio varies(pitch & loudness) between episodes in a season, the plugin will have difficulty in detection. There is nothing we can do about it, we tried changing the sensitivity of the detection and it yields weird results. THANKS: @chef @samuelqwe @rbjtech @Cheesegeezer for all their hardwork to get this where it is today, especially chef and Sam who did all the hard work with the Fingerprinting and Detection methods. Also to the all the testers for putting up with us. FFMPEG VERSION - Current Release version of Emby Server NOT contain the correct ffmpeg version that facilitates Chromaprint. You will either have to upgrade to the latest beta version 4.7.0.11 minimum or copy over the FFmpeg Binaries from a beta version to your Release version. INTROSKIP WIKI PAGE - PLEASE CLICK HERE FOR INSTRUCTIONS

this crazy. Thank you Mr. Richard Hamming! The man who makes it all possible!

That is really the tip of the ice berg and so easy to display and change how it's displayed. As Bill says, we need to get the button into the core code. There is plenty of testing to do first, however I think certainly within a couple of weeks to a month, everything from chromaprint to detection and endpoints will be solid enough to push Eric & Luke to spend a little time on implementing this.

https://github.com/Scarfsail/AdvancedLogViewer Once you have setup a 'template' to read the emby log format - then you can just filter/parse all the IntroSkip messages with a single click .. If you want to have a play - this is my parser for any emby log :

I would Like to suggest to everyone to run the fingerprint task and stop Don't do anything else. We may have improved the detection quite considerably so we are just Dev testing at the moment to see how the results fair. If it's good we will release and let you go loose with it.

Hi. If you're looking at a Fire, then I would also consider a Mi box or a Google Chromecast with Google TV. All are fine devices but the Google ones will have a little bit less "stuff" forced in your face in the main interface. Unless, of course, you're a heavy Amazon prime video user and, then, the Fire is the best choice.

The Docker builds should have chromaprint included since Emby 4.6. However, it’s possible that using a third-party Docker container like the ones from LinuxServer and Binhex instead of the official Emby one, could not have the same FFmpeg build. I can’t confirm if that’s the case since I have only ever used the Docker official container. @Markadmin I am on unRAID as well and I am using the official Emby container. In my case, it works perfectly. If you can open a console for your Emby container (click on the icon of the container in unRAID, then Console), then you can run the following command: /bin/ffmpeg -formats Then, see if you can find a line (they’re in alphabetical order so look in the C’s) that says: E chromaprint Chromaprint Because that’s what this plugin requires to function. If you do have the line, then we can try looking further at why it’s not working.

Or maybe go simple and have all Emby servers accessible and assign users to servers. Not load balanced of course but should be able to get you past your problem without jumping through all kinds of hoops.

Yes. That is absolutely possible. I can make the thumb image clickable. Will that do?

I understand where you're coming from and I believe I was one of the people to originally ask for this Exit Confirmation, but there really should have been an option to disable it when it was first implemented, but it was deemed unnecessary by Eric. TBH, I have now become used to it so much, that I don't even think about it. The long-press on the back button from wherever you are in the UI, to take you back to the home screen of the app, is also a very useful function, for those that aren't aware.

Perhaps @Cheesegeezer is okay with handling releases? I'm gonna mess it up.

Is it this what you're looking for? https://emby.media/community/index.php?/topic/101687-introskip-instructions-beta-releases/

@CBers I think I know what went wrong with your task. I will put an update on GitHu and here this morning. There was a task progress report which finished the task to early. I dont know how it got moved, but it did. It should be fixed. You might not even have to remove the database file.

just having a giggle to myself

whoa! I'm checking if this resulted in proper start and end times... but...

Depending how custom your current install is and if you want to keep 'watched' status - it may be easier to just install a 'portable' version of emby directly onto the external disk - start from scratch and and run emby from there. You can of course also copy the contents of your current emby over the top of the new portable version, but that's a little bit more involved (but keeps your watched status) Lastly, if you are a premier user - then you can backup your current setup using the backup plugin and simply restore the config to your new location. A new metadata scan is still needed in all cases.

As I mention in a related post, I love the additional subfolders for Movie Extras (eg, Shorts, Scenes, Interviews, etc.)! It would be awesome to extend this functionality to TV Series as well. Specifically to add support for many/all of the same folders supported for Movie Extras, eg, extras specials shorts scenes featurettes behind the scenes deleted scenes interviews trailers As well as any additional folders that get added in the future (eg, hopefully Galleries). Support Placement of "Extras" Folders Within Each Season Folder, Plus A Naming Scheme to Link A Particular Extras Folder with a Specific Episode (eg, "\Season 1\E1 - Deleted Scenes\" for episode 1 deleted scenes): I want to clarify that it would be great if these various "extras" folder types could reside within each Season folder. So for example, within a Season 1 folder we could then have an "Extras" folder, a "Deleted Scenes" folder, a "Featurettes" folder, etc. And furthermore, that we could designate a particular folder to refer to a specific episode (eg, "\Season 1\E1 - Deleted Scenes\" for episode 1 deleted scenes). See more below, particularly why I think this would be so useful: https://emby.media/community/index.php?/topic/55915-emby-server-theater-additional-extrasspecial-folder-types-for-tv-series-similar-to-movies/&do=findComment&comment=587195 Thanks for your consideration! PS - If this is something you might like to see implemented, be sure to "Like" this top/first post (as well as any subsequent posts in this thread that highlight particular aspects of what you are interested in) -- "Liking" the top/first post helps the Devs to know how much interest there is in a given Feature Request.

We're still going through the approval process for our DSM6 packages, but for DSM7 the stable release is now available. I'll get the website updated as soon as I can. Thanks everyone.

I'll wait until the latest and greatest is up then run it again.

libreElec on pi2/3 version 9.2.8 also do have a pi4 on the 10 beta and i believe the issue repros on that as well nextgen test build 49 ex9 (and other builds) server beta 4.10.11

ok, will check it. No need for a log at the moment.

It was me, I can see when it got moved in the code comparison. It was that morning when I messed everything up last week. It's fixed. My bad.

Hey Sammy, I will post a new one this morning. I will '@' you on the post so you don't miss it. We appreciate your involvement! Thank you.

Ahah I actually meant chgrp as well, not chown, as I forgot the first time around. But if you 777d should be fine. I thought the linux branch had chromaprint enabled already, but based on what @chef is saying possibly that doesn't apply for the docker builds :).

And Silent Witness - 24 seasons.

A Feature Request for the future, but when you have a TV show with multiple seasons (TBBT = 12), it's a pain having to change the seasons when checking the Title Sequences, so could you add an All Seasons so that all episode are listed in one page please? Thanks.

what is that notepad reader you are using mate? You can see below the tidy up, and whether it's part of the task running or if it's editing the chapters.

I also think that if @chef new detection code is a mega winner -- we can Consolidate the FP and Detection tasks into 1 Task to avoid confusion for the masses when released.

I've removed all of the Introskip prefixes now

Do you mean App Prefix, we can't change that as it just references the pluginName. Chapters are prefixed, depending on what is being accessed.... either Chapter Tasks or the Chapter Edit Methods as you can see below.

We are getting very good at it, I can almost do it blindfolded

Sorry mate.... I have no experience at all with Linux. There are a few on this thread that will be able to help you out. @Micael456 can you help?

@chef, that's fantastic!!! And might even make the discussion around a communityDB irrelevant if it's quicker to process locally. Let me know when you have a chance to release a new version with that and I'll start afresh on my main emby instance. We'll see if TNG fingerprinting can get beneath 90 seconds ;).

We don't even need to provide the chromaprint, just the intro times. Obviously the hashing has its own resource use, but the lower-powered system you go, the better it would be to try the "community db" first. That's a really good idea yeah. Without the hashes it's bound to keep the numbers down even more (potentially at the cost of false positives, but it should be worth the tradeoff). If we find it doesn't work, we can always go down the hash route. The way I see it: FP/Detection: Most Accurate but Slowest Hash Matching: Fully Accurate but may be incomplete, medium speed. Duration Matching: Less Accurate (fuzzy matching), may be incomplete, very fast speed. I was also thinking about how to pre-emptively prevent the database from getting filled up with unwanted (bad) data. Re: the lengths: the online databases, i.e. tvdb have a runtime value. We can use that to sanity check any lengths we come across as well. Any that are wildly out could be prevented from being added to the DB and force a manual scan. i.e. Show Episode Expected Duration Actual Duration Match? Stargate Atlantis 101 ~45:00 90:01 N Stargate Atlantis 102 ~45:00 00:00 N Stargate Atlantis 103 ~45:00 43:41 Y With some added logic, around it, we could accomodate two parters as well. Show Episode Expected Duration Actual Duration Match? Stargate Atlantis 101 ~45:00 + below 90:01 Y Stargate Atlantis 102 ~45:00 00:00 N/A Stargate Atlantis 103 ~45:00 43:41 Y Likewise, any episodes which aren't in the tvdb etc won't get checked against the online DB, as they're likely to be Home Movies or the like. Much further down the line... When submitting the entries, we can also say who submitted each entry, by hashing the name of the emby server instance and using it as part of the submission API. That way if we get a lot of bad data (though how we detect?) we can prevent some people from submitting values.

Couldn’t figure out how to delete it, but I removed all mentions from the post itself. Totally understand wanting to keep this to yourself…

We'll see. Maybe if it's a less formal review process.

This is optional to use and there is a warning right on the option. "On some systems this can take a long time and cause video playback to stall during the extraction process. Disable this to have embedded subtitles burned in with video transcoding when they are not natively supported by the client device." So if it's not working then you need to turn it off. That's likely going to mean instead of direct playing the media you now have to transcode to burn in the subs. How fast you can transcode is going to depend on factors such as machine hardware, config and of course the type of media. As GrimReaper is pointing out certain codecs types are going to be problematic regardless. In those cases the absolute best thing to do is convert them to a better format.

Are those AVC Hi10p encodes you're having trouble with?

If it works as intended, then it’s a pretty insane speed increase! It makes sense though, that specific calculation happens thousands of times per pair of episodes. In fact, the majority of the detection is using just that algorithm. So just by speeding up that part you’re also significantly speeding up the detection as a whole.

Guessing here but it looks like something to do with the session going idle as this happens 15 time in this log.. 2021-09-16 03:12:05.488 Info SessionManager: Session d0b3c07cfa4a4d0cf7cf545e19b567c5 has gone idle while playing 2021-09-16 03:12:05.488 Info SessionManager: Playback stopped reported by app Emby Web 4.6.4.0 playing Chaos Walking. Stopped at 2620681 ms

It would be better to just add the convert function into the multi-select tool, that way you can at least pick the ones that are going to be converted. If you have a folder of 500 movies and you create a job on it with limit 10, how useful is that really. You can't control which ten get converted, you might as well just pick the ones you want.

Oh my... They are correct This is the last frame of the intro.

Stable versions are now available in Synology store for DSM 7 which should auto update Emby Server for DSM7 Now in Synology Package Center - Synology - Emby Community

If people need help with the logistics of how to implement, plex has a working skip intro button for a little while now. I believe a large chunk of their code is still under GPL and is open to the public. Not saying we have to copy them but maybe their code and method of implementation could help with this effort...?

New version available 6.0.8 build 49 (ex9): Delta changelog: progress update fix for Kodi 18 No need to update for Kodi 19 users.

latest version has logging fixed

Hi, you may want to take a look at the hardware section where you can find opinions of different hardware options for use with Emby Server: https://emby.media/community/index.php?/forum/168-hardware/