This is an audio-synced offline rendering of one of Apple's Quartz Composer OpenCL code sample's Aurora.
It does not make any use at all of static .dae meshes.
Straight out of the box, the iTunes music visualizer example, Aurora, doesn't even produce much apart from fog.
The default setup is to be using audio spectrum data to dynamically generate the graphical meshes, but that doesn't even work in iTunes, although it does work AOK in Quartz Composer.
By queueing a smoothed input of audio peak data, a structure is made available that allows for the production of dynamically generated meshes in iTunes and QC.
This offline render has had to be tweaked somewhat to make it work in a fashion not dissimilar to how the visualizer works in iTunes.
That said, Aurora's still a beautiful and inspiring piece of work, with loads of hidden extras to burden the CPU and GPU with. I've learnt loads from looking at the .qtz's structure and programmable components.
Only remaining snarl up is that being based upon the parallel queueing of structures into OpenCL, there is a tendency for odd graphical artefactions and crashes when being run in iTunes [bug report submitted] :-) .
It's early days in regards of OpenCL and much of what it is meant to do is not specifically intended to support graphics and graphics alone, so this is not , by any means , a typical use of OpenCL, apart from the size of the data sets that become vertices, normals and so on.
Audio is a MIDI revamp of a tabulation of Peon.
I would make my reversioning of Aurora available as a fully fledged iTunes visualizer, if only it weren't for the fact that I know that doing some of the really simple things that a typical iTunes user might do, like switch between visualizers, will almost definitely result in a crash.
Speaking of which, the eccentricities of this example do extend even further, for instance, some reset and selection parameters are obtained via keyboard entries actually reserved for iTunes menu functions. Of course, these can be reset, but they do seem to suggest that this example was protocolised to be a visualizer, but not seriously tested within iTunes.
Finally, the use of generated meshes is not impossible after a fashion within iTunes, or elsewhere. A couple of other examples that create reactive meshes work AOK in iTunes, more on those later .... :-)
Having said , that the new and spruced QuickLook daemon can also precipitate the sort of graphic buffering crash that comes with running this item in iTunes when viewing directories with icon preview enabled - ouch - flourescent light bulb flicker.
Loading more stuff…
Hmm…it looks like things are taking a while to load. Try again?