Windows Indexing and custom transcode path fyi

[Vicpa 577]

Hi

 

Sometimes I am my own worst enemy. I moved the temp transcoding path to a data drive. People either love or hate windows indexing, I use it. By default user app data is excluded (location of default transcoding temp path). I have indexing setup on my data drive. Stupidly I forgot about this when I moved the transcoding path. By chance I thought I would check cpu usage while transcoding was going on and found ffmpeg using about 40%-50% of the cpu and the indexing service another 50%. Don't know if this was a coincidence but since have excluded the temp transcode path from indexing. Anecdotally cpu usage seems a lot lower although don't check it much if at all. 

 

I can't think of any logical reason to index a temp dir and thought I would pass it on so others can avoid my stupid mistakes.