Sevenfold

A few notes if you're having trouble tweaking because it's too complex or using Xcode just for the Property List Editor is overkill. First, for tweaking basic values you can use the free app Text Wrangler. When you open the plist file, it will look like XML, but the code can be folded/collapsed. Hold the option key while clicking the arrow next to the "" on line 4 and everything inside will collapse too. Now reopen by clicking the arrow next to the "" line (without the option key this time!). You should see only a few lines now. Open the line under "AssetSets" by clicking the arrow, then open the line under "Colors". You can then open "PianoRoll", "Arrange" and "Ruler" from there. TweakLogicColors.scpt.zip Text Wrangler has some pretty extensive search capabilities. I've attached an Applescript file that will find tweak 3 brightness settings for the Piano Roll, Ruler and Arrange backgrounds. It will prompt you with the default value and you can change it to a brighter value. The script just uses search and replace within Text Wrangler, so it needs to be installed (it's free).

It sounds like PT handles bus labels better, and that would help a lot. I think what would help even further is for outputs, inputs and sends to get "smarter" in the way they present their labels. For example, since Apple is simplifying for novices, I wonder what novices think when they create a summing Track Stack from basic tracks with friendly "Stereo Out" outputs, and then scratch their heads at the "bus 5" (or whatever bus Logic chose) now shown on the outputs for those tracks. I know Logic is just automating functionality it already has, but I still get confused by the bus assignment. Since "bus 5" in this case is just the route to the Track Stack, the name of the Track Stack is what should show as the outputs. What I dread the most, though, are complex projects that I haven't worked on for a while, and that have dozens of strips with multiple sends. It used to be that if I had changed my bus labels since I worked on the project I was doomed, since its a global setting. But sharing with other Logic users has lead me to stop labeling my busses all together, so now my projects have the generic "bus" everywhere on outputs, inputs and sends. I've made "cheat sheets" that map out what bus assignments are used for, but it would work so much better to see descriptive names as labels.

Well, I'm not an expert but also not a novice (after all, I own and have read David's awesome Logic Pro 9 book ), but I have somehow survived making complex mixes with that exact mentality of track = channel strip, lol. In LP9 I left track names in "auto" mode and it pretty much kept names in sync with channel strips and was happily oblivious to them being different entities. I was trained years ago on studio mixers and patch bays, but I don't feel any urgency to apply that workflow when I work in Logic. I do agree, though, that advanced users like you should have an option to keep the names separate. I agree, the way it chooses an arbitrary name like that is bad. They should just remove "channel strip name" as an option from the "additional name column" and keep the track name consistent. What would make the most sense to me would be a per-track option like "keep track name and channel strip name the same" that defaults to ON. At least I would understand what's going in with the names then.

Thanks for the tip, David! That got me half way there, but unfortunately its even more convoluted than that on several of my projects. When I choose "channel strip name" for track names in LP9 and resave, the project opened in LPX shows some of the tracks with the expected channel strip names, but others are not in sync. For example, I have 2 similar audio tracks with the same output bus, but one doesn't sync the track/channel strip name, and yet the other one does. As a work-around I can duplicate the non-syncing track, move the regions to it and delete the old track... now I can rename the channel strip or track and the names stay in sync. Very flaky, and I haven't found what the difference between tracks that sync vs not-sync.

If it hasn't already been discovered, fonts can be tweaked in the same file. I tested with track header "TrackHeader_Name_RG" and it worked, and there appear to be dozens more settings, many under "AttributedStringStyles". You can also narrow down the list with a search for "NSFont:{" and if provided change the size value (11 in this example): NSFont:{Helvetica Neue UI Medium, 11}

(replying from another topic that I don't want to hijack) No it was not. Thank you for pointing it out! I'll take care of it now. EDIT: Ok I've now fixed it, please let me know if you see anything else wrong!! Thank you. I've added a picture as an attachment to a post, but when not logged in the following message is displayed: "You do not have the required permissions to view the files attached to this post." The post is in the "Logic Pro X New Feature Suggestions" forum, and I'm not sure if I'm doing something wrong or if it also has something to do with forum permissions: http://www.logicprohelp.com/forum/viewtopic.php?f=41&t=97496&p=508699#p508699

I'm not sure if it was intentional, but it looks like both of the new "Logic Pro X New Feature Suggestions" and "Logic Pro X Bugs & Workarounds" forums are locked to viewers and require login to read any posts.

LPX still displays the word "bus" all over the place – in sends, outputs routed to Aux channels, and now whenever I add a summing Track Stack. Please bury it! In most instances it doesn't mean anything to me. In the output and send menus, Logic is smart enough to detect and display the Aux/Stack name in parentheses next to the bus number, and this name is what I need to see most of the time. I need to know I've routed the output through "Gtr Sub", but instead I get to see "bus 3". Or when I'm adjusting a Send to "Reverb", I get to see "bus 10" – what is that? Showing the bus number is antiquated and unneeded most of the time, and if I don't remember what "bus 10" is, I have to go searching for what it is connected to. Yuck! I understand that a bus can have a more advance routing. In the case where a bus has more than one endpoint the send/output could display the bus number/label like it does now. But even bus labels can be a problem in LPX. With the new summing Track Stacks, Logic picks the bus it routes through, and if I've given that bus my own label it likely won't make sense – like if I create a Stack for guitars but Logic picks a bus I've labeled "Vocals". I can reroute the stack after creating it, using my choice of bus that has the correct label, but that seems like a complicated work-around made through sludge. In general I feel that bus labels are useless anyway since I can't save them per project, which makes it very frustrating sharing projects with other Logic users who haven't labeled their busses the same as mine. Bus labels, when needed, should be a per project setting that can be stored in a template and available for import from other projects. In a nutshell, my two suggestions, in order of importance, are: 1) Display the Aux/Stack name on sends and outputs when the routing bus has a single endpoint. 2) Save bus labels per project, but only show the label if the bus has more than one endpoint, or is not connected to an endpoint. Otherwise use suggestion #1.

Had to bring up adequate penetration? It's not the depth of your penetration, but how much your offering is enjoyed. A properly stimulated market will naturally grow in size (but it needs more than 4 months).

+1. I've thought the same thing and find the number of views useful. If it's not too difficult to add into the View Forum lists, then I think it would be worthwhile. Also, I find it easier to browse through the search/new posts lists than the View Forum lists. The column shading helps, and I prefer the way the Topics and Last Post columns are consolidated by stacking the info. Hey, that would even leave a little room for a Views column

I have a Mac Mini setup with Logic 8/9 and between the demos and my own projects I haven't had any performance issues. That may not be the case with some larger projects, but I tend to be very liberal with assigning CPU hog plugins and the Mini runs sweetly. Some thoughts... the new Minis can now run dual monitors which really helps. The specs are pretty close to the white Macbook. Mine has the maximum 4 GBs of RAM, which seems just enough for me. Your buddy will probably need an external HD since the internal is only 5400 RPM, and using a separate drive for the project files is recommended anyway. If you want to upgrade the Mini's hardware, be forewarned: You need to get adventurous with a putty knife, which is required to open the unit. I successfully upgraded my internal HD (to a 7200 since Apple doesn't currently offer that option) and memory ($$$ cheaper than Apple's), but it was a test of nerves with tiny and tight spaces and several parts that needed to be disconnected/reconnected.

Or enter this address in your browser (or save as a bookmark): file:///Applications/Logic%20Pro.app/Contents/Resources/English.lproj/logicpro_help/index.html Edit: Oh, and thanks Eric for the great tip!

Sevenfold,are you singular? Six of us are, but the other guy's married (hence the "fold").

For a company, the Economist says it's singular. So the original "Has Apple.." thread was correctly named, if not a flaming pile of...never mind. For the gun example, like a conflicted fashion designer it can go both ways. You (singular or plural) have a gun, but he (always singular) has a gun. The saying "have gun will travel" could represent the implied phrase "if you have a gun you will travel safely". But bear in mind (not "bare in mind", at least in this instance) if you have a gun, you will *not* be allowed into an Apple development building.

Insanity: doing the same thing over and over again and expecting different results. Albert Einstein I've seen SO MANY bitching comments about Apple's secrecy and silence, in numerous forums over the last few years. The best you can hope for is to vent some of your anger. I don't like Apple's attitude, but I blame Microsoft and their willingness years ago (and since) to blatantly knock off so many of Apple's ideas. Now Apple guards everything, and from that end I don't blame Apple for keep everything close to the chest. But realize all DAW companies have an NDA. And as far as communication, I was a Cubase user for years and much of the info regarding future updates was flat out wrong. Just look up how they handled the whole solo issue to understand how worthless communication can be. The only company I've seen communicate well is Cockos (Reaper) and even they refuse to answer some critical questions, like if/when they plan to implement key features. Repeatedly bitching about the same thing and somehow expecting anything to change seems a bit loony to me, though. Thousand before us have been ranting about it over the years and have made little difference, and Logic has such a small percentage of Apple's total revenue. So study Apple's track record over the last few years and definitely assume more of the same. You should also assume that the latest version of Logic will be it's last, since it wouldn't be far fetched for Apple to roll it into another product or just discontinue Logic at any time. If you feel the need to warn others, request a sticky post to inform new users about the lack of Apple's attention. If you enjoy "cutting off your nose to spite your face", then file that class action lawsuit mentioned earlier. I can guarantee it will burn your energy much more than it will solve anything, or hurt Apple. Then be done with it. Now you're free to decide if you should stay or go, since you are no longer adopting the insane stance that Apple will miraculously change. If you choose to stay, you've accepted Apple's lack of communication and have committed to making the best of Logic's current version, or whichever version you choose to use. Rest assured that great music has been made on much cruder systems. Try to resist penis envy when you hear about other DAWs, and instead focus on what you really need. Continue to post bugs, issues, tips, and requests. You never know when/if it may get heard. But don't waste your energy and work yourself into a funk, or expect anything different from Apple. It's just not worth your mental health.