Abeilles Azurées (Composition by leegrosbauer)

There are some pretty blue bees at 110 iterations.

go and add in an audio loop of merrily buzzing bees and you'll be laughing :-) - sync it to the rotation and other tweaks.

there's a lot of different permutations that could result from amending dynamically the feedback & / or lighting patch components.

cybero wrote:
go and add in an audio loop of merrily buzzing bees and you'll be laughing :-) - sync it to the rotation and other tweaks.

nah ... it needs African music. I keep tryin' to tell you guys ... ;-)

cybero wrote:
there's a lot of different permutations that could result from amending dynamically the feedback & / or lighting patch components.

That's a fact. It's reasonably adaptable, happily. Difficult to decide which aspect of it to display.

I think I'll go set up an Audio Expo for the comp you've posted here, give a few djemba loops a try.

That would be truly interesting. Same demand from me to everyone as last time: don't defame my character in so doing. :-)

OK, you asked for it here's a djemba and dumbeck african drum loop mix accompanying and affecting the previously uploaded assembly, with track in tow [2Mb]

Extra freebie skippy mix version for , well nowt :-)

heh. You're just as odd as me, it would seem. I need to learn GarageBand a bit. I have it on the todo list. :-)

My only concern about repetitive audio is that I have the impression that people tire of it faster than they tire of simple imagery. If that impression were to be correct (and it may not be) it would seem that it might be reasonable to attempt to evade audio burn-out for a while with a drone style tune such as that found in many video games. Frankly, I personally would find that circumstance to be acceptable if I were to do it, but I don't have the GarageBand skills to create a decent drone tune.

the skippy mix points towards ways of intermixing audio, especially if one incorporates live input permutations. the straight throughput is arguably of boring repetitive audio. in a way, the best thing to do is to run the loop and cease the render at the end of the audio.

boring repetitive audio should generally be avoided.

Ah. We get to stop the render. Ok. That's different. Under that circumstance, I would agree. But then .. it's about the same as viewing a movie, no? Might as well just make a movie of it and call it good?

In regards of the fairly rudimentary audio skippy version, it really is a rudimentary hint of jumbling up audio.

Even with just one audio player and just mixing it up algorithmically , randomly and so on. would,due to the random nature of the calculation process for the speed and duration / position, end up with totally unique results.

Although an approximation of that kind of installational assembly could be rendered within QC so you got odd results that kind of replicated the actual live render, you've still got the offline render / audio re-sync / dice and splice and mixdown process & that just won't give the same sort of results at all.

In this case live render is the main point . It will never be precisely the same, if appropriately set up , especially if incorporating live input.

Does need Audio Tools beta, should have mentioned.

also , although this example mightn't wet your appetite, it doesn't mean there isn't mileage in the underlying methodology.

cybero wrote:
it doesn't mean there isn't mileage in the underlying methodology.

Understood and agreed. The methodology will be studiously regarded before I delve into GarageBand.

Well, here we are in OS 10.6, as of this posting.

My computer now runs like dog feces and this composition no longer works correctly past 65 iterations or so. So I'm thinking ... I wonder how much other stuff across the web is now laying around in a crippled heap due to 10.6? Should I fix the comp? Cap the iterations, re-upload and shrug it off? That would be the mature and polite thing to do, for sure.

hmmmmm. Tough decision. :-)

Things that don't seem to run well can be doing so because of a reallllllly wide variety of reasons right now. It can be a combo of everything from Apple bugs, to 3rd party plugins, to particular combinations of each running on specific machines (or even other apps running in the background, previewing in Finder, etc...).

It might work the same or better on someone else's system as well. It's hard to say with a small sample group. Updates are still being rolled out as well... maybe you could go through all the work to change it, and then the old ends up working well in an update?

It does say "10.5" compatible as of now :) Things like this are good to stay around unchanged, because they show what to work towards, at least in my opinion.

Maybe post a new 10.6 "tuned" variant and just mark it as such? I guess that's how I'm thinking about it.

What does it do that's not right when the iteration count gets high?

The objects fade in without coloration and then display in a markedly jittery fashion.

I'm not going to do anything with it, for the moment. I just wanted to vent because I've begun experiencing alarming performance issues with the OS update and because I'm simply outraged about the ATI card fiasco. I'm hard pressed to find civil words to convey my repugnance for that move.

Anyway, I've now documented the issue and everybody is now on their own with this comp. Your milage may vary.