This is a question for people who create (or might create) plug-ins using Pixel Bender.
What kind of data security do you want for your Pixel Bender source code in your output files?
Right now, if you write a plug-in using our C/C++ SDK, you know that the plug-in that you actually deliver is a compiled binary file that is (relatively) opaque—i.e., people can’t just open it up and read your source code.
Similarly, if you write a script using the ExtendScript Toolkit, you can choose to create a .jsxbin binary file as the output, which similarly obfuscates the source code.
Do you need something like this for Pixel Bender? Would having additional data security for your source code in the output files be an important factor in how or whether you created and distributed Pixel Bender plug-ins?
Please respond in the comments on this blog post. Or, if you’d rather respond in private, send me a message at kopriva [at] adobe (dot) com.
Oh, and in case some people reading this don’t know what Pixel Bender is: It’s a programming language and toolkit for creating effects and filters that run in After Effects, Photoshop, and Flash. Here’s one of my favorite examples. There’s a lot more information on the Pixel Bender Technology Center site.