Jump to content

David Nahmani

Admin
  • Posts

    98,953
  • Joined

  • Last visited

  • Days Won

    324

David Nahmani last won the day on March 27

David Nahmani had the most liked content!

About David Nahmani

Personal Information

My Logic Pro book

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

David Nahmani's Achievements

  1. Just tried it and I don't get any errors, the install went flawlessly here. Maybe the download wasn't finished when you tried to decompress the .zip file?
  2. VSL offers a free overblown contrabass flute, the Fujara Flute (this one has really cool timbres): https://www.vsl.co.at/en/Free_Instruments/Fujara_Flute
  3. On the Stereo Out channel strip? When this occurs, is it after you've left your Mac idle for a period of time?
  4. If they have the same specs (Processor, number of cores, RAM and disk), then the main difference is that the MacBook Pros have one or more fans, which can get noisy. So I would say that if the specs of a MacBook Air are enough for you then get the MacBook Air which does not have a fan, does not get hot and won't need a fan, and thus won't make any noise.
  5. I would save a copy of the project, so that you can do some tests in the copy while leaving the original untouched. Now in the copy, open the Mixer and remove all plug-ins. Is the latency now gone?
  6. Make sure all those plug-ins on the Aux are stereo? You can click hold the little double-arrow symbol that appears on the right of the blue plug-in inserts when you hover your mouse pointer over the insert to check its mono/stereo format.
  7. I think MPE controllers are sending channel pressure events, with a different (rolling over) MIDI channel for each incoming note. If that's the case with your controller then you need to figure out a way to make one assignment work independently of the incoming MIDI channel. If you can't figure out an easier way, that's something that could be done with Scripter.
  8. Well there you go. The discrepancy is because the LCD display gives you a rounded off value of the project tempo. So it displays 94 bpm but if you double-click that value you'll see the true project tempo value of 94.2821. It sounds like your project tempo should be 94 bpm so you can double-click the value and enter 94 again, which will set your tempo to 94.0000. See if that works? Could it be that you've tried to use beat mapping or smart tempo at some point during your edits?
  9. Very sorry to hear. Unfortunately it's a known issue in Logic Pro that you can get unexpected behaviors when multiple projects are open. I wasn't aware of the behavior you're describing, but one that has been widely reported multiple time here and elsewhere is the scrambling of channel strips playing wrong instruments etc. 😞
  10. The only downside of my M1 MacBook Air is the lack of of a MagSafe port. 😪
  11. I agree with the MainStage recommendation here! 🙂
  12. I'm not sure which display you're seeing, but for example the bars and beat display rounds up the values. To see the tempo list, at the top right of the main window, click the Lists button then the Tempo tab:
  13. I agree, I loved my intel MacBook Air so much that I purchased an M1 MacBook Air, and I love it. 🙂
×
×
  • Create New...