Custom Skip1 lets you define client-specific filter sets with rules for when tracks should be skipped automatically.
Some preferences are not enabled by default.
⬅️ Back to the list of all plugins
- LMS version >= 8.0
- LMS database = SQLite
- Comes with 30 ready-to-use skip/filter rules.
- Look-ahead filtering: Have Custom Skip check not only the current song, but also the following songs to see if they have to be skipped/removed from the playlist. Helps avoiding short but unpleasant playback interruptions when a current song is skipped.
- Use the context menu to (temporarily) filter artists, albums, genres, years, tracks or playlists.
- Should work with online library tracks (see FAQ).
- Clear and informative user interface.
- …
You should be able to install Custom Skip from the LMS main repository (LMS plugin library): LMS > Settings > Plugins.
If you want to test a new patch that hasn't made it into a release version yet, you'll have to install the plugin manually.
It usually takes a few hours for a new release to be listed on the LMS plugin page.
If you want to report a new issue, please fill out this issue report template.
»I can't find my filter sets.«
Custom Skip automatically creates a folder called CustomSkip3 at a location that you can set in the CustomSkip settings. The default location is the LMS preferences folder. Grouping CustomSkip filter set files in a dedicated subfolder helps reduce clutter. Just move your old filter set files (file extension .cs.xml) into the new subfolder. You can also move the CustomSkip3 folder out of the LMS preferences folder to any other location (with the necessary file permissions for LMS).
»Can I call Custom Skip from the context menu?«
Artists, albums, genres, years, tracks and playlists have a CustomSkip content menu that lets you add a filter/skip rule to the active primary filter set. Example: you want to skip all tracks of the selected artist for the next 15 minutes.
»I can't save new Custom Skip filter rules/sets. I get this error message: “Could not create the CustomSkip3 folder“.«
The CustomSkip3 folder is where CS stores your filter set files. On every LMS (re)start, CS checks if there's a folder called CustomSkip3 in the parent folder. The default parent folder is the LMS preferences folder but you can change that in CustomSkip3's preferences. If it doesn't find the folder CustomSkip3 inside the specified parent folder, it will try to create it.
The most likely cause for the error message above and matching error messages in the server log is that CS can't create the folder because LMS doesn't have read/write permissions for the parent folder (or the CustomSkip3 folder).
So please make sure that LMS has read/write permissions (755) for the parent folder - and the CustomSkip3 folder (if it exists but cannot be accessed).
»Does Custom Skip handle online tracks?«
Custom Skip will process online tracks that have been added to your LMS library as part of an album. LMS does not import single online tracks or tracks of online playlists as library tracks and therefore they won't be processed by Custom Skip.
»The web menu doesn't have a filter rule for skipping single tracks. How can I skip single tracks?«
You can create a skip rule for single tracks from a track's context menu.
»Look-ahead filtering doesn't delete all tracks that should be filtered but always leaves one in the playlist.«
Custom Skip's look-ahead filtering will leave at least one last track in the playlist after the currently playing track to avoid problems with plugins that use song change events to trigger actions.
»Is Custom Skip v3 compatible with Dynamic Playlists v2?«
Custom Skip v3 works with Dynamic Playlists version 4. Anything else is untested and unsupported.
»Why are the filter rules 'recently played track/artist/album' only available for look-ahead filtering?«
As soon as a new song starts playing LMS will set its last time played to the current time and then notify other plugins like Custom Skip of the song change event. So Custom Skip's filtering doesn't kick in until after the last time played has been set to the current time. Therefore if Custom Skip checked currently playing tracks against a recently played filter rule it would find that all currently playing tracks have been recently played and skip them resulting in endless skipping. That's why these rules are only available for look-ahead filtering.