volition

While there's still no official support for Sierra (or betas), I'm using UAD 8.7.4 08-08-2016 build 56895 fine with an Apollo Quad since the last 11.12 public beta (now at 11.12.1 16B2333a (beta)). No issues that I'm aware of.

Haven't really looked into this too much, but it seems MIDI FX follow as part of the instrument? Would be great if this were optional, or if you could have MIDI FX both for an instrument and a track.

Would be great to have. I often run out of MIDI FX slots for child tracks, so it would be great if the ones shared between all of them could be placed at a higher level. Hopefully this would be introduced and work with nested summing stacks.

I'd love this and stack freezing (/viewtopic.php?f=41&t=101296) but weirdly enough I haven't seen a lot of demand for either. Maybe it's something to do with the planned obsolescence forced hardware upgrade conspiracy!

As a follow-up to this, I have been trying to find workarounds. The only one I have found is to solo a stack, bounce the whole project, add the bounced file to the project and manually bypass all plug-ins used while making a chart of which were(n't) engaged. I'm a UAD user and this is the only way I have found to free UAD DSP resources. I was hoping you could just power off the stack (powers off all nested tracks) and it would bypass everything, but this doesn't seem to be the case. If anyone has any suggestions for how to work around this quickly that still retains the information in the stack, i.e. settings, regions, etc, that would be great. The best I can think of is making alternatives where I bounce replace all tracks, then going back to past alternatives and reworking whatever I have into stems that are then imported into the newer alternative... the problem with that is that as projects change, even just structurally, it's something of a guessing game.

Would be a great, permanent solution to a long-standing issue. I would use Auganizer, but as I understand it, you don't get the taxonomic options of tagging. I.e. a plug-in being listed in multiple contexts (folders).

Just curious if any of you (maybe with better machines) can reproduce this. You can see an example at http://quick.as/31l7C37B It doesn't seem to affect playback and could be caused by the computer having integrated graphics? Have tried various buffer (processing) sizes, etc. GUI tempo mismatch.zip Empty project with tempo changes to illustrate potential GUI problem

Here's a simple demo of nesting folder tracks http://quick.as/mdj3tn7e The end of it shows that it's not very flexible (i.e. can't drag a folder onto an empty folder and expect it to nest, etc), that you can't nest summing stacks, etc. Still it's a great start and can make projects a lot tidier. Probably about as much as they can do before it makes sense to refactor Logic's audio routing.

Yeah I'm having this too. Just sent them this «Tried updating around 15 times now in the App store. Size says 828 MB. It’s stopped downloading anywhere before ~700 MB and jumps to 828 MB before a dialog appears stating ‘Logic Pro X failed to download. Use the Purchases page to try again’. Afterwards it says ‘An error occurred.’ where the update button would be. I’m pretty sure it’s not my connection since I can stream something with it still happening.» EDIT: Fixed it by restarting my machine. Update size was then 80.2 MB.

Oh, wasn't aware of that. I do have a few RW configurations as templates. Needing many or few adjustments as the case may be but it does help. Maybe it's as simple as avoiding code duplication and overcoding, since only using auxes has it's applications too and you could solve the rest, to a degree at least, with routing. I don't know if Logic implemented ReWire 1 or not, which had a 64 channel limit anyway. Then the implementation of 2 might just have been a continuation of that. That's my day's worth of speculation.

Sorry about that I fumble with terminology sometimes. I mean strips. The point you're making is that you can delete the bus strips so you're only left with the aux (and if recording audio) strips for a corresponding RW channel? That does take away a lot of the clutter in terms of strips in the mixer view, but it's an even more laborious process since you have to delete the bus strips hehe. I don't really care about that though. My real 'gripe' is that you have to go through that process at all instead of just having RW as an input option for audio tracks, and that you're still using 1/64 of the available buses for every RW channel you want to route to an audio track. With RW as an input option for audio tracks you could secure track correspondence between Logic and it's slave(s). So when committing something, you'd just record to the corresponding track(s) in Logic and that would be the end of it. No moving around clips, routing, altering track states, etc. This would be especially useful if you had batches of tracks that you'd like to commit to Logic at the same time for whatever reason. One being if there's some sort of relationship between them in the slave(s). (In my case I'm using Renoise as a slave where I have sets of tracks interacting with each other through various things like signal followers, etc. The most practical way to preserve those interactions at the moment, if I don't want to lose a lot of time to routing, altering track states, etc, is to record them as stems, but I then lose a lot of control when it comes to mixing in Logic.)

(This is too obvious not to have been suggested but I couldn't find a request for it.) Is there some reason why ReWire channels can't be selected as inputs for Audio tracks directly? Instead of having to do all the routing where ReWire channels become inputs for Aux channels which in turn become inputs for buses which in turn become inputs for Audio tracks. Since more and more people seem to be using a combination of X hosts through ReWire and other means to get more unique workflows and results, and since there doesn't seem to be anything on the horizon to replace ReWire, wouldn't it make sense to simplify this, in order to (re)gain users? Apart from the added tediousness and clutter of the above solution (though I can see why you would want the option of having ReWire as aux or bus inputs), my projects' channel count, especially if ReWiring (sometimes to multiple slaves) often exceeds 64. Having to assign a bus to each, when many of these already used for internal routing, you quickly run out. It then becomes a bit of a nightmare when you have to juggle things around, sum stuff together, record/bounce, etc to include everything. If you have existing global bus labeling, etc, it quickly becomes confusing since each project tends to be different in terms of channel use, counts, etc. That's why I never liked the absolute set and reference to buses found in Logic and other big DAWs.

LiveCut's listed on the 32 Lives compatibility chart as being 'live'. I don't have 32 Lives or I'd try it.

Having this too (with an Apollo Quad so experiencing the same dilemma as the OP). I notice it when opening a project or undoing like mentioned, but it also seems to happen arbitrarily from time to time. It's a big problem and most of my projects are now unworkable because freezing (many tracks) takes a very long time with the machine often stalling from it. I get disk too slow or audio midi mismatch errors when all tracks have freeze engaged with the CPU and HD meters spiking. Other times the same project will play fine with nothing frozen. It just seems totally random.

LPX has worked very well here since the previews. Coincidentally had problems with Flux:: SampleGrabber V3 crashing the validation so I disabled it. The update seems to have fixed it.