I was the one that reported that first this as a bug. If you can re-compile the libraries on your own machine (real pain, assumes source is available), then I think that that sorts it out (locally at least) worked for peasycam.  I've checked the Anar library v20 on my machine (Processing 1.2.1 64 bit linux AMD NVidia drivers), no signature issues there ( it is possible as I originally reported that neither of these libraries are creating the conflict, the existence of another library in the folder will give the issue even if its not called???????).

Just tried the Voltron library and that does give me the signature issue....

Looking at the library I'm not surprise either, checkout what Fry has to say about including opengl libraries in your library...............

Well I can now confirm that if you recompile the library which is basically just volTron.java which is included with the library it works absolutely fine. I did the compiling in NetBeans6.9 which is my preferred ide (you need to have processing core.jar, jogl.jar, opengl.jar etc on the compile path). You do not, should not include these jars in your library....................... which is almost certainly the reason for the signature error, and the included runtime libraries almost certainly would not have worked for me on my 64 bit linux box.

PS I liked the presentation you linked to (on your Twitter account) which was probably the inspiration for your interest ( pity about the volume, I had to turn my speakers to ma x)

Full Example did not work properly for me possibly outdated P5Control stuff.

-- @insan3

I did not isolate these libraries to check wich one was giving me problem, until yesterday. Anar works as charm by its own, it´s volTron the responsible of the signature issue.