Jump to content

riffybeats

Member
  • Posts

    3
  • Joined

  • Last visited

riffybeats's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Reacting Well Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later Rare

Recent Badges

1

Reputation

  1. The trim option no longer works how it used to. I used to be able to use the trim tool to lower automation data across an entire track... Now, if there are any points set to ∞ (dragged all the way down), you cannot lower the automation data with the trim control. I know you can hold option and click and drag automation down, but this doesn't work as well as the trim function. Here's a link to the issue. Logic Pro - 10.7.8 System Version: macOS 13.4.1 (22F82) Model Name: MacBook Pro 16″ Processor Name: 8-Core Intel Core i9 Processor Speed: 2.3 GHz Number of Processors: 1 Total Number of Cores: 8 Memory: 64 GB
  2. And at last, if you want to measure it, you can ! Send anything with a constant level in the input of your choice at -18 on a Logic track and then insert on that track a VU Meter plugin. If it says 0 dB, your audio interface is "calibrated" at -18 dBFS. If not, adjust the level until it says 0 on your VU Meter to find out. So I did this (put gain plugin at beginning of strip) and increased it until I was averaging around 0 VU on the Waves VU meter (I have the "headroom set to 18 on VU meter). So 0 in Logic's fader meter = -18 VU. I thought that each logic track (to start a mix) should be around -18 / -15 dB in the fader meter, and have been leaving about -6dB headroom in my logic meters... that makes the VU meter come in around -5 VU... I'm more confused than I was when I started lol.
×
×
  • Create New...