This could yield unexpected behavior.Ī checkbox choice done inside of Project Settings/General, and it could then easily be document portable. Implementing the choice as an app preference (possibly Preferences/Display/General) would have the drawback of that app level setting not actually carrying along with projects across systems. No mix and match possibility of setting from each channel though, which might limit some use cases. This would probably be a simple way to handle it, and would allow only a single structure of names to be drawn from for that tab. Checking one option would uncheck and grey out the other option both options couldn’t be checked off at the same time. But the lack of standardization drives me nuts.Īn alternate way to handle the initial case is to have two checkboxes in either app preferences, or project preferences.ĭefault would be IO label, since this is current behavior. I know that both Logic and ProTools are great programs and lots of people do great work on them. I'm a lot more interested in working on music than in learning the quirks of software, which often appear to be a moving target. But the problem being discussed is also a perfect example of the sort of confusing thing that keeps me working on my hardware console.
Logic pro 10.4 stuck updating pro#
But I've been working in both Pro Tools and Logic extensively for the past couple of years, and I don't think anyone could guess which mixes came from Logic and which from Pro Tools.įair enough. If Apple chooses to implement these changes, then it will be a better system for myself and many others.
Logic pro 10.4 stuck updating how to#
It's another case of DAWs being designed and programmed by people who are not actually experienced audio engineers.Īnd your post is an example of someone who hasn't the slightest idea of how to record or mix on a modern DAW. (Me, I can't conceive of not having a real hardware patchbay.which keeps expanding.) If the person setting up the system is a studio guy, and he has all his outboard set up through a hardware patchbay or equivalent, things could get pretty SNAFUed pretty quickly.
To wit - Logic seems to be set up with the assumption that all your hardware outboard is going to stay patched into a specific set of converter I/O all the time, which makes sense from the viewpoint of a programmer whose head is stuck inside the box and can't see beyond its walls. I'm trying to figure out what's actually the issue that you're having here.!ĪH! I might, in my occasionally blundering way, have hit on something. The Hardware I/O labels are global (as you would want as a "per studio" setup) and do not travel with the project. Steve, the labels that appear when you send to an Aux are per-project. None of this changes the label on the send tab in a channelstrip, of course. Come to think of it, maybe I should just write the hardware details in the track note slot to start out with.
Then you have a NEW area right below the usual labels, where you can write whatever secondary label you want, nice and large. You can do this in the mixer or the linear editor portions of the app. Often the hardware label moves to Track Notes, which I add by control clicking on a channel and adding that component. As a project progresses, I often swap names for something more instrument specific or descriptive of what the function is (short reverb, etc). Those templates tend to have track and aux names in a shorthand that tells me what the hardware is for that channel.
When I load a certain style drum tracking template, for example, I know that it is going to work 100% as expected when I setup the hardware in the way that goes along with it. Various tracking scenarios, mixing scenarios, and such, where I have my gear hooked up in fundamentally different ways. I have multiple templates that are setup for different hardware configs that I use.
On the note of different hardware setups.