Jump to content

rafesco

Member
  • Posts

    85
  • Joined

  • Last visited

Recent Profile Visitors

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

rafesco's Achievements

Apprentice

Apprentice (3/14)

  • Conversation Starter Rare
  • First Post Rare
  • Collaborator Rare
  • Week One Done
  • One Month Later Rare

Recent Badges

7

Reputation

  1. Anyone else having issues with the Rotate tool randomly creating some sort of take folder? And if you double click the take folder, Logic brings you to a new tracks area window with just that track viewable. Weird.
  2. I dig the rotate tool. Pretty cool improvement over the regular Slip Tool IMO. But it's still pretty glitchy. The rotate tool is creating these weird looking take folders as soon as I click and drag a region with them, and when I double click the take folder, suddenly it brings me to a new tracks area window with only that current track being displayed. Also, how does Logic still doesn't have a native plug-in search function? I wonder when Apple will give some priority to such a basic feature. With every update my hopes go high and fall back right away lol.
  3. In 10.7.8 we were supposed to get a input monitoring button for software instrument tracks and it didn't show up. Now on 10.7.9, nothing either. This is weird, they announce a feature that never gets implemented lol. Did this button show up for anyone?
  4. Anyone else having issues with Remove Silence (CTRL + X) causing Logic to crash? Been happening in some projects here with fully produced songs.
  5. I do. In this example, I selected bars 34-36 with the Marquee Tool and pressed CMD + R. I was expecting bar 39 to be empty space only, but that section of the pre-existing region stays there, chopped. The same happens if I do it with CMD + C and CMD + V. What am I missing?
  6. The input monitoring button for software instrument tracks is not showing up here either. Weird. I have some questions regarding a few other release notes which I've tried and didn't seem to work the way I expected: If my count-in is of 1 bar and I hit record at bar 2.3, for example, the playhead jumps to bar 1.1. It still behaves like this. I was expecting the playhead to jump to 1.3 (which is exactly 1 bar behind 2.3). Anyone gets what this update does exactly? Not working here either. The existing region is still present in the "supposed-to-be-empty-space" area after I paste a Marquee selection containing empty space. I don't get these two either. Any examples? Thanks!
  7. Thanks so much man! This was driving me crazy. Happened to me after I updated to Monterey too. I was starting to think I'd have to manually find each file for every project I worked on my career, which is obviously impossible. Curiously enough though, I managed to open the projects if I copied them from my external drive to my Mac's internal drive, which clearly showed that something was wrong when opening from the external storage only. The Full Disk Access solution made it for me. Thanks!!
  8. I'm running through the same issue after I updated my Dropbox app. Has anyone managed to fix this?
  9. Thanks for your reply guys! If SSD speed is not a big deal in audio, guess the M2 Pro might indeed be the strongest contender for my studio then 🙂 I do look forward to hearing some feedback on running Logic projects with the new chips in the meantime!
  10. Apparently, the new M2 powered Macs also suffer from a slower SSD due to the use of a single NAND storage device, versus multiple chips on the M1 generation, including the Pro and Max lineup, even for 512GB storage options. This is causing the 512GB SSD Macs to reach Read/Write speeds of ~3.2GB/s as opposed to 4.7GB/s in the previous generations, which is quite a sad downgrade. For 512GB models, is this something that could impact music production in Logic a lot? I’m considering getting myself an M2 Pro Mac Mini - I’ve been waiting for this one since the M1 Pro Macbooks were launched - but now I’m afraid the M1 Max Mac Studio or even a M1 Pro Macbook might better bang for the buck. Not sure if the M2 Pro performance increase is worth the SSD downgrade. Thanks! 🙂
  11. Yes. If anyone else could report too so that it gets some more attention, I'd really appreciate! 🙂
  12. I just found out what's up with the autopunch/marquee glitch I mentioned yesterday. The "Play from Marquee Selection" option is affecting the Record command. It makes the playback start from the marquee selection when i hit R. This basically renders the "marquee line engages autopunch" feature useless, because it will always make the playhead jump to the marquee selection (instead of where I wanted it to start) and start recording straight ahead. Just made a video showing the issue: https://drive.google.com/file/d/1zOnLmV0Z9wVGE3cCxPtI6UlKGFTdScoY/view?usp=sharing In the meantime, the workaround for this is to deselect "Play from Marquee Selection" when using "marquee line engages autopunch". This is disrupting my workflow quite a bit though. PS: I did delete the preferences file as suggested earlier, but the issue persisted.
  13. Thanks for the suggestion regarding deleting the preferences file guys, I might try that soon. I’m a bit afraid of what that could cause though. What preferences would I be resetting to default exactly? Only those under Logic Pro > Preferences (now called Settings for some reason lol)? If I back up the prefs file somewhere else, am I able to easily get them back after deleting if I want? Edit: I just checked the "Stop" button options as polanoid suggested and, in fact, "Stop and Go to Last Locate Position" got checked in 10.7.5 for some reason. I switched to "Stop" only and the behavior went back to normal. I was in a production session today and the autopunch issue happened again though. I hope it doesn't come back again. I'll post here in case it does. Thanks for the help!
  14. I just tested it using Guest User and it behaves normally in there... welp. Now this is a bit concerning, I guess
  15. I went to 10.7.5 again to test it out, still going back to the original locate position (see attached screen recording). Weirdly enough though, autopunch behaviour suddenly went back to normal now. Only the playhead is weird. Link to video: https://drive.google.com/file/d/1vldTEyqcm0aKVVope6wXKcCKQ4uKgAC2/view?usp=sharing By the way, you may notice that the track had flex time enabled, which I turned on by accident. It also happens with flex turned off.
×
×
  • Create New...