Infirium

Hi David, thanks for the reply! 😄 Yes, understand how the routing works and how the busses relate to the track stacks. My question was purely about the (imo) cumbersome way things are labeled. Your example above is very clear, bus "17 <- sub kick, hard kick, boom" (and I'm well aware that my personal workflow may just not lend itself well to this) that way it's very easy to determine which stack bus 17 relates to. But when I start organising my projects after the first initial "creative flow" I start putting everything in track stacks, but for example, inside my Drum stack, there might be a bunch of tracks that have clear names like "kick" sub" etc.. but there's also a bunch of tracks usually that are for later use and they might just have *insert random sample pack name sample* still and that + the fact that the track names in the side chain dropdown are not in any particular order, I might just end up having "bus 1 to 17 <- *random sample names*" that make it hard to figure out which bus I'm looking for if I want to side chain my Bass stack to my Drum stack without having to open the mixer, or go through the arrangement window to see which Bus my Bass stack is routed to. So to avoid any confusion, I wanted to know if there was a way to ensure that the clearly labeled track names would show up in the side chain dropdown first, like say, putting those tracks at the top or bottom of the track stack, but that seems to make no difference to how they show up in the dropdown. I'll add a quick screenshot as an example of how I'm seeing it most of the time and once you start adding AUX FX to into the equation it starts getting messy real quick, this is just a small project still:

Hey everyone, I don't think there's any way to change this in settings since I've looked all over, but maybe someone has a handy little workaround: So whenever you create a track stack, you can give it a name that appears in the arrangement view and the mixer and said stack will have a Bus as the input with a number, all very logical. But when you go to the Side Chain dropdown tab in any plugin and go to set a Bus as your Side Chain input you are presented with a list of Bus 1, 2 etc.. followed by a slew of track names that are routed to that bus (or inside that Track Stack, depending on how you look at it) and those track names appear to be in random order that don't align with the ascending or descending order of the Track Stacks they are in and nowhere in that list is the Track Stack name to be found. So once you've got a bigger project with a bunch of Track Stacks and nested Track Stacks inside of those and you're working in the arrangement view where you're just seeing your well organised Track Stack names and you quickly want to Side Chain something to your Drum stack, you either have to decipher whatever track names are listed and remember that those relate to the Drum stack, or you have to click the Drum stack in the arrangement view to look at what bus number it has. It would be so much nicer if inside the Side Chain dropdown in Plugins you could just see: Bus 1 *Track Stack Name* <- *All the track names inside*, or something similar.. I'm not sure if there is some way to achieve something like this? It would drastically improve workflow. Cheers 😄

Some more of the Apogee stuff just got native support with the release of their Apogee Control 2 software beta: https://apogeedigital.com/home-feature-news/apogee-products-and-macos-big-sur-apple-silicon-compatibility-information

Hey David! Great thread Btw, I think you can move Valhalla to Native support. I can't find the blog update about Apple Silicon support, but if you look at the plugin page, you'll see that all the latest builds have native Apple Silicon support. https://valhalladsp.com/plugins/

From what I remember, if the thermal sensor isn't put on correctly, it makes the system run the fans at full RPM constantly, so if your mac doesn't sound like a jet taking off all the time, it's probably not that, but it's worth a shot!

Not sure if this helps you out in any way.. But those Mid-2011 27" iMacs have faulty GPU's and there was even a "quiet" repair program for it years back. I don't remember exactly what the GPU configs of that model were and if all models were affected, but I had a Mid-2011 27", and years later the GPU in mine failed too.. Of course, Logic doesn't necessarily rely that much on GPU power, but if the GPU is failing, that could explain the weird results you're getting, since it might inhibit the rest of the system from running optimally.

I feel your pain.. I think there is a thread somewhere that explains how to not have to re-download all the content, but I'm not sure where/how exactly that worked.. I think it was something along the lines of having logic only download the "essential content" and then placing the rest of the full library you already have in the location of the newly downloaded content, but don't quote me on this.

I know this is an older thread, but I might have some additional info and insight that could save others from the same headache that I had with this.. Anyway, I've had the dreaded "some additional content is needed for this project" thing for quite a while with Ultrabeat, Drum Machine Designer (which makes sense, considering the back-en is the same, or whatever exactly the relation between the 2 is..) and recently while doing a livestream stream, one of the Logic Drummer kits gave me the same thing.. Like other people have noted, downloading said additional content never really worked, or it only loads a few of the missing samples etc.. Also, sometimes I could "fix" Ultrabeat by manually loading the kit in question using the 'Import' tab in Ultrabeat. This would fix all kits, but after a reboot of the machine it would be back to square one. At this point I had enough of this and promised myself I'd look into fixing it when I had some time. Initially I used the "Reinstall Sound Library" function, figuring it might just be an error with the current content.. 60gb over potato internet later: no luck.. I started reading some things online and then realised I probably still had my Sound Library Sym-linked to my external HDD, like ye olde days. I also deduced this from the fact that the "Relocate Sound Library" option was greyed out. Okay, cool, we're getting somewhere. Deleted all my old Logic and Garage Band symlinks, had logic download the 60gb.. again.. and what do you know! it worked! Everything loads fine in Ultrabeat and the other drummers etc.. great, now let's just use the "Relocate Sound Library" function like a good boy, following all of Logic's modern rules and finally properly have the Library on my external HDD. Spoiler alert: the problem came back.. ugh.. At this point I was about to call it a day, but went back to this trusty forum one more time, to possibly read up on some solutions that I could ponder and apply the next day. I read a different thread where someone suggested deleting the Logic prefs plists, considering that might be related and some corruption could've happened in there. Seemed Logical (hehe), this method has resolved issues in the past, So I figured I'd give it a shot the next day.. Really wasn't looking forward to having to reset all of my custom preferences again, but wanted to get this solved.. Anyway, I guess in my melty-brain state at 3am I closed the tab with the thread that had this advice and today I took it as a sign to do some more digging, before going through all the trouble of the Preferences thing. I found this thread and the and the Spotlight re-indexing thing seemed like a eureka moment to me, hadn't thought of this. So I gave it a shot and let Spotlight re-index my Mac HD.. whilst in the Spotlight preferences Privacy tab I saw that I had set it up to not Index my external HDD, like ages ago, so this gave me another thing to try if re-indexing my Mac HD didn't solve the problem. Good foresight, Mac HD re-index didn't solve it. So I decided to remove my external HDD from the "index blacklist", but set it up so it would only index the Library folder containing the Logic Content and excluded the rest of the disk, cuz I don't need all the junk in there to get indexed by Spotlight all the time.. and what do you know? IT FIXED THE PROBLEM!! Sorry for the long-winded response.. I just needed to share and work through my pain with some fellow Logic users haha. I just felt this might be useful info to add to the vast amount of great info and resources on this Forum! TLDR: When all Logic Content is fully installed and correctly moved to the desired location using the "Relocate Sound Library" function within Logic and you still get the dreaded "Some additional content is needed for this project" prompt: Don't delete your logic prefs like an absolute madman! (okay, sometimes it's a good way to solve issues, but not necessary here). Instead, have Spotlight re-index the location at which the actual Logic content is located (So not the Logic-created Symlinks on your Mac HD, from using the Relocate Sound Library function, but the actual destination of the content). And make sure that if said location was excluded from Spotlight Index to begin with.. (like my dumb self) that you actually re-add it and have Spotlight Index that location. To let Spotlight Re-Index a disk or folder: Open System Preferences -> Spotlight -> Privacy -> click "+" -> add the folder or disk containing the Logic Content Folder -> after it's added, remove it again by clicking the "-", this will prompt Spotlight to Re-Index said location. So it seems Ultrabeat, Drum Machine Designer and the Drummer's ability to properly find and access all the necessary samples is directly tied to Spotlight Index. I definitely learned something new today! Oh yeah, I'm on Logic 10.4.8 still, I doubt the new 10.5 functions any differently, but hey, who knows.. Anyway, I wanted to resolve this issue before updating to 10.5 (after finishing some urgent projects, look at me being responsible) so that my shiny new Logic update wouldn't still be plagued by this issue.

I wouldn't be worried about RAM usage, unless Memory Pressure is really high, or Swap is being used. If RAM is available, the system will use it. Otherwise, what's the point of having a lot of RAM? I have 64GB of RAM in my studio machine and even when doing nothing, the system uses way more RAM than my 8GB Macbook. Why? Because it can. macOS is also really good at managing RAM, so unless you are noticing degraded performance, the system will manage itself just fine.

Bit of a late reply. Ended up going with MIDI Player X and it does exactly what I need. Nice to have an something for when Quicktime7 (32bit) will get the axe in Catalina, haha.

The Spectrasonics website says minimum requirements are 2,4Ghz and 8gb of RAM, or higher. It runs fine on my early 2013 MBP with 2,4Ghz i7 and 8gb of RAM, so you should be fine on your machine too

This test is really fun! On my machine (see signature) with I/O Buffer Size at 128 and Small Process Buffer range I get up to 84 tracks stable, sustained. With the Process Buffer on large I can get about 93 Stable, sustained!

4578U is an i7 dual core processor (2 physical cores, 4 threads) so it's not an actual Quad Core.. When buying secondhand Macbooks you need to really research and read carefully, the secondhand Macbook market is notorious for shady sellers trying to convince you the machine is a certain thing, which it's not (ie: trying to pass off a 4578U as a Quadcore processor ) Whenever you come across a listing you're interested in, try googling the specs of that machine to see if it checks out, goodluck!

You could go to the automation view, select the channel with the synth you want the pitch bend on and search for pitch bend in the list of automation paramaters. Most soft synths have a pitch bend automation parameter and that will usually show the semitones, or at least some value that can be made sense of.

Let us know your findings