# Function to reverse Filter

**URL:** https://community.mp3tag.de/t/function-to-reverse-filter/16629
**Category:** General Discussion
**Created:** [February 25, 2015, 8:06pm UTC](https://community.mp3tag.de/t/function-to-reverse-filter/16629 "2015-02-25T20:06:37Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Zerow](https://community.mp3tag.de/user_avatar/community.mp3tag.de/zerow/32/11379_2.png) [@Zerow](https://community.mp3tag.de/u/Zerow)
#### Post date: [November 25, 2019, 4:13pm UTC](https://community.mp3tag.de/t/function-to-reverse-filter/16629/5 "2019-11-25T16:13:27Z")

</div>

> [@Zerow](#):
>
> [...]  
> Mp3tag could act like this:  
> [...]  
> c] Mp3tag creates a temporary file with all the loaded files  
> [...]

Now that a different file creation was reworked

> [@Mp3tag v2.86 released](https://community.mp3tag.de/t/mp3tag-v2-86-released/19711):
>
> I've just released Mp3tag v2.86! This version comes with a wide variety of changes, most notably: orange_book Library to permanently store metadata Normally, Mp3tag reads metadata from files when loading files, directories or playlists and stores the data in memory. Then, when you close Mp3tag, the data once read from the files is discarded and must be read again the next time you're working with those files in Mp3tag. This can become both time consuming and memory intensive, especially …

can my idea somehow be built utilizing the mechanisms of those [upgraded Library] processes?  
` `  
` `  
But come to think of it: if Library back then was using a temporary file - then why cannot there be such temporary file created when a search is done? And then used quickly for an immediate reverse search?

---

_[View the full topic](https://community.mp3tag.de/t/function-to-reverse-filter/16629)._