I noticed that no matter how large I set the size limit on the decoding cache, Live will remove some of the decoded files (but not all). For example I can put a 40GB size limit on the decoding cache (on a harddrive with 100's of gigs of free space) load up a live set that decodes 25 mp3 files into wav (about 1.5 GB). Save the set, open it a week later after not messing with Live at all (or maybe dealing with only one other set) and when I open the set with the 25 mp3 files Live will need to decode about 1/3 of them again....
Anybody figure out the rhyme or reason to how this works? I wish it would just wait until you hit the cache size limit and then delete some of the oldest (in terms of being accessed) files to make room for new stuff.
I know people have suggested just preconverting all mp3's to wav's for their library, but I make extensive use of mp3 tagging and keep my music synchronized on laptop/desktop so their is not an easy way to transfer wav "tags" from one MediaMonkey database to another whereas the mp3 tags are stored within the files themselves...
Decoding Cache removes files well before it's size limit
Re: Decoding Cache removes files well before it's size limit
I just had a revelation: If you change an mp3's tags, Live will have to redecode the file. This must be what was happening in the majority of the cases that have been puzzling me...