OSX and GBX are likewise fully up-to-date.
I have a slightly aged MOTU Microbook (version I) for my interface, but again it works reasonably well for running into GB 6x, and I have the latest drivers installed. My new iMac still has only the stock 8GB of RAM that it came with and probably needs more, but again the problem seems to affect GBX particularly.
So I'm not quite sure what the problem is, except that it seems to occur particularly when using GBX. (I think one latency problem popped up, but I made it go away with the usual "switch drivers in/out" trick, and carried on.) Then, heading back to GBX, the latency problem was immediately there again.
I read somewhere online that imported pre-GBX projects might have latency issues in GBX, so I started a whole new project, but couldn't get more than a couple of real instrument tracks down before the same latency issue started popping up.Ĭuriously, I don't seem to have the same problem in GB 6x! I went back to the original GB 6x version of my project, and was quickly able to add several new tracks of real instrument audio without any significant latency issues. I thought it might be because I was using the "semi-supported" Amplitube plugin via the manufacturers workaround, but running instruments through GBXs own amp simulation effects had the same latency problems. No matter how many times I switched the audio driver, or restarted the machine, any attempt to play/record the real instrument input alongside the already recorded tracks reintroduced the latency issue in GBX. However, then doing anything else - play, record, select a different tracks and then go back, whatever - reintroduced the latency issue. Switching the Input source in and out via the Preferences has usually solved temporary/minor latency issues in the past when working in GB 6x, and it initially seemed to work here. So far, so good - but when I went to add bass as a third real instrument, I ran into insurmountable latency issues. I laid down 2 guitar tracks in my imported project (which had consist basically of half-a-dozen Software Instument tracks), and stuck in a GBX/LPX drummer track to see how that worked (pretty cool stuff, actually). However, I've been running into significant latency issues in GBX that I don't seem to get when running GB 6x. I decided take an old demo project from GB 6x and work it up into something more polished in GBX to start getting the hang of things. I recently got a new late-2013 27" iMac, and after some effort got most of my plug-ins and stuff (even Amplitube, via a slightly kludgey workaround from the maker's support team) up and running on GB 6.0.5 and GBX. Still, I figure that GB 6x will probably cease to be supported by Apple at some point (conceivably with Yosemite!) and I should get used to the new GBX/LPX world. I haven't messed with GBX much until recently, as the Amplitube plugin that I use heavily hasn't been supported in it, but was still working fine in GB 6.0.5.
'I may receive some form of compensation, financial or otherwise, from my recommendation or link.I'm relatively new on this forum, but have lurked a little since GarageBand X came out and I started contemplating a move towards Logic Pro X.
I explain all the details about the Drummer in my graphically enhanced manual " GarageBand X - How it Works"
You can load those Patches to a Software Instrument Track and record your standard MIDI Region to create your own grooves using those Sample Instruments.
When you load those those Patches to a Dummer Track, then the Drum Pattern Generator on that Track uses that instrument. This is the actual Software Instrument (it is actually an EXS24 Instrument), the sampler that has all the drum samples loaded. When you load different "Drum Kit" Patches from the Library, you just swap different Drum Samples. When you load a Drummer Track, GarageBand creates that special Track that includes a Drum Pattern Generator, which "automatically" creates drum grooves based on the parameters set in the Drummer Editor. "automated" is the wrong term to describe the Drummer.