It's too bad that I can't tell whether one of the following two scenarios happened during last night:
1) acemd.exe stopped after finishing a job, then restarted with a new job, PT changed the priority to "above normal", and lateron, at some point of time, acemd.exe changed the priority back to "below normal".
2) acemd.exe stopped after finishing a job, then restarted with a new job, and - for whatever reason - PT did NOT change the priority to "above normal". Although I had seen PT already once (some time yesterday) changing the priority right when acemd.exe started.
The thing is that these jobs take between 10 and 14 hours, so I don't always have a chance to watch what's happening when a job gets finished and a new one starts. Some time this happens during the night, some time I am not at home exactly at that moment, ...