toxiclibs-0020 release

toxmeister

in Library and Tool Development • 2 years ago

Still as fresh as the new year, today I've released the latest version of the toxiclibs library collection incl. countless updates & additions from 6 months since the last release. You can find more info and download links in the related blog post here:

http://toxiclibs.org/2011/01/toxiclibs-0020/

Noteworthy might also be the fact that there're now 95(!) examples of different complexities bundled with the various library modules. Approx. 35 of them are also available on OpenProcessing.org:

http://openprocessing.org/portal/?userID=4530

Happy coding!

Replies(10)

robbby

Re: toxiclibs-0020 release

2 years ago

I thank you very much for this release, I've been looking forward to it.

I've downloaded it twice and I still get many errors when running the examples; these are just a few:

The function origin(Vec3D, int) does not exist.
Cannot find a class or type named "VolumetricSpaceArray"
The function addBehavior(GravityBehavior) does not exist.
cannot convert from TriangleMesh.Vertex to Vertex
The function computeCentroid() does not exist.
The method CreateMersh(int, float) in the type SurfaceMeshBuilder is not applicable for the arguments(null,int, int).
cannot find a class or type named "WETriangleMesh".
constructor AABB(int) is undefined
Cannot find a class or type named "WeightedRandomSet".

I'm running win XP with 1.2.1
Is it my machine or did you miss something?

PhiLho

Re: toxiclibs-0020 release

2 years ago

I just downloaded the toxiclibs-complete-0020.zip file and unzipped its folders under a 'toxiclibs' folder. I can run the examples without problem, discovering that library folders doesn't need to be at the top level of the 'libraries' folder.
Well, I have a problem (UnsatifiedLinkError) when running the SynthBasics sketch. The comment mentions a JOAL library. Does it need to be installed in addition to the toxiclibs?

cedrickie..

Re: Re: toxiclibs-0020 release

2 years ago

fantastic. thanks a lot Karsten!

toxmeister

Re: toxiclibs-0020 release

2 years ago

Hi guys,

thanks a lot for the feedback. Still slightly worried that some people keep on having the same old issues with every release, though - and always for the same reasons:

phi.lho - did you had a look at the README.txt file in the audioutils folder? You'll need to install an OpenAL driver manually under Windows... get it from http://openal.org/

robby - I don't know, but you don't seem to have the new version installed, but are running the new examples?! Is that possible? Do you have 2 toxiclibs library folders in your main "libraries" folder? Due to the level of refactoring behind the scenes it was impossible to avoid some small API changes this time around. Before bundling everything up, I've updated & tested the syntax of ALL examples to reflect these changes, though. So the errors you're getting indicate you're having your own local versioning conflict, which I unfortunately can't help you with...

The installation should be a simple unzip, and copy & paste into the libraries folder of your sketchbook. Really, somewhat dumbfounded how this can break things for you... Apart from bundling Readme files, what else can I do to make this more fool proof? Other Processing libraries don't even have the correct folder structure after unzipping, but people hardly ever seem to have problems with those libs? What's wrong with this picture?

amnon.owed

Re: toxiclibs-0020 release

2 years ago

Thanks Karsten. The new examples are really inspiring! For the record, tried a bunch of 'em and they all work flawlessly.

Gotta finish some other projects first, but then I'll dive right into this and get as creative with it as possible.

Thanks again for another great release.

velvetkev..

Re: toxiclibs-0020 release

2 years ago

Great stuff, and examples working fine for me. The only issue I've seen is in the MeshFaceExtrude example- looks like line 54 should read

Vec3D centroid = new Triangle3D(etc)

instead of

Vec3D centroid = new Triangle(etc)

Thanks for the incredible amount of work this must take to release!

monkstone

Re: Re: toxiclibs-0020 release

2 years ago

Yeah that bugged me too, yet Triangle class appears in documentation. Otherwise usual brilliant stuff!!!

Note for audio utils on linux:-

Openal source available here. This is a CMake build, since I've been compiling the latest source of blender a lot, I used qtcreator for the build, it is just like click and go (far too easy).

A download of 64 bit joal (java binding) is available here includes a compiled native binary, so you may not even need the source above, although you will need it for 32 bit linux. I used a combination of both, worked for me.

robbby

Re: toxiclibs-0020 release

2 years ago

Thanks Toxi; I thought it must be my machine. I even deleted the old libraries. I'm going to try a clean install of processing and then Toxilibs. I've been looking forward to this release since it was first announced.

To answer your question; there's not anymore you can do to keep us on the right track, you go out of your way to make these libraries available, if we can't get it right...that's on us. I do appreciate your work.

robbby

Re: toxiclibs-0020 release

2 years ago

I've discovered what the problem was. I had 1.2.1 and 1.1 on my computer. I was using 1.2.1, I thought, that's where I added libraries but it was actually the 1.1 folder that the program was using...all fixed now.

PhiLho

Re: toxiclibs-0020 release

2 years ago

" did you had a look at the README.txt file in the audioutils folder"
No, of course!

I just loaded the libraries examples from the Processing menu... I expected to see a warning or something in the sketch comments on the header... Even a simple notice sending to the more complete README.txt would be enough.
Note there is a slightly confusing Readme sketch in the audioutils folder, which seems outdated.

Somehow, I have put myself in the shoes of somebody trying to quickly discover the possibilities of the library, so I give feedback to allow you to complete your already quite elaborate process of being foolproof (but there is always somebody more fool than you supposed...

)

Top Reply