reflekshun

Another one to watch out for, is opening older versions of your projects (you might do this to check on older settings and compare etc, there are a few reasons for it). When I open older projects with mARA in them, it completely breaks the edits, and even if you load the most recent project it will be broken there too. So you are completely screwed with no way to retrieve the edits (that i know of) that you may have taken an entire week to do. If you reset the daw and computer, it may fix the problem and restore edits, but it's not guaranteed. I've lost a lot of work this way at the last moment of almost finishing a project and it is rather heart breaking. So just be careful with opening older versions. I actually bounce out ARA stems if I am ever going to close the DAW because I don't trust Melodyne to save edits. If the edits break, I can then replace stems with the ones I have bounced out and continue working. It's not ideal because now you lost the reference to the original material, but it's better than losing all of your work!

That's a nice work around! For my purposes (Displaying only one track constantly), unfortunately there's a few issues. New track windows can't be resized super freely, they have to be fairly large, it's also a bit hard to work with this workflow in full screen mode. Lots of screen real estate lost. I also think the track window is always coupled / linked to the selected track in arrange, so it will constantly change as you move around the project.

Thanks for confirming. I must have confused it with another daw

Is there a way to say stick the 'instrumental' track to the top of arrange, even while I'm scrolling down through a project? Hope that makes sense!

Hmm thanks for confirming, it's good to know what's possible. I will send the suggestion to apple.

I almost never use the plugin window header on most plugins, is there a way of making this default to hidden when opening a plugin window? Basically its just another click for every single plugin window I open which is fine at first, but after 100 it gets a little tiring!

DAMN - you are my hero thank you so much!

I saw in a recent Spitfire Audio / LPX template video they somehow managed to use three lines in the mixer description for each track - any idea how one can do this? I attached a screenshot of part of the video

(emphasis added) Very useful way to describe your situation! And we do understand your frustration a lot better, now. As you can probably guess, there’s been a whole lot of dismissal based on other DAWs which “already do it better”. Chances are that people who already had both Live and Logic might be less interested in this update, especially if their use of Logic Pro X is as specific as yours. We get that. It’s harder to deal with the outright naysaying. On their own, Live Loops are already an impressive feature which can probably help enhance some clip-based workflows. And there’s a whole lot more to this update, especially if you put things in perspective. It makes new workflows possible which are quite distinct from what exists already. Unfortunately, a nasty bug means that it blocks your typical workflow. We really do sympathize and there’s no use in saying “we told you so”. In this sense, your original PSA was a very useful reminder to others. And it doesn’t mean that this update is useless to them. As you now made clear, this update doesn’t add to your existing workflow, which is completely fair. We’ll never force anyone to switch but there’s value in understanding what all of these new features make possible, in practice. Because of the depth of integration, that understanding comes from experimenting for a little while. The advice to only update major parts of your setup during slow times is as valid as ever. And, as we all know, this is a slow time for a lot of musicians, which explains all the extended trial versions of major software out there. So… Fair warning: Logic Pro X 10.5 might not be for everyone. While it doesn’t require Catalina, our recent experiences with Apple’s updates should remain a lesson. Still, for those of you who have the opportunity to explore new ways to work, Logic now offers more than meets the eye to new users, including “Hip Hop and Electronic composers and producers”. Thanks for understanding, the new Logic update has some amazing features for music production, notably the new sampler with faster workflows and the clip mode, this is no joke, really huge deal for production workflows and generally having fun with making music in different ways. And yeah for everyone it's gonna be a different experience and that's normal, nothin wrong with it, just mean's we're all human and unique!

Just throwing out another method for getting 10.4.8 back if you need it: Time Machine or any backup system you have, just dig into that. I found a copy of it myself that way. Good luck!

you mean, outside of the new 'banner' features, the bug fixes, enhancements, and improvements have no value? i am also in the middle of mixes, and cannot edit massive X sounds (so far, my only issue). but everything else is great, and am excited about the new, the fixes, etc. so it goes... If it works for you that is honestly awesome, but there's no need to roll eyes when you don't know other people's problems! Working well for you does not mean working well for everyone else I know you weren't directing at me or anything, but the new banner features are of no use to me as I use Logic X for mixing and vocal tuning jobs. The features are all composition and production focussed, a few smaller things relating to groups workflows don't actually work (on my system at least), and the new ARA features they added are severely bugged and make it very hard to work with Melodyne in its current state. I read through each and every bug fix to check their value in the release notes and it is a very long list of bugfixes, but none of them solve the major problems I'm having in logic, and a few new dealbreaker bugs when working with Melodyne ARA (Esp. Melodyne Studio) have been introduced only now in 10.5. Overall, Logic is less useable to complete projects on time than it was before 10.5 for me. I have reported them both to Apple and Celemony, but it ends up being a lot of unnecessary and unwanted work to keep chasing and investigating the root cause of bugs etc. when I have enough deadlines to chase. There was one bugfix that I thought might be useful to me 'Fixes an issue where Logic occasionally quits with certain plug-ins.' But I had 5 crashes last night so... maybe not haha (small project around 10 tracks using waves and UAD plugins). I have an iMac Pro with 64GB RAM, Xeon CPU etc, the system is not bottlenecked, and other DAWs on the same system don't have this many problems or crashes. Not trying to be down about it by the way, I want to love Logic because that would mean the years of effort finding great workflows (which logic has) wouldn't be wasted. But the past year or so of updates have introduced so many crash bugs and non-fixed melodyne ARA integration issues, that I got a lot of reasons to walk away and invest another year or so building solid workflows in another DAW that solves more problems than it creates with updates (I work with a few that are a lot better in that regard compared to logic over the past year). Anyways. Honestly I'm happy for anyone that has a good experience with Logic X because there is a lot to love about this awesome DAW! Is it my fault for updating without backing up the old app - absolutely. Everyone should be aware of this and take this advice from David because it's gold:

I am having some pretty serious trouble with Melodyne ARA behavior in Logic 10.5. I've submitted a report to Celemony and about to send one to apple but in the mean time I need to get work done. Is there any way to roll back to an older version of Logic Pro X? I'm guessing no but I thought I'd ask. And here is a PSA: Don't be dumb like me, only update to 10.5 if you have no serious projects running.

Is anyone else experiencing a large number of crashes (Beachballing) when using Melodyne Studio ARA (say around 15-20 layers) with Logic Pro? It often happens when I press play, especially if i press it within one second of pressing stop (most common audio engineer move in history). Last night i had around 20 crashes. I have learnt to save every 2-3 minutes manually (logic autosave doesn't save melodyne edits). But with 20 layers of Melodyne it takes around 10 seconds for the manual save to complete! I'm running a fairly strong setup, iMac pro 3.2 GHz Xeon 8-core, 64GB RAM, Mojave 10.14.6.

To add to this, if you do a lot of summing and bussing with fx processing on each bus, that generally decreases your core's ability to call on hyper threading technology, as things need to be processed in serial. Hyper threading requires some different processes (ie tracks) to have independence from each other.

So experimenting around I found the answer, it's not super intuitive: 1. Select the region to the left of the crossfade 2. Adjust the fade out value on the info pane. This is the only way I know of keeping the crossfade centered on the region cut while adjusting its width. Hope this helps someone else!