I get the same using Colorista. As with Colin, it doesn't seem to affect performance at all.
One thing that has me curious though is your version of Premiere. I didn't notice this using 5.0.2. I wonder if the new and improved "effects interface" of 5.0.3 has anything to do with it.
I've had the problem, too. I contacted Red Giant support about it. Their response was not to worry about it, since it wasn't really a problem, but just an error mesage. That was kinda ok, but unsatisfying.
Yesterday I took advantage of their sale, and purchased the Colorista upgrade, from 1 to 2. No error messages now. Now I understand the earlier response. In any case, Colorista 2 is great, and it is a really good upgrade.
I can preview and render, just two thing bothering me:
1. RG Plugins take lot of memory, I could not preview in Full Reso. and have to do a lot of guess work. Maybe that it is the way all the Third Party Plugins work. Especially BCC 7 crashes PrePro quite offten. Some time to sync image and music I have to turn it off.
2. I don't find anything doesn't work, but the "Red Error X" is always there on the right bottom : (
I keep getting those too, great that it worked for You Bill, but i still get them with Colorista2...
I contacted RG and they allowed me to post this conversation here:
felix: "Couldn't load kPFColorParamSuite"
Sophya: just a moment
Sophya: We haven't found this event message to effect either the plug-in or the host. You should have no issues closing the message and continuing. Should you not find that to be the case, please let us know right away.
Sophya: Is there anything else I can help you with today?
felix: thank you. it also seems to me that the performance and the host app are not affected in any way, still it's tough, if the whole error log is flooded with this message (1 message per change in colorista...)
felix: because i constantly have to search through the error log in case i get a REAL error, after all, that's what it's for ;-)
Sophya: We are working to solve why it occurs and correct it as soon as we can. Are you on our newsletter?
Sophya: Perfect- that will be one of the first ways we announce any updates for Colorista II
felix: thank you so much for your time.
Sophya: Of course! Thank you for your patience.
felix: something else, since some fellow editors are experiencing the same problem, would you permit that i copy part of this conversation to our forum?
Sophya: Of course! They should be on our newsletter for any updates, as well.
felix: i'll pass it along.
Sophya: Thank you very much.
felix: thank you and have a great day
Sophya: You as well!
So they're working on it and they want you all to subscribe to the newsletter...
Me it doesn't bother that much to get these errors, since they don't really do anything and seem to only be a bug, just that i have to check the log more regularly, in case some REAL error sneaks in between these little buggers.
yepp. me too.
i've only recently been getting these errors (didn't have them with Colorista 1) so i searched for solutions here before contacting RG.
Found this thread, quite an old problem as it seems.
Still i'd like to see it solved, since i like Colorista and am not sure what speedgrade will bring in comparison to what it was before adobe bought it.
But since DaVinci is a different league ( i leave it to the "real" colorists), the MB Suite is quite a charm for quick grading and i use it regularly.
maybe too few people file bug reports at RG since the problem seems only to be the error message itself... :-/
I just started to see this error a couple days ago with PPro CS5.5 when trying to render out a time line for DVD prep. The error would stop the rendering with an unknown error, but the Timeline error list was a slew of 20 or so of this "Couldn't Load kPFColorParam Suite" error.
Fortunately, I could open the .m2v file in of all things Windows Media Player (This is in Win7, 64-bit), and look to see at what point & clip the error occured. I've Black Magic Design capture hardware, but in every case the problem was with a non captured clip that I've been forced to use, usually a Quicktime of some variety, most often an mp4 or mov.
I could convert the troublesome clip to an MPeg4 flavor of AVI, perform a Replace Footage and be good to go, at least until I encountered yet another problem clip.