Badcatblackcat

I installed Big Sur 11.6 last week and I still can't see the Logic 10.7 update. Any idea why that might be?

Thanks Eric!

Since I upgraded to 10.4, whenever I do anything in a track, the automation parameter changes to that function. For example, If I solo the track, the automation parameter changes to solo. Is there any way to turn this off? Thanks in advance.

On the just flat out entertaining front (also quite informative), I really enjoyed David Byrne's book How Music Works (2012).

Do your UAD plugins show up as authorized in the UAD Meter & Control Panel? I would try UAD Support. I have found them to be helpful.

I copied the regions out of Logic, deleted the track that the regions were on, created a new track and put the regions in it and all seems well.

I just went and checked to see If I had done this accidentally and it looks like the regions are all unlocked. Thanks for the suggestion though.

I am trying to move a group of regions in a track up a couple of bars. I have been dragging stuff around all day and everything has worked normally. With this group of regions, however, instead of moving when I drag them, a copy is created and where the copy overlaps the original location of the regions, crossfades are created. I made a copy of the track and tried deleting the regions and they won't delete. It is like the regions are protected somehow. And I can't imaging why it is creating all of these crossfades. Anybody have any idea what might be going on? Thanks in advance for the help.

Anyone? Be nice to know if I am at least trying to figure this out in the right general vicinity in Logic.

I am trying to figure out how to send MIDI control change messages from Logic to a Moog Moogerfooger MF-108M Clusterflux. The Clusterflux manual says that you can set clock divisions on the Clusterflux's LFO by control change #71 and specifies various CC71 values for quarter notes, eighth notes etc. I have the Clusterflux MIDI synced to Logic (David taught me how to do that a while back). Reading the Logic Pro X Manual, it seems like the way to do this would be with an External MIDI Track. So I created one and specified MIDI control 71 in the pull down in the External MIDI Track header (MIDI Control 71 is interestingly is labeled "Resonance"). Having done this, however, I can't figure out how to specify a CC71 value. Am I even within the right zip code of figuring out how to do this? Is there a way to specify a CC71 value in the External MIDI Track that I am missing? Thanks in advance for the help.

Apparently you can disconnect the fan with no ill effects. OWC PCIe expansion chassis - fan noise? Thunderbolt PCIe expansions: too noisy? Sonnet told me that this wasn't a good idea so I didn't try it.

One word of caution. I bought an i7 iMac recently to replace an aging Mac Pro (as I was starting to wonder whether the new Mac Pro would ever be released) and am very happy with it. The one problem I had was that I bought a PCIe chassis (made by Sonnet) to house two UAD-2 cards. The fan on the chassis was so loud that I couldn't use it and had to send it back. So if you have a way to check out the noise level of the chassis before you buy, it would probably be a good idea. I wound up with a UAD Satellite which works great.

The install took a while but was pretty painless. For authorization, in my case, I had to have serial numbers from the last two Logic boxes (Logic 8 and the Logic Studio upgrade). The update was really quick.

I recently replaced an aging Mac Pro with a new i7 iMac and am very happy with the new machine. Logic is running very smoothly on it. My only issue with the iMac was the lack of PCIe ports (I had two UAD-2 cards installed in my Mac Pro). I tried an external thunderbolt chassis for the UAD cards, but the chassis had a loud fan so it wasn't workable in the studio. Replaced it with a UAD-2 Satellite. You can install 9.0.0 in Mountain Lion. You just have to do a Logic update before it will open.

This seems to have worked. Thanks again for the help Eric.