Robert Randolph

Of course it's acceptable, but I think you can understand how some people are confused and under the impression you're implying it's not acceptable. Yes, that's the most important point to take away, but this most important point is completely missing from your conclusion summary for part 2 and hence leading to confusion. I think you've done a great thing here by doing these measurements, but you've definitely inspired some people to think the sky is falling by the way you've presented it . These things go together unfortunately. The only DAW that displays automation how it is performed is Pro Tools. Everything else does it differently than displayed AND they don't document it. So the implication that the behaviour is incorrect would be reasonable. Based on what the DAW tells you, it should work a certain way. They do not work that way. Something is wrong. But there's two ways at looking how to "fix" it. You can fix it with instant fades (I think this is bad), or you can fix it with documentation and correct display (good?).

I wanted people to become curious and look for themselves. That's all

Well, 1 sample no.. Ardour (region gain) uses a 10 sample transition. Reaper 0.1ms. Pro Tools is less than 1ms. Logic does start/end at the correct place, but that doesn't matter if you have a transient or room tone that makes it in when you don't want because of a fade. 5ms seems like a small thing, but 5ms of room tone extra on all of your edits is going to sound off to anyone paying attention. 5ms off on drums is going to mess up transients all over the place. We can also go the other direction (which I prefer!) that the 5ms fade is acceptable. I think it is. The problem now is that it's not documented and it's not displayed. You have to encounter an error, debug the error and then remember to not make the error again (when you may do hundreds of automation moves a day!). If it was documented and/or displayed, then super cool. That'd be easily defendable as a design decision. It's a design decision that even makes sense, but as a professional tool it needs to be communicated to the user correctly.

Maybe we should ask them to have sample accurate automation on by default. Before I did this video, I installed Logic on a computer with no Logic, and sample accurate automation was on by default.

I just want to be sure everyone knows that I agree with this, and I say so explicitly in the article. I'm just trying to show differences between products, for the people that care about it. Some of these things in the series so far (and upcoming articles) don't matter in the slightest for most products. Some of them do matter. Hopefully I've been encouraging enough for people to make their own decisions, do their own tests and take nothing I say as absolute fact. I'm glad you guys are trying this for yourself (even if I end up being "wrong"... that'd actually make me rather happy!)

Not that I can think of. I would really look into Track Stacks as an organizational tool. Great, thank you for the reply. I understand that I obviously would have to relearn how I work in the case that I started using LPX, so I will look in to these organizational methods. Perhaps it will benefit my work in other DAWs as well.

1. Is there like a simple list of tracks that you can use to hide them? Or do you have to physically go through the project to select and hide tracks/groups? I'm not terribly keen on scrolling/mousing around a project to click various tracks. 2. Hiding groups is useful, but can you recall different full setups of hidden/visible tracks? AFAIK, groups can't share tracks, so this doesn't seem particularly effective. For instance I frequently may have an electric bass performance that I'd want to view when looking at percussion, bass and/or lead. It seems like splitting that all in to different folders would get confusing really quick. Is there a way to show ONLY a certain group (hide everything else) easily? 3/4. I'm already aware of, and using folders. It leaves a lot to be desired as a sole method of navigating as far as I've experienced. (compared to other DAWs, of which I'd rather not compare to directly). I'll continue to work with this if this is seen as the primary method of project navigation in LPX. I am actively looking for these capabilities, but I'm coming up at a loss right now. I suspect this is largely due to a failure of the terminology that I'm using to search. If there's any resources on this topic (videos, blog posts, specific manual pages) that I should look in to, I'd be all over it. Thank you very much for the help so far!

My interest in LPX has been piqued recently. I'm curious what features are available for working in a large project. 120+ tracks we can assume. Other DAWs have things like track selectors, track visibility states, track search, and other various features for narrowing down a large project to a focal area, or easily finding items in a project. I'm currently bringing over a recent 160 track project for testing LPX, so I'll have plenty to mess with and experiment in this regard.

Ok, thank you. Marked as solved.

Is that the only way? That is quite a few clicks

I seem to be unable to find out how to do this. I would like to stop all processing in Logic, without closing it, so that I can use another heavy-cpu application without having to close Logic.

I had this same issue today with an audio region. I tried every combination of the grid settings (relative, absolute, division, beat, measure etc...). I would love to know how to deal with this.

That is excellent. Thank you for the response!

I'm very new to Logic and I'm using 10.0.7. I was looking for a way to quickly select tools using key commands and I noticed that they are not listed in the key commands editor or any key commands reference. I then found the T key to pull up the Tool Menu. However I've noticed that it seems to list shortcuts next to all the tool names? I tried these shortcuts using various modifier keys and they all seem to relate to something else. Is this a bug or am I missing something obvious? http://i.imgur.com/YfiEaKL.png