Jump to content

crimsonnoise

Member
  • Posts

    136
  • Joined

  • Last visited

crimsonnoise's Achievements

Newbie

Newbie (1/14)

1

Reputation

1

Community Answers

  1. Moving from Logic 10.6.3 to 10.7.1 and 10.7.2 introduced a new bug for me. Can anyone confirm? Importing SMPTE locked markers don’t import to the original absolute SMPTE time position when “at the original absolute SMPTE time position” is selected. They always get positioned at the same time position relative from project start regardless if “at the original absolute SMPTE time position” or “at the same time position relative from project start“ is selected. A really useful feature is suddenly broken now. It had worked fine for probably a decade. Logic 10.7.2 Big Sur 10.6.1 Mac Pro 2019 16 core 256GB RME UFX II
  2. Thanks both. Yes indeed tit seems to have to do with the scaling of the 4k display. Updating to Logic 10.7.1 solved it all though. Just a bit nervous installing these latest versions!
  3. I am getting serious graphics glitches after updating to Big Sur. Regions seems to be in the wrong place vertically, and it's almost impossible to select them. Things were fine before the Big Sur update. Any ideas? LG Ultra HD Display 3840 x 2160 LPX 10.6.3 macOS Big Sur 10.6.1 Mac Pro (2019) 3.2 GHz 16-Core Intel Xeon W 256 GB 2933 MHz DDR4 MD Radeon Pro W5700X 16 GB
  4. Thanks David. True, it depends on the material. Sometimes Flex causes low end bumpiness that Time and Pitch doesn't. Waves' ancient Sounshifter has its own sound that can be quite nice at times too.
  5. What's better quality for transposition for up to 4 semitones: Quality of Flex Time or Time and Pitch Machine?
  6. Amazing, Joshj, I never realised that. So incredibly useful to know.
  7. Yes I have checked the event list with all selection buttons enabled. Completely empty.
  8. Thanks for the reply. Sorry, I may not have explained this properly. I put Logic into record, and after a few bars stop again. I play no note. There is now an empty region. This is not normal. Or: I start recording on bar 3, but only play midi notes on bar 9. The newly recorded region starts on bar 3. But normally it would have automatically been trimmed to start on bar 9.
  9. Whenever I record on a software instrument track, and play no notes, Logic creates a 1 bar empty region during the count-in. There is no sysex in there either, no midi at all in the region. When using "drop" then an empty region is created from the point where the track is dropped into record. Problem has only recently started, after trashing preferences. On Logic 10.4.8, in Mojave, Mac Pro Trashcan 8 core.
  10. Channel EQ adds 15 samples of latency with oversampling enabled. You can turn oversampling off by clicking the triangle bottom left to open the extra options and unticking the box. Save as your new default so future instances have it turned off too. Oversampling is may not necessarily improve the sound. (I have it turned on though).
  11. Yes that could be the case. In any case, the template itself is fine, it's just when session get big when the problem appears. I reported the bug to Apple, whom have kindly gotten back. They have now the sessions. Let's hope for a fix.
  12. In fact the template works fine too. So the problem appears when the sessions get bigger and have a lot of midi and audio regions. Those sessions don't have the record repeat & unwanted undo problem in Logic 10.4.4 but have that problem in 10.4.6.
  13. Yes they were created from the same template. It takes months building those big and complex templates for film scoring. The issue is that the template and its related files worked fine until version 10.4.6. (or 10.4.5 which I never tried).
  14. New strange behaviour in Logic 10.4.6. Record Repeat now also triggers one Undo step. For example if I transpose a sequence, then start recording on a completely different track, then use the 'record/record repeat' command, then recording starts again, as expected, but ALSO REMOVES the transposition I did earlier. I can't reproduce the behaviour on a completely new empty session, but all my existing sessions are affected - it's hundreds I have to work with at the moment. Anyone came across this or have suggestions?
  15. I have just come across this problem now. It started with Logic 10.4.6. Whenever Record Repeat is triggered, Logic add an undo step. Basically it will start the recording again, but always goes back one step in the undo history. I can't reproduce the problem with a new empty session, but all the existing sessions exhibit this problem. Did you find a solution?
×
×
  • Create New...