So, does Corel Interprocess Controller actually serve any purpose other than burning up CPU resources? Because as far as I can tell it's sole purpose is to crash and cause problems.
Seriously. Any input that could justify such a waste of code and CPU time, would be greatly appreciated. Why would such a thing be needed, and if not needed, then why saddle us with such nonsense?
And ten moths later... still not a single answer to the question. Corel, drop the interprocess controller nonsense NOW. Kill it with fire. It's bloody useless and causes NOTHING but problems. It doesn't solve a problem, it creates them.
Clearly you're one of the very few having this issue.
Well, I genuinely cannot find any actual REASON it exists... Earlier versions did not need it. New versions don't NEED it either. It's just another prime example of Corel overcomplicating things for no real benefit. Perfect example is the new trace engine which is literally 10 times slower than previous versions while adding no benefits to the results. How is it that a version of the software that is 10 years older can do the same trace in 1/10th the time? How is that in ANY way beneficial to the user? I don't want stupid gadgets and useless gee-whiz features at the expense of stability and efficiency. Sorry.
Revvygirl said:Well, I genuinely cannot find any actual REASON it exists..
I think it was introduced to help deal with problems caused by the introduction of multitasking, allowing Draw to do things in the background whilst you carry on working. This was recognised as causing crashes.
I have tried disabling and enabling background tasks with no changes in stability.
I'm of the opinion that GPU use is more of a stability issue than anything else.