Why is plextranscoder.exe using 45 percent CPU at idle?

According to Process Explorer 64, this, plextranscoder.exe is running this command:
“C:\Program Files (x86)\Plex\Plex Media Server\PlexTranscoder.exe” -codec:v mpeg4 -i “S:\TV\SomeTVShow\Season 05\Some TV Show - 05x15 - Some Episode.avi” -threads 0 -nostats -q 3 -loglevel quiet -progressurl http://127.0.0.1:32400/video/:/transcode/session/bif/progress -filter_complex “[0:V:0] scale=w=320:h=240:force_original_aspect_ratio=decrease [out]” -map [out] -r 0.5 “D:\Plex Media Server\Media\localhost\8\c586900d5514234579d04d02d7a39a8061b2c6e.bundle\Contents\Indexes mp\img-%06d.jpg”

I’ve checked it several times over the last hour and it hasn’t changed. It’s eating 25-45% of my CPU. What is it doing? How do I make it stop? When I restart Plex, it eventually goes back to this file and does this again…

I forgot to mention, no active streams, nobody is using this server… it shouldn’t really be doing anything right now.

bif indicates, Plex is creating video preview thumbnails.
You can either wait until this is done or disable them.

https://support.plex.tv/hc/en-us/articles/202197528-Video-Preview-Thumbnails

It’s always this same file, it’s been doing it for hours.

If it always gets stuck at the same AVI file, remux the AVI file into the MKV container. This won’t change the quality of the video, but it will be more compatible with Plex.
MKVtoolnixGUI

Side note: you are still using the Kodi-style method of designating season and episode.
Consider changing that.
https://support.plex.tv/hc/en-us/articles/200220687-Naming-Series-Season-Based-TV-Shows

I bet that will fix it.
In regards to the episode naming, is there any reason to actually change it? I have a comprehensive backup system in place with hashing, on site and off site storage using archive flags. I never found a good reason to change it. I don’t have any issues with matching media…

@lotekjunky said:
In regards to the episode naming, is there any reason to actually change it? I have a comprehensive backup system in place with hashing, on site and off site storage using archive flags. I never found a good reason to change it. I don’t have any issues with matching media…

Then consider changing it for new entrants. No need to change it retroactively if matching works.