Well, Jeff,

Three items: 1. After thinking it over for a couple of decades, yes, I'll consider writing the liner notes for you.

2. I got your M-Audio Liquid Cinema Volume 2 collection of juicy loops and it seems to be the center of a mess with GB 09. Compositions that worked with earlier versions of GB now jam on opening with a "Converting to new song format..." message that renders all work that contains them now unable to load in GB 09.

Is there anything I can do to fix/tweak/adjust/reprocess them to make them available?

The Vol. 1 collection of Pro Sessions seem to work just fine.

Oddly, some individual loops fail immediately after being loaded. Test songs show the jam immediately, but most of them pass this test.

However, if they are used only with each other, they can save and reload ok.

BUT, if some are used and Apple's own Software Loops are combined in a new song, the jam shows up. Same bed of your loops now fails when a software loop joins the file. I can't tell you how long it took to find all this out.

3. I like how your pictures haven't aged, though...

-iNova

We've never heard of this happening in any previous incarnation of GB, or any other music app. WE tried everything with everything we could.

Might be a question for an Apple Genius, if you can get your hands on one. And let us know if you figure anything out.

Sorry to hear about the problems.

It's even worse. Now GB 09 is DOA. This phenomenon happened in the same sequence on the other hard drive when it was the boot drive—but in a G5 computer.

The more recent drive started as a complete, utter virgin when the phenomenon appeared on my new Intel 8 core machine back in November. But I had used the migration wizard to pull stuff from the previous drive, so I thought that some bug or other had arrived with the data.

The new drive had all its software built from original disks. iLife 09 included. At first, every newly minted song file behaved. Then I made the fatal move: I installed the LC collection and immediately things began to get hinkey. After extensive install/test/delete install/test/accept operations I got a bunch of LC loops into the machine, but then noticed the conflict between real and software loops.

Now, real instrument song files save and reopen only sometimes, but even software loop only compositions will fail to reopen.

The ONLY thing that stands between GB working before and failing now was the inclusion of the two M-Audio collections.

The Geniuses are (understandably) pointing at the loops.

New info: After locating and trashing ALL the Pro Sessions Vol 1 and Vol 2 loops from GB, its functionality returned. Once again I could mix Real and Software Instrument tracks.

GB either isn't 100% back to spec, or there is a lingering issue, since after trashing all Apple Loop Index files from the main Library > Audio and User Library > Audio, simply dropping loops from Vol. 1 would not cause a re-index directly, nor would the files show up in logical places.

However, by dropping clusters of loops onto the timeline, they would appear, function and save/reload. Dragging them from the timeline into the browser area would load them into GB one at a time and index them properly. Before that was achieved, the loop evaluation window would appear, letting (forcing?) me to evaluate (dry/processed, clean/distorted, etc.) and flag each loop by instrument type.

Now all these work and play fair with Software loops, saving and re-opening without a hitch, but it took a long time.

Next, I'll test loops from Vol. 2, which is where many of the best sounds are for cine applications. I've used these in the past for soundtracks in example videos about the Nikon D90's D-Movie mode in HD.

I have no explanation for the appalling behavior of loops from Vol. 2—utterly devastating GB's functionality as they have on two completely different computers with two completely different processors—and I ask the question again: What could one possibly do to loop files in .aif and/or .aiff form that would intentionally CAUSE such behavior? If one knew how to cause it, one might be able to un-cause it.

At one point in my process of trying to rid GB of previous "LC *****" loops, I used Mac Automator to select, delete, confirm files from the GB browser, which has me wondering if there is a way to automate a translation process that would convert potentially damaged loops into being usable loops? Worst case, perhaps, would be the one by one re-evaluation loading process the way Vol 1 loops were entered.

-iNova

Ok so I understand how to implement a loop when you know how many times you need to repeat that loop but I need to know how to do it when the number of iterations will be determined by a user when the program is run. Any ideas?
Make Money Online

It can't be the loops. It must be something in the OS or subsidiary files.

I'll try trashing things that can be rebuilt from backups next.