rofus

I thought so, very annoying. I submitted a feedback/bug report to Apple, as it's a quite obvious bug/inconsistency (in what I consider anyway a quite cumbersome way to set a default channel strip...in Live is much easier but also there is not possible to do that for Auxes for some reason!).

Hi all I know how to set the default audio and instrument channel strip (save the setting, set is as default in the Library, make sure that new track dialog loads default patch). Now if I save an aux channel strip, I can still go in the Library and set is as default, BUT then it doesn't work: I send/create another bus, another aux track is created, but my default channel strip/patch for aux is not loaded. Anyone knows if that's possible at all and how?

Thanks I basically solved rebooting in Safe Mode to empty cache, then forced App Store to re-download Logic X, started it successfully without any themes, restarted again in Safe Mode to clean again cache, Logic X still working fine (without any theme). Then I re-installed my usual theme I used before in 10.9, all working now...probably something in the app got corrupted when upgrading to Yosemite, now all working again. Thanks!

Hi all, I've been using Logic X with themes since they started coming, including new ones being released/updated to latest 10.1.1 version of Logic X (under Mavericks 10.9.5). I've recently updated to Yosemite and I'm having a strange problem. Suddenly Logic X doesn't start anymore if I use a theme, with a screen saying it might be corrupted. Checking the log/report I see that the problem is somehow related to the themes, because error message is Dyld Error Message: Library not loaded: @rpath/MAResources.framework/Versions/A/MAResources Referenced from: /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X Reason: no suitable image found. Did find: /Applications/Logic Pro X.app/Contents/MacOS/../Frameworks/MAResources.framework/Versions/A/MAResources: code signature invalid for '/Applications/Logic Pro X.app/Contents/MacOS/../Frameworks/MAResources.framework/Versions/A/MAResources' So basically looks like on Yosemite latest Logic X enforce a signature check (I suppose an md5 check?) so that if MAResources.Framework is tampered/modified for themes it doesn't work. Anyone having similar problem? Is it a well known one? I already tried disabling code signing from the boot, obviously disabled all gatekeeper/firewall etc., basically same setup was working on Mavericks and it doesn't on Yosemite. I also tried redownloading it, it works normally until I try to load a theme, then it gets to the same error. Anyone?

Not yet, thanks for the link will do it just now, would be great if they can finally sort this out...they already supposedly fixed Flex in previous update recently, so sadly I'm afraid that to make it easy they made it not good for professional use (I suppose most bedroom studios don't have projects like this one). Anyway....submitting it just now!

To close on this topic, after many tests and research, I found the solution of the problem, that is a BUG in Logic X and the fact that it uses all the RAM (without really any limit, to the point of crashing the whole system: 16gb of RAM and 200gb free of SSD and only Logic X running, on Mavericks and MBPRO 15 Retina top spec). Anyway, the only solution to solve SLUGGISH UI and EXCESSIVE RAM usage, in a project with complex mixing, loads of automation, 24 tracks 24/96 and 2 hours long (!), is to do all the flex you need, then bounce in place all the flexed regions and DISABLE THE FLEX from any track, in particular ones with many regions and many FLEX adjustements. Done that...all is back to normal. I verified this also importing the project at different stages (with and without flex) into a new one: without flex all is good, as soon as there are the flex enable tracks then all becomes slow and RAM usage out of control. So Apple stil has to solve performance problems with Flex, they obviously never tested it to the limits.

Did anyone found a solution for this problem? I always worked in Logic 9, now moved to X and started all new projects there...and now that they're growing, I get this lag even with most tracks frozen (just a few bus with plugs not frozen). We talk about complex projects, more than OP, and that kind of stuff always worked on Logic 9. I am on latest MBPRO Retina 15 custom specs (all to maximum incl cpu, 16gb ram and 1TB ssd), on latest Mavericks and latest LPX. Any solution instead of ditching LPX? That would be a disaster and honestly would mean that cheap software from Apple is cheap because is now rubbish...

Hi all, I have two versions of the same song played live, without metronome. Second one is played slightly slower (< 4%) than firtst one, but obviously there are also oscillations so I cannot just stretch. I only have the stereo masters but with good drums/kick volume on the whole length of the song. Is there a way I can try to force tempo of first take on the second take? Maybe with a beat map triggering as low/regular beats as possible on the first and applying it on second take? Or make logic project follow first track variations/tempo and applying the same on second take? I have video of first one and trying to make second one matching time to fit with the video of first one. I'm quite confused looking online as well about how to do this with no loops/electronic/house stuff but good classic rock band live recording

I tried and it worked, but I'm not sure still how much it helped, seems still very heavy. I froze the previous flexed tracks, and I created now a new/duplicate for one of those, pasted there a portion to fix after Converting it to new audio file, indeed Logic finally analysed only the small new audio file, and that's all ok. But when loading the project the RAM usage by Logic is unchanged...even if frozen it seems it still loads/keeps in memory all the previous Flex even if the tracks are all frozen now...is that possible? Consider that being just a mixing session I have no RAM heavy plugins loading samples etc..., it just seems freezing does not free Logic from loading in RAM all previous Flexes? Could it be something related to other things like Undo's to be deleted in the project or similar??

Right, got it now what you mean! I thought you meant bouncing the 'flexed' track, but you meant the other way round....ok will give it a try

Thanks I'll try that. Problem is that if, let's say on the bass, I already fixed some notes in the previous hour, all those are small regions cut from the main audio track into a new one with Flex. I do convert to new audio file for the previous (already fixed) regions, and go on with editing/mixing the rest...it does not change the erratic behaviour of Logic. I cut a small region of 5 seconds, move it to the Flex track, and on that track Logic starts again analysing Flex for the WHOLE audio file, not just that single region I'm working on...and so I do not solve the RAM usage problem. I can see many already noticed this, and I can see also htat some recent LogicX updates where in theory solving problems of Logic and Flex when Undoing or other intensive operations that can block Logic for this reason. Any way to make sure Logic analysis for Flex only the region that's on the Flex-enabled track and not the whole file behind it?? Just to say I have latest Retina 15 custom machine with top CPU and 16gb ram....so usually projects with 10s of tracks and intensive plugins just go smoothly...but I read LogicX keeps in RAM (understandably) all LogicX Flex and so with very long files even a computer like this is just failing...but I honestly think it's just wrong that if I pass a small region the software wants to analyse the whole file! It should make me wait if I extend the region because it needs to analyse something more...not the opposite.

Hi, I'm mixing a live album and on a few tracks I need sometimes flex pitch to adjust minor pitch problems. Now I always mix live projects in a unique project, creating alternatives for every track (to keep an history). I created a separate 'copy' track for each of the original tracks I need to flex pitch, enabled flex pitch only on those additional tracks (4 total), and if I need to fix something I cut the original region, move that portion to the 'flexed' track, and apply the flex there. I did so in the hope that was the good strategy, but Logic anyway analyses the flex pitch of the WHOLE audio file not only the region I cut/pasted, and so for a 2h show (and original length of files), after I have three or four flex pitch tracks with such huge files (24/96) it produces sometimes memory errors because Logic behind the scenes is 'flex pitching' the whole file instead of the single regions. My question: is there a way I can tell Logic to calculate flex only to the region and not to the whole original audio file? Or in alternative, on the 'flexed' tracks can I 'freeze' the previous flexed regions to reduce the amount of memory used? To be honest in Pro Tools it works much better so it's definitely something wrong (or not optimised) with the way Logic handles Flex tracks, too bad because otherwise is brilliant and easy. I need to speedup so any suggestion to limit ram usage using Flex on hours long files (but very short regions copied on separate track) would be VERY welcome Thanks!

For everyone needing to use their UAD Solo Laptop to new Macbooks without express card, despite what Universal Audio says it's CONFIRMED WORKING. I can officially confirm that the Sonnet Echo Express Card: http://www.sonnettech.com/product/echoexpresscard34thunderbolt.html Works perfectly with UAD Solo Laptop connected through Thunderbolt, on my Macbook 15 Retina Late 2013, Mavericks 10.9.1 and UAD software 6.5.2 (it should work with anything 6.2 or more). The reply I received from Universal Audio about this was very shady and not honest, trying to sell me new products instead of telling the truth: "The now discontinued UAD2 Solo Laptop card must be installed directly in the ExpressCard/34 or ExpressCard/54 port. You cannot use any adapters ( SD, USB, FIREWIRE, THUNDERBOLT etc ). The laptop must have an ExpressCard/34 or ExpressCard/54 port. I believe at this time, your trusty Solo Laptop has met it's end with it's compatibility (your new Mac)." And when I asked why they declared false things, they replied two cold lines making it all even worse I think: "We can only suggest supported/tested configurations. The Solo Laptop was never tested with these adapters so no way to guarantee functionality." Well now you can OFFICIALLY write this considering I'm not the only one confirming this. I think probably with new powerful computers and new native contenders like Slate Digital, Softube and Nebula, they're more desperate to sell (or that's how appears to me). I'm happy to not spend anything more on UAD and keep my 'trusty' Solo Laptop for retro compatibility with my old projects, all for just £120 for the Sonnet and £25 for the Thunderbolt cable. Happy music!

Yes I'm looking for confirmation about the Sonnet Echo adapater with UAD Solo Laptop. I read from several forums that UAD added support for Thunderbolt aware cards with driver UAD 6.2...so in theory the Sonnet Echo if confirmed (but it seems already confirmed on several forums) could solve all together the pcie driver in Mavericks (it uses the Thunderbolt pcie) and the pcie slot missing on 15 inch. I wrote a DM to 'beej', looking forward for confirmations, I'll keep here updated.

Thanks, but beej is actually saying IT WORKS (if not on Mavericks I can anyway use Mountain Lion not a problem). Also on UAD forums several people say it works...confirmations?