Timpani

True. Got bitten by the same annoying thing today. AARGH! Now I"m attempting to install Yosemite and Logic 10.1, but Logic keeps saying it's downloaded the update, but DOESN'T ACTUALLY UPDATE. I'm starting to lose whatever enthusiasm I once had for Apple and their products. I don't mind that they want to make things simple. But I hate it when they treat me like I'M simple!!!!

These are great - thanks. I hope every Logic user will remind Apple that they should be making it EASIER, not harder, for users to create and share their own icons. Really disappointed that LPX has taken a step backward in this regard. Thanks for your efforts. T

So did anyone every find a fix to this "error -120" that prevents fade files from updating? I'm having it on my system now on 2 projects -- one of which began life on my laptop, but I don't see how that should cause it. Never seen this before but now it's frikkin annoying as heck.

Thanks. I'll check it out and report back. I get the strange silent gap at the end of many .caf and Apple Loop files too... Often, it's just the waveform overview that shows the last few seconds as silent, even though audio continues to play.... I'm also getting Apple Loops which cut off abruptly before the end of the loop or song, even though the region has been stretched to its maximum length. Time to trash prefs again (and back up key commands....). cheers I have a feeling that doesn't matter. L9 worked great for a while, with regard to creating Apple Loops. I made a bunch of them. Then one day I started having the problem you described. What triggered the change? I have no idea. But I do know that the problem went away immediately and completely as soon as I hit on the idea of trashing prefs. And someone else (in the thread I cited above) had the same experience. Why hasn't the problem returned? I don't know. Maybe it had something to do with 10.6.1, or 9.0.1. I don't remember the exact sequence of events, as far as what upgrade I did at what moment. No. I have a feeling that doesn't matter. I already have lots of proof, in the form of Apple Loops that all have the same bizarre silent gap at the end. But from my perspective the proof has no relevance, because the problem seems to be gone for good.

You might find a solution here. I've done a ton of stuff with Apple Loops in Logic 9 (including creating many of my own), and it works fine, aside from that problem which got solved. Thanks - I'll try that, though I trashed my prefs when I installed L9 in the first place... Worth a shot though. Are you using the loops at 48k? Maybe I'll have to get one of those screen recorder programs to demonstrate the bizarre Apple Loop behavior I'm currently getting...

Anyone else noticed Apple Loops behaving oddly in L9, especially in projects at 48k sampling rate? - Loops don't loop properly in browser - .caf files play unpredictably in arrange page - .caf files ("jingles" for example) have waveform overview errors. - .caf files are oddly truncated and don't play completely to the end I'm experiencing A LOT of bizarre behavior in 9 that makes working with Apple Loops a nightmare. Going back to L8 solved the problems completely.... FUN!

For another option, I do stuff like this using the side-chain input of Logic's own "gate" plug. Just put the 'gate' on the track you want gated, then create a "trigger track" using somethnig percussive. Set the trigger track's output to "none", and then just make sure the gate plugin has the trigger track as its sidechain input. HOpe that's clear enough... Its' really not that complicated, and you can use the threshold settings on the gate to vary how pronounced you want the effect to be.

Just got my new Mac Pro (woo hoo!) but so many of the plugins aren't Universal Binary yet, I think I'll be sticking with the trusty dual G4 for a while. But can I use the new Mac Pro as a 'node' somehow with my current setup? (I realize the node can only process Logic's own plugs, but that could still be quite useful). Thanks for any info. I'm running 7.11 now, but have 7.23 on the way. cheers.

Quickest way I know to arm multiple tracks is to make them all part of the same "GROUP", then in "Group Options" be sure to tick "Record enable" as one of the things the group will share... Also, make sure each of your tracks have different inputs enabled. Coz if two tracks have the same input source, only one of'em will stay armed at a time, far as I know. cheers.

Sounds very promising, thanks! But wouldn't this solution over write all the plug in and instrument assignments in my environment? I haven't done a cut n' paste Audio Config before, so I'm just asking so I'll know what to expect before I try. Thanks again. This is a great forum. TB

That's what I figured as well, but at least in my opinion it seems like shabby programming to include menu "features" that evidently aren't going to be useable for about a year or more... Normally the stuff that doesn't work yet is the stuff you should leave out of the software. But I ain't no programmer - obviously. Okay, so you can't add multiple aux's. On to my next work around... What about "import Environment layer"? I tried this with aux layers and it also doesn't appear to work. If I have a song where I decide to add a multi-channel instrument like Kontakt or DFHS, can I import the auxs' from another song? I'm guessing the answer is no...

Thanks for the replies.. though to be honest I was hoping for a better solution. Oh well. Why would Apple/Emagic put "Auxes" and "Outs" in the Create Multiple menu and not have them ever work? Seems pretty half baked to me... Oh well, I'm sure Version 8 will be along soon enough with plenty of new GarageBand looping tools and... no solution to the klunky Multichannel instrument mess. Hooray! (Can ya tell I'm just a tad bitter? Sorry bout that.. Thanks for the help!)

How come when I use "Create Multiple...", the options are only "Instrument" and "Track" but "Auxilliary" is always ghosted out? I'm trying to import a Multi-Channel instrument (like Drums from Hell Superior) into another Logic Song, and it has it's own environment page with 10 or so Aux channels. But "Import Layer" doesn't work, and there doesn't seem to be a quick way to create 10 or so new Auxes... Or is there? (Is it just me or does Logic's way of 'handling' multi channel instruments seem incredibly awkward and kludgy?)

Okay - I figured it out! Now, I'm pretty sure I'd figured this out once before and forgotten. Hopefully this time it will 'stick'. (And to the previous poster, yes I do know all the different variations on 'next XXXX setting"... For what it's worth.) It seems that Logic "Pro" always uses the + and - keys for editing the 'last selected' parameter value. So if you use it to advance presets, that's what it'll do. Until you nudge a parameter, and then that becomes the new function of + and -. So the solution to having a dedicated 'next/previous preset' command is simply to make sure you DON"T USE + and - . Doesn't matter if you add a shift key/control key/command or any other modifier. Don't use'em. I switched my 'Next $%&? setting' command to: > and < for 'previous', and now everything works fine regardless of what parameter I've nudged. Phew! Now if somebody could just get hold of the wizards on the AU 'standards' committee and force them to develop a basic preset increment/decrement standard like MIDI has had for the last 20 years or so... that would be sweet. But at least for now I'm good with > and <. Thanks me!

Yes, thanks - I'm aware of the key commands for 'settings'. But as I hoped to say in my original post, the problem is that "next setting" doesn't apparently mean the same thing as "next preset". It will just nudge the values of the last plugin parameter you edited. At least that's what it's doing here, and I've checked for key command conflicts.. I appreciate the effort to help though. Anyone else have this happen?