# \[X\] filtering %\_path% exceptional
**URL:** https://community.mp3tag.de/t/x-filtering-path-exceptional/9749
**Category:** No Bugs
**Created:** [January 22, 2010, 1:54pm UTC](https://community.mp3tag.de/t/x-filtering-path-exceptional/9749 "2010-01-22T13:54:21Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@petigabi.2](https://community.mp3tag.de/u/petigabi.2)
#### Post date: [January 22, 2010, 1:54pm UTC](https://community.mp3tag.de/t/x-filtering-path-exceptional/9749/1 "2010-01-22T13:54:21Z")
Maybe, it's not bug, then I cann't understand the concept.
Filtering found matches in any field, except %\_path%. Also the \* HAS {string} doesn't search the %\_path% field. Filtering directories or drives the expressly %\_path% HAS {string} have to be used.
---
### Author:  [@petigabi.2](https://community.mp3tag.de/u/petigabi.2)
#### Post date: [January 22, 2010, 3:00pm UTC](https://community.mp3tag.de/t/x-filtering-path-exceptional/9749/2 "2010-01-22T15:00:53Z")
Ok, I tryed a lot of placeholder. The above case is present at the path relative placeholders, that are: %\_path%, %\_folderpath%, %\_directory%, %\_parent\_directory%. That means, we could think, it's conceptual, these fields have to be expressly named to filtering, otherwise not checked. But %\_filename\_ext% and %\_filename% are checked, even if not shown. From my viewpoint this is not coherent (even if don't regard as bug).
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [January 30, 2010, 9:39pm UTC](https://community.mp3tag.de/t/x-filtering-path-exceptional/9749/3 "2010-01-30T21:39:16Z")
Yes, it only filters tag fields and the filename.
---
### Author:  [@petigabi.2](https://community.mp3tag.de/u/petigabi.2)
#### Post date: [February 1, 2010, 2:36pm UTC](https://community.mp3tag.de/t/x-filtering-path-exceptional/9749/4 "2010-02-01T14:36:52Z")
What is the benefit of handling the parts in filename two different ways? What the meaning of, what for the **\*** , if used the same way, if omited? May the \* mean **any** field, if some of them excluded?
Moreover, what deliberation is over that, to filter not shown fields, even if them contents simply technical? e.g. some iTune-relative ID code-like strings, what are totaly meaningless for human reading.
How to decide if a field is technical or not (by the developers), and filtered or not, and must or not to specify expressly? e.g. duration, bitrate, ID version vs. iTune-codes, ISRC, and hence, filename vs. path.
OK, this is not bug. But also not useful...
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [December 28, 2018, 2:28pm UTC](https://community.mp3tag.de/t/x-filtering-path-exceptional/9749/5 "2018-12-28T14:28:09Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.