Jump to content

TheBigV

Member
  • Posts

    6
  • Joined

  • Last visited

TheBigV's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Thanks for the suggestion. When I use the key command suggested, it just adds a secondary ruler with the musical grid measurements. However, I did notice something weird, that may be the cause of this. The time ruler starts all the way past the end of the project. Perhaps I offset the time somehow? Not sure how I did this. I also noticed when I'm working in the song, the time constantly remains at zero. When I move the playhead into this end area, the time starts.
  2. Hi David - Thanks for the suggestion. They're still missing when I zoom out. Weird thing is, I tried creating a brand new LPX project from scratch, created one track in it, and tested the same process. The ruler shows the time instead of musical grid. I'm wondering if it's some weird bug...I'd hate to have to rebuild this project in a new file. I used the apply region tempo to project tempo in the original project. I wonder if that had any effect on whether the time would how up.
  3. Have a LPX issue that's been driving me nuts, but I can't seem to figure out how to resolve it. I want to change my primary ruler timeline from the musical grid to time. I go into the Project Preferences and uncheck "Use musical grid" under the General tab. It removes the musical grid, but I see no time. Just a blank ruler. Any thoughts? See area outlined in red from screenshot. Thanks.
  4. I think I was using the latest version of Logic Option, because i know the program repeatedly alerts me to update until I do so. I hadn't seen the notice in a long time. I hear you...I'm bummed as well, cause I have a Logitech MX Master 2S and it would be nice to have that program to customize. Nice recommendation on "Steermouse"-- I'll have to check it out. Thanks!
  5. Dave - Thanks! Appreciate the responses. Mark R - Thanks for your responses, as well! I do have a Logitech Mouse and I uninstalled Logitech Options. Bingo! You were right. All of the key commands I mentioned work now. This is great!! Thanks again.
  6. Hi everyone, This is my first post here, but I have been reading the great advice and comments from this board over the past few years to help in my journey in learning Logic. I just took the Logic Pro X 10.4 certification exam and passed with a 96%! I'm really excited about it, and have to say thanks to David Nahmani for writing an excellent book to assist with the studying. It was well put together and structured. As an active Logic Pro X user for over 5 years, there were lots of tips and tricks I discovered while studying, as well new ways to understand concepts I thought I had understood. I'm not sure if the following topics have been addressed in previous posts,but as I was going through the book, I found some key commands/functions just did not work as written in the book. Could it be that they are bugs in Logic? I am currently running version 10.4.8: 1) Key commands that include all modifiers (^ Ctrl + ⌥ Opt + ⌘ Cmd) don't work: I swear these key commands worked in earlier versions of Logic, but every time i try to execute a key command that uses all 3 modifier keys, like Solo all on/off (^ Ctrl + ⌥ Opt + ⌘ Cmd + S), hide toolbar (^ Ctrl + ⌥ Opt + ⌘ Cmd + T), etc. nothing happens. It's been pretty frustrating, because these are some really convenient key commands. I know you can go define your own key commands, but I prefer to stick to the default key commands at this point. Also, in case I ever want to define my own key commands using all 3 modifiers, it looks like I'm out of luck :/ 2) In the mixer, double-clicking the Bus Send does not highlight the corresponding Aux channel: Again, very useful trick to help navigate large projects. I swore this work in a previous version of Logic as well. 3) Opt-click a marker to position the playhead at the beginning of that marker does not seem to work: Nothing happens other than selecting the marker 4) Latch mode in Automation reverts back to default position when playback is stopped; automation does not stay at the value you last were at prior to stopping: This just basically makes the automation mode kind of act like Touch? Has anyone else encountered these issues? Or know if they are bugs? Thanks for any comments!
×
×
  • Create New...