![]() |
|
Extent "excludePattern" from file/folder level to path level - Printable Version +- MinimServer Forum (https://forum.minimserver.com) +-- Forum: MinimServer (/forumdisplay.php?fid=1) +--- Forum: Support (/forumdisplay.php?fid=4) +--- Thread: Extent "excludePattern" from file/folder level to path level (/showthread.php?tid=7687) Pages: 1 2 |
Extent "excludePattern" from file/folder level to path level - z624391 - 11-12-2025 18:55 Is it possible to extent "excludePattern" from file/folder level to path level and maybe introductie also regex possibilities? RE: Extent "excludePattern" from file/folder level to path level - simoncn - 12-12-2025 11:09 MinimServer scans one folder at a time, so the pattern is applied to each folder individually as the folder is scanned. The current implementation is designed for high performance. This is important when scanning a large library. Using regular expressions would be much slower with a big increase in rescan times. Can you give some examples on what you would like to do with regular expressions that isn't possible with the current support? RE: Extent "excludePattern" from file/folder level to path level - z624391 - 12-12-2025 12:16 To manage my libraries I like to exclude some folders. In this case I like to exclude the folder: "## ROEL ##" from "/share/CACHEDEV1_DATA/Music Library" but not at all places. In this case "## ROEL ##" does also exists here: /share/CACHEDEV1_DATA/Music Library/Qobuz/ /share/CACHEDEV1_DATA/Music Library/Tidal/ and they must not be excluded. RE: Extent "excludePattern" from file/folder level to path level - simoncn - 12-12-2025 14:14 Thanks for this example. To make this possible, MinimServer could add the option to include a folder path prefix in an exclude pattern. With this support, you could do what you want by using the exclude pattern /share/CACHEDEV1_DATA/Music Library/## ROEL ## With this setting, the folder path prefix would be /share/CACHEDEV1_DATA/Music Library/ and the exclude pattern would be ## ROEL ## With this setting, MinimServer would check if the folder path is /share/CACHEDEV1_DATA/Music Library/ and apply the exclude pattern ## ROEL ## to this folder only. The folder path prefix would be a literal string without an option to include wildcard characters. Does this sound like a suitable solution? RE: Extent "excludePattern" from file/folder level to path level - z624391 - 13-12-2025 10:45 Yes, I think this will solve my case. I presume this will not undermine the great and amazing performance MinimServer is offering. Thx for your suggestion and active support. Very small side step: again I tested Roon against MinimServer. But now Roon was running externally on his preferred Roon OS from a hub. And again the same sound quality degradation was easy to hear. So, the choice is between sound quality (against a very limited price level) or functionality (against a high price level). RE: Extent "excludePattern" from file/folder level to path level - z624391 - 17-12-2025 13:19 Do I understand it well that you will add the "folder path prefix" setting to MinimServer? Or must I change my settings? RE: Extent "excludePattern" from file/folder level to path level - simoncn - 17-12-2025 18:58 I have added this to the list of requested enhancements. The next step is to try making this change and make sure it works as intended without causing any problems. If everything looks OK, the change will be available in a future MinimServer update. I cannot commit to a date for when this update will be available. If you need an immediate solution now, you will need to change your configuration settings. RE: Extent "excludePattern" from file/folder level to path level - z624391 - 02-01-2026 17:19 Alright I fill wait for an MinimServer update. What is your "normal" update/upgrade scheme? RE: Extent "excludePattern" from file/folder level to path level - simoncn - 02-01-2026 18:10 If a serious bug is reported, I try to release an update with the fix as soon as possible. Enhancements and minor bug fixes are usually grouped together into a combined update. In this case I would expect to release the update sometime this month unless there are issues with implementing the change. RE: Extent "excludePattern" from file/folder level to path level - simoncn - 27-01-2026 22:42 I am working on this now. The solution is slightly different from my original proposal. In the solution I am implementing, each exclude pattern string can be one or other of the following: 1) a file name or directory name with wildcards (currently supported), for example: ## R*L ## 2) an absolute directory path without wildcards (new), for example: /share/CACHEDEV1_DATA/Music Library/## ROEL ## You can't combine these as a single value, so it is not possible to specify this: /share/CACHEDEV1_DATA/Music Library/## R*L ## As I understand it, the new option 2) will provide what you need. The change from my original proposal was needed to reduce complexity in the implementation and ensure good performance when scanning the library. I will post back here when this change is available for testing. |